A SaaS invoice used an unexpected customer credit

An invoice with little or nothing to collect may have consumed a credit from an earlier dispute, overcharge or manual adjustment. Start with the credit transaction history. Identify the original amount, currency, approval, related invoice and any restriction agreed with the customer. A net customer balance hides these separate events and cannot explain whether the latest application was appropriate.

Keep promotional reductions separate from cash the customer has sent and from credit notes correcting an earlier bill. The ledger treatment and refund implications can differ. If the history contains an opening balance from a migration, retrieve the old system's support before assuming it is available for any new subscription. Assign an owner to unsupported credits instead of recreating their reason from memory.

Stripe's customer credit balance is different from its customer cash balance. Its documented credit balance applies automatically to the next finalized invoice and cannot be directed to a chosen invoice. That behavior can conflict with an informal promise that a credit will be saved for a specific renewal. Check the customer's actual configuration before making that promise.

Consider a hypothetical account with a $900 credit intended commercially for an annual renewal. A separate $300 service invoice finalizes first and uses part of it. Finance must explain the $300 application and the $600 left, then decide whether the intended arrangement needs a supported adjustment. Issuing another $900 credit without that review would increase the customer's benefit beyond the approved amount.

Prepare a short statement showing credit created, credit used and credit remaining. Connect each use to an invoice number, and identify any reversal. Send the customer the same calculation that finance uses, with a clear explanation of any proposed correction. A message saying the account was fixed is insufficient when the next invoice still shows an unexpected opening credit.

Ask the accountant to review the original accounting entry and the new application together. A credit arising from an invoice correction may affect a different service period from the invoice that eventually consumes it. Avoid treating every use of credit as a new discount. Preserve links between the old adjustment and the new invoice so the reporting schedule remains understandable.

Sort credit creation, application, reversal and manual adjustment events by their effective timestamps. Preserve the order in which invoices were finalized. A customer reviewing an invoice date alone may not understand why a credit reached that bill instead of another one, particularly when several subscriptions share the account.

Build an illustrative running balance from $0, add a $250 approved credit, apply $180 to one invoice and show $70 remaining before the next bill. Then compare that expected sequence with the actual history. A missing or duplicated movement becomes easier to locate than it is in a single ending-balance screenshot, and the same workpaper supports a clear explanation to the customer.

Limit manual adjustments to authorized staff and require a reason and supporting reference. Review unusual debit entries as well as credits; an unexplained debit can reverse a customer benefit without resolving its commercial basis. Where the platform records corrections through additional transactions, retain that trail instead of trying to make the history look as though the mistake never happened.

At month-end, review large, old or frequently adjusted balances with the account owner. For a customer leaving the service, resolve the remaining credit under the contract and applicable requirements before closing the account. Keep any refund evidence separate from the balance reduction and verify the final amount in both the billing platform and the ledger.