Remittance advice template: the fields AR needs to match

A remittance advice should name the payer, the payment reference and date, and list every invoice the payment covers with the amount paid on each. If it does, an AR specialist can apply the payment without a phone call; if it does not, the desk guesses.

This page gives the template as a field list and a plain-text example, then shows what a program can and cannot read from the remittances customers actually send.

What fields should a remittance advice include?

At the top: payer name, payment reference (check or ACH number), payment date and total paid. Below that, one line per invoice. Each line needs the invoice number, the amount paid, and, when the customer paid less, the deduction and the reason.

Optional but useful: the customer's account number with you and the PO number. They help a person who reads the remittance by hand; Remit Reader matches on the invoice number and amount and does not use them.

What does a good one look like?

Here is a layout you can send to customers who ask what you need:

Payer: Harbor Point Grill Group LLC
Payment reference: ACH 004417
Payment date: 2026-10-09
Total paid: 9,001.17

Invoice no.   Amount paid   Deduction   Reason
104511        1,284.60
104517          455.20         57.60    Damaged on delivery

(The amounts are example data.) Keep one invoice per line, print the number as it appears on your invoice, and make the lines add up to the total.

Why do real remittances not look like that?

Because each customer's AP system prints its own layout. In the sample the customer adds an "INV-" prefix to every number. Others print dates in a different column order, merge a credit memo into the payment, or send an Excel sheet with a title line above the headers.

Remit Reader handles that by normalizing invoice numbers (uppercase, prefixes such as INV and # removed, leading zeros, spaces and punctuation stripped) before matching them to your open invoices.

Can a program read my customers' remittances?

If the PDF has text in it, yes. Remit Reader reads text PDFs, Excel and CSV remittances, lists every paid line with its amount and reason, and shows each line with a confidence flag beside the PDF. You edit, add or delete a line, then approve.

A scanned PDF is just a picture, so it goes to manual entry: you type its lines beside the preview. That is the honest limit of the tool.

What happens after it reads one?

Each line is matched to your open-invoice export and classified: applied in full, short-pay, overpay, invoice not found, already paid or not open, or ambiguous. You download a CSV of the applied lines and a second file of the lines that need a person.

Next: how a short-pay gets flagged, the full cash application process, and how to choose cash application software.

What should you do when a remittance leaves something out?

Check what is missing before you guess. The most common gaps are listed here with what to do about each.

• No invoice numbers, only a total. The line cannot be matched by number. Remit Reader will match only if the payer has a single open invoice at that amount; otherwise it lists the line for a person.
• Lines that do not add to the total. The remittance is flagged when they differ by more than $1, so you can see whether the customer or the reader made the error.
• A deduction with no reason. Record the difference as a short-pay and ask the customer, if your policy says to.
• A credit memo netted into the payment. It shows up as a deduction line; keep the reference the customer printed.

How do you ask customers for a better remittance?

Send them the template above and ask for three things: one invoice per line, the number as printed on your invoice, and a reason for any difference. Some will adopt it and some will not, which is why the reading side has to cope with both.

Where do the remittances arrive?

Usually as email attachments or portal downloads, saved as PDFs, or as spreadsheets from larger customers. Remit Reader takes uploads, several at once; it does not read your inbox or forward emails. Save the attachments to a folder and upload them as a batch. Each PDF is uploaded in its own request, and the reader's limit is 10 MB per file.

FAQ

Can I turn a remittance advice into Excel?

For a text PDF, the free run reads the lines and gives you the result as a CSV, which opens in Excel. Scanned PDFs need manual entry.

Do I have to use a template?

No. Customers send what their system prints, and the reader copes with the differences above. The template is for the customers who ask.

Are bank details kept?

Lines that look like bank or routing details are dropped from the extracted text and lines. The original file is kept as uploaded.