e-Ledger

For a subsidiary in Türkiye the e-ledger is the statutory book itself, not a report about it. The journal and general ledger are produced in the electronic format the tax administration prescribes, a seal is generated for each period and filed with the administration for approval, and the ledger files themselves stay with the company. Nothing changes in how entries are made; this is the statutory form of postings you already have. It also sits on the opposite side from the invoicing documents: e-invoice and e-archive documents are exchanged with a counterparty, while the e-ledger never leaves your side. Your customer never sees it; your auditor does.

Reconciliation is not performed on the ledger file itself but on the records that feed it. What you actually work with is the subsidiary ledger detail, the account statement and the invoice lists; the e-ledger is the legal photograph of those at period end. That sets the correct order of work: find the difference, explain it with a written reason, post the correction, and close the period last. iFinances keeps no books, creates no entries and closes no line on its own; it matches ledger records against bank statements and invoice data in one table and puts the unexplained lines in front of you with their reasons. Records can be uploaded as Excel or CSV, or taken through the direct connection your system offers; which route is used is decided together during setup.

The most common mistake is treating a sealed period as a reconciled one. The seal concerns the integrity of the books; it says nothing about whether the accounts inside them agree with the counterparty's records. The second is assuming that moving to electronic ledgers reduces reconciliation work. Because correcting a closed period is nothing like editing a spreadsheet cell, catching a difference inside the period is worth more, not less. The third is simple name confusion: e-ledger, e-invoice and e-archive are not interchangeable. A fourth point concerns evidence: an auditor asks less about the file itself and more about how each difference was explained.