How do I reconcile invoices — tying invoice records to their supporting or corresponding records?

What are you actually reconciling your invoices against?

"Reconcile the invoices" is not one task. A reconciliation compares two sets of records to find the differences, so you need to know what the second set is. An invoice can be tied to five kinds of counterpart record:

• The order or agreement that authorized it. A sales order, contract, quote or subscription schedule. This shows whether the invoice should exist at all, and whether it bills the agreed price.
• Evidence that the goods or service moved. A shipping log, delivery note, receiving record or timesheet. This shows whether something was billed without being delivered, or delivered without being billed.
• The payment or remittance that settled it. A payment record, remittance advice or cash application. This shows what is still open.
• The ledger entry that recorded it. The receivable or payable in your books. This shows whether every invoice made it into the accounts once, at the right amount.
• The other party's record of the same invoice. The customer's list of what it owes you, or the supplier's list of what you owe. This shows whether both sides agree on what exists.

To pick one, ask what decision the reconciliation has to support, and which record would prove an invoice wrong for that decision. If you are about to pay a supplier, the risk is paying for something never ordered or received, so the order and receipt are the counterparts. If you are closing a month, the risk is invoices missing from the books, so the ledger is the counterpart. If a customer says it owes less than you think, the counterpart is the customer's own record. The other counterparts don't answer that question, so leave them out of this run.

Direction matters too. For invoices you issued, you control the numbering, and the main risk is work delivered but never billed. For invoices you received, the supplier controls the numbering, and the main risks are invoices that never reached your books and invoices recorded twice. Who can fix an exception also differs: you correct your own billing, but only the supplier can correct its invoice.

Some neighboring exercises have their own guides: matching supplier invoices to purchase orders and receiving documents (two-way and three-way matching), matching bank-feed items to records in your software, and tying a periodic statement of account to your books.

What shape does every invoice reconciliation take?

Every version has four parts, whichever counterpart you picked:

1. Two defined populations. Population A is your invoices, for example every invoice issued with a date from June 1 to June 30. Population B is the counterpart records, with a cut-off that makes the two comparable. The cut-off date marks where transactions start being recorded in the next period, so both populations need boundaries you can state.
2. A stated match key. The field or combination of fields that says record A and record B describe the same invoice.
3. The match. Pair every record you can.
4. A classified residual on each side. What is left in A with no partner, and what is left in B with no partner. Each leftover is a reconciling item.

A residual exists on both sides. A B-side item with no invoice (a shipment never billed, a payment with no invoice) matters as much as an invoice with no counterpart.

Two totals that agree do not make the reconciliation complete. An invoice missing on one side and an unrelated extra entry can cancel out, leaving both records wrong. The job is done when the residual list is empty or every item on it is classified and resolved.

What should the set-up checklist contain?

Write this down before you match anything:

• Population A: the source (billing system export, sales ledger, supplier invoice folder), the date field used (invoice date, entry date) and the date range.
• Population B: the source and date range, plus the cut-off field and how it lines up with A's.
• Control totals: the record count and total value of each population as extracted, so you can later show nothing was dropped.
• Match key: the primary key, the fallback keys in order, and how each field is normalized.
• Tolerance: the largest amount difference you will accept on a matched pair (for example 0.05 for rounding), and a note that every pair inside the tolerance will still be listed and reviewed.
• Residual categories: timing, missing from one record, same invoice under a different identifier, should not exist, duplicate. Each item left over must be cleared into one of these before you finish.
• Owner and date: who prepared the reconciliation, who reviews it, and when.

How do you choose a match key when the records share no identifier?

Most small-business records share no single clean identifier. A supplier's invoice number sits on the supplier's document but may be keyed differently in your books. Your order number may not be on the delivery note. Rank the candidate fields by how reliable they are:

1. The document number assigned by the issuer, normalized. Invoice numbers are the main identifier for supplier invoices, and accounting software uses them to flag invoices it has already recorded. Normalize them first: strip leading zeros, dashes, spaces and other punctuation on both sides. Drop a prefix only when it carries no meaning; never drop one that distinguishes document types, such as an invoice from a credit memo.
2. A reference the other party quoted back to you. Your order number or customer reference printed on its document.
3. Counterparty plus date plus amount. Useful as a compound key, but dates drift. Invoice date, dispatch date and entry date can all differ by days.
4. Amount alone. Never use amount alone as a key. Identical amounts repeat across invoices and customers, and a false pair hides two real exceptions at once.

