Phase Two of Electronic Invoicing
Phase Two of Electronic Invoicing.
When researching Phase Two of electronic invoicing in Saudi Arabia, knowing a solution’s name or reading a generic feature list is not enough. A sound decision begins with understanding your establishment’s procedures, invoice types, and transaction volumes, followed by testing how invoices are issued, stored, and reviewed. This guide presents practical steps for distinguishing regulatory requirements from day-to-day operational needs, with references to the Zakat, Tax and Customs Authority (ZATCA) where appropriate.
ZATCA defines an electronic invoice as an invoice issued and stored in a structured electronic format through an electronic system, rather than merely an image or a manually edited file. The generation and storage phase took effect on December 4, 2021, while the integration phase began gradually on January 1, 2023. An establishment’s specific obligations depend on its invoice types and the phase applicable to it.
What Should You Understand Before Getting Started?
Phase Two of electronic invoicing involves an end-to-end process that starts with recording a sale and ends with retaining a document that can be retrieved later. Where Phase Two requirements apply, it may also involve exchanging data with the Fatoora platform. It is therefore important to distinguish choosing suitable software from demonstrating that it meets the requirements in your establishment’s actual workflows. Labels such as “approved” or “best” should not be treated as regulatory assurances without specific evidence.
Business owners search for terms such as “integration phase,” “Phase Two requirements,” and “integration with the Fatoora platform.” Although these expressions are closely related, search intent may differ: purchasing a product, understanding regulations, or resolving a technical issue. This article focuses on the differences between the two phases and approaches the other topics from an implementation perspective rather than duplicating general e-invoicing guides.
Differences Between the Two Phases
In the area of “Differences Between the Two Phases” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Differences Between the Two Phases
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Differences Between the Two Phases
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Differences Between the Two Phases
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
To explore the operational side further, review the accounting and point-of-sale system and confirm that the service meets your actual needs.
Covered Establishments and Implementation Waves
In the area of “Covered Establishments and Implementation Waves” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Covered Establishments and Implementation Waves
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Covered Establishments and Implementation Waves
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Covered Establishments and Implementation Waves
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
For the management of related operations, see purchasing management as a contextual resource, not as a substitute for official guidance.
To compare implementation options, you can request a demonstration after preparing a list of scenarios you need to test.
Preparing the Technical Solution
In the area of “Preparing the Technical Solution” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Preparing the Technical Solution
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Preparing the Technical Solution
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Preparing the Technical Solution
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
To explore the operational side further, review purchasing management and confirm that the service meets your actual needs.
Integration with the Fatoora Platform
In the area of “Integration with the Fatoora Platform” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Integration with the Fatoora Platform
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Integration with the Fatoora Platform
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Integration with the Fatoora Platform
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
For the management of related operations, see customer service management as a contextual resource, not as a substitute for official guidance.
To compare implementation options, you can view subscription plans after preparing a list of scenarios you need to test.
Tax Invoices and Simplified Tax Invoices
In the area of “Tax Invoices and Simplified Tax Invoices” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Tax Invoices and Simplified Tax Invoices
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Tax Invoices and Simplified Tax Invoices
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Tax Invoices and Simplified Tax Invoices
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
To explore the operational side further, review customer service management and confirm that the service meets your actual needs.
Pre-Launch Testing
In the area of “Pre-Launch Testing” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Pre-Launch Testing
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Pre-Launch Testing
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Pre-Launch Testing
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
For the management of related operations, see distribution solutions as a contextual resource, not as a substitute for official guidance.
To compare implementation options, you can register your establishment after preparing a list of scenarios you need to test.
Error Monitoring
In the area of “Error Monitoring” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Error Monitoring
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Error Monitoring
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Error Monitoring
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
To explore the operational side further, review distribution solutions and confirm that the service meets your actual needs.
Business Continuity Planning
In the area of “Business Continuity Planning” under Phase Two of electronic invoicing, start by documenting your establishment’s current situation: the types of customers you serve, the number of invoices you issue, the channels used to issue them, and the people responsible for reviewing them. Then define the intended outcome precisely. Is the goal to reduce errors, speed up processing, improve traceability, or prepare for regulatory requirements? Priorities differ by business activity, so do not copy another establishment’s settings without testing them.
Practical Objective — Business Continuity Planning
Start by identifying the decision this step must support: who performs it, which document they rely on, and when the process is considered complete. Clear responsibility makes errors easier to detect and reduces reliance on the judgment of a single employee. A function appearing on a software feature list is not enough; what matters is whether it works consistently in the establishment’s actual scenarios.
Practical Scenario — Business Continuity Planning
Consider a Saudi retail store that issues daily sales invoices and handles returns, discounts, and different payment methods. First test the scenario with sample data, then reconcile the invoice against the sales record, the accounting entry, and the tax data. If discrepancies appear, document their causes before moving to the next step rather than correcting the outcome manually at the end of the month.
Verification Checklist — Business Continuity Planning
Check user permissions, the accuracy of invoice fields, how the electronic copy is stored, and whether an auditable record can be retrieved later. Also test interrupted connectivity, duplicate submissions, customer-data changes, and error handling. Implementation details depend on the invoice type and the applicable compliance phase; an operational checklist is not a substitute for official regulatory documentation.
For the management of related operations, see Nezami services as a contextual resource, not as a substitute for official guidance.
To compare implementation options, you can discuss your requirements with the team after preparing a list of scenarios you need to test.
You may also find it useful to review the accounting and point-of-sale system to understand the relationship between invoicing and sales.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
A Practical Implementation Plan for Your Establishment
1. Inventory and classify current invoices: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
2. Define responsibilities and access permissions: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
3. Prepare realistic test data: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
4. Test invoices and credit or debit notes: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
5. Review accounting and tax impacts: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
6. Document errors and retest: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
7. Train employees on recurring scenarios: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
8. Monitor results after launch: Assign an owner, a deadline, and an acceptance criterion to the task, then keep evidence of what was tested and the result. Do not approve a step merely because the screen displays a success message; inspect the electronic document and the transaction log, and resolve exceptions before rolling the procedure out more widely.
Frequently Asked Questions
Is buying a Phase Two e-invoicing solution enough to achieve compliance?
No. You must identify the requirements that apply to your establishment, test the solution’s configuration and workflows, and consult the Authority’s latest documentation.
Is a PDF image alone considered an electronic invoice?
Not necessarily. The official definition requires an invoice to be issued and stored in a structured electronic format through an electronic system; the detailed format requirements vary by phase.
Does Phase Two apply to every establishment on the same date?
No. Integration is implemented gradually in groups determined by the Authority, and the targeted establishments are notified.
How can I test the system before relying on it?
Test a standard invoice, a return, a discount, and an unstable connection. Then review the documents, accounting entries, logs, and data-exchange results where integration applies.
Does calling software “approved” mean that ZATCA guarantees it?
You should not assume so. Request specific evidence of conformity and consult the official requirements; compliance must be verified in your own operating environment.
Conclusion
Choosing or operating a Phase Two e-invoicing solution is not an isolated technical decision; it is a small project to control data, processes, and responsibilities. Start with the most frequent use case, then move to exceptional scenarios. Do not overlook the Authority’s requirements or your team’s ability to resolve errors. Document the verification results and review them whenever the system is updated or the scope of mandatory implementation changes.
If you would like to assess your establishment’s needs, explore the available options. You can also explore Nezami services for more context about the available solutions.
Official Sources to Review Before Publication
Definition of Electronic Invoicing and Invoice Types
Electronic Invoicing Implementation Phases
Guidelines and Educational Materials
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.