A remittance advice is a notification sent by a buyer to a supplier listing which invoices a given payment covers, so the supplier can allocate the received cash to the correct open items.
A remittance advice exists because a payment and its justification travel separately. One transfer of 48,200 euros may settle fourteen invoices and two credit notes. Without the accompanying detail, the supplier receives an amount it cannot allocate, and the same balance stays open on both ledgers.
Remittance advice is transmitted in four common formats:
- a PDF or email issued alongside the payment run
- an EDI 820 message in retail and industrial supply chains
- structured remittance data carried inside an ISO 20022 pain.001 instruction
- a CAMT.054 credit notification retrieved from the supplier bank
The practical constraint is field length. A SEPA credit transfer carries only 140 characters of unstructured remittance information, rarely enough for more than three or four invoice references. Beyond that, the remittance advice has to travel as a separate document, and any divergence between the two becomes a supplier statement reconciliation task. A supplier unable to allocate a payment does not absorb it, it opens a query, which returns to the buyer accounts payable team as inbound work created by its own missing document.
Phacet reconciles payment confirmations against the invoices they were meant to settle, so a partial payment or a deduction applied without notice is raised as an exception instead of surfacing at the next statement review. The same logic drives SEPA payment reconciliation on the collection side.