If no single field is reliable, match in passes. First, match exactly on normalized invoice number plus counterparty. Then match unpaired records on counterparty plus amount within a date window, such as 7 days. Then list what is still left for review by hand. Record which pass paired each item. Anything paired in a looser pass gets a second look.

When an invoice arrives with no number at all, set a rule for building one, such as the invoice date or the packing slip number. That way, anyone entering the invoice derives the same number, and the invoice is less likely to be entered twice.

How do you prove that no invoice is missing?

A match only covers the records you started with. If population A is just the invoices you already know about, a missing invoice can never show up. Completeness is tested by direction. Test in both directions: from source documents forward into the records (catches what was never recorded) and from the records back to the documents (catches what should not be there).

For invoices you issued:

• Sequence check. Sort by invoice number and list every gap. Gaps in invoice numbers are a known warning sign in billing. Each gap needs an explanation: a voided invoice kept on file, a number skipped by the system, or an invoice missing from the extract. The limit: a sequence check only proves that numbered invoices are all accounted for. It cannot detect work that was never invoiced at all.
• Trace from delivery. Match billings to the shipping log or job records. Items can ship without an invoice, and invoices can be raised with no shipment. This is the test that catches unbilled work.

For invoices you received:

• No sequence to test. Supplier numbers belong to the supplier, and you only see some of them.
• Trace from the inflows. Start from everything that could produce an invoice: the invoices mailbox, receiving records, contracts and recurring services. Confirm each one reached the ledger. A recurring service with no invoice this month is a candidate missing invoice.

Cut-off, for both directions. Look at the records a few days either side of the boundary. For invoices you issued, compare invoice dates with shipment dates to check each sale landed in the right period. For invoices you received, compare the receiving date or service period with the date the invoice was entered. The limit: a cut-off check covers the boundary, not the middle of the period.

What must agree inside a matched invoice?

A matched pair still needs checking. Compare the parts of the invoice, not just the total:

The same small difference turning up across many invoices is a finding, such as a recurring charge, a rounding rule or an unclaimed discount.

How do you catch duplicates without deleting real repeat invoices?

Duplicates are the exception that costs money directly. There are three kinds:

• Same number, entered twice. A computerized payables system searches for duplicate invoice numbers automatically and catches this if the numbers were entered identically, but check that yours does and that the warning is on. If you work from a spreadsheet or paper, no system is searching for you, and a manual duplicate search is much harder: sort by counterparty and invoice number and look for repeats.
• Same invoice, different number format. For example 0000078234 and 78234. Normalizing the number, as described above, exposes these.
• Same invoice, different document. A copy sent by email and later by post, a pro forma followed by the final invoice, or an invoice re-issued after a dispute. To find these, group by counterparty and amount within a date window, then compare line detail.

A monthly service fee is a real repeat: same supplier, same amount, every month. To tell a repeat from a duplicate, check the service or delivery period and the underlying order or receipt. Two invoices for the same period or the same delivery are duplicates. Two invoices for different periods, each with its own delivery, are repeats. Never delete a suspected duplicate from the record. Mark it, keep both documents, and resolve it with the issuer.

How do credit memos, adjustments and cancelled invoices change what should match?

These break the one-invoice-to-one-record assumption. Handle them before you classify anything:

• Credit memos (also called credit notes). A credit memo reduces what the buyer owes under an earlier invoice. It may be issued for returned goods or to correct a billing error. Match each credit memo to the invoice it reduces, and compare the net amount. An invoice that shows as short-paid may be fully settled once its credit memo is counted.
• Credit memos after the cut-off. Check credit memos issued just after the period end to see whether they relate to invoices inside the period. If they do, the invoice amount in your reconciliation may be overstated.
• Cancelled or voided invoices. A voided invoice should have no delivery, payment or ledger balance behind it. Keep it in population A, mark it as void, and expect no match. That way, it explains its sequence gap and doesn't show up as an exception.
• Adjustments. A price change or a re-bill should point to the original invoice. If it doesn't, find the original and link the two before matching.

Is an unmatched invoice a timing difference or an error?

An unmatched item is one of four things. They look the same in a residual list but call for opposite corrections:

1. Timing. The partner exists but falls on the other side of the cut-off. Timing differences are temporary reconciling items that clear on their own in a later period.
2. Recorded in one record and never in the other. An error of omission. Permanent reconciling items come from recording errors or omissions, and they need a correcting entry.
3. The same invoice under a different identifier. A key failure, not a real difference. Link the two and re-run the check.
4. An invoice that should not exist in either record. A charge for something never ordered or delivered, or an invoice raised by mistake. Resolve it with the issuer. Don't record it and don't pay it.

A duplicate is a special case of the fourth: the second copy should not exist; test it as described in the duplicates section.

How to decide which one. First search the other side's residual for the same counterparty and amount, or the same line detail, under another number. If you find it, it is the same invoice under a different identifier: link the pair and stop. Only then look past the cut-off. If the partner appears in the next period's records, with dates that explain the gap (dispatched after the billing run, or received after the month closed), the item is timing. Check that it actually clears, and treat it as an error if it doesn't. If no partner exists on either side of the cut-off, go to independent evidence of the underlying event: was there a valid, uncancelled order or agreement, and did the goods or service actually move (delivery note, receiving record, timesheet)? If the event happened, the item was omitted from the other record. If the order was cancelled or nothing was delivered, the invoice should not exist.

What does a worked example look like?

Suppose a wholesaler reconciles June's issued invoices (population A: invoice date June 1–30) against the June shipping log (population B: dispatch date June 1–30). The match key is the order number printed on both, with customer plus amount within 7 days as a fallback.

Classifying SH-593: July's register shows INV-1048, dated July 1, order 5518, 960.00. The shipment left after the June 30 billing run. The partner exists just past the cut-off and the dates explain the gap, so this is timing. Note the July invoice number on the reconciliation. It is timing for this match, but it is also a cut-off exception: goods left on June 30 and were billed in July, so June sales may be short by 960.00. List it for whoever closes June to decide whether the sale belongs in June; do not treat it as cleared until that is answered.

Classifying INV-1044: there is no shipment in June or July. The order file shows order 5513 was cancelled before picking. The invoice should not exist. This is an error, fixed with a credit memo against INV-1044, not by waiting.

The totals show why totals are not enough. Population A had 800.00 with no shipment and population B had 960.00 with no invoice. The June totals differ by only 160.00, which looks like one small problem when there are actually two unrelated items behind it.

What changes when the other record belongs to a customer or supplier?

When population B is the other party's record, you can't clear an exception on your own. For each exception, send the other party the invoice number, date, amount, how it appears in your record, and the document that supports your side. Ask for their document in return: their copy, a proof of delivery, or a remittance.

Until it is resolved, change only what your own evidence supports. Reconciliation adjustments bring the records into line with the supporting evidence, not with the other party's list. Don't book a supplier's invoice just because it appears on the supplier's list. Don't drop one of your invoices just because a customer doesn't have it. Either change could accept a debt that was never owed or discard proof of one that was.

How do you run it on thousands of exported invoices?

The method stays the same. The checks move from the eye into the data:

• Before matching, check each extract's record count and total against the source system. Exports get cut off by row limits, filters and date formats.
• Normalize keys in a separate column and keep the original value. Test for duplicates on the normalized key.
• Check that nothing is paired twice. If one shipment or payment pairs with two invoices, one of those pairs is false.
• Review the tolerance band as a list, sorted by the size of the difference and grouped by counterparty.
• Take a sample of matched pairs and read the documents, because nobody reads the documents one by one at this volume.

What should you leave behind when you finish?

Someone who didn't do the work should be able to follow it without redoing the match. Keep:

• The set-up checklist, with the extracts and their control totals.
• The matched list, showing the key or pass that paired each item.
• The residual list, with each item's category, the evidence that settled it, the action taken (credit memo, correcting entry, query to the other party) and the date it cleared.
• Timing items carried forward, so next period's reconciliation starts by confirming they cleared.
• The preparer's and reviewer's names and dates.

As a routine control, the populations, sources, keys, tolerance and categories are set once. Each period you repeat the extract, the match, the classification and the carry-forward. When a reconciliation is prompted by a dispute, a balance that looks wrong or a payment decision, limit it to the counterparty or balance in question. Resolve the items that bear on the payment or the amount in dispute before you pay or agree to it. Invoices that matched and are not in question are not held up by this exercise.