Start by identifying invoice sources

Before configuration, document where your business creates invoices: sales, point of sale, an online store or an external system. Identify what each source sends to Odoo and who owns data accuracy and follow-up.

This is a project checklist, not an assumption that every invoice follows the same path. Ask the scope to identify included invoice sources and systems requiring separate integration. Otherwise, a successful test inside the sales screen may leave another channel outside the work.

Ask for configuration checks before go-live

It is useful for the project review to cover business and customer information, accounting and tax configuration, product data sources, and the roles responsible for issuance and follow-up. The purpose is to identify missing information and assign its correction before it is used in live operations.

Do not copy another business’s configuration simply because its activity looks similar. Ask the implementer to explain what has been configured for your business, what still needs your information or decision, and which points need checking against ZATCA’s published requirements.

Test the invoice, not just its appearance

ZATCA explains that a paper invoice converted into electronic form by scanning or copying is not an electronic invoice. Viewing or printing a file is therefore insufficient evidence of e-invoicing compliance.

Ask to test scenarios representative of your operations, review integration results, and record errors and warnings with an owner for their resolution. Then test the accounting effect of sales, collections and the notes your business uses. These are suggested project acceptance checks; their results do not guarantee that the accounts contain no other errors.

Do not confuse a provider directory with solution approval

ZATCA explains that its provider list is indicative and non-binding, and does not constitute its approval of the listed technical solutions. A taxpayer may use an unlisted provider if the solution used meets e-invoicing requirements. A directory entry should therefore not replace checks on the actual implementation in your business.

Base project acceptance on what has been configured and tested in your business, and on issues that remain open within the scope of work.

Define what the project should hand over

Ask for a scope identifying included invoice sources, completed configuration, tested scenarios, test results, open issues and team training for issuance and follow-up. Agree post-go-live support boundaries and responsibility for resolving each issue.

Sources

https://zatca.gov.sa/en/E-Invoicing/Introduction/Pages/What-is-e-invoicing.aspx https://zatca.gov.sa/en/E-Invoicing/SolutionProviders/Pages/SolutionProvidersDirectory.aspx

Your next step towards integration

If you use Odoo and need an invoice-readiness assessment, explore Aleem’s E-invoicing Readiness and FATOORA Integration: assessing the existing system, preparing it for integration, testing invoices and training the team within the agreed scope. If the problem extends to accounts and balances, you can start with an Accounting System Health Check. The check covers diagnosis and a report only; remediation requires a separate proposal.

Aleem Consultations