# AWS Funding Activate, submit, and track AWS funding requests directly in Fours. --- ## Overview Fours connects directly to the AWS Partner Central Funding Benefits API, so you can submit, track, and manage funding requests without leaving your workflow. Once funding is activated, you can create requests from either the Fours Console or your CRM, follow them as they move through AWS review, respond to rejections, file cash claims, and reconcile against your funding wallets. The **Funding** page in the Fours Console has two tabs: | Tab | What it holds | | --- | --- | | **Funding Request** | Every request you have created, with its status and stage. This is where you draft, submit, and work a request. | | **Wallet** | Your available budgets, remaining balances, and historical spend across AWS programs. | Before funding can be activated, two prerequisites must be in place. Once those are confirmed, a Fours admin enables funding on your ACE integration and (for Salesforce users) assigns the funding permission set. ## Prerequisites Make sure the following are in place before creating a funding request: ### 1. AWS ACE connected to Fours - Your AWS ACE integration must already be set up and active in the Fours Console (go to **Settings > Integrations** to verify). - This connects Fours to your AWS Partner Central account via the Partner Central API. - If you have not yet set up this integration, complete it first before proceeding. See [AWS Partner Network API Integration](/integrations/aws-partner-network-api). ### 2. ACE portal migrated to Partner Central 3.0 (PC 3.0) - Your ACE portal must be fully migrated to Partner Central 3.0. - This migration is a mandatory AWS requirement before funding benefits can be enabled. - The Funding Benefits API is only available on the PC 3.0 platform. - Contact your AWS Partner Manager if you are unsure of your migration status. :::warning The Funding Benefits API only works with AWS Partner Central 3.0. If your account has not been migrated, funding requests will return errors. Enable **Enable Funding Application** only after your Partner Central 3.0 migration is confirmed. ::: ## Activate funding Before your team can submit requests, a Fours admin needs to enable the funding feature and (for Salesforce users) set up CRM permissions. ### Enable funding in the Fours Console Once both prerequisites are satisfied: 1. Log in to the [Fours Console](https://console.suger.io). 2. Go to **Settings** and click the **Integrations** tab. 3. Find your AWS ACE integration and click **Edit** to open the configuration panel for **AWS - ACE (Partner Central API)**. 4. Turn on the **Enable Funding Application** toggle (“Enable funding application for AWS”), then click **Save**. > Edit Integration modal for AWS ACE showing the Enable Funding Application toggle This step uses the Partner Central Funding Benefits API and only works after AWS has confirmed your Partner Central 3.0 migration. If migration is not complete, enabling funding will fail with an error. ### Set up Salesforce permissions (Salesforce users only) Without this permission set, team members will not be able to see the funding interface inside Salesforce. 1. Go to **User settings** in Salesforce. 2. Assign the **Suger Funding** permission set to each team member who will draft or submit funding requests. ## Choose a funding program Fours offers **seven** funding programs when you create a request: | Program | What it funds | | --- | --- | | **Market Development Funds** | Marketing activity that builds pipeline around your AWS solution. | | **Proof of Concept** | A customer proof of concept or pilot on AWS. | | **Migration Acceleration Program** | A customer migration to AWS, applied for per migration phase. | | **ISV Workload Migration** | Migrating an existing ISV workload onto AWS. | | **MPOPP Grow** | Marketplace Partner Opportunity Program (Grow) credits. | | **PIF: SCA GenAI Proof Of Concept Funding** | A generative-AI proof of concept under the Strategic Collaboration Agreement. | | **PIF: SCA GenAI Marketing Development Funds** | Generative-AI marketing activity under the Strategic Collaboration Agreement. | ![The Create Fund Request menu — the funding programs you can start from the console](images/51-funding-programs-menu.png) :::note The two **SCA GenAI** programs were withdrawn for a period and have since been restored. They are available again in the **Create Fund Request** menu, the opportunity actions menu in the [Salesforce app](/salesforce-app/salesforce-app-cosell/), the Suger card on a HubSpot deal, and the program dropdown on the funding field-mapping configuration page. Both support **Cash** and **Credit**. ::: ## Submit a funding request Once funding is activated, you can create a request from either the Fours Console or your CRM. :::info Before creating your request, make sure you know which fields AWS requires for your chosen program. Incomplete submissions will be rejected and require correction before resubmission. ::: 1. Open the **Funding Request** tab in the Fours Console, or go to the relevant opportunity in Salesforce and open the Fours component. 2. Click **Create Fund Request** and select one of the seven funding programs above. 3. Fill in all required project details. Use the built-in validation tool to check for missing or incorrect fields before submitting. This catches errors before they reach AWS, which helps avoid delays. - If your POC request is over $10,000, AWS requires an AWS Pricing Calculator link plus a project plan. The MRR you enter in ACE must exactly match the calculator's output — even a small mismatch gets the request rejected. Double-check this before submitting; it's the single most common reason POC requests get sent back. 4. Click **Submit**. Fours sends the request directly to the AWS Partner Central API. ### Migration Acceleration Program requests The Migration Acceleration Program (MAP) has its own requirements on top of the standard project details: | Requirement | What to supply | | --- | --- | | **Migration phase** | Choose **Assess** or **Mobilize**. | | **ARR** | The annual recurring revenue for the migration, which must be at least **100,000**. | | **VMware attestation** | Required on **Mobilize** only. It is not asked for on an Assess request. | | **AWS opportunity** | A MAP request associates an **AWS opportunity** — it is not drawn against a wallet. | #### The MAP request form in Salesforce Salesforce users raise a MAP request from the Fours funding table on the opportunity: open the **New Funding Request** menu and choose **New Migration Acceleration Program Request**. That opens a dedicated MAP form rather than the generic funding form. **MAP is cash-only.** There is no cash-or-credit choice to make — every MAP request is submitted as a cash request, which is why the form always includes a Cash Request Detail section. The form is organized into five sections: | Section | What it collects | | --- | --- | | **Migration Details** | The **Migration Phase** (Assess or Mobilize), **Annual Recurring Revenue (ARR)** — which must be at least 100,000 — and, on Mobilize only, the attestation that over 75% of the servers being migrated are VMware-hosted VMs. | | **Opportunity Information** | The **AWS Opportunity** the request is associated with. Just the one field. | | **Project Information** | The requester's first name, last name, email address and job title; project name, business description, AWS Account ID, **Project Start Date (UTC)**, **Project End Date (UTC)**, the country and states the activity is executed in, and an optional AWS Pricing Calculator link. | | **Cash Request Detail** | Currency, total cost of the project, total amount requested from AWS, and the **Payee Central Account Profile ID**. | | **Supporting Documents** | Any documents you need to attach to the request, each with its type — see [Attach supporting documents](#attach-supporting-documents). | Two date rules shape the request, and they are worth planning around: - **Project Start Date** — the form will not accept a date less than **14 days** from today. AWS's own guidance, shown on the field, is that work must start at least **14 business days** after you submit, which is the longer of the two — so leave more room than the picker strictly demands. - **Project End Date** — cash claims are due **30 days** after this date. The form does not enforce that deadline; it only requires the end date to fall on or after the start date. :::warning **Payee Central Account Profile ID is required.** It must be **10 to 13 alphanumeric characters** and comes from your Payee Central profile. The form rejects anything outside that pattern, and because MAP is a cash program the request cannot be submitted without it. ::: ### Fields you may be looking for A few fields have changed, and knowing which are gone saves time hunting for them: | Field | Status | | --- | --- | | Invoice fields | **Removed.** Invoicing is handled in Payee Central, not in the request. | | **Payee Central account profile ID** | **Required for cash programs.** A 10–13 character identifier from your Payee Central profile. | | Public Sector Agreement checkbox | **Removed.** | | WWPS consent | Still present — continue to answer it on public-sector requests. | ### Attach supporting documents Each program's request form has a **Supporting Documents** section. In the Fours Console, click **Add Attachment** once per file, pick the file's type, and upload it. The type is the business use case AWS files the document under; the console labels the picker **Attachment Type** on Market Development Funds, PIF: SCA GenAI Marketing Development Funds, and ISV Workload Migration requests, and **Business Use Case** on the other programs. Every program except ISV Workload Migration offers the same 19 types: Project Plan/Checklist, Innovation Plan, Marketing Plan, Proof of Cost, Assess Analysis Report, Well Architected Review Report, Success Criteria Report, Customer Sign Off Template, Partner Sign Off Template, Customer Satisfaction Survey (CSAT), Migration Capability Review, Migration Completion report, AWS Pricing Calculator, Migration Assessment Scope Checklist, Statement of Work, Migration Assessment Report, Managed Services Agreement, Partner Scope Checklist, and Other. ISV Workload Migration offers seven of them: Project Plan/Checklist, Migration Assessment Report, AWS Pricing Calculator, Statement of Work, Customer Sign Off Template, Partner Sign Off Template, and Other. The lists are the same in the Fours Console, the Salesforce app, and on a HubSpot deal. :::note **Business Case** and **Quote** are not attachment types AWS accepts. Market Development Funds requests used to offer them, and a request that still carries an attachment typed either way is rejected when it is submitted to AWS. Change that attachment's type — to **Marketing Plan** or **Other**, for example — and submit again. ::: ### Create AWS funding from a HubSpot deal You do not have to start in the Console or in Salesforce. HubSpot users can raise a request straight from the deal they are working. 1. Open the deal in HubSpot and find the Suger card on the deal record. 2. Click **New Funding**. 3. Complete and submit the request as usual. :::note The HubSpot deal card offers all seven programs, with the same funding types as the console. See [Create Funding](/hubspot-app/hubspot-app-funding/) in the HubSpot app docs for the card itself. ::: To control how HubSpot deal fields populate a funding request, open the funding mapping configuration page in the Fours Console and set the **CRM Source** dropdown to **HubSpot** (the other option is **Salesforce**). Each CRM source keeps its own mapping, so configuring HubSpot does not disturb an existing Salesforce mapping. ![The funding field-mapping page for MDF / CASH — the CRM Source dropdown open at the top showing Salesforce (selected) and HubSpot, above the per-field mapping rows with their AWS field name, the CRM field they draw from, and the transform controls on each row](images/60-funding-crm-source.png) In **Settings > Funding**, under **Funding Configs**, each saved mapping is its own card, named for its CRM, program, and funding type — for example, `AWS - HubSpot / Market Development Funds / CASH`. A Salesforce mapping and a HubSpot mapping for the same program sit side by side as two cards. **New Config** asks for the **CRM Partner** (Salesforce or HubSpot), **Program Type**, and **Funding Type** before it opens the mapping page, and deleting a card removes only that card's mapping. ### Test a funding field mapping Before your team relies on a mapping, check what it produces for a real record. On the funding field-mapping page, click **Test** to open the **Test Funding Field Mapping** dialog: 1. Pick the source record. For **Salesforce**, select or search for an opportunity; the test runs as soon as you pick one. For **HubSpot**, enter the deal ID and click **Run**. 2. Read the **Result JSON**. `preview` holds the funding request the mapping built from that record, and `validate` lists the fields that would fail validation. The same mapping pre-fills a new funding request started from a CRM record, so the test shows what your team will see when they start one. How mapped values are read: - **List fields get a list.** AWS fields that take several values, such as the states where the activity is executed, receive a list even when the mapping yields a single value: `CA` becomes `["CA"]`, and semicolon-separated multi-select picklist values are split into separate items. - **Blank stays blank.** An empty CRM field adds nothing to an expression's output, so an expression that reads only that field produces an empty value. - **Salesforce: fields on related records resolve.** A mapping can read beyond the opportunity itself, for example `Account.BillingState`, in direct mappings, expressions, and AI prompts. - **Salesforce: a field that can't be queried doesn't stop the preview.** The preview continues from the base record only (the opportunity and its account) and adds a warning on `_source` that starts with `failed to query configured source fields, using base record only:`, followed by the query error. ## Track the funding lifecycle After submission, Fours keeps your request synchronized with AWS. To stay on top of where a request stands, track two separate data points: - **Status** — the overall state of the request (for example, `PENDING_SUBMISSION`, `IN_REVIEW`, `APPROVED`, or `REJECTED`). - **Stage** — how far the request has moved through AWS's fund request process, from creation through the approvals to completion. See [Read the stage](#read-the-stage). :::info **Stage is driven by AWS and is read-only.** Fours renders it as a stepper showing where the request has reached in the AWS review — it is not a list you configure, and there is nothing to add, rename, or reorder. The stage advances when AWS advances it. ::: Funding data is refreshed on a schedule, roughly **every three hours** — not in real time. A status or stage change made on the AWS side appears in Fours on the next sync rather than the moment it happens. To filter and prioritize your requests, use the **Advanced Filters** in the Fours Console or your CRM. You can filter by program type, fulfillment type (Credits or Cash), or stage. ### Read the stage The stepper at the top of a request's page in the Fours Console has six steps — the same six AWS Partner Central shows for a fund request's progress. Every step up to and including the request's current one is checked, and the current step's name is highlighted. ```d2 direction: right creation: "Application\ncreation" business: "Business\napproval" finance: "Finance\napproval" pre: "Pre-approval" claim: "Cash claim" complete: "Application\ncompletion" creation -> business -> finance -> pre -> claim -> complete ``` AWS reports the stage in its own terms, and Fours places the request on the matching step: | Step | Stage AWS reports | | --- | --- | | **Application creation** | No stage yet — for example, a request that has not been submitted — or a value Fours does not recognise | | **Business approval** | `BUSINESS_APPROVAL` | | **Finance approval** | `FINANCE_APPROVAL` | | **Pre-approval** | `PRE_APPROVAL` | | **Cash claim** | `Invoice` or `Disbursement` — the claim's two steps | | **Application completion** | `FULFILLMENT` | The Salesforce app's funding page shows the same stepper once AWS has reported a stage. Where the stage appears as a label instead — the **Stage** column of the **Funding Request** tab, the Salesforce app's funding table and opportunity card, and the funding details on a HubSpot deal — it uses the same names, and a value Fours does not recognise is shown exactly as AWS sent it. Until AWS reports a stage, the console's **Stage** column is empty, the Salesforce app shows a dash, and the HubSpot deal card leaves the field out. The stage filter — **Stage** in the console, **Fund Request Stage** in the Salesforce app — offers **Business approval**, **Finance approval**, **Pre-approval**, **Cash claim (invoice)**, **Cash claim (disbursement)**, and **Application completion**. A request with no stage yet matches none of them. ## Respond to action required and rejections If a request is paused or rejected, Fours gives you what you need to fix and resubmit without starting over. ### If a request is flagged as `ACTION_REQUIRED` 1. Open the request and check the **Status Reason Codes**. These indicate exactly what is missing, such as a project plan or design win document. 2. Update the request in Fours based on the reason codes. 3. Resubmit to restart the review process. ### If a request is rejected 1. Review the rejection reason. You can find it in the automatic rejection email, in the **Approval History** in the action bar, or under the **Actuals** section of the request. 2. Select **Resume fund request** from the action bar to reopen and update the request. 3. Submit once your changes are complete. ## Submit and track cash claims Once a project is complete and your request has been approved, you can file a claim to receive your reimbursement. :::note **There is no separate "MAP Cash Claim" program.** The cash claim was a legacy benefit of MAP, and it has been replaced by the [**Migration Acceleration Program**](#migration-acceleration-program-requests) entry in the program list. Apply for MAP as a program in its own right — choosing a Migration phase, supplying ARR, and associating an AWS opportunity — rather than looking for a cash-claim program to apply to. ::: **A cash claim is not a second row in the Funding Request tab.** Allocations fulfilled by a disbursement are filtered out of that tab, so its counts and its list hold funding *requests* only. Track the claim from the request it belongs to, not by looking for a separate entry. Cash claims themselves still work the same way on any approved cash-based request: 1. Navigate to the **Cash claim** stage for the approved request. 2. Submit your actual project expenses (actuals). 3. The status updates to **Awaiting Approval** while AWS reviews your submission. 4. Once AWS approves, Fours provides a direct link to Payee Central where you can submit your invoice. 5. Track the claim until the invoice is approved and the reimbursement is finalized. :::info For credit-based requests, the request stays in the **Pre-approval** stage until all credit codes are disbursed. For cash-based requests, Pre-approval is the final waiting period before you can file a claim. ::: ## Monitor wallets and purchase orders Open the **Wallet** tab on the Fours **Funding** page to see your available budgets, remaining balances, and historical spend across all AWS programs. Not every program draws on a wallet — a **Migration Acceleration Program** request is associated with an AWS opportunity instead, so it does not appear as wallet spend. To support internal reconciliation, open the funding details for any request to find the PO numbers associated with your approvals. In the Salesforce app, the Funding Detail page's **Cash Request Information** section shows the **PO Number** and the **Payee Central Account Profile ID** for MDF and POC cash requests, and both sync to the Salesforce Funding record — see [How Funding records open](/salesforce-app/salesforce-app-settings/#how-funding-records-open). ## Frequently asked questions **Can I edit a request after submitting it?** Once submitted, a request's status becomes `IN_REVIEW`, and it can no longer be edited through standard means. For minor corrections requested by AWS reviewers, use the **Amend fund request** option in the action bar. **Can I update a draft before submitting?** Yes. You can edit a draft at any time while it is in `PENDING_SUBMISSION` status. **Can I link a request to a specific opportunity?** Yes. Before submitting, you can associate the request with a related customer opportunity or an existing benefit allocation from within the request builder. **What happens if my request fails validation on submission?** Fours will show you the specific fields that need to be corrected. Update those fields and resubmit. **Why doesn't my ACE opportunity show up when I submit an MPOPP (Marketplace Partner Opportunity Program) request?** This is a known AWS Partner Central 3.0 bug tied to CPPO-to-ACE association. Before resubmitting, confirm the Marketplace Offer ID is linked to the opportunity — this is the root cause in most cases. **Why have my funding requests stopped updating?** If AWS reports that your AWS account is no longer an active AWS partner, Fours pauses the scheduled funding sync for your organization, because retrying cannot succeed until that changes. Once your partnership is restored, contact [support@suger.io](mailto:support@suger.io) to have the sync resumed. --- For assistance with any step in this guide, contact your Fours Customer Success Manager.