The smallest hidden enemy of any finance operation is disconnected data. A payment lands on the bank statement but never shows up in the ledger. An e-invoice is registered in the GİB (Turkish Revenue Administration) system but has no counterpart on the bank side. A ledger entry exists but cannot be tied to any real bank movement. Three sources, three different versions of the truth.
Three-way reconciliation was born to close exactly that gap.
What do the three sources stand for?
Source one — the bank statement. The money movements that actually happened in your company. Pulled via API or as .xlsx/.mt940 files. Did money come in or go out, to whom, and when — concrete facts.
Source two — e-invoice / e-archive. Commercial documents officially registered for tax purposes in the GİB system. They establish the invoice's existence, its amount, and the taxpayer details. Paid or still pending — that, they do not tell you.
Source three — the ledger entry (your accounting system). The truth your company's books accept. The records kept in your ERP, your accounting firm's software, or your accounting package.
If one of these three sources is missing, your financials are never the real picture. If all three don't agree, you are not audit-ready.
Classic manual reconciliation and its limits
In the traditional approach, each source is exported to Excel as a separate sheet. Then you try to match one against the other:
- You hunt for the bank line in the e-invoice list
- If the description carries no customer name, you guess by hand
- If the ledger line is missing, you add it by hand
This process takes one hour for 50 rows in a single sheet and a week for 5,000 rows. And because human attention has limits, the error rate sits in the 5-10% range.
Why Excel is not the answer
Three-way reconciliation done in Excel breaks down at three points:
1. Matching rules are static. Single-layer rules like "match if the description contains a reference" cannot do fuzzy name matching. 2. No trail of past mistakes. Once a decision is made, there is no answer to "why did I make this match?" 3. The audit trail is manual. Every change lives in yet another Excel version; "who changed what, when, and why" gets lost.
The anatomy of modern three-way reconciliation
iFinances' Reconciliation module brings the three sources together in a single layer of intelligence. Here is how it works:
Step 1 — All sources are normalized. Bank API, e-invoice webhook, and ERP polling are converted into one data shape. Customer names are standardized and amounts are converted to TL (using the CBRT (Central Bank of Türkiye) rate — see the CBRT official rate guide).
Step 2 — The 6-layer matching engine runs. In order:
- Exact amount + date match
- Reference number match (e-invoice number, ETN, payment description)
- Fuzzy name matching (the customer name may be spelled differently at the bank)
- Amount + date window (±3 days)
- ML patterns (patterns learned from historical matching data)
- Manual suggestion (matches below high confidence are queued for user approval)
Step 3 — Every decision rests on a reason. Each match is logged with a justification: "These two records matched because the amounts are identical + the reference is a 95% fuzzy hit + same-day dates." When audit season arrives, the auditor can read that trail in a single click.
A modern reconciliation engine is not a black box — it is explainable AI. For the full picture, read the explainable AI guide.
Three practical wins
1. Month-end close drops from 3 days to 4 hours. With an automatic match rate of 94%+, there are hardly any rows left for the team to review by hand.
2. Missing invoices and duplicate entries become visible. The anomaly detection module flags cases where a bank movement exists but no e-invoice does — that is lost revenue.
3. The audit team's answer to the one question is ready. "Why did this invoice match this payment?" gets answered in 15 seconds.
What company size is it right for?
Three-way reconciliation makes economic sense for any company generating 500+ invoices or transactions a month. The SME-scale starter plan is detailed on the iFinances pricing page.
Conclusion
Bank, e-invoice, and ledger — when these three sources confirm one another, your finances are safe. When they don't, an invisible friction slows down every financial decision the company makes.
Modern three-way reconciliation cuts that friction to zero. To put it to the test, request a demo — in a 30-minute demo, your own three sources connect to our system and the results appear instantly.
Frequently Asked Questions
What is three-way reconciliation?
Three-way reconciliation means checking the same transaction against three independent sources side by side: the bank statement, the e-invoice record, and the ledger entry in your accounting system. The bank proves the money actually moved, the e-invoice proves the document formally exists, and the ledger shows what your books accept. When all three confirm each other the figure is trustworthy; when one is missing or they disagree, you are usually looking at an uncollected receivable, an unrecorded payment, or a movement with no supporting document.
What does cross-source reconciliation mean?
Cross-source reconciliation is the practice of confirming that a financial transaction appears the same way in more than one independent record. Unlike counterparty reconciliation, where you compare balances with a trading partner, cross-source reconciliation compares your own systems against each other: bank, e-invoice, and ledger. Independent sources corroborating one another produce stronger evidence than any single system alone, which is why audit standards also treat evidence from independent sources outside the entity as more reliable.
How do you compare bank, e-invoice, and ledger records?
In three steps: normalise the sources, match the records, then investigate whatever is left over. Normalising means standardising company names and converting foreign-currency amounts at the official Central Bank of Türkiye rate so the three sources become comparable; matching then runs on amount, date, reference number (invoice number or payment description), and name similarity. The unmatched rows are where the real findings sit — a collection with no invoice behind it, an invoice that was never paid, a movement that never reached the ledger. iFinances consolidates the three sources into a single table and records the rule behind each match.
Can you do three-way reconciliation in Excel?
You can, but it breaks down on volume in three places. Spreadsheet matching rules are static, so they cannot recognise the same customer written differently on the bank side or match on similarity rather than exact text. The reasoning behind a decision is never stored either, so months later there is no answer to why two records were matched. And the change history scatters across saved versions of the file, which turns the audit trail into manual work.
Are Ba-Bs forms still required in Türkiye?
No. Form Ba and Form Bs — the monthly declarations of purchases and sales that Turkish taxpayers used to file, which the tax administration cross-checked against each other — were abolished by General Communiqué No. 565 on the Tax Procedure Law, published in the Official Gazette of 25 September 2024 (issue 32673), starting with the September 2024 period and effective from 1 October 2024. The stated reason was the spread of e-document systems, which lowers compliance costs because the underlying records are already available electronically. In practice, cross-checking purchases and sales is now something companies do inside their own data — bank, e-invoice, and ledger — rather than through a mandatory filing.
