Skip to content
BarmajTek
العربية

Guides · national invoicing

How your system submits an invoice to JoFotara

JoFotara developer guide for ISTD submission. How your system submits an invoice to JoFotara: this guide explains the engineering path as BarmajTek builds it, and it separates what the Income and Sales Tax Department has published from claims its pages had not confirmed as of 26 August 2026.

Discuss a JoFotara integrationRead the integration service

JoFotara is Jordan’s national e-invoicing system, operated by the Income and Sales Tax Department. Software builds the invoice document against the technical guide, posts it to the published interface, then waits for acceptance or rejection plus an identifier and a verification payload before treating the invoice as cleared for the customer. The taxpayer registers on the official portal and obtains credentials. BarmajTek does not accredit anyone; the Department does not run a software-vendor accreditation programme. On 1 April 2025 the Department published an expense-recognition rule for local purchases that requires an invoice from the national system or a linked system. Onboarding “waves” from 2019–2024 and a 2026 hard QR deadline were not dated as such on the Department HTML we reviewed.

Copy reviewed on 2026-08-26.

In operations

Four rules that show up on day one

  • The taxpayer owns the keys

    The Client-Id and Secret-Key are created in the JoFotara portal after a device is linked. We do not ask anyone to publish them in a public repository or a marketing page.

  • Clearance before the customer copy

    A receipt printed before the system responds is not a cleared invoice in this model. Design the till to wait for status or to follow an explicit offline path.

  • Rejection is a path, not an exception

    Persist the response, show the operator the reason, and resubmit after correcting the source. Do not mint a new number because a request timed out.

  • No vendor accreditation

    Any vendor claiming an official Department certificate for its software is selling a status that does not exist. Legal duty sits with the taxpayer.

What we cite from the law, and where we stop

The Department’s Fawateery FAQ cites Regulation No. 34 of 2019 on organizing and controlling invoicing, including accepted invoice form and retention. The Department hub also lists the 2023 invoicing regulation. We cite those pages, not a gazette PDF in hand. On 1 April 2025 the Department published news about amended expenses regulation No. 2 of 2025: local purchases of goods and services should be supported by invoices issued from the national system or a linked system, or the expense may not be accepted. We do not collapse that into a vendor slogan that every seller entered “Phase 2”. Dinar fine amounts were not listed on the pages we reviewed; we say non-compliance is subject to tax law and Department follow-up.

Three document families you must not mix

The technical guide distinguishes income-tax invoices with no sales-tax block, general sales invoices with statutory rates and tax categories, and special sales invoices with a compound calculation. Software that sends one shape for every customer will fail at the first clinic or trader outside that template. Ask the accountant what the registration status is today, not what marketing hopes it is. BarmajTek’s JoFotara packages cover the six document types in the technical guide we implement against; they do not decide when a commercial invoice is issued. That remains your billing system’s decision.

The submission contract as we implement it

Live submission goes to the published host on the JoFotara domain with two headers — Client-Id and Secret-Key from the portal — and the invoice document encoded as the guide requires. The response returns a status, a verification payload, an identifier, a national invoice number on acceptance, and a result list of information, warnings, or errors. Design storage around those fields before polishing the screen. If the response says the invoice was already submitted, look up the first attempt; do not delete it or mint a new number. A public sandbox URL, the Sanad decode path, and portal self-test tools had no documented public address in our review, so this page says they are unknown rather than inventing a link.

Where fields must come from so validation does not fail

Live failures are rarely “the interface is down”. They are usually a name that does not match the tax record, a governorate code outside the guide list, line totals that do not equal the amount, or an invoice family that does not match the taxpayer type. Source fields from one accounting record: tax number, address, governorate code as in the technical guide, tax rate, and an internal invoice number that never repeats. Do not hand-edit the submission in support; correct the record then resubmit so the chain stays auditable. Governorate codes in our implementation match the technical guide we follow; if the guide changes we update the package, not this page with a silent rewrite.

What BarmajTek builds, and what stays yours

We write adapters around a living billing system, or we fold the path into a product such as Clinic Tek. The published developer packages use the same names as the implementation. What we do not do: collect portal credentials instead of the taxpayer, announce that the connector is “accredited”, or ship a Saudi e-invoicing connector. If your current system is sound, start at the JoFotara integration service. If the invoice leaves a clinic consult, read the clinic JoFotara page, then Clinic Tek prices on the company site, with checkout on the product host.

How to read this guide next to the blog

The national e-invoicing article for owners covers operating readiness. The correction and cancellation article covers what to do after acceptance if you find an error. This guide is for the developer or systems lead who will write the connector. None of the three pages replaces the official portal or a tax adviser. When they conflict, the current text on the Department site wins.

Hard limits so this guide is not copied as legal fact

We do not publish a public sandbox URL, a fine amount, a wave timetable the Department page did not date, or a partnership claim. The software package implements the technical guide version we pin; a guide change requires an implementation review. If a vendor asks you for a “JoFotara certificate”, ask which legal text creates a certification programme. You will not find one in our work or on the official pages we reviewed.

Device linking steps on the portal, JoFotara integration for a live system, Clinic invoicing through JoFotara, Owner-facing national e-invoicing guide, Correct or cancel an electronic invoice, Jordan market and the Amman office.

Questions

BarmajTek guides
We do not publish a universal timetable of our own. We relay the 1 April 2025 expense-recognition wording as the Department wrote it, and we send readers to the current portal for any broader mandate.

Turn the guide into a written scope

We start from the current billing system and rejection cases, not from an accreditation promise. Send a brief after you read the registration steps.

Discuss a JoFotara integrationRead the integration service