In Türkiye, companies above a certain revenue threshold have been required to use e-invoicing since 2014. As of 2026 the threshold has dropped even further — even small businesses now have to switch to e-invoices. It has become the standard for digital accounting.
But here is the reality: issuing an e-invoice is not the end of the job. Did the other party actually receive it, accept it, pay it — every link in that chain needs to be verified through reconciliation.
Inbound vs outbound e-invoices: the basic distinction
Outbound e-invoice: The invoice you issue to your customer. It lands in the system of GİB (the Turkish Revenue Administration) and is delivered to the customer. For you, it is a revenue or receivable item.
Inbound e-invoice: An invoice that arrives from your supplier. It passes through GİB and lands in your system. For you, it is an expense or payable item.
The two directions mean different accounting flows, different VAT (KDV) logic, different due-date tracking. Managing them in a single system is critical.
The 7 statuses of every e-invoice
Over its lifecycle, an e-invoice can be in 7 different statuses:
| Status | Meaning | |---|---| | 1. Draft | Created in the system, not yet sent | | 2. Sent | Landed in the GİB system | | 3. Delivered | Reached the recipient's system | | 4. Accepted | The recipient accepted it | | 5. Rejected | The recipient rejected it (mismatch, error) | | 6. Paid | Payment cleared on the bank side | | 7. Canceled/returned | Canceled after the fact |
A modern reconciliation system must track all seven statuses automatically — manual tracking simply stops being feasible beyond 100+ invoices.
The critical items in status tracking
Rejected e-invoices (status 5)
If an e-invoice has been rejected:
- What is the reason? (wrong tax ID, amount error, wrong invoice type)
- Can it be corrected and resent?
- If it isn't corrected, how should it be handled in the books?
What automation does: Flags every rejected invoice with a risk score and prioritizes it through the anomaly detection module.
Late-paid e-invoices (a long gap between status 4 and 6)
An invoice was issued and accepted, but 60 days have passed and it still hasn't been paid.
What automation does: Runs aging analysis, builds customer segmentation ("this customer consistently pays late"), and recommends collection actions.
Missing matches (status 6 but no bank transaction)
An invoice was marked as paid, but there is no corresponding entry in the bank statement. This could be a duplicate payment or a mislabeled record.
What automation does: Catches this disconnect through three-way reconciliation.
The technical anatomy of e-invoice reconciliation
1. Data flow
Outbound side: `` Company ERP/Software → e-Invoice Integrator → GİB Portal → Buyer's System ↓ Ledger Entry (automatic)
Inbound side: `` Supplier → GİB Portal → Your Integrator → Your System ↓ Ledger Entry (automatic or after approval)
2. Automatic categorization
When an inbound e-invoice arrives, the system needs to determine:
- Which account code does it belong to? (automatic categorization)
- Was the correct VAT rate applied?
- Does withholding tax need to be deducted?
- Is it an expense or an investment?
- Should it enter an approval workflow?
A good system learns from historical patterns and suggests the most appropriate category for each new invoice.
3. Matching — bank against invoice
Was the invoice paid? Which bank transaction does it match? This matching should be automatic — powered by a 6-layer matching engine.
4. VAT reconciliation
Critical at the monthly VAT return close:
- Total outbound e-invoices vs total sales in the ledger
- Total inbound e-invoices vs total expenses in the ledger
- Consistency with the totals on the BA-BS forms (Türkiye's mandatory monthly purchase/sales declarations)
For the detailed process, read the e-reconciliation and GİB requirements guide.
The 5 layers of full automation
A modern e-invoice reconciliation system includes these 5 layers:
Layer 1 — GİB integration Native GİB Portal connectivity plus the major integrators (Logo, Mikro, Paraşüt, Foriba, Sovos).
Layer 2 — Status tracking Automatic monitoring of all 7 statuses, with notifications on every status change.
Layer 3 — Smart categorization ML-driven account code suggestions, VAT and withholding tax checks.
Layer 4 — Bank matching Payment verification through three-way reconciliation.
Layer 5 — Tax reconciliation VAT return consistency, automatic BA-BS generation, audit-ready reporting (see the audit-ready guide).
The limits of the classic manual process
Manual e-invoice reconciliation is doable at small scale (50-100 invoices a month). At 500+ invoices a month, the math works like this:
- An average of 2 minutes of tracking per invoice
- 500 invoices = 1,000 minutes = 16 hours / month
- Annually: 200 hours of team capacity
- Error rate: 3-5%, driven by the limits of human attention
With automation:
- Automatic tracking + ML categorization = 2 hours/month of manual review
- Error rate below 0.5%
Which companies are required to use it?
The GİB e-invoice mandate keeps expanding as the revenue threshold is updated each year. As of 2026, it covers:
- Companies with annual revenue above 3 million TL
- Companies selling through e-commerce
- Companies doing business with the public sector (via KİK, Türkiye's public procurement framework)
Companies below the threshold are not required to switch, but the customer chain can make it unavoidable — if a major customer of yours uses e-invoicing, you will need to start using it too.
Choosing the right infrastructure for e-invoice reconciliation
Choosing the right software comes down to 7 criteria. The detailed guide: Reconciliation software selection guide.
The key questions:
- Is the GİB integration native?
- Does it support multiple integrators? (for the flexibility to switch providers)
- Is status tracking automatic?
- Is there ML categorization?
- Does it generate VAT/BA-BS reports automatically?
Conclusion
E-invoice reconciliation is the backbone of modern Turkish accounting. Done manually, it caps your capacity; automated, it transforms your company's financial visibility.
The iFinances Reconciliation module manages inbound and outbound e-invoices from a single panel, tracks all 7 statuses automatically, matches them against bank statements, and generates VAT/BA-BS reports automatically.
Request a demo or explore the pricing plans.
Frequently Asked Questions
How do you reconcile e-invoices?
E-invoice reconciliation starts by treating inbound and outbound flows separately and comparing the invoice list held by your integrator or the GİB portal (Türkiye's Revenue Administration) against your own ledger, matching on invoice number, tax ID, date and amount. The second step is to classify the mismatches: invoices in your books that the counterparty does not show, invoices sitting in your inbox that were never posted, and invoices that were rejected or cancelled. The third step links the matched invoices to bank movements and payment records, and whatever difference remains is confirmed with the counterparty through a reconciliation letter. iFinances runs these three steps in one panel and shows the reasoning behind every match.
What is the difference between inbound and outbound e-invoices?
An outbound e-invoice is the one you issue to your customer, while an inbound e-invoice is the one your supplier issues to you; the first feeds revenue and receivables, the second feeds expenses and payables. The difference is not only direction: the two sides carry different VAT logic, different approval flows and different due-date tracking. On the outbound side you verify that the invoice reached the buyer and was accepted; on the inbound side you verify that it was posted to the right account code with the right VAT rate.
Do e-archive invoices need to be reconciled?
Yes. An e-Arşiv (e-archive) invoice is the electronic invoice issued to buyers who are not registered e-Fatura users in Türkiye, and it belongs in the same reconciliation list as your e-Fatura volume. The difference is that there is no accept-or-reject response cycle on the buyer's side, so these invoices are tracked through collection and ledger entries rather than through status changes. The scope is also widening: from 1 January 2026, taxpayers outside the e-Fatura and e-Arşiv systems (other than those taxed on the simplified or business-account basis) must issue every invoice as an e-Arşiv invoice regardless of amount.
What is e-invoice status tracking?
E-invoice status tracking means continuously monitoring which stage an invoice is in: draft, sent, delivered, accepted, rejected, paid, or cancelled and returned. Three of those states matter most for reconciliation: rejected invoices (why, and whether they will be corrected and reissued), invoices accepted long ago but still unpaid, and invoices marked paid that have no matching entry on the bank statement. As volume grows this becomes impossible to keep up manually, because the problem lives in the gaps between lists rather than in any single invoice. iFinances follows status changes and flags paid-but-unmatched items as anomalies.
How do you reconcile e-invoices with the VAT return?
At period close you compare total outbound e-invoices against recorded sales and total inbound e-invoices against recorded purchases and expenses; the gap usually comes from invoices never posted, posted twice, or rejected and cancelled but never removed from the list. In Türkiye this cross-check is now made directly against e-document and ledger data: the Form Ba and Form Bs monthly declarations were abolished by General Communiqué No. 565 of the Tax Procedure Law, published in the Official Gazette on 25 September 2024 and effective from the September 2024 period onwards. Aligning your e-document, ledger and bank lists for the same period before filing removes most of the corrections that would otherwise surface later.
