FBR POS integration and digital invoicing in Pakistan

What FBR POS integration costs in Pakistan

Published market pricing for adding FBR e-invoicing to a POS or ERP already in production sits at PKR 150,000 to 400,000. That is a wide band for what sounds like a single job, and the width is informative. At the low end sits one till in one branch, running a product with a documented extension point, selling for cash. At the high end sits a chain with tills across several cities, mixed payment methods, returns that have to be reported against something already transmitted, and a back office expecting the reported figures to reconcile to the general ledger.

Count the tills, then count the branches, and price the second number rather than the first. Twenty tills in one shop share a network, a local queue and one person watching the failure screen. Four tills across four cities are four network arrangements, four sets of counter staff to train and four places where somebody has to notice that transmissions stopped at eleven this morning. Branch count moves this quotation far more than till count, which is the opposite of what buyers assume.

Three items belong in any comparison because they are what a cheap quotation leaves out. Offline queueing with retry, so trading continues when the link drops. Correct handling of returns, voids and credit notes against invoices already reported. And a daily reconciliation between what the till took, what was reported and what the ledger shows. Where the POS is old or closed, add an assessment of whether it can be extended at all. Everything here is market pricing. A real figure follows discovery, once we have seen the POS product, the branch list and the payment methods in use.

• Adding e-invoicing to an existing POS or ERP quoted in the market at PKR 150,000 to 400,000
• Branch count priced ahead of till count, since each site is its own operational problem
• Offline queueing, retry and a failure screen with a named owner included in scope
• Returns, voids and credit notes against reported invoices handled rather than deferred
• Daily reconciliation between takings, reported invoices and the general ledger

How long FBR POS integration takes

Reported figures put FBR integration at six to twelve weeks where the system underneath it is already stable, and that holds up well in practice. The build itself is short. What fills the calendar is registration and credentials, sandbox testing against the real endpoint behaviour, receipt layout changes that have to be approved by somebody in the business, counter staff training, and a pilot in one branch before anything is rolled out to the rest.

Stability of the system underneath is the condition that matters in that sentence. Where the POS is current, supported and has a documented extension point, six to twelve weeks is realistic. Where the till software was written years ago by somebody no longer contactable, the assessment alone takes time, and the honest answer may be that the integration is not the cheapest route to compliance. We establish that early rather than after a month of investigation billed to you.

Rollout across branches adds elapsed time that has nothing to do with engineering. Each site needs its counter staff trained on the awkward minute: what to do when the screen says failed, what to tell a customer waiting for a receipt, who to call. Piloting one busy branch through a full week, including a weekend, is worth more than any amount of laboratory testing, because a queue behaves differently from a test script.

• FBR integration reported at six to twelve weeks on a stable point of sale system
• Registration, credentials and sandbox testing completed before production traffic
• Receipt layout changes approved by the business and kept under version control
• One busy branch piloted through a full week, including a weekend, before wider rollout
• Counter staff trained on failure handling rather than only on the normal sale

Integrating the till you have or replacing it

Most retailers should extend what they already run, and we say so against our own commercial interest, because replacing working tills is an expensive way to solve a reporting problem. The test is not age. It is whether the product exposes a usable extension point, whether the supplier is still contactable, and whether the receipt layout can be changed without rebuilding the product. Where those three hold, integration is the cheaper and less disruptive route by a wide margin.

Replacement earns its place in a narrower set of cases than vendors suggest. A closed product whose supplier has disappeared, where no extension point exists and the database is undocumented. Software so old that it cannot make a modern secure connection at all. A chain running four different POS products across its branches, where integrating each one separately costs more than standardising on one. In that last case the compliance requirement is doing something useful, since it forces a decision the business had been avoiding.

Count the full cost of replacement before choosing it, because the licence is the smallest part. Hardware at every counter. Product, price and customer data migrated. Staff retrained across every branch at once. A period where takings are reconciled twice while confidence is rebuilt. Set against that, an integration to an imperfect but working till is usually the sensible answer even when it is the less elegant one.

One thing does not change either way, and it is worth stating plainly. Section 3(9A) of the Sales Tax Act requires Tier-1 retailers and other notified persons to integrate their point of sale with the FBR computerised system for real time reporting, and non compliance can mean disallowance of a substantial share of input tax adjustment, currently sixty percent. Whether your business falls inside that classification is a question for your tax adviser rather than for us. Once they confirm it in writing, we build and test to that instruction.

• An extension point, a contactable supplier and a changeable receipt layout as the three tests
• Replacement reserved for closed products, undocumented databases or a mixed till estate
• Hardware, data migration and retraining counted in any replacement comparison
• Section 3(9A) integration required of Tier-1 retailers and other notified persons
• Classification confirmed in writing by your tax adviser, then built to that instruction