Pakistan FBR Digital Invoicing (IMS)

ECOSIRE builds this as a proper Frappe app (its own installable module with a versioned git repo), not a pile of loose customizations. We add custom DocTypes such as FBR Settings (single DocType holding your NTN/STRN, environment endpoints, licensed-integrator token, and certificate references) and an FBR Invoice Log child/linked DocType that records every request payload, FBR response, returned IRN, and status per invoice. Custom fields for irn, fbr_qr_code, fbr_status, and fbr_submission_datetime are attached to Sales Invoice, POS Invoice, and Purchase Invoice so the data lives on the native documents you already work in.

Technically, submission is driven by hooks.py document events — on_submit of a Sales Invoice enqueues a background job (via frappe.enqueue, so the cashier is never blocked) that calls the FBR IMS endpoint through a whitelisted server-side method and stores the IRN and QR on the document. Failed or offline submissions are caught, logged, and retried by a scheduler_events hook (a periodic worker that sweeps fbr_status = "Pending" records), so a dropped connection at the counter never means a lost invoice. B2B and B2C, sale and purchase flows are all recorded in real time. Client scripts surface the FBR status and QR directly in the form, and the QR is embedded in the ERPNext print format for the customer receipt. Access is governed by a dedicated role profile so only authorized users can change FBR Settings or re-submit. Everything is reachable over the Frappe REST API for your own reporting, and we integrate cleanly with a licensed integrator / PRAL-style gateway where your rollout requires one.

Because this is build-to-order, nothing is auto-downloaded. We start with a short scoping call to confirm your FBR notice category, integrator, invoice types, and ERPNext version, then build against a staging copy of your instance. Typical delivery is 2 to 4 weeks from confirmed scope. You get UAT sign-off on staging with a documented rollback plan before we touch production, followed by installation, a training session, and a post-go-live support window. You keep the full source in a git repository we hand over — no black box, no lock-in.