Start with the transaction, not the setting's name

We recommend documenting actual sales, purchase and return scenarios used by your business and agreeing expected treatment with the specialist before testing. Do not copy another business's configuration merely because item names look similar.

ZATCA's VAT-return service states that the return discloses transactions relating to taxable sales and purchases and requires total sales and purchase details. Our proposed test therefore focuses on tracing report data to transactions, not only the visible invoice layout.

Build an understandable test sheet

For each in-scope scenario, we recommend recording:

  • The transaction and its supporting document.
  • Expected treatment reviewed by the specialist.
  • The configuration used and resulting entry.
  • Where the amount appears in the report and any unexplained difference.

Do not change classification simply to suppress an error message or match a previously assumed total. Even when the aggregate looks right, consider whether differences between scenarios have offset one another.

Separate integration from tax treatment

Testing transmission to Fatoora does not replace accounting and tax-classification testing. Create separate acceptance evidence for each workflow and identify who reviews meaning and who reviews technical configuration.

Tax configuration forms part of Aleem's agreed implementation scope; it is not a promise of return approval. Return services are delivered through an accredited partner firm with which the client contracts and pays directly; that firm performs and signs its professional work. Aleem neither performs nor signs that work and receives no referral commission.

By Aleem Consultations.

To define test scenarios, configure the system and train the team, request Odoo accounting implementation.