Correcting Posted Entries: Are Backdated Entries Legitimate?

One of the most contentious questions inside corporate finance departments is: “We discovered an error in a prior-year entry — do we correct it with a backdated entry, or post it in the current period?” The answer is not merely technical; it touches the integrity of the financial statements, shareholder rights, the rights of tax authorities, and management’s accountability to auditors. A wrong answer can take an organization from an accounting mistake into a regulatory breach and accounting fraud punishable by law.

This in-depth guide examines: when posted entries may be modified, the difference between correction and manipulation, the proper treatment under IAS 8 (Accounting Policies, Changes in Accounting Estimates and Errors), and the limits a professional ERP imposes on these operations.

1) The golden rule: posted entries cannot be edited or deleted

The bedrock principle of every professional accounting system and international auditing standard is unequivocal: once an entry is posted to the general ledger, it becomes part of the official record and cannot be deleted or directly modified. This is not technical rigidity; it is a substantive safeguard for:

• Audit-trail integrity — every change must be visible and traceable.
• Tamper resistance — preventing retroactive editing that hides facts.
• Regulatory compliance — a clear ZATCA requirement for e-invoicing and accounting systems.
• Auditor credibility — any system that allows deletion of posted entries is deemed unreliable in the audit report.

Professional ERPs enforce this technically: there is no delete button for posted entries and no editing of their core fields. Even reversal is done via a separate reversing entry dated in a new period, not by erasing the original.

2) Legitimate correction methods

a) Reverse and re-enter

The most common approach. Create a reversing entry in the current period that fully neutralizes the erroneous entry, then create a new correct entry. Pros: full transparency, every step documented. Cons: multiple entries for one transaction.

b) Direct correcting entry

A single entry that fixes only the erroneous portion without reversing the original. Suitable for simple errors such as correcting an account when the amount is right.

c) Restatement

For material prior-period errors, restate the comparative financial statements under IAS 8, with full disclosure of the error’s nature and impact.

3) What is a backdated entry and when is it lawful?

A backdated entry is one recorded today but carrying an accounting date in a prior period. The practice raises legitimate concern because it can be abused: shifting expense between years, deferring revenue recognition, polishing quarterly ratios, or concealing fraud.

Narrowly lawful cases:

• Period-end adjusting entries posted technically after close but before the formal period lock, dated the last day of the period.
• Correcting material errors discovered before the financial statements are released.
• Soft-closed periods that grant a specific window (e.g., 5 days after month-end) for late entries.

Strictly prohibited cases:

• Any entry dated in a fiscal year whose statements were issued and approved.
• Any entry dated in a period whose tax return was submitted to ZATCA.
• Any entry dated in a period that has completed external audit.
• Any entry intended to alter a period’s result after it was announced to regulators or markets.

Bottom line: a backdated entry is not necessarily wrong, but it always deserves scrutiny. Practical rule: if you cannot justify a backdated entry in writing before an external auditor, do not post it.

4) Error treatment under IAS 8

a) Current-period errors

Corrected within the same period before its statements are approved, with a correcting entry dated appropriately inside the period.

b) Prior-period errors

Per IAS 8, material prior-period errors are corrected retrospectively through restatement of comparative figures and adjustment of the opening balance of retained earnings in the earliest period presented. This does not mean editing posted entries in the system — it means correcting the presentation in the new financial statements.

5) Error vs. change in accounting estimate

• Error: omission or misapplication of information that was available when the statements were prepared. Treated retrospectively.
• Change in accounting estimate: revising a prior estimate due to new information (asset useful life, provision rate). Treated prospectively only.

Example: discovering that a machine was recorded with a 5-year life instead of 10 due to a clerical error → error, corrected retrospectively. But if management decides based on new technical assessment that the machine will run 8 years instead of 10 → change in estimate, treated only in future depreciation.

6) Restatement of financial statements

