How to set up daily reconciliation: bank, e-Invoice and ERP

· Panda Yazılım

Daily reconciliation means matching bank movements, e-invoices and ERP records every day, without waiting for month-end. You write the rule once, matched items close, unmatched ones fall onto an exception list and someone resolves them. At month-end you are left with that day's few exceptions, not hundreds of lines. The agent reads and matches; a person approves the closing.

Why every day instead of month-end?

When a difference is found at month-end reconciliation, it is hard to remember the cause. The amount may be left over from the start of the month, a collection may have been posted to the wrong customer/supplier account, an invoice may not have been recorded yet. Looked at the same day, the person involved still remembers and the document is at hand.

Look at it in process time: if two people reconcile for two days each month, 8 hours a day, that is 32 person-hours a month and 384 person-hours a year. Daily matching does not divide or remove this load; but the one big job that piles up at month-end becomes small jobs of a few minutes each day.

Which three sources are matched?

Reconciliation links three sources to each other. The bank statement shows what the money actually did. The e-Invoice shows the official amount you agreed with the other party. The ERP holds your own records.

  • Bank: collection, payment, expense and commission movements
  • e-Invoice: outgoing and incoming invoices, returns
  • ERP: customer/supplier account movements, open items, payment and collection records

All three must be current within the same day. Pulling the bank statement automatically every morning, pulling e-Invoices from the integrator and reading the ERP directly are preconditions of the daily flow.

How are matching rules written?

Order the rules from the most certain to the least certain. Each rule has a confidence level; high-confidence ones close automatically, low-confidence ones go to a person.

  • Exact: amount, account and invoice number are the same. If the invoice number appears in the description field, it is the safest match.
  • Amount and account: no number in the description, but amount and sender are the same. The account name may be abbreviated at the bank; keep that in a mapping table.
  • One payment, several invoices: the total equals the sum of several open invoices.
  • One invoice, several payments: a partial payment or instalments.
  • Commission and expense: movements whose amount fits the expected commission rate go to the relevant expense account.

Documenting the rules is important. Why a match was made must be readable afterwards; the accountant and the auditor should be able to see the answer to the same question.

The biggest trap in writing matching rules is a single payment closing several invoices. Customers often pay three invoices with one transfer and write only one number in the description. Only a rule that looks at the sum of open items catches such a movement; restricting that rule to a subset (for example only overdue invoices of the same customer/supplier account) reduces the risk of a wrong match.

How are tolerance and the exception list determined?

Not every difference is an error. Exchange-rate differences, rounding, bank charges and small cent differences happen in real life. Define a tolerance for them; but set the tolerance yourself, do not take an estimated figure as given. It is safer to separate the tolerance both by amount and by account type.

  • A difference within tolerance closes automatically and shows in a separate account.
  • A difference outside tolerance falls onto the exception list.
  • An unmatched bank movement (money whose sender is unknown) goes to the top of the exception list.
  • Open items that have an invoice but no visible payment are sorted by due date.

The exception list is the day's work. Every exception should have an owner, a reason and a closing date. If the same reason repeats (for example a certain customer always pays with no description), update the rule.

How are agent automation and human approval balanced?

This job suits an AI agent, because the inputs are irregular: bank descriptions are free text, account names are written differently, PDF attachments arrive. The agent reads the statement and invoices, matches them by the rules and writes the reason. If it is unsure about a match, it asks a person.

Human approval stands at the critical point. For high-confidence exact matches you can give approval in bulk; uncertain ones you see one by one. The agent writes a closing proposal to the ERP and the person who approves makes the entry. The team does not shrink; its work changes: instead of matching line by line, it resolves exceptions.

  • The agent shows what it matched on; the evidence line stays in the record.
  • Who holds approval authority is written down; you can set an amount limit.
  • When the agent's wrong match is corrected, the rule or the mapping table is updated.
  • Data stays in the company's own environment; you decide which sources are read.

Which errors does daily reconciliation catch early?

A difference that waits until month-end is often one error with other errors piled on top. Looked at daily, errors are caught while they are small. Some of the common ones:

  • A collection posted to the wrong customer/supplier account: the bank movement exists but it was written to another customer's account.
  • An invoice paid twice: same amount and same counterparty, on two separate days.
  • A forgotten expense: it left the bank but has no counterpart in the ERP.
  • A payment made against a cancelled or returned invoice.
  • The other party paying the wrong amount: money arriving short or over.

When each of these is found late at month-end, it means correspondence with the customer, hunting for bank receipts and a correcting entry. In a daily flow the same error is usually resolved with a single phone call.

Whose job is reconciliation?

If daily reconciliation is tied to one person, the process stops when that person goes on leave. Instead, separate the roles: one resolves the exception list, another gives approval, a third reviews the weekly summary. In a small company these three roles may fall to two people; but the person who approves and the person who matches should not be the same.

When working with an agent, reconciliation has one more feature: lasting improvement comes from your corrections. When you reject the agent's wrong suggestion, write the reason briefly. Add this note to the relevant rule or mapping table; at month-end these notes become your reconciliation handbook.

There is one more point to watch on the bank side: the date on the statement and the value date can differ. Transactions made on weekends and holidays appear on the statement on the next business day. If your rule does not know this difference, it shows a payment that is actually correct as unmatched. In matching, define the date as a short range instead of a single day.

How do you start in the first week?

Start with a single bank account and a single month of data. Put your manual matching and the agent's or the rule's matching side by side. The lines with differences show where your rules are lacking. Once trust is built, add the second account and the customer/supplier account cards.

Fix the daily routine too: the statement is pulled in the morning, the rules run, the exception list goes to one person, and by the end of the day the list is empty or the reason for carried-over items is written. Month-end close becomes the last day of this list.

Frequently asked questions

What data is needed for daily reconciliation?

The bank statement (automatic or as a file), the e-Invoice list and the customer/supplier account movements in the ERP are enough. Pulling the statement fresh every morning and having the correct tax number on account cards affect matching success the most.

What happens if the agent matches wrongly?

The agent prepares the closing as a proposal, and the entry goes in with human approval. A wrong match is caught at the approval stage and the correction is reflected in the rule or mapping table. That is why the agent also writes its reason for the match.

Is reconciliation only for large companies?

No. Daily matching pays off as soon as the number of bank movements and invoices makes manual tracking hard. A small company starts with fewer rules and a single account; the setup is kept small accordingly.