The remittance says one thing. The payment says another.

Short answer

Treat the remittance as evidence, not as instruction. Reconcile the money to the obligations first, then use the remittance to explain any difference — deductions, part payments, a credit note, a self-billed reference that is not your invoice number. Where the two still disagree, hold the difference visibly unresolved rather than writing it off to make the ledger balance.

Why the remittance and the payment arrive apart

The payment moves through the banking system. The remittance moves through email, a supplier portal, a PDF attachment, or occasionally the post. They are produced by different systems inside the payer, and released on different schedules.

The practical consequences are the ones worth planning for. The remittance may arrive days before the money or days after it. It may go to a person rather than to a shared mailbox, and sit unread while somebody else reconciles the bank. It may never arrive at all, which is common and not a sign that anything is wrong. And when it does arrive, it describes the payer’s intention at the moment it was generated, which is not always what their payment run actually did.

The five ways they fail to agree

Almost every mismatch is one of these, and each needs a different response.

1. One payment, several invoices. The most common case. A single credit settles six invoices, and the bank line shows one number that appears nowhere in your ledger. The remittance is the only thing that breaks it apart, which is why its absence is felt most here.
2. Part payment. The payer has paid some of an invoice, or some of several. A remittance that lists the full invoice value against a smaller payment is describing intent, not settlement, and allocating the full value will leave a balance nobody is chasing.
3. Deductions at source. The payment is smaller than the invoice on purpose. In construction this is usually a Construction Industry Scheme deduction and often contract retention as well; elsewhere it may be a rebate, a settlement discount, or a charge the customer has raised against you. The remittance may show the deduction, summarise it, or omit it entirely.
4. Self-billing. The customer raises the invoice on your behalf under a self-billing agreement, so the reference on the payment and on the remittance is their document number. Your own invoice numbers may never appear on the money at all, and matching by reference is not merely unreliable here, it is looking for something that was never sent.
5. Credit notes and adjustments. A remittance that nets a credit note against invoices produces a figure that matches no single document you hold. It is correct, and it will not reconcile line by line.

Work the difference in a fixed order

The order matters, because starting with the remittance means starting with the least reliable object in the process.

1. Identify the payer from the payment, not the paperwork. Sort code and account number are set by the payer’s bank rather than typed by a person, so they are the strongest identifier you have.
2. Assemble what is open for that payer. Every outstanding invoice, every credit note, every agreed deduction. This is the set the payment has to be explained against.
3. Compare expected against actual. A difference is information, not an error. Note its size before you look for a reason, because the size usually tells you which of the five causes above you are dealing with.
4. Bring in the remittance to explain the difference. Now, and only now. Used at this point it is evidence for a conclusion you have already reached independently. Used first, it is an instruction you have no way to check.
5. Record what the difference was, not just that it resolved. “Short by the CIS deduction” and “short and we never found out why” look identical in a ledger six months later, and only one of them is finished.

What to do when there is no remittance

A payment can be reconciled without one, and often has to be. Amount and payer together is a reasonable threshold: two independent agreements rather than one. A payment that arrives on the same working day each month, for the same amount, from the same account, is not a mystery even with nothing attached to it.

What matters is the residue. Where a payment cannot be fully explained, the unexplained part should stay visible as an unexplained part. Allocating it to the nearest plausible invoice makes the month look finished and moves the problem to whoever opens that account next.

Making it happen less

• Ask for remittances to a shared address. The single highest-value change, and the easiest. A remittance sitting in one person’s inbox is not available to the person doing the reconciliation.
• Put your reference where the payer’s system will carry it. Not merely on the invoice: in the field their payment run actually reads.
• Agree how deductions will be shown with the customers who make them regularly, before the first one arrives rather than after.
• Record the self-billing relationships you have, so that a payment referencing an unfamiliar document number is recognised rather than investigated.

Where the difficulty actually sits

None of the above is hard on its own. It is hard because the information is scattered: the money is in the bank, the obligation is in the invoicing system, the explanation is in an email, and the agreement that makes the deduction correct is in a contract nobody has opened since it was signed. A person joins them, from memory, every month.

That gap is what Tervra is being built to close. Your bank sees a payment; the reason it arrived is somewhere else in your business. Tervra is designed to assemble what a receipt relates to from the payer, the amount and the obligations already recorded, to say what it cannot establish rather than guessing, and to leave the unexplained visible instead of allocated. How money in works.