Hiring guide
Customer credit notes: separate a lower invoice balance from a cash refund
By CFO Index · Published
A credit note can reduce a customer's debt without moving money. On an already paid invoice, the agreed remedy may instead involve a refund or value usable against another invoice. Ask your fractional CFO to make those routes explicit before a collections report or cash forecast interprets an invoice status as a bank receipt.
Keep the original invoice and the reason for adjustment
Record legal entity, customer, currency, invoice ID, credited lines, reason, approval and credit-note ID. Retain the original invoice rather than replacing its history with an unexplained lower number. Stripe describes credit notes as adjustments that reduce open or paid invoices without voiding and replacing the invoice. This is the cited product's behaviour, not a universal legal format. The accounting owner determines the necessary document, tax correction and posting treatment under the applicable rules.
Classify the cash route before aggregating
In Stripe, an open-invoice credit reduces the amount due without recording payment; a credit that brings the balance to zero can make the invoice status paid. That status is therefore not, by itself, evidence of customer cash. For paid invoices, document whether the remedy is a payment-method refund, customer-balance credit or an externally recorded refund. Link the actual disposition and its settlement evidence. A credit-note amount and a separately reported refund may refer to the same remedy, not two outflows.
Reconcile one unpaid invoice
Hypothetical example, excluding taxes, fees and currency effects: a €12,000 invoice has €4,000 of confirmed receipts. An authorised €2,000 credit note corrects overbilling on that same invoice. The remaining receivable is €6,000: €12,000 less €4,000 less €2,000. The credit note adds no new cash and does not refund the €4,000 already received. If the remaining €6,000 is later paid, total receipts for this corrected invoice are €10,000, not €12,000.
| Item | Receivable effect | New cash effect at adjustment date |
|---|---|---|
| Original invoice | €12,000 | Not a receipt |
| Confirmed payment | −€4,000 | €4,000 received previously |
| Approved credit note | −€2,000 | €0 |
| Remaining amount to collect | €6,000 | Future receipt, not yet cash |
Track an already paid invoice differently
Separate hypothetical case: a fully collected €3,000 invoice receives an authorised €600 credit. Assume €400 is to be refunded and €200 retained as customer credit for future use. The disposition totals €600. Until the €400 refund settles, show it once as expected outgoing cash; after settlement, remove the pending outflow and retain the transaction evidence. The €200 is not another immediate bank outflow in this assumed route. If applied to a future €1,000 invoice, that invoice's expected cash receipt becomes €800, subject to the agreed terms and other adjustments.
Keep proposal, authorisation, issue and settlement distinct
An account manager's proposed concession is not an issued credit note. An issued document is not proof that a promised refund settled. Suggested register fields are proposed amount, approved amount, issue date, receivable allocation, customer-credit allocation, pending refund, settled refund and next owner/action. Link reversals and voids to their originals rather than deleting them. Keep disputed concessions in a sensitivity until authorised; do not suppress the customer's claim merely because the internal approval is incomplete.
Test the report at its misleading boundaries
Use a supported test environment or synthetic records to test an unpaid invoice reduced to zero without payment, a partial credit after partial payment and a paid invoice split between refund and future credit. The bank receipts report must not count the zero-balance status as money, and the cash forecast must not subtract both the credit note and its refund. Reconcile at invoice level before comparing customer totals. Report unresolved allocation differences with an owner and deadline; a dashboard total that agrees by coincidence is not sufficient acceptance evidence.