Statement of account: the document that gets invoices paid without chasing
A statement of account shows the whole relationship, not one invoice. Sent on a schedule, it resolves most payment queries before anyone has to make a call.
A payment without a remittance advice leaves the supplier guessing which invoices it covers. That guess becomes your chase email three weeks later.
A remittance advice is the note a payer sends alongside a payment listing which invoices the payment covers, in what amounts, and with what deductions. It carries no money and creates no obligation — its only job is to let the supplier allocate the cash correctly the first time.
That sounds minor until you sit on the receiving side. A payment of 47,318.22 arriving from a customer with twenty open invoices, three credit notes and a disputed line is not a payment; it is a research task. The remittance advice is what turns it back into a payment.
The deductions line is the one that matters most. A short payment with no explanation is treated by most suppliers as a partial payment and chased as arrears; the same short payment with "settlement discount 2% per agreed terms" against it is closed on receipt.
It is easy to see a remittance advice as a courtesy to the supplier. In practice the payer gets the larger benefit: fewer chase calls, fewer statements to reconcile, fewer credit holds triggered by cash the supplier could not allocate, and a written record of the deduction you took while the reasoning is still fresh.
It also protects the relationship in the one situation where it counts. When a genuine dispute arises, the remittance history shows exactly what was paid against what, and the argument narrows to a single line rather than a whole account.
Send the advice at the same time as the payment, not after it clears. A supplier who sees the cash before they see the explanation has already started the query, and stopping a chase costs more than preventing it.
Where the ledger already knows which invoices a payment settles, producing the advice is a formatting step rather than a task. Ettex Books builds the remittance from the payment allocation itself, so what the supplier is told and what the ledger recorded cannot drift apart, and the copy sent stays attached to the transaction.
If you are the supplier and remittances are not arriving, ask for them explicitly and give a specific address to send them to. Most payers will comply; the ones that will not are usually paying from a system that cannot produce them, which is worth knowing before you build your collections process around cash you cannot allocate. Either way it is cheaper than the alternative, which is credit control chasing invoices that were paid a fortnight ago.
Generally no. It is a commercial courtesy that has become standard practice because allocation errors are expensive for both sides.
The payer sends the advice to say what is being paid. The supplier issues the receipt to confirm money was received. They travel in opposite directions.
For any payment covering more than one invoice, or carrying any deduction, yes. For a single invoice paid in full it adds little beyond the invoice number appearing on the bank reference.
Yes, and that is now the normal channel. Some large payers use EDI or a supplier portal instead; the content requirement is the same.
A statement of account shows the whole relationship, not one invoice. Sent on a schedule, it resolves most payment queries before anyone has to make a call.
The bank flags items that do not match your issue file. If nobody decides by the cut-off, the default in your agreement decides for you.
There is no such thing as approved software. What is examined is whether your system separates costs correctly and whether people record time daily.