--- title: "AWS Fund Request Status, Stages and Claim Deadline" url: https://www.suger.io/resources/blog/aws-fund-request-status/ canonical: https://www.suger.io/resources/blog/aws-fund-request-status/ type: Blog description: "What each AWS fund request status and stage means, what you can still recall, amend or extend, and why December 15 caps the claim on a cash request." --- # AWS Fund Request Status, Stages and Claim Deadline > Canonical HTML version: https://www.suger.io/resources/blog/aws-fund-request-status/ 1. [Home](/) 2. / 3. [Resources](/resources/) 4. / 5. [Blog](/resources/blog/) 6. / 7. AWS Fund Request Status, Stages and Claim Deadline # AWS Fund Request Status, Stages and Claim Deadline Status and stage are two separate fields on an AWS fund request. Here's what each value means, what you can still change at each point, and the December 15 date that decides whether a cash claim gets paid. [![Sabrina Xie](/authors/sabrina-xie.jpg)](/resources/blog/author/sabrina-xie/) [Sabrina Xie](/resources/blog/author/sabrina-xie/) Sep 28, 2026 ![AWS Fund Request Status, Stages and Claim Deadline](/images/blog/aws-fund-request-status/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-fund-request-status%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-fund-request-status%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-fund-request-status%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.suger.io%2Fresources%2Fblog%2Faws-fund-request-status%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20AWS%2C%20Co-Sell. "Summarize with Perplexity") Table of Contents - [What is an AWS fund request status?](#what-is-an-aws-fund-request-status) - [What does each AWS fund request status mean?](#what-does-each-aws-fund-request-status-mean) - [What does each fund request stage mean?](#what-does-each-fund-request-stage-mean) - [What can you still change on a submitted fund request?](#what-can-you-still-change-on-a-submitted-fund-request) - [When is the claim deadline for an AWS fund request?](#when-is-the-claim-deadline-for-an-aws-fund-request) - [Cash or credit: which path does a fund request take?](#cash-or-credit-which-path-does-a-fund-request-take) - [How many attachments can a fund request carry?](#how-many-attachments-can-a-fund-request-carry) - [How does Suger track AWS fund requests?](#how-does-suger-track-aws-fund-requests) - [Frequently asked questions](#frequently-asked-questions) - [Takeaways](#takeaways) _An AWS fund request status is the condition AWS reports for a partner funding request: pending submission, in review, action required, approved, rejected or canceled. It is tracked separately from the stage, which records how far the request has moved through approval and payout. Status decides what you can do now, stage decides whether you can still pull the request back, and the claim deadline decides whether a cash request gets paid._ * * * An MDF request shows `IN_REVIEW` in one place and Business Approval in another, and someone on the deal team asks whether it’s stuck. It may not be. Those are two different fields. AWS spreads the rules for a filed request across several Partner Central pages and its Benefits API guide, and the page that defines the stages never mentions December 15. This post puts them side by side. It starts where [choosing the right AWS partner funding program](/resources/blog/aws-partner-funding-programs/) ends: the request is filed, and now it has to be approved and paid. ## What is an AWS fund request status? **An AWS fund request status is** the condition AWS reports for a funding request: still a draft, under review, waiting on you, approved, rejected or canceled. It is not the stage. AWS says partners track a request “based on two attributes: the Stage and the Status,” where the stage “indicates the current phase in the overall Fund Request lifecycle” and the status “the current health or condition of the Fund Request.” The two move independently. On submission the status becomes `IN_REVIEW`, and the request enters an approval workflow that “may include business approval, technical approval, and finance approval stages,” tracked in the stage field. A request can read `IN_REVIEW` through several stages in a row. ## What does each AWS fund request status mean? Six values come back from AWS’s Benefits API, the set Suger displays, and only a draft can be changed freely: Status What it means `PENDING_SUBMISSION` A draft: created and not yet submitted, or recalled back to draft `IN_REVIEW` Submitted, with the approval workflow running; the stage shows which approval `ACTION_REQUIRED` AWS needs something from you, named in the status reason codes `APPROVED` AWS has approved the application `REJECTED` AWS has rejected it; you can revise and resubmit `CANCELED` Withdrawn by you. It can’t be reactivated Partner Central’s own funding pages use different labels: Active, Pending, Terminated, Expired, Completed and Deleted. AWS documents both sets but doesn’t map one onto the other, so don’t translate between them. Two of those labels matter most near a deadline: Terminated, a request you cancelled, which “cannot be reactivated,” and Expired, a request past its expiration date, which AWS gives as “30 days after delivery end date.” An expired request “can no longer have actions taken.” ## What does each fund request stage mean? **A fund request stage is** the step a request has reached in AWS’s approval and payout process. AWS’s Partner Central guide defines eight, and not every request passes through all of them: Stage What AWS says happens there Created A draft not yet submitted, or a rejected request waiting for your changes AWS Review With an AWS reviewer. POC and the Miscellaneous motions (Jumpstart and ISV WMP) only Tech Approval A Partner Solution Architect checks the project plan or statement of work for technical feasibility. POC only Business Approval With the program’s business approver, who varies by program Finance Approval AWS Operations raises a purchase order for cash, or generates codes for credits Pre-Approval All approvals are in, and you can start the activity. MAP requests skip this stage Cash Claim You submit actuals when the project or milestone is complete and AWS reviews them; once they’re approved, you invoice through Payee Central. The stage holds until the invoice is approved Completed All credits redeemed, or all cash claims completed Through the API the stage is looser. AWS’s Benefits API guide gives “Business Approval”, “Tech Approval” and “Finance Approval” as examples, and its API reference types the field as a plain string with no published list of values. When a tool shows you a stage, check whose name it is. ## What can you still change on a submitted fund request? Less as it moves: edit only a draft, recall only before Pre-Approval, amend only the fields AWS names, extend once, and cancel for good. Find your request’s condition: - **Status `PENDING_SUBMISSION`.** Edit anything, and link or unlink the opportunity or benefit allocation. Neither is possible after submission. - **Submitted, stage before Pre-Approval.** Recall it for real changes. Partner Central returns it to the Created stage, and the API to `PENDING_SUBMISSION`, with your entries intact. From Pre-Approval on, it “can no longer be recalled.” - **A reviewer asks for a small fix.** Amend rather than recall. An amendment replaces single fields, and AWS’s API reference names only a few: the account ID on MAP requests and the second-tranche consent on ISV Workload Migration requests. - **Status `ACTION_REQUIRED`.** Read the status reason codes before changing anything. AWS’s examples are Checklist Incomplete, Project Plan Missing and Design Win Missing. - **Status `REJECTED`.** Read the reason in the rejection email or under Approval History first, because the resubmission screens don’t show it. Then choose Resume fund request, revise and resubmit, with a start date at least 14 days out. - **Approved, and the activity is running late.** Extend the planned end date before the activity expires: once, by 1 to 90 days, never to a date between December 16 and January 1, and not across the year on MDF. - **Stage Pre-Approval.** Start the activity. A credit request waits here until every code is disbursed and applied. - **Stage Cash Claim, activity complete.** Submit your actuals within 30 days, and by December 15 at the latest. - **Claim rejected.** Read the reason in the claim’s Actuals section, choose Edit cash claim, and resubmit the actuals. - **Claim approved.** Invoice in Payee Central before the expiration date. - **Funding no longer needed.** Cancel, knowing it’s permanent: a cancelled request can’t be reactivated, so needing the funding later means a new request. - **Partner Central shows Expired.** Nothing more can be done on that request. ## When is the claim deadline for an AWS fund request? Within 30 days after the activity completion date, and never later than December 15 of the calendar year of the request. In AWS’s words: “Claims must be submitted within 30 days after the activity completion date or by December 15th of the calendar year of the request.” For a 2026 request, that outside date is December 15, 2026. December 15 is a ceiling, not an alternative. The same page sets the Funding Expiration Date to “30 days from the new completion date or December 15th of the calendar year of the request,” and adds: “If December 15th is selected as the end date, the expiration will be the same day.” When What AWS’s rules say Before the activity expires Extend the end date once, by 1 to 90 days; not into December 16 to January 1, and not across the year for MDF Project or milestone complete File the cash claim with your actuals 30 days after completion The claim is due, and the Funding Expiration Date arrives December 15 of the request’s year The latest claim and expiration date for that year’s requests After AWS approves the claim Invoice in Payee Central, before the Expiration Date After the Expiration Date The request is Expired, and no further action can be taken The claim isn’t the last step. Invoices go into Payee Central “after Claim approval, and prior to the Expiration Date,” the same date the claim is due, so a claim filed on its last day leaves no room for AWS to approve it and for you to invoice. Treat the expiration date as the invoice deadline. An illustrative example: Acme’s 2026 MDF request covers a webinar series ending November 20, 2026. Thirty days would run to December 20, but the cap is December 15, so Acme’s actuals, AWS’s approval and the invoice must all fit in 25 days. An extension can’t help, because an MDF end date can’t cross the year or fall between December 16 and January 1. Decide who owns the claim before the activity ends: in Partner Central, a standard user sees only the fund requests they own, while alliance leads see every request on the account. ## Cash or credit: which path does a fund request take? A cash request is paid through a claim and an invoice; a credit request is paid in credit codes and has no claim to file. The routes split at Finance Approval, which raises a purchase order for cash and generates codes for credits. A cash request’s Pre-Approval is then “pending final finance confirmation” before it moves to Cash Claim. A credit request stays in Pre-Approval “until all credit codes have been disbursed and applied,” and completes once the credits are redeemed. Only cash requests face the claim calendar above. ## How many attachments can a fund request carry? Up to ten files per application under AWS’s Benefits API guide, and each file can be tagged with the business use case it supports. The tool you file through may allow fewer files and fewer types, so keep its rules apart from AWS’s: - **AWS’s limit.** The guide allows attachments “such as project plans, SOWs, proof of cost, or customer satisfaction surveys,” to a “maximum 10 files.” The API reference’s field accepts up to 30; until AWS reconciles the two, plan on ten. - **AWS’s types.** The business use case is a plain string in the API, and the API reference lists no accepted values. - **Suger’s forms.** Suger offers 19 attachment types on every program except ISV Workload Migration, which offers seven. The console adds one attachment row per file, and [Suger’s HubSpot funding form](https://doc.suger.io/hubspot-app/hubspot-app-funding/) takes one attachment per application. Those are Suger’s interface limits, not AWS’s. - **Business Case and Quote.** Suger’s documentation reports that attachments typed Business Case or Quote, which its Market Development Funds form used to offer, are rejected when the request is submitted to AWS. That is Suger’s observation of AWS’s API, not a rule AWS publishes. Retype either one, for example to Marketing Plan or Other, and resubmit. - **Quarantined files.** Partner Central scans each attachment. One that fails is Quarantined, usually over a formula outside the accepted set: remove the formulas or convert the file to PDF, then reattach it. ## How does Suger track AWS fund requests? Suger files and tracks requests through AWS’s Partner Central Benefits API, from the Suger Console, Salesforce or a HubSpot deal, and shows AWS’s status and stage in the console and on the Salesforce opportunity or HubSpot deal. The console draws the stage as a six-step stepper. The step names are Suger’s; the values behind them are the ones Suger’s documentation says AWS reports: Suger step Stage value AWS reports Application creation None yet, as on an unsubmitted draft, or a value Suger doesn’t map 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` There is no step for AWS Review or Tech Approval, and where the stage shows as a label, a value Suger doesn’t map appears exactly as AWS sent it. Three more behaviours matter near a deadline: - **Sync is scheduled.** Funding data refreshes roughly every three hours, not in real time, so on the day a claim is due, check Partner Central too. - **Fixes happen on the request.** Suger shows the status reason codes on an `ACTION_REQUIRED` request. A rejected one reopens with **Resume fund request**, and a reviewer’s small fix goes through **Amend fund request**. - **The claim stays with its request.** A cash claim isn’t a separate row in the Funding Request tab, and once AWS approves it, Suger links straight to Payee Central for the invoice. [How Suger tracks the AWS funding lifecycle](https://doc.suger.io/cosell/cosell-funding/#track-the-funding-lifecycle) covers each view in the console and both CRMs. ## Frequently asked questions ### What does IN\_REVIEW mean on an AWS fund request? It means the request was submitted and AWS’s approval workflow is running. The stage shows which approval it has reached, such as business or finance approval. You can no longer edit it freely: recall it before Pre-Approval, or amend the few fields AWS allows. ### Can you recall an AWS fund request after Pre-Approval? No. AWS’s Partner Central guide says recall is only available before a request enters the Pre-Approval stage. After that, you can still amend a few specific fields, extend an approved activity once, or cancel the request, which is permanent. ### When is the claim deadline for an AWS fund request? Within 30 days after the activity completion date, and no later than December 15 of the calendar year of the request. The Payee Central invoice is due before the same expiration date, so file the claim early enough for AWS to approve it first. ### Can you extend an approved AWS fund request? Once, before the activity expires, by 1 to 90 days past the original planned end date. The new date can’t fall between December 16 and January 1, and an MDF activity can’t cross into the next year. ### What is the difference between a cash and a credit fund request? A cash request gets a purchase order at Finance Approval and is paid through a claim and a Payee Central invoice. A credit request gets credit codes instead and stays in Pre-Approval until every code is disbursed and applied. Only cash requests file a claim. ### Why was a funding attachment typed Business Case rejected? Suger’s documentation reports that attachments typed Business Case or Quote are rejected when a request is submitted to AWS. AWS’s API reference lists no accepted types, so this is observed behaviour, not a documented rule. Change the type, for example to Marketing Plan or Other, and resubmit. ## Takeaways - Status and stage are separate fields: status says what you can do now, stage says how far the request has got and whether you can still recall it. - Edit only a draft, recall only before Pre-Approval, amend only the fields AWS names, extend once, and treat a cancel as final. - A cash claim is due within 30 days of the activity’s end, never later than December 15 of the request’s calendar year, and the Payee Central invoice has to beat the same date. - AWS’s API guide allows ten attachments per application; Suger’s forms set their own limits. Retype any Business Case or Quote attachment before you submit. Suger files AWS fund requests from the console, Salesforce or a HubSpot deal, and keeps each request’s AWS status and stage on the opportunity or deal it funds. See how funding fits the rest of the partner motion in [Suger for alliances and partnerships teams](/solutions/alliances-partnerships/). ## Sources Primary sources for the platform rules cited above. Last verified September 28, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [AWS Partner Central: Creating a fund request](https://docs.aws.amazon.com/partner-central/latest/getting-started/create-fund-request.html) — Stage and Status as two attributes; the eight stages from Created to Completed and who holds each; credit requests wait in Pre-Approval until all codes are disbursed and applied; MAP has no Pre-Approval stage; the Payee Central invoice once actuals are approved; the six dashboard statuses, including Expired at 30 days after the delivery end date; Quarantined attachments - [AWS Partner Central: Updating a fund request](https://docs.aws.amazon.com/partner-central/latest/getting-started/update-fund-request.html) — Recall returns a submitted request to the Created stage with its information intact, and is only available before the Pre-Approval stage - [AWS Partner Central: Extending a fund request](https://docs.aws.amazon.com/partner-central/latest/getting-started/extend-fund-request.html) — One self-extension of an approved activity by 1 to 90 days, not to a date between 12/16 and 1/1, not across years for MDF; the Funding Expiration Date at 30 days from completion or December 15th of the calendar year of the request, the same day if December 15th is the end date; claims within 30 days or by December 15th; invoices in Payee Central after claim approval and before the Expiration Date - [AWS Partner Central: Resubmitting a fund request or claim](https://docs.aws.amazon.com/partner-central/latest/getting-started/resubmit-fund-request-claim.html) — Where the rejection reason is shown for a request and for a claim; Resume fund request; the start date moved out 14 days from the current date; Edit cash claim to resubmit a claim - [AWS Partner Central: Managing fund requests](https://docs.aws.amazon.com/partner-central/latest/getting-started/manage-fund-request.html) — Standard Partner users see the requests they own, alliance leads see all requests for the account; separate stage and status filters - [AWS Partner Central Benefits API: Working with Benefit Applications](https://docs.aws.amazon.com/partner-central/latest/developer-guide/working-with-benefit-applications.html) — The six status values; PENDING\_SUBMISSION at creation and after a recall; updates and resource associations only before submission; IN\_REVIEW on submission, with Business, Tech and Finance Approval as stage examples; amend for minor corrections; cancel is permanent; file attachments up to a maximum of 10 files; status reason code examples - [AWS Partner Central API Reference: AmendBenefitApplication](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_benefits_AmendBenefitApplication.html) — The field paths that can be amended by program type: $.AccountId for MAP, $.IsvWmpSecondTrancheConsentCaptured for ISV WMP - [AWS Partner Central API Reference: CreateBenefitApplication](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_benefits_CreateBenefitApplication.html) — FileDetails accepts up to 30 items, against the developer guide's maximum of 10 files - [AWS Partner Central API Reference: FileInput](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_benefits_FileInput.html) — BusinessUseCase, the type on each attached file, is a string with no published list of valid values - [AWS Partner Central API Reference: GetBenefitApplication](https://docs.aws.amazon.com/partner-central/latest/APIReference/API_benefits_GetBenefitApplication.html) — Status valid values; Stage is a string with no published list of values - [Suger docs: AWS Funding](https://doc.suger.io/cosell/cosell-funding/) — Suger behaviour: requests filed through the Partner Central Benefits API from the console, Salesforce or HubSpot; the six-step stage stepper and the AWS stage value behind each step; 19 attachment types, seven on ISV Workload Migration, and Business Case and Quote rejected on submission to AWS; sync roughly every three hours; status reason codes, Resume and Amend; the Payee Central link after claim approval - [Suger docs: Create Funding in the HubSpot app](https://doc.suger.io/hubspot-app/hubspot-app-funding/) — Suger behaviour: one attachment per application on the HubSpot deal card ## Keep reading - [Co-SellAWS Partner Central Leads from Salesforce AccountsSep 24, 2026](/resources/blog/aws-partner-central-leads-from-salesforce/) - [AWSAWS Marketplace Request Private Offer: Who Answers?Sep 19, 2026](/resources/blog/aws-marketplace-private-offer-requests/) - [AWSTurning re:Invent Conversations Into ACE ReferralsAug 27, 2026](/resources/blog/reinvent-conversations-to-ace-referrals/) - [AWSMigrating to the New AWS Partner Central (ACE)Aug 24, 2026](/resources/blog/migrating-to-aws-partner-central/) [Browse every post on the Suger Blog](/resources/blog/) ### Stay Updated Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.