Defending an Iraqi tax position becomes difficult when the taxpayer’s own documents tell different stories. A contract may state one price while invoices show another. Revenue recorded in the accounts may differ from amounts certified by the client. Expenses may be booked to one entity while the contract names another. A payment described in the ledger as a reimbursement may appear in the contract as a fee. When the tax authority sees these discrepancies, it may conclude that the records are unreliable and issue an estimated assessment, or choose the version of the facts least favourable to the taxpayer.
Discrepancies are common, and many have innocent explanations: amendments not documented, timing differences, administrative errors or practical changes in how contracts were performed. The challenge is to identify the true facts, explain the discrepancies and present a reconciled picture the authority can accept.
The Income Tax Law No. 113 of 1982, as amended, requires taxpayers to maintain proper books and records and empowers the General Commission for Taxes to reject records it considers unreliable and estimate income. The Iraqi Civil Code No. 40 of 1951 governs the interpretation of contracts and amendments. The applicable accounting framework, local audit requirements and any sector-specific rules should be confirmed; accounting figures must be reconciled to the tax position.
Common types of discrepancies in defending an Iraqi tax position
Typical discrepancies include:
- Price differences. Contract price differs from invoiced or recorded amounts due to variations, discounts or currency conversions.
- Timing differences. Revenue or expenses recorded in a different period from the contract milestones.
- Party differences. The contracting entity differs from the entity recording the transaction.
- Characterisation differences. The contract describes a payment differently from the accounting entry.
- Scope differences. Work performed differs from the contract scope without a formal variation.
Establishing the true facts
The first step is to determine what actually happened. This requires reviewing all available documents: contracts and amendments, correspondence, invoices, payment records, delivery documents, certificates and internal approvals. Interviews with staff involved may help. The aim is a factual narrative supported by evidence, not a reconstruction designed to fit a preferred tax outcome.
Explaining discrepancies
Each discrepancy should be explained:
- Variations and amendments. Provide variation orders, correspondence or later agreements showing changes.
- Timing. Show how the accounting treatment follows a consistent policy and reconcile to contract milestones.
- Party differences. Explain intra-group arrangements, joint venture structures or assignments, with supporting documents.
- Characterisation. Explain why the accounting description differs and which reflects the substance.
- Errors. Acknowledge genuine errors and show their correction.
Explanations should be documented, not merely given orally.
Preparing reconciliations
A reconciliation linking contract values, invoices, accounting entries and payments for each significant contract is the most effective tool. It shows the authority that differences are explainable and that the totals are complete. Tax advisory services in Iraq can prepare contract-level reconciliations.
Choosing which document governs
Where documents conflict, the taxpayer should consider which reflects the substance of the transaction. A later amendment may supersede the original contract. Conduct of the parties may show how the contract was actually performed. The taxpayer should present the position that reflects reality, supported by evidence, and explain why other documents do not.
Avoiding retrospective documents
Creating documents after the event to resolve discrepancies, such as backdated amendments, undermines credibility and may have serious consequences. Where documentation was missing, the taxpayer should explain this honestly and support the facts with other contemporaneous evidence.
Preventing future discrepancies
Lessons from the dispute should inform processes: formal variation procedures, consistent entity use, alignment between finance and contract management and periodic reconciliations. Commercial contract advice in Iraq can help establish contract management processes.
Practical checklist
- Identify every significant discrepancy between contracts and accounts.
- Gather all related documents and correspondence.
- Establish the factual narrative for each discrepancy.
- Prepare written explanations supported by evidence.
- Build contract-level reconciliations.
- Present a coherent position to the authority without retrospective documents.
- Fix processes to prevent recurrence.
Common sources of discrepancy
Discrepancies often originate in a few predictable places: variations agreed orally on site but never formalised; contracts signed by one group entity and performed by another; currency conversions recorded at rates different from those in contracts; invoices issued late, after period end; and accounting systems that record transactions by cost centre rather than by contract. Identifying these sources helps prevent discrepancies as well as explain them.
Working with auditors and advisers
Statutory auditors may have already identified discrepancies in their audit work. Their findings, and management’s responses, can help explain discrepancies to the tax authority. Tax advisers can help determine which discrepancies are material for tax and which are merely presentational, focusing effort where it matters.
Credibility as the central concern
The underlying issue in any discrepancy is credibility. The authority must decide whether to trust the taxpayer’s records. A taxpayer that acknowledges discrepancies, explains them with evidence and demonstrates that totals are complete is more likely to be trusted than one that denies or minimises them. Honest, documented explanation is the strongest defence.
Discrepancies with client records
Discrepancies may exist not only within the taxpayer’s own records but between its records and those of clients. Public clients may report payments to the tax authority using different amounts or dates. The taxpayer should obtain client statements and reconcile them to its own records, explaining differences such as timing, deductions or currency conversion. The tax authority is likely to rely on client records where they differ, unless the taxpayer can show why its own figures are correct.
Systems and data quality
Many discrepancies result from accounting systems that do not record transactions by contract, from manual adjustments made without documentation, or from migration between systems. Investing in systems that track revenue, costs and deductions by contract, with audit trails for adjustments, reduces discrepancies and makes them easier to explain.
Illustrative example. A supplier’s contract with a ministry states a price in US dollars, while its accounts record revenue in dinars at a different total. The tax authority treats the contract value as revenue and assesses tax on the higher figure. The supplier demonstrates that the ministry paid in dinars at the official rate on payment dates, provides payment records and the ministry’s payment certificates, and reconciles the dollar contract value to dinar revenue. The authority accepts the reconciliation.
Key takeaways
- Defending an Iraqi tax position requires explaining discrepancies between contracts and accounts.
- Establishing the true facts comes before choosing a tax argument.
- Contract-level reconciliations are the most effective way to show completeness.
- Retrospective documents damage credibility and should be avoided.
How Etihad Law Firm Can Help
When records differ, defending an Iraqi tax position depends on establishing the facts, explaining each discrepancy and presenting reconciled evidence that the authority can verify.
Etihad Law Firm assists taxpayers in reconciling records, preparing explanations and defending positions during audits, objections and appeals in Iraq. We help clients turn inconsistent records into a coherent case.