If your business is mandated onto Jordan's ISTD JoFotara platform, every taxable Sales Invoice now has to be transmitted to the national system, cleared, and stamped with an official invoice UUID and QR before it is legally valid. ERPNext out of the box has no idea JoFotara exists: it produces its own invoice numbering and print formats, but it cannot build the ISTD-mandated UBL XML, cannot call the JoFotara API, cannot carry the returned UUID, and cannot reconcile Sales tax, General tax, and Special tax the way the ISTD schema expects. Teams end up re-keying every invoice into a government portal by hand, which is slow, error-prone, and impossible to audit at volume.

ECOSIRE builds a proper Frappe app that closes that gap end to end. We ship it as a real app in your bench (its own module, not loose customizations), so it upgrades cleanly and is fully reversible. The core is an ISTD-compliant UBL generator that maps ERPNext's Sales Invoice, Customer, Item, and Sales Taxes and Charges data onto the JoFotara invoice schema, including the Sales/General/Special tax categories, buyer tax identifiers, and rounding rules. A hooks.py on_submit doc event (with an optional manual "Submit to JoFotara" action for controlled rollouts) signs and posts the UBL to the JoFotara API, handles the clearance response, and writes the returned invoice UUID, QR payload, and submission status back onto the Sales Invoice via dedicated custom fields. The QR is rendered into your print format so the customer-facing PDF carries the official mark.

Under the hood the integration is built the Frappe way. Credentials and the environment toggle (sandbox vs production ISTD endpoints) live in a single settings DocType with encrypted password fields and permissions locked to an accounting/compliance role profile. A JoFotara Submission Log DocType records every request/response, HTTP status, UUID, and error detail so failures are diagnosable instead of silent. Whitelisted server methods expose submit, re-submit, and status-check actions that your users trigger from the form or that we call over the Frappe REST API; a scheduler event sweeps invoices left in a pending or failed state and retries or flags them for review. Client scripts surface status badges and block invalid submissions before they reach the government system. Credit notes / returns are mapped to the corresponding JoFotara cancellation flow where the ISTD rules allow it.

Because this is build-to-order, nothing ships blind. We start from your actual chart of accounts, tax templates, company tax registration, and invoice volume, confirm the exact ISTD scope that applies to you, then build against a staging copy of your site. You get the installable app source for your version, install and configuration on your environment, UAT sign-off on staging before we touch production, and a post-go-live support window. Typical delivery is one working week from confirmed scope, targeting Frappe/ERPNext v15 or v16.