1. Quantify the total error and its impact on each affected line for each affected period.
2. Restate the comparative figures in the new financial statements (the old issued statements are not changed).
3. Adjust the opening balance of retained earnings in the earliest period presented.
4. Detailed disclosure in the notes.
5. Notify the external auditor, board, and audit committee before approving the new statements.
6. For listed entities: notify the market regulator.

7) Adjustments in closed periods

A closed period is a technical concept in ERP that blocks any new posting dated inside it. Closing is performed deliberately by the chief accountant or CFO once all entries have been processed.

When may a closed period be reopened?

• Material error discovered before financial statements are released.
• An adjusting entry requested by the external auditor.
• Mandatory correction based on regulatory instruction.

Proper procedure: formal written request → CFO and CEO approval → period reopened under exceptional authority → only the specific entry posted → period re-closed immediately → operation logged in a reopening register.

8) Tax impact of retroactive corrections

• Amended tax return filed via the ZATCA portal for the affected period.
• Settlement of difference if liability increases.
• Penalties and interest may apply on delinquent amounts.
• Refund claim if liability decreases.
• Complete documentation retained for future ZATCA inspection.

Principle: do not perform a correction affecting a closed tax period without consulting a tax advisor and assessing the legal and financial impact.

9) Correction governance inside ERP

• Technical prohibition of deletion — no delete button for posted entries.
• Technical prohibition of backdated postings after close — only allowed under exceptional authority.
• Dedicated approval workflow for correcting entries with higher authority than routine entries.
• Mandatory “reason for correction” field with attachments.
• Immutable audit log for every correction and period reopening.
• Automated alerts to CFO and internal auditor for corrections above a defined threshold.
• Periodic correction report submitted to the board.

10) Practical scenarios

11) Red flags that uncover manipulation

• Unusual spike in correcting entries near period end, especially large ones in the final days.
• Repeated requests to reopen closed periods.
• Large correcting entries from users with elevated privileges.
• Entries that materially improve the period result in the last days.
• Entries with vague or boilerplate justifications.
• Entries hitting sensitive accounts (retained earnings, related parties, provisions).
• Entries immediately reversed in the following period — the classic “temporary close adjustment” pattern.

12) Case study: prior-year missed invoice

Situation: A company issued its 2024 financial statements approved by the general assembly in April 2025. In July 2025, an SAR 1,200,000 purchase invoice (plus SAR 180,000 VAT) dated December 2024 surfaces; a major supplier demands payment and produces a valid e-invoice already registered on Fatoora.

Analysis under IAS 8:

1. The amount is material (e.g., 1.2M on a net profit of 15M = 8%).
2. The information was available when the statements were prepared → classified as a prior-period error, not a change in estimate.
3. A backdated entry to December 2024 is strictly prohibited because the statements were approved and the tax return was filed.

Correct action:

1. Post an entry in July 2025 charging the effect directly to Retained Earnings:

2. In preparing 2025 statements, present 2024 comparative figures restated as if the invoice had originally been recorded.
3. Full disclosure in notes: nature of error, amount, EPS impact, tax effect.
4. File an amended tax return with ZATCA for the original tax period to recover the input VAT of SAR 180,000 within statutory deadlines.
5. Notify the external auditor and audit committee before approving the 2025 statements.

13) Legal and professional responsibilities

• Executive accountant liability — may include professional discipline and suspension by SOCPA.
• CFO and board liability — joint responsibility for the integrity of the financial statements.
• Tax liability — late penalties up to 25% under the VAT regulations, potentially treated as tax evasion in severe cases.
• Criminal liability — in cases of intentional fraud to mislead investors or creditors.
• External auditor liability — if the auditor failed to flag manipulation, professional and financial accountability may follow.

Golden rule for the professional accountant: no management pressure justifies a personal signature on an unlawful entry. Document the refusal in writing, escalate to internal and external auditors, and never compromise professional integrity under any pretext.

FAQ