Jordan is moving quickly toward a tax environment that is based on digital technology, with electronic invoicing at the heart of this change. As countries across the globe begin to implement real-time reporting and compliance, Jordan has also decided to step up its game and follow the same best practices across the world.
The e-Invoicing project, managed by the Income and Sales Tax Department (ISTD), strives to achieve consistency, greater visibility, and compliance through e-invoices.
For those organizations operating out of Jordan, it is important to understand that this is an attempt to make their accounting processes more transparent and compliant.
Key Snapshot (Estimated values)
| Value | Description |
| 16% | Standard General Sales Tax (GST) rate on most B2B, B2C and B2G transactions requiring e-invoicing |
| Dec 2022 | JoFotara national e-invoicing system officially launched by ISTD as a voluntary platform |
| 1 Apr 2025 | Phase 2 mandatory enforcement under Amended Billing Regulation No. 2 of 2025: applies to all VAT-registered taxpayers |
| Real-time | Centralised clearance / CTC model: every invoice must be validated by JoFotara before it is legally issued (no 72-hour window) |
| JOD 75K | Annual turnover threshold that defined Phase 1 in-scope businesses (deadline closed 31 May 2024) |
| JOD 500 | Maximum administrative fine per non-compliance violation; non-compliant invoices also lose VAT input deductibility |
| 4 years | Standard digital invoice & record retention period under Jordan’s Income & Sales Tax Law |
| JOD 10K | Buyer-identification threshold: invoices below this value may omit buyer details (still archived for audit) |
What Is Jordan e-Invoicing?
e-Fattura or the e-Invoicing program of Jordan, also referred to as the ISTD E-Invoicing System, requires that firms who are registered for VAT must create, transmit, and store their invoices online through an authorized platform. It needs to be noted here that unlike the usual PDF invoices that are transmitted via emails, e-invoices need to be in a machine-readable format (UBL XML/Equivalent).
The goal of the system is to minimize instances of tax evasion, increase VAT collection efficiency, and modernize Jordan according to international norms for electronic trading. All companies in Amman, Zarqa, Irbid, and other commercial hubs will be covered under the jurisdiction of the system.
The ISTD e-Invoicing Rollout Timeline
| Period | Phase | Status | Key Details |
| Dec 2022 | Voluntary Launch | Complete | ISTD officially launches JoFotara as the National Electronic Billing System under the Income & Sales Tax Department, in collaboration with the Ministry of Digital Economy & Entrepreneurship. UBL 2.1 XML standard adopted; REST API specifications published |
| Jan–Feb 2023 | Registration & Integration | Complete | Mandatory registration phase begins (Jan 2023); integration testing phase begins (Feb 2023) for early-adopter taxpayers to align ERP/POS systems with JoFotara APIs |
| 31 May 2024 | Phase 1 — Threshold Mandate | Complete | Hard deadline: All taxpayers with annual turnover ≥ JOD 75,000 (≈ €99K / US$105K) required to register and onboard. Real-time pre-clearance (CTC) model active. ISTD Director-General publicly called for compliance to avoid penalties |
| Oct 2024 | Final Compliance Notices | Complete | ISTD issues final reminder notices to all in-scope taxpayers urging immediate registration and integration ahead of Phase 2 |
| 1 Apr 2025 | Phase 2 — Full Mandate | Complete | Amended Billing & Control Regulation No. 2 of 2025 takes effect. Mandatory for ALL VAT-registered taxpayers (resident & non-resident) across B2B, B2C and B2G. Invoices not cleared via JoFotara are invalid for input-VAT deduction and accounting |
| May 2025 | Penalty Freeze Ends | Complete | Soft-landing period concludes; ISTD begins active enforcement of administrative fines (up to JOD 500 per violation) and disallowance of input-VAT credit on non-compliant invoices |
| 2025–2026 | Enforcement & Stabilisation | In Progress | Active enforcement, audit activity, and ongoing onboarding of remaining mid-sized taxpayers; ISTD provides continued technical-support window for late integrators |
| 2026 (TBD) | Small-Business Extension | Upcoming | Planned extension of the mandate to small businesses below the JOD 30,000 GST registration threshold; specific date and modalities pending official ISTD announcement |
Jordan’s phased approach is intentional. Starting from big corporations, which constitute a major percentage of all VAT revenues in terms of value, ensures that during early stages, the implementation of ISTD has the greatest fiscal impact. Companies approaching the requirements for the second or third phase of ISTD should not consider impending deadlines distant occurrences. Integration of ERP-enabled e-invoice solutions usually takes 3-6 months’ time period; hence early preparation would be advisable.
Key Components of the Jordan e-Invoicing Framework
Mandate is based on four pillars that together enable a real-time, government-integrated compliance model.
1. Structured invoice format requires all invoices to be issued in UBL 2.1 XML, a machine-readable schema validated at the ISTD portal level. Structured machine-readable invoice formats are expected to become the primary compliance format under Jordan’s evolving framework.
2. Centralized reporting means that invoice data is submitted directly to the ISTD at the time of issuance rather than at period end, giving tax authorities an ongoing real-time view of commercial transactions across the economy.
3. Real-time data exchange requires B2B invoices to be sent to the ISTD portal as part of the invoicing workflow itself, necessitating API-connected systems with reliable error handling rather than batch or manual uploads.
4. System integration brings everything together: ERP and billing systems must be configured or connected via certified middleware for compliant XML generation and digital signature application and automatic transmission of invoices; without integration, other three pillars cannot work at scale.
Who needs to comply?
The mandate applies to all VAT-registered taxpayers making B2B, B2G, and B2C sales in Jordan. The scope is defined mainly by annual revenue; however, it has been progressively reduced by the ISTD over the phases.
| Business Category | Annual Turnover | Phase | Status | Notes |
| Large & medium taxpayers (Phase 1 cohort) | Turnover ≥ JOD 75,000 | Phase 1 (deadline 31 May 2024) | In Scope Now | First mandatory wave; B2B, B2C and B2G all covered |
| All VAT-registered taxpayers (resident) | Turnover ≥ JOD 30,000 (GST registration threshold) | Phase 2 (1 Apr 2025) | In Scope Now | Universal mandate under Regulation No. 2 of 2025 |
| Non-resident businesses with Jordan tax liability | Any taxable supply triggering ISTD jurisdiction | Phase 2 (1 Apr 2025) | In Scope Now | No physical PE required; covers digital service providers |
| Government / public sector (B2G) | All entities | Active since launch | In Scope Now | B2G obligations applied from earliest phases — not 2025 |
| Free zones & development areas (ASEZ, Zarqa, etc.) | Any turnover | Phase 2 (1 Apr 2025) | Zero-Rated | Must e-invoice via JoFotara at 0% GST — NOT exempt from invoicing |
| Exempt supplies (residential property, most financial services) | n/a | Phase 2 (1 Apr 2025) | In Scope Now | Issuer still e-invoices; no GST charged. Exempt categories cannot reclaim input VAT |
| Small businesses below GST threshold | Turnover < JOD 30,000 | Phase 3 — date TBD by ISTD | Upcoming | Planned 2026 extension; specific date and modalities pending |
| Voluntarily-registered micro businesses | Below threshold but registered | Already in scope via voluntary registration | In Scope Now | Once registered for GST, must comply with JoFotara |
Businesses situated near a threshold boundary should take initiative and assess their scope position rather than waiting for formal notification from the ISTD. Revenue changes during a fiscal year can move a company into scope mid-cycle with very little time left for implementation. Free zone entities and businesses with mixed domestic and export revenues should get specific guidance from the ISTD on applicability.
The e-Invoicing Process: Step by Step
Knowing how an invoice moves through its life helps finance and IT departments map out who does what in each department easily. Below is the five-step flow that represents the usual journey of B2B e-invoicing under the ISTD setup.
A very important point that gets missed often: The buyer may only get an invoice after clearance from the ISTD has been confirmed. Sending an invoice before clearance or completely bypassing the portal would be a compliance violation, even if everything about the transaction is legitimate. Clearance response times must be factored into billing workflows by finance teams, especially in environments with high-volume transactions.
Technical Requirements: What Your System Must Support
Jordan’s e-invoicing mandate is built on internationally recognised standards, but the ISTD has defined specific implementation requirements that go beyond generic XML invoicing.
Any solution that is compliant, whether it be developed internally or provided by a partner fintech firm that is certified, needs to fulfil all the following conditions.
Invoice format and structure: Jordan’s framework is expected to rely on structured machine-readable invoice formats, potentially including UBL XML-based standards and API-driven reporting mechanisms. This is a structured machine-readable schema which allows automatic validation through the ISTD portal. Standard tax invoices, simplified invoices as well as credit or debit notes have different field requirements, and these fields must be populated correctly at generation time.
Digital signature: Every invoice should have a cryptographic digital signature from a certified authority to ensure authenticity and prevent tampering after issuance. This is mandatory for ISTD clearance; hence any invoice without valid digital signing will automatically be treated as non-compliant irrespective of content accuracy.
Unique identifies (UUID): A unique identifier must be assigned to every invoice at creation point since this UUID serves primarily as reference for tracking by the ISTD during audit matching and dispute resolution processes.
API transmission and reporting windows: Invoices need to be sent into the ISTD portal through REST API. Real-time or near-real-time reporting will occur regarding business-to-business transactions whereas business-to-consumer transactions are reported up to 72 hours after the transaction occurs. It is important to ensure that the software used by firms can handle API integration correctly with proper error handling measures if required.
QR code: A QR code is required on simplified invoices generated from B2C transactions allowing buyers verification of authenticity against the ISTD portal; this creates another consumer-facing layer of transparency in compliance.
Archive retention: All issued and received e-invoices must be kept in an easy-to-access digital format for at least five years. The archive should be open for inspection when requested by ISTD and should maintain the original signed XML, not just a version that people can read easily.
Jordan in the MENA e-Invoicing Landscape
Jordan’s mandate places it within a rapidly digitizing regional tax ecosystem. Understanding the difference makes it easier for multinational corporations to plan an overarching compliance strategy rather than implementing piecemeal approaches for individual countries.
Regional Strategy Insight: unified e-invoicing solution that would support multiple countries’ regulations, thereby minimizing the overall compliance costs while providing an opportunity for streamlined audit trails for Amman, Riyadh, Cairo, and Dubai entities.
| Country | Authority | Mandate Start | Model | Format |
| Jordan ★ | ISTD | 2024 (Phase 1) | Clearance | UBL XML |
| Saudi Arabia | ZATCA | 2021 | Clearance + Reporting | UBL XML / FATOORA |
| Egypt | ETA | 2020 | Clearance | JSON / XML |
| UAE | FTA | 2026 (expected) | Reporting | Peppol UBL |
| Turkey | GIB | 2012 | Clearance | UBL-TR XML |
Choosing the Right e-Invoicing Partner
The complexity of Jordan’s technical specifications makes an experienced e-invoicing solution provider with deep MENA regulatory expertise a strategic advantage over building in-house. While considering vendors, think about these selection criteria:
- ISTD-certified or ISTD-aligned platform with active API integration and sandbox testing environment
- Out-of-the-box integration options with SAP, Oracle, Microsoft Dynamics and other enterprise ERPs
- Multi-country MENA coverage for scalable regional compliance from a single platform
- Dedicated compliance monitoring, regulatory update alerts and managed services model
Trusted digital transformation partners serving enterprises across Jordan GCC and broader MENA markets offer end-to-end e-invoicing compliance services – from initial gap assessment through to go live support and ongoing regulatory maintenance. Explore how proven fintech compliance platforms have helped businesses navigate mandatory e-invoicing transitions across the region.
Jordan in the Global e-Invoicing Landscape
The mandate in Jordan reflects how there has been a global shift from periodic self-reporting to continuous transaction-level tax compliance. In MENA, this places Jordan after Saudi Arabia and Egypt but before the UAE’s expected 2026 mandate thus positioning it as a mid-wave adopter benefiting from regional infrastructure already in place.
Its clearance model and alignment with internationally recognized standards (UBL XML, REST API, digital signatures) make its framework technically compatible with other mandates across the region; for multinationals operating across Amman, Riyadh, Cairo and Dubai this creates a very strong business case for building one unified multi-country compliance platform rather than country-by-country solutions that are disconnected from each other
Conclusion
Jordan’s e-invoicing mandate is among the most significant regulatory changes impacting businesses in the country today. Though the phased rollout provides different market segments with varying lead times, the goal is clear: full electronic invoicing compliance will be mandatory and subject to enforcement and auditing.
Organizations that opt for early implementation are rewarded not only with a penalty-free operation but also benefit from other perspectives. In addition to the fact that the implementation of the e-invoice process eliminates manual reconciliation processes, improves cash flow management, and provides clean audit trails making VAT returns simpler, properly designed investment in compliance will pay back much more than simple compliance with regulations.
For companies doing business throughout MENA with operations in Amman, Riyadh, Cairo, Dubai, or Istanbul it’s time to consider whether a single multi-country compliance platform can supplant the currently prevalent fragmented country-by-country solutions used by most organizations.
Comply with Jordan’s National E-Invoicing System Using a Secure, Scalable Solution from Cygnet.One
FAQs
Businesses in Jordan can keep using their systems but these systems must work with the governments e-invoicing system. The businesses need to send the invoice information to the Income and Sales Tax Department in the format. This way the businesses can follow the rules. Still do things their own way.
You cannot change an invoice once it is issued. If you need to make a change you have to use a credit or debit note that is linked to the invoice. This way everything is clear and easy to see. It helps with keeping track of all the money.
The e-invoicing system in Jordan also includes transactions between businesses and individual customers. Businesses may need to report sales information or issue electronic invoices for these transactions. This way all taxable transactions are included in the system.
The requirement of the electronic copies stored safely and are readily accessible will suffice. You might not need to keep copies yourself but should ensure that it is easy for you to access your records when you must do so.
In Jordan, the standard practice is usually that invoice data is provided on time. This allows eliminating any delay issues. It ensures that the tax authority has the latest information available.
If a business has branches all of them have to follow the e-invoicing system. The business needs to have a way of reporting and doing things and make sure everything is the same across all locations.
The automation of the process is essential in case of large transaction volumes since it is vital to provide an automatic handling of them. A solution should enable sending out lots of invoices at once while being scalable.
Automation in Jordan e-invoicing helps with checking, reporting and keeping track of everything in real time. It reduces mistakes. Makes sure everything is done correctly. For businesses that are growing automation is necessary to handle all the transactions. Jordan e-invoicing and automation go together to make things easier for businesses, in Jordan.