One SaaS customer transfer covers several invoices: allocate it from the remittance

A single transfer from an enterprise customer can cover invoices for several teams, service periods or purchasing references. Request its remittance advice and compare the invoice numbers with the open account. Matching the transfer to whichever invoices happen to total the same amount can leave the customer's intended debts open and clear unrelated ones.

Confirm the paying legal entity and currency as well as the name on the bank entry. A shared-services team may pay for several subsidiaries, or a trading name may differ from the invoice customer. Keep those relationships documented. If the sender cannot yet provide an allocation, retain an unapplied receipt with an owner and follow-up date while the explanation is obtained.

Stripe documents both automatic and manual reconciliation for customer cash balances. Its automatic process can use payment references, amount combinations and other matching rules. Those rules are useful processing aids, but the result still deserves review when one remittance covers several invoices or the customer has specified an unusual allocation.

Make a comparison with the intended invoice, intended amount, applied amount and remaining balance. If the platform applied funds differently, follow its supported correction process and preserve the earlier application reference. Check reminders and any automatic payment attempts on the invoices that the customer believes have been settled before the next collection run.

For an illustrative transfer, a customer might list invoices of $4,000 and $3,000 but send $6,800. The $200 difference needs an explanation. It could be a bank charge, an asserted credit or an amount omitted accidentally. Confirm who bears transfer fees under the agreement and whether any deduction has been approved; do not automatically reduce revenue to force a match.

Where the remittance references a credit, locate the actual approved credit note and ensure it has not already reduced another invoice. If the customer has used a credit from a different legal entity or currency, escalate the proposed offset for review. Keep disputed deductions visible by invoice so the collections team can discuss a specific amount and reason.

Equal totals can conceal different intended allocations. Suppose, hypothetically, a customer sends $4,000 while two $2,000 invoices and one $4,000 invoice are open. The amount alone cannot tell you whether the transfer pays the two smaller bills or the larger one. Obtain the remittance reference or an authorized clarification before clearing balances that determine the customer's next reminder.

Record the allocation evidence with the receipt, including any later customer correction. If the platform already matched the money differently, reconcile the supported reassignment and check the resulting aging. Keep the original cash receipt unchanged as evidence of what arrived; the allocation explains which obligation that receipt settled.

Reconcile the complete receipt across bank or processor records, billing applications and ledger entries. The amount applied plus any unapplied balance should explain the gross receipt, with separately supported fees or currency effects where relevant. Preserve the remittance document alongside the allocation so a reviewer can repeat the calculation without searching an account manager's inbox.

Send the customer an updated statement when the allocation changes which invoices remain due. Review repeated matching failures with the customer and systems owner: a consistent invoice reference format or a dedicated remittance address may solve the underlying problem. Keep a record of the agreed format and check the next transfer to confirm that it reaches the intended invoices.