Finance teams running ERPNext in Pakistan hit a wall every filing cycle: ERPNext's stock tax templates can hold a 17% sales-tax rate, but they know nothing about FBR's monthly sales-tax return, the Annexure-A/B/C layout of the IRIS portal, further-tax on unregistered buyers, the Sixth/Eighth Schedule reduced rates, or the section-by-section withholding matrix under the Income Tax Ordinance. Add SRB (Sindh) and PRA (Punjab) services tax with their own rates, jurisdictions, and return formats and the reality is that most teams end up rebuilding the whole thing every month in spreadsheets, keying CNIC/NTN and buyer status by hand, and reconciling against the general ledger after the fact. Errors here are not cosmetic — a wrong further-tax flag or a missed WHT section is a real compliance and cash exposure.

We build a proper Frappe app — its own module, DocTypes, and hooks.py doc events — installed into your ERPNext v15 or v16 bench, that models FBR and provincial rules natively instead of bolting them onto tax templates. Concretely: buyer/vendor registration status (registered / unregistered / active-taxpayer-list) and NTN/STRN/CNIC live as validated fields on Customer and Supplier; a Tax Profile DocType maps each item or item group to its schedule, rate, and further-tax treatment; and server-side hooks on Sales Invoice, Purchase Invoice, and Payment Entry validate/on_submit compute output tax, input tax, further tax, and the applicable WHT section as documents are posted — so the numbers are correct at source, not patched later. A FBR Sales Tax Return DocType aggregates a filing period into Annexure-C (sales) and Annexure-A/B (purchases/imports) rows, and a WHT Statement DocType assembles withholding by section and payee for the monthly/quarterly statement.

Reporting and export are where the hours actually go, so we build them as first-class outputs. Query Reports and Report Builder views reconcile every computed figure back to the ERPNext GL and the ledger, and whitelisted export methods (@frappe.whitelist(), reachable over the Frappe REST API) produce the IRIS-ready annexure files — CSV/Excel in the exact column order and code lists the portal expects, plus challan-friendly summaries. Client Scripts add guardrails in the UI (e.g. blocking submission when a registered buyer is missing an STRN, or flagging a further-tax mismatch), and Scheduler Events can pre-stage the period return and email a pre-close checklist to the finance role before the filing deadline. Everything respects ERPNext permissions: a dedicated Role and Role Profile keep return preparation and submission scoped to the right people, with the standard audit trail intact.

Because every business's item catalogue, buyer mix, and provincial exposure differ, this is delivered build-to-order rather than as a generic marketplace download. We start with a short scoping call, confirm the schedules, sections, and provinces in play, and then build against your actual chart of accounts and tax setup. Typical delivery is one working week from confirmed scope. You get the installable source for your version, UAT on a staging bench with a rollback plan, install and configuration on your environment, documentation and a training session for your finance team, a post-go-live support window, and full handover of the git repository so you own what we built.