E-reconciliation digital documentation — tax and invoice records
Insights
Regulation

What is e-reconciliation? GİB requirements, BA-BS forms, and a process guide

iFinances EditorialApril 08, 202610 min

The Turkish regulatory requirements behind e-reconciliation, the role of the BA-BS form, what GİB expects, and a step-by-step guide to getting your company compliant.

In Türkiye, the word "reconciliation" means different things in different contexts. To an ERP user it means bank reconciliation; to an accountant, account reconciliation; to a CFO, customer/supplier reconciliation. In recent years, though, they have all converged under a single umbrella: e-reconciliation.

E-reconciliation is the process of verifying financial records digitally, against electronic sources. It is the modern successor to classic paper-based reconciliation.

The 4 types of e-reconciliation

1. Bank reconciliation

Agreement between the company ledger and the bank statement. Does every bank transaction have a counterpart in the ledger? Missing entries, duplicate entries, and FX-difference items are checked.

2. Account reconciliation (customer/supplier)

The receivables balance between your company and the counterparty (customer or supplier) is verified. You ask the other side to confirm: "we have a receivable of X TL from you." In Türkiye this is mandatory at year-end (under BDS, the Turkish independent auditing standards).

3. E-invoice reconciliation

Agreement between the e-invoices your company issues and the e-invoices that land on the counterparty's side. For a detailed guide, read our e-invoice reconciliation article.

4. BA-BS reconciliation (VAT reconciliation)

Form BA (the statement of goods and services purchased) and Form BS (the statement of goods and services sold) — monthly filings mandated by GİB (the Turkish Revenue Administration). Your BA-BS filings must be consistent with the counterparty's.

What is the BA-BS form, and why does it matter?

The BA-BS filing has been in force since 2007, mandated by GİB. It rests on one principle:

The amount a company reports as a purchase must equal the amount the selling party reports as a sale.

When they don't match, a discrepancy surfaces — and the tax office may open an investigation.

What Form BA contains

  • Who you purchased from (tax ID, legal name)
  • For what amounts (VAT inclusive/exclusive)
  • In which month

What Form BS contains

  • Who you sold to (tax ID, legal name)
  • For what amounts
  • In which month

It is mandatory for every transaction that exceeds the 5,000 TL monthly threshold — filings are due by the 25th of each month.

The 3-layer architecture of e-reconciliation

Layer 1 — Data collection

Every source flows into a single pool:

  • Bank statements via bank APIs or .xlsx/.mt940 files
  • E-invoices via the GİB Portal or an integrator
  • Ledger system (ERP, accounting software) integration
  • Counterparty statements (where shared)

Layer 2 — Matching + consistency checks

The sources are compared against one another:

  • Bank → ledger (bank reconciliation)
  • E-invoice → ledger (VAT reconciliation)
  • Ledger → BA-BS filing (tax reconciliation)
  • Counterparty statement → company records (account reconciliation)

For detailed three-way cross-reconciliation, read this guide.

Layer 3 — Reporting discrepancies

Deviations fall into three classes:

  • Missing entry — present in one source, absent in the other
  • Amount difference — the same transaction recorded at different amounts
  • Date difference — the same transaction recorded on different dates

Each deviation is prioritized with a risk score (details: anomaly detection guide).

The monthly e-reconciliation workflow

An ideal e-reconciliation month flows like this:

Throughout the month (automated):

  • Bank statements are pulled daily
  • E-invoices land as they arrive
  • Automatic matching runs in the background

The 10th (manual approval):

  • Low-confidence matches go to the team for approval
  • Anomalies are reviewed by risk score

The 20th (counterparty account reconciliation):

  • Account reconciliation forms go out to major customers/suppliers
  • Confirmations and objections are put on record

The 25th (BA-BS filing):

  • The auto-generated BA-BS draft is reviewed
  • Submitted to the GİB Portal
  • Cross-checked against counterparty filings

Month-end (close):

  • VAT return
  • Monthly financial reports
  • Audit-ready file update
Done manually, this process consumes 40% of the team's time. With e-reconciliation automation, it drops to 5%.

Questions to ask when choosing e-reconciliation software

1. Is the GİB integration native? Are e-invoice, e-Arşiv (e-archive invoicing), and BA-BS automated? 2. How many banks does the bank API cover? It should include at least the 7 major Turkish banks (Garanti, İşbank, Akbank, Yapı Kredi, Ziraat, Halkbank, QNB). 3. Are account reconciliation forms generated automatically? As PDFs or e-signed documents? 4. Is there an audit trail? Which user gave which approval, and what was decided on each deviation? 5. Does it support multiple currencies? Automatic official CBRT (Central Bank of Türkiye) rates (see the CBRT guide)? 6. Does it integrate with accounting firms? Can multiple companies be managed from a single panel? (see the accounting firm portfolio guide) 7. Does it offer audit-ready reporting? (see staying ready for KGK (Turkish Public Oversight Authority) audits)

Recommendations by company size

SME (1-50): Cloud-based, modular starter plan — bank + e-invoice reconciliation only, with automated BA-BS.

Mid-market (50-500): All three modules together (bank + e-invoice + anomaly), automated account reconciliation forms, multi-user with approval workflows.

Enterprise (500+): Multi-entity consolidation, IFRS-compliant exports, a dedicated success manager, ERP integration via API.

You can see the plans for all three sizes in detail on the iFinances pricing page.

The next 2 years of e-reconciliation

Turkish regulation is evolving fast toward digital accounting. The roadmap GİB has announced:

  • 2025: e-Defter (electronic ledger) adoption became widespread
  • 2026: Continuous audit pilot programs begin
  • 2027: E-signature becomes mandatory for account reconciliation forms
  • 2028: AI-based tax audit pilot
By 2027-2028, companies without e-reconciliation will face a widening compliance gap and rising risk. Starting today means avoiding tomorrow's cost.

Conclusion

E-reconciliation is not just a technical process — it is the backbone of Türkiye's financial digitalization. BA-BS, e-invoicing, bank integration: designed as a whole, they make your company audit-ready and modern.

iFinances is a Türkiye-native solution that integrates all of these layers. Request a demo, or explore the plans.

Monthly newsletter

One post a month.

Get new insights straight to your inbox. No spam, just well-crafted reads.

iFinances Editorial
Regulation, reconciliation, engineering. From the desks of Türkiye's finance teams.
Monthly newsletter

2-3 more posts next month. Subscribe to the newsletter.

Get new insights in your inbox. No spam.

info@iwise.co

Chat on WhatsApp