Which SaaS credit grant will the next invoice consume?

Take one customer with several grants and describe which balance should fund the next eligible charge under the accepted terms. Record the expected amount against each grant, rather than only the total discount visible to the customer. A promise that free credit is used first needs to match the actual configuration.

Stripe records paid and promotional grant categories and exposes a separate priority setting. Its Credit Grant reference identifies zero as the highest priority and 100 as the lowest. Keep the actual category and priority in the test record; the grant name alone does not establish application order. Ask the commercial owner to resolve any disagreement between the configured behavior and the customer promise.

Build the candidate list for the specific invoice. Check currency, relevant effective and expiry times, available amounts and the prices to which each grant applies. A grant with a favorable priority can still be outside the permitted population. Record the reason for excluding it so a reviewer can distinguish an eligibility result from an ordering error.

Stripe limits billing-credit application to supported metered subscription items and allows price-level applicability. Its eligibility rules also consider the invoice period end, grant dates and balance at finalization. Inspect those actual attributes with the billing owner. A customer-level available total is insufficient evidence that every item on the next invoice can use that total.

Stripe applies priority before expiry, then category, effective date and creation date when distinguishing eligible grants. Lower priority numbers go first; promotional category is a later comparison. Verify the documented behavior for the integration in use and retain the resulting grant-to-invoice applications.

For an illustrative test, both grants cover the same charge and meet every eligibility condition. Purchased credit of $800 has priority 10, while promotional credit of $200 has priority 50. A $150 charge should consume the higher-priority purchased grant under that configuration, leaving $650 purchased and $200 promotional. That result can be technically correct while conflicting with an employee's promise that the promotion would be used first.

Change one test attribute at a time when investigating a difference. Preserve the initial settings and expected result before asking the authorized owner to approve any production change.

Preview the customer's other subscriptions and identify invoices that can consume the same grants. Stripe explains that credits apply at finalization and that separate subscription invoices can finalize in an order it does not guarantee. A draft allocation can therefore change when another invoice uses the balance first.

Test that competing-invoice case through the supported testing process. Retain both invoice identifiers and finalization outcomes, then explain why the second invoice received a different amount from its earlier preview. Check customer communications that quote a draft amount before collection, particularly where the customer expects a specific promotional allowance to cover a particular product.

Compare expected and actual consumption for each grant and each tested invoice. Classify differences as eligibility, priority, competing consumption or an unsupported assumption in the customer terms. The correction should address the identified cause; issuing another promotional grant can conceal the configuration problem while changing the commercial benefit.

Retain the approved settings, test cases and actual applications with the billing change record. Give accounting the funding split for the completed invoices under its existing policy. When a campaign changes its products, dates or priority, repeat the affected cases before release so the commercial promise continues to describe what the billing system will do.