A €3,000 transfer reaches the bank account. Four invoices for the same customer remain open: €1,100, €1,900, €1,400 and €1,600. Two combinations equal the money received. Which invoices should be settled? The bank total cannot answer that question. An arithmetically correct allocation can leave the wrong invoices waiting for reminders.
A payment covering several invoices needs evidence of allocation. The received amount, payer identity and remittance advice should describe the same transaction. This becomes especially useful when a customer deducts a credit note, pays for several establishments together or uses a bank reference too short to list every document. For French and European accounts, treating that evidence carefully helps prevent avoidable disagreement after payment.
Start with the remittance advice, not a matching sum
A remittance advice explains what the customer intends to pay: invoice references, allocated amounts and any deductions. It may arrive separately from the transfer. Ask accounts payable for it when the bank reference cannot support a reliable allocation, and include the amount and date received so the customer can find the relevant payment.
A missing invoice list does not always reflect carelessness. The European Payments Council’s description of a standard SEPA Credit Transfer includes remittance information of up to 140 characters. Several lengthy references may exceed that space. This explains the value of a separate advice or structured information; it does not justify an arbitrary allocation. Source: EPC SCT scheme overview.
Preserve the complete message when an advice exists. An internal forward containing only “payment made” can lose the attachment or the lines explaining its allocation. The useful request becomes “Please forward the advice associated with this transfer”, rather than another general question about whether the customer has paid.
Confirm the account before allocating the funds
Check the billed legal entity, currency and payer identity. A group may centralise payments for several subsidiaries, so a different bank account name does not automatically mean an error. It does mean that the relationship between payer, customer and invoices needs to be established. An allocation across entities requires an arrangement that finance has checked.
Also determine whether the movement is new to your records. The same transfer may appear in a bank import, a manually registered payment and an advice supplied by the customer. Those records can describe one amount, not three receipts. Allocating it must not create another cash entry.
When funds are present but their destination remains uncertain, follow your process for tracing unallocated cash. The record should show both facts: money has arrived, and the invoices it settles are still being established. A general “customer paid” label removes visibility of the uncertainty without resolving it.
Follow the customer’s instruction and review cases without one
For French obligations, Civil Code article 1342-10 allows a debtor with several debts to specify which one a payment settles. Without an indication, it provides successive criteria involving debts already due, the debtor’s interest in settling them, age and, all other things equal, proportional allocation. “Always pay the oldest invoice first” does not fully describe that rule. Source: Légifrance.
Your procedure should therefore prioritise obtaining a clear instruction and route undocumented cases to the appropriate finance or legal reviewer. Interest, existing agreements or a dispute may require further assessment. A software suggestion based on matching amounts can support the investigation, but it is not an independent legal determination.
Do not change an allocation merely to improve an aging report. Settling the oldest documents may make the dashboard look healthier while contradicting the customer’s advice. The next conversation then starts with a disagreement introduced by your own records, even though the original payment could have been identified correctly.
Why equal totals do not establish the right allocation
Return to the first example, which is entirely hypothetical. Invoices A and B are €1,100 and €1,900; C and D are €1,400 and €1,600. A + B equals €3,000, and C + D also equals €3,000. The payment fits both possible groups.
Suppose the customer’s advice identifies C and D. Those documents should be treated according to the verified instruction, while A and B remain open for €3,000. If an earlier allocation had settled A and B, the account total would still be correct, but the references being chased and their aging would be wrong.
| Hypothetical result | Verified customer allocation | Allocation based only on a matching sum |
|---|---|---|
| Invoices settled | C and D | A and B |
| Total account balance | €3,000 | €3,000 |
| Invoices remaining open | A and B | C and D |
| Supporting evidence | Matches the verified advice | Not established |
The check cannot stop at “the account adds up”. Confirm that the payment reduced the correct documents and that the residual balance can be explained to the customer. That distinction is particularly important when some invoices are disputed and others have been accepted for payment.
Investigate credits and residual differences separately
In a second simulation, the advice lists invoices of €1,100, €1,900 and €2,400 and deducts a €400 credit note. Expected payment for that scope is €5,000: €1,100 + €1,900 + €2,400 − €400. If the actual transfer is €4,700, a €300 difference remains to be explained.
First confirm that the credit note is valid and correctly allocated. Then investigate the €300: an announced partial payment, another adjustment, a disputed deduction or a mistake. Do not create an accounting adjustment simply to make the reconciliation complete. The reason for the residual amount should determine its treatment.
If the payment follows a dated payment promise, compare the receipt with the promise’s scope. A commitment may be partly fulfilled without covering every invoice on the customer account. Establish the residual amount on the relevant documents before preparing another request.
Agree a lightweight convention for future payments
For customers regularly paying several invoices together, agree a consistent advice format: transfer reference, date, currency, invoice number and allocated amount on each line. Ask for credit notes to be identified separately. A stable spreadsheet may be enough; what matters is whether the references correspond to the documents in your accounting records.
The EPC also describes an Extended Remittance Information option, or ERI, for sending details of several invoices and credit notes with a single transfer. Payment service providers must adhere separately to that option. Check whether it is supported through your banking chain before making it a requirement for the customer. Source: EPC ERI option.
Test the convention on a real payment before rolling it out widely. Compare the advice received by the customer-facing team with the information finance sees, including any truncated references or missing attachments. The process should remain usable when the usual accounts payable contact is absent.
After reconciliation, review the case from the screen used to send reminders. Fully settled invoices should leave the queue, partially paid invoices should retain the correct balance and the evidence should remain accessible. When evaluating debt collection software, this is a precise test: one bank entry, several documents and a verifiable explanation for every amount allocated.
