Jordan e-invoicing: a step-by-step JoFotara guide
A practical walkthrough of Jordan's national e-invoicing system (JoFotara): who it covers, how to link your accounting system, which invoice types exist, and how to handle rejections, outages and returns.
Jordan e-invoicing runs through JoFotara, the national electronic invoicing system operated by the Income and Sales Tax Department (ISTD). If you sell goods or services in Jordan and are bound by the invoicing rules, your invoices must pass through it, either typed on the JoFotara portal or app, or sent automatically from your own accounting system. This guide walks through the process step by step, from the portal credentials to credit notes, and points out the mistakes that cause most rejections. If you want to see how this looks inside an ERP, our page on JoFotara integration for Jordan e-invoicing shows the same steps in Aspirations.
What JoFotara is and who must comply
ISTD launched the national e-invoicing system in December 2022 and opened the joining stage for companies and establishments. The legal basis is Article 23(f) of the Income Tax Law, which requires an original invoice for every sale of goods or service in the Kingdom, together with the Regulation for Organizing and Controlling Invoicing Affairs No. 34 of 2019 and its instructions. ISTD's billing news names establishments, companies, professionals, craftsmen and service providers among those covered.
ISTD has also published turnover thresholds that keep some small activities outside the obligation. According to an ISTD news item, these include licensed shops and groceries with annual sales below 75,000 dinars, licensed crafts with annual revenue below 30,000 dinars, and bakeries selling only bread with annual sales below 150,000 dinars. Thresholds can change, so confirm your position with ISTD or your tax adviser before relying on them.
Enforcement is real. In February 2026 ISTD notified 379 non-compliant businesses and gave them one week to correct their status. The Income Tax Law treats failing to issue a proper invoice as a violation; we don't quote fine amounts here because the right figure depends on the case, so ask your tax adviser.
Three ways to issue an e-invoice
- The portal: businesses without an invoicing system issue invoices directly on portal.jofotara.gov.jo.
- The mobile app: suitable for a small number of invoices.
- Integration (API): your accounting, ERP or POS system sends each invoice to JoFotara as it is issued. You keep working in your own system and never type an invoice twice.
If you issue more than a handful of invoices a day, integration is usually the only practical option. The rest of this guide assumes integration.
Step 1: get your integration credentials from the portal
ISTD's linking procedure manual describes the steps:
- Log in to the national invoicing system with your company's tax number, username and password.
- Open Connect Devices and choose New link.
- Enter a username for the device and select the income source sequence the invoices belong to.
- Press Add. The portal shows a user number (Client-Id) and a Secret-Key.
These three values are what your system needs: Client-Id, Secret-Key and income source sequence. They are sent in the header of every API request. Treat the Secret-Key like a password: store it encrypted and never paste it into email or chat. A branch registered separately for tax has its own tax number, so it needs its own credentials.
Step 2: know your invoice types
Each invoice sent to JoFotara is classified along two lines.
- Cash or receivables (credit): the type follows the payment method. A receivables invoice carries the buyer's name. According to ISTD's invoice manual, buyer details are not required on invoices below 10,000 dinars, and for invoices above that amount ISTD's news says the seller must be able to prove the buyer received them.
- Sales tax invoice or income invoice: a business registered for sales tax issues invoices with tax lines (the general rate is 16%, with zero-rated and exempt items; see our guide to Jordan sales tax rates). A business not registered for sales tax issues income invoices without tax lines.
On top of these sits the credit note (return invoice), which references an original invoice and reverses all or part of it.
Step 3: build the invoice as UBL 2.1 XML
JoFotara expects each invoice as XML following the UBL 2.1 standard, encoded and sent with your credentials. In practice this means your system must fill in, at minimum: your tax number and income source sequence, a unique invoice number and identifier, the issue date, the invoice type, each line's quantity, unit price and tax category, and totals that add up exactly. Amounts are in Jordanian dinars with three decimals. Small rounding differences between line totals and the invoice total are a frequent cause of rejection, so the calculation must be done the same way on every line.
Step 4: submit, then print the QR code
When JoFotara accepts an invoice it returns a QR code. Store it with the invoice and print it on the invoice and the POS receipt. Buyers can scan it in the government Sanad app to check that the invoice was registered. JoFotara may also return warnings with an accepted invoice; keep them, because they often point at data you should fix before the next invoice.
Two rules keep the books clean. First, submit only after the sale is fully saved, including stock and the journal entry, so JoFotara never receives a sale that was rolled back. Second, once accepted, an invoice is final. Don't edit it in your system or try to fix it on the portal.
Step 5: handle rejections and connection failures
There are two different situations, and they need different handling.
- Rejected: JoFotara received the invoice and refused it, with an error message. Read the message, fix the cause (a missing buyer name, wrong income source sequence, totals that don't add up, wrong credentials) and resubmit.
- Not delivered: JoFotara could not be reached, timed out or returned a server error. The invoice is not rejected; it is pending. Keep it, and resubmit once the service is back.
In Aspirations, a pending JoFotara invoice is resubmitted manually with one click from the invoice, and resubmitting an invoice JoFotara already accepted is safe. A rejected invoice notifies the accountants and the invoice owner with JoFotara's message. Many rejection causes are checked before the invoice takes a number, so they are caught early.
Step 6: returns and corrections with credit notes
Because an accepted invoice cannot change, every correction is a credit note:
| Situation | What to do |
|---|---|
| Customer returned some items | Credit note for the returned lines only |
| Wrong price or quantity | Full credit note, then a new correct invoice |
| Invoice issued to the wrong customer | Full credit note, then a new invoice to the right customer |
| Return at the cash register | Credit note against the original POS sale |
A credit note should reference the original invoice number, its unique identifier and total, and carry a reason. The original must already be accepted. In your accounting software, the credit note should reverse revenue and sales tax, and return goods to stock where relevant.
Common JoFotara mistakes
- Wrong income source sequence. Credentials generated on one sequence and invoices sent under another.
- Testing with live data. There is no public test environment, so the first real invoice is the test. Check it on the portal and scan its QR code in Sanad before going fully live.
- Wrong tax category on items. Zero-rated and exempt are different categories; confirm each item with your accountant.
- Editing sent invoices. This breaks the match between your books and the portal. Use credit notes.
- Treating an outage as a rejection. A pending invoice is not rejected and should not be re-issued under a new number.
- Foreign currency. Domestic e-invoices are in dinars.
- Nobody watching rejections. Make sure the right people get notified the same day.
Checklist before going live
Your company has joined the system and can log in; Client-Id and Secret-Key are generated on the correct income source sequence; tax number and address are complete; separately registered branches have their own credentials; every item has a tax category; credit customers have names; the connection test passes; and your first real invoice is accepted and visible on the portal. Aspirations' integration is ready (UBL 2.1) and needs your own JoFotara credentials; during onboarding we check the first real invoices with you. Domestic invoices in dinars are supported today; export and development-zone invoices are not yet.
Official sources
- ISTD: launch of the national e-invoicing system
- ISTD: billing system news (Regulation 34/2019, thresholds)
- ISTD: procedure manual for linking to JoFotara
- ISTD: procedures manual for organizing the invoice
- Income Tax Law No. 34 of 2014 as amended (ISTD)
- Petra: ISTD notices to 379 non-compliant businesses (Feb 2026)
