What can e-ledger data reveal?
Turkey’s e-ledger contains all of a company’s accounting entries in a standard, machine-readable format. Examined with the right questions, it reveals inconsistencies and unusual transactions that sampling cannot see.
The e-ledger (e-defter) is the system in which a company’s journal and general ledger are kept electronically in line with standards set by Turkey’s Revenue Administration (GİB). Entries are stored in an XML structure based on XBRL GL, an international standard for accounting data. That structure makes the e-ledger not just a legal obligation but a powerful source for analysis.
Traditional review looks at a sample of entries. With e-ledger data, all entries can be examined at once.
What is in the e-ledger?
For each journal entry, the following are typically available:
- Entry date and journal number,
- Account code and account name,
- Debit/credit amount,
- Description,
- Document type, number and date.
Using these fields together reveals relationships that cannot be seen by looking at a single account.
Examples of analysis
| Analysis | What it looks for | Why it matters |
|---|---|---|
| Chart-of-accounts consistency | Accounts with the wrong-sign balance (e.g. a credit balance on cash) | Posting error or classification problem |
| Weekend and holiday entries | Entries dated outside normal working days | A point of attention for unusual transactions |
| Round amounts | Large entries in perfectly round amounts | Estimated or manual entries |
| Reversals | Entries cancelled and re-entered within a short time | Correction intensity, process problems |
| Period-end clustering | Revenue/expense entries bunched near the close | Cut-off and accrual errors |
| Document–entry date gap | Long gaps between document date and entry date | Close delays, late documents |
| Digit distribution (Benford) | First digits deviating from the expected distribution | A signal of unusual patterns in large data sets |
| Description analysis | Blank, repetitive or meaningless descriptions | Entry quality and traceability |
None of these analyses proves an error or irregularity on its own. Their purpose is to direct limited review time to the entries that most need attention.
Who benefits?
- Finance teams: checking the quality of their own entries before the close and finding errors before the audit.
- Management: seeing where the close slows down and which accounts attract many corrections.
- Audit and review work: basing risk assessment on data and setting the scope of review.
I describe where control points should sit in key control points in financial processes.
How is it done technically?
The e-ledger XML files are parsed into a tabular structure, and the analyses run on that table. Once parsing is set up correctly, the same analyses can be repeated every period in minutes. You can see this approach applied in the E-Ledger Analysis Engine.
For a broader view of how data analytics changes the audit approach, see the audit and financial control page.
Frequently asked questions
Is special authorisation needed to analyse the e-ledger?
A company’s own e-ledger files can be analysed by its finance team or by advisers it authorises. For confidentiality and security, access should be limited and the analysis carried out in a controlled environment.
Can Benford analysis be applied to any data set?
No. Benford’s distribution is meaningful for large, naturally occurring data sets that span several orders of magnitude. It is not suitable for fixed-price transactions or amounts confined to a narrow range.