Skip to content

How the software matches feed lines to records

Up to date as of November 20, 2026

The software doesn't know a bank line is your invoice. It compares a few facts about the line with the records you've already entered and offers the ones that fit. You make the final call.

How a suggestion is madeBank line arrivesCompare amount, date, referenceOffer candidate recordsYou accept or pick another
The software compares fields on a bank line with open records, then offers candidates.

What it compares

One accounting manual tells users to compare amount, date, reference, party and description when looking for a match.1 In plain terms:

  • Amount. A deposit of the same value as an open invoice is a likely pair.
  • Reference. A check number, invoice number or payment reference that appears in both places.
  • Date. Close dates point to a pair, but dates can differ, as the section on timing below explains.
  • Party. The customer or supplier named on the record, if the bank line names them.
  • Description. Free text from the bank, which varies a lot.

Programs differ in which fields they use. Your own help pages say which fields yours uses.

A narrow rule that shows the idea

One manual documents an automatic option that matches a bank transaction only with an entry whose reference number is the same as the transaction's reference number.2 It adds that entries with a different or empty reference must be matched by hand.2

That's a strict method. It leaves anything without a reference for you to match yourself. Other programs may use looser methods, so check how yours works.

Where matches go wrong

Timing. A customer pays on one day, and the bank posts it on another. The same manual suggests widening the matching date range when settlement dates differ.2

Combined deposits. One deposit can cover several invoices. The bank transaction manual says one deposit may cover several sales invoices after fees and refunds.1 The line then matches several records, or none that equal it. A card processor payout is a common case.

Fees taken out. A customer owes a certain amount, but the bank shows a lower one because a fee came off. The amounts no longer agree, so no automatic match appears.

Reused or vague descriptions. If three different customers send the same amount, the description may be your only clue. Don't edit the bank's wording to make it fit. The manual says not to overwrite the bank's description merely to make matching easier.1

Duplicates. The manual suggests comparing transaction ID, reference, date, amount and source file to spot a line that appeared twice.1

What to check before you accept

A suggestion is a guess with good odds. Before you accept it:

  1. Check the amount to the cent.
  2. Check the name matches the right customer or supplier.
  3. Check the record isn't already matched to another bank line.
  4. Check the currency, if you use more than one.

The manual's checklist for a line with no suggestion is similar: verify the amount, date, currency, reference number and bank account.2

When nothing matches

Then you have a decision to make. Either the record is missing, or the line is something new such as a fee. Search for the record first, as the step-by-step page advises.

If you've lost track of a whole period, you may have to match the lines one by one.3

For lines that always look the same, such as a monthly fee, a bank rule can categorize them without matching.

Notes and sources

  1. Bank Transaction, ERPNext Documentation
  2. Bank Reconciliation, ERPNext Documentation
  3. Reconciliation (accounting), Wikipedia