Since every sales-tax-registered business in Pakistan now has to transmit invoices as they are issued, "does it do FBR" has become the first question asked of any accounting or ERP system. It is the right question, asked in a way that is too easy to answer yes to.

There are three genuinely different architectures behind that yes, and the differences show up in month three rather than in the demo.

Built into the sales module

The invoice cannot be completed without a response from FBR. Submission happens where the document is created, the verification reference is written back to the same record, and the printed copy carries it because the document and the reference are one thing.

This is the cleanest arrangement. The rule is enforced at the point of creation rather than policed afterwards, and there is one record rather than two that have to agree. It is also the hardest to retrofit, which is why vendors who did not build it this way rarely move to it later.

A middleware layer in front

The ERP posts its documents to a separate service that handles submission, retries and reconciliation, then writes the reference back.

This is the right answer when you cannot change the ERP — an older system, a vendor who has not implemented it, or a business running several systems that all issue invoices. Done well it is genuinely robust, and it has one real advantage: a single compliance layer across multiple sources beats three partial implementations.

The thing to check is what happens when the write-back fails. If the submission succeeds but the reference never reaches the ERP, you have a filed invoice your own system does not know about, and you will find out at reconciliation.

A separate system someone re-keys into

This is sold as integration and is not. Invoices are raised in the ERP, then entered again in a compliance tool or on a portal.

It works at a dozen invoices a day. At a hundred it fails, and it fails in the worst way — the two records diverge, nobody knows which is authoritative, and the discrepancy surfaces when a return is being prepared. If a vendor's answer to "how does it connect" involves a person, you are buying this.

Questions that reveal which one you are being offered

Ask these in the demo, not afterwards.

Show me an invoice being submitted, live.
Not a slide. If the demo environment cannot submit, ask why.
Can an invoice print without a verification reference?
The answer should be no, or configurable to no. If unsubmitted documents can leave the building, the control is decorative.
Where does the HS code live?
It is mandatory on every line. If the item master has no field for it, that work has not been done and it is the longest task in any integration.
How do you connect — PRAL or a licensed integrator?
Only eight companies hold integrator licences, published on FBR's own site. "We are FBR approved" from a company not on that list means something has been overstated.
What does month-end reconciliation look like?
A view of every document filed, pending and rejected, with reasons. If the answer is an export to Excel, nobody will do it.

What this should not cost

PRAL is FBR's own technology arm and is reported to integrate at no charge. That is the baseline, and a paid vendor should be able to say plainly what the fee buys — normally the work around the connection rather than the connection itself: mapping your document types, cleaning the item master, clearing the sandbox scenarios, and operating the thing afterwards.

A vendor who cannot articulate that distinction is charging for something you can get free, and it is a fair question to put to them directly.

Common questions

Does our ERP need replacing for FBR digital invoicing?

Usually not. If the ERP cannot be modified, a middleware layer handles submission, retries and reconciliation and writes the reference back. Replacing a working ERP for this reason alone is rarely justified.

What does "FBR integrated ERP" actually mean?

It can mean submission built into the sales module, a middleware layer in front, or a separate system someone re-keys into. Only the first two are integration. Ask to see an invoice submitted during the demo.

Is the HS code really mandatory?

Yes, on every line. It is the single most common cause of delay, because most item masters in Pakistan were never built with it and populating it is a data exercise rather than a software one.

Can one compliance layer serve several systems?

Yes, and it is often the better architecture for a group running different software in different companies — one place to reconcile rather than three partial implementations to chase.