By Faubix

Does your accounting software support FBR digital invoicing?

A plain comparison of the accounting software Pakistani businesses really use. See what each one has built in for FBR, how invoices can leave it, and a checklist to test any vendor’s claim that it is “FBR-ready”.

A laptop showing an accounting dashboard

Answer first. No popular accounting software used in Pakistan sends invoices to FBR on its own. QuickBooks Online and Zoho Books have no Pakistan edition. NetSuite has no Pakistan version either. Business Central comes to Pakistan through partners, on Microsoft’s worldwide version. Tally has no Pakistan edition, and its HS code fields only come with GST features that Pakistan doesn’t use. Odoo has a real Pakistan set-up for accounts and taxes, but no FBR e-invoicing. The real difference is how easily each one lets invoices leave for a service that sends them to FBR. That decides how much work FBR digital invoicing will be for you.

The short answer

FBR digital invoicing needs things that no ordinary accounting software stores out of the box. It needs an HS code and an FBR sale type on every line, a rate in FBR’s wording, and FBR’s unit names. It needs the buyer’s registration type, and the SRO references for anything not at the standard rate. It also needs the right habits: send each invoice as soon as you create it, read FBR’s answer line by line, and never send the same invoice twice.

So the real question is not “does my software support FBR?” It is “how does my software pass an invoice to something that does?” Every system below can be connected. In some, it is a settings job. In others, it is a job for developers.

Seven systems side by side

Accounting systems compared for FBR digital invoicing
SystemPakistan set-upHow an invoice can leave itRoute to FBR
SAPDepends on the SAP product and versionBilling output, software in between, scheduled exports, message-based linksSAP stays the main record; a separate service sends invoices to FBR
OdooPakistan localization from version 15: chart of accounts, taxes, tax reportsCustom module (Odoo.sh, self-hosted), automation rules that call another system, external APIA small add-on that sends each invoice when you confirm it
TallyNo Pakistan edition; HS code fields only come with its GST featuresXML gateway on your local network: you can read from it, but it can’t send anythingPrepare invoices in bulk, or run a reader on your network
QuickBooks OnlineGlobal edition; taxes set up by handInstant alerts (webhooks) announce new invoices; REST API to read themA small add-on that acts on each alert
NetSuiteNo Pakistan versionSuiteScript, REST web services, RESTletsScripts that line up invoices and send them in the background
Business CentralPartner set-up on Microsoft’s worldwide versionAL extensions, API, Power AutomateAn extension or flow that runs when you post
Zoho BooksGlobal edition; a tax is a name and a rateWorkflow rules that call another system (higher plans), Zoho Flow, REST APIA trigger you set up to pass each invoice on for sending to FBR

Two patterns stand out. Cloud systems (QuickBooks Online, Zoho Books, NetSuite, Odoo and Business Central online) can announce a new invoice the moment you create it. That makes sending in real time easy. Tally is a desktop program, so it can only be asked; something has to keep checking it. And every system, without exception, needs the same FBR data added to it.

What “FBR-ready” should mean

“FBR-ready” gets used for anything: a module, a plug-in, a template or a promise. Whatever you are offered, inside your accounting software or beside it, ask these questions. They separate a tool that really sends invoices to FBR from a demo:

  1. Does it send the invoice data in FBR’s own format? That means header and lines, with HS code, sale type, rate in FBR’s wording, FBR unit and SRO fields. Something close to it is not enough.
  2. Where do the rate and SRO come from? FBR publishes a rate lookup based on sale type, invoice date and supplier province. A fixed 18% fails on the first reduced-rate or exempt line.
  3. Does it read FBR’s answer line by line? FBR sends a success reply (HTTP 200) even when it rejects an invoice. A reply can also look accepted overall while one line fails. A good tool treats an invoice as sent only when FBR has issued its number and every line has passed.
  4. What happens when no answer comes back? FBR does not block duplicates. A tool that simply sends again can file the same invoice twice.
  5. Does it send each invoice as soon as you create it? FBR expects each invoice to be sent when it is issued. An end-of-day batch breaks that rule.
  6. How does it handle corrections? FBR’s API has no way to edit or cancel a sent invoice. A genuine mistake is fixed inside FBR’s own system, within a 72-hour window. A tool that promises to “cancel from your ERP” is promising something FBR doesn’t offer.
  7. What does it keep? The rules ask for records that can re-create exactly what was sent, kept for six years. The FBR number alone doesn’t do that. The invoice data sent and FBR’s reply do.
  8. Who updates it when FBR changes? FBR adds and renumbers error codes and updates its technical rules. Someone has to keep up with that for as long as you invoice.

A tool that answers all eight well is FBR-ready, whatever it is called. If it can’t answer the last question, you will be maintaining it yourself.

System by system

SAP

The smart set-up keeps SAP as your main record and adds a separate service that sends invoices to FBR. That beats rebuilding every FBR rule in custom SAP code, where each FBR change means another round of SAP changes and testing. The right link depends on your SAP set-up, your volume, and whether you send invoices instantly or in batches. Read the SAP guide.

Odoo

Odoo is the only system here with a real Pakistan localization: a Pakistani chart of accounts, sales tax set-up and tax reports from version 15. That makes its taxes a good starting point for matching to FBR sale types. It still has no FBR connection. On Odoo.sh or your own server, a custom module can send each invoice to FBR when you confirm it. Odoo Online doesn’t accept custom modules. There, the link runs beside Odoo through its external API, which Odoo Online offers on its Custom plan. Read the Odoo guide.

Tally

Tally is common among Pakistani traders and distributors, and it is the hardest to connect well. It can’t send data out on its own. Its gateway has no password, so it belongs on your local network only. And a standard Pakistani company file holds no HS codes or sale types at all. There are two practical routes: prepare invoices in bulk from Tally, or run a reader on your network that checks Tally every few minutes. Read the Tally guide, and the technical traps for the person who builds the reader.

QuickBooks Online

Intuit serves Pakistan through QuickBooks’ Global edition. You set up sales tax by hand, and there is no documented field for a Pakistani tax number. Its strength is instant alerts: a small add-on hears about each new invoice almost at once and sends it to FBR within moments. Many QuickBooks users sell services, so know your tax authority first: FBR, or your province. Read the QuickBooks guide.

Oracle NetSuite

NetSuite has no Pakistan version, but its custom fields and scripts make a clean link easy. Mark each invoice for sending when it is saved, send it from a background script, and save the FBR number back on the invoice. In OneWorld, each subsidiary sends under its own NTN. Read the NetSuite guide.

Microsoft Dynamics 365 Business Central

Business Central is sold in Pakistan by partners, on Microsoft’s worldwide (W1) version, not a local one. Sending to FBR happens when you post an invoice, through an AL extension, a Power Automate flow or an outside service. FBR’s fields are added with table extensions, and the sale type is matched from your VAT posting set-up. Read the Business Central guide.

Zoho Books

Zoho Books has no Pakistan edition, so Pakistani businesses use the Global edition and set up each tax themselves. Custom fields hold what FBR needs. A workflow rule, Zoho Flow or the API starts the sending, and your plan decides which of these you get. Because the trigger is set up in settings, not written in code, a small team can connect it without a developer. Read the Zoho Books guide.

What every system shares

Whatever software you run, three jobs are the same:

  • Matching your data to FBR’s. Match tax codes to FBR sale types, items to HS codes and FBR units, and customers to registration types and provinces. You build it once, then keep it up to date. Our article on matching tax codes to FBR sale types covers it in detail.
  • A place for FBR’s answer. Keep the FBR invoice number, the status and the invoice data sent with each invoice. See what to store once FBR answers.
  • A test stage. In FBR’s test system (the sandbox), each business gets its own test scenarios. Passing them is what gets you the production token for live invoicing. No system skips this.

That is also why a service like eInvoicePro makes sense, whichever system you use. The FBR parts are the same for all seven: the invoice data format, reference lookups, line-by-line results, safe resending and FBR’s rule changes. There is little reason to build them seven different ways.

If you’re choosing new software

Don’t choose accounting software for its FBR story alone. You can add FBR invoicing to any of the systems here. The effort depends more on your data, meaning how clean your customer and product records are, than on the brand. Choose the system that fits how you sell, stock and report. Then check how easily invoices can leave it in real time.

And if you raise few invoices, you don’t need an integration yet. Create tax invoices directly in eInvoicePro’s screens and they go to FBR at once. The product and customer details you set up there carry over when you connect your accounting software later.

FAQs

Which accounting software is best for FBR digital invoicing? None has FBR invoicing built in. So the best choice is the one that fits how you run the business and lets invoices leave it easily. Cloud systems that announce new invoices make real-time sending simplest. Desktop systems like Tally need more care.

Does Odoo’s Pakistan localization include FBR digital invoicing? No. Odoo’s Pakistan localization, from version 15, covers the chart of accounts, sales tax set-up and tax reports. You add FBR e-invoicing through a module or a small add-on.

Is there a Pakistan edition of QuickBooks or Zoho Books? No. Intuit serves Pakistan through QuickBooks’ Global edition. Zoho Books’ country editions don’t include Pakistan, so Pakistani businesses use its Global edition. In both, you set up sales tax by hand and add FBR invoicing through an integration.

Can we avoid an integration altogether? If you raise few invoices, yes. Create tax invoices in eInvoicePro’s own screens and they go to FBR directly. An integration pays off when you raise many invoices, all day long, or when typing them in twice costs you hours.

How do we check a vendor’s “FBR-ready” claim? Ask where the rate and SRO come from, and whether FBR’s answer is read line by line. Ask what happens when no reply comes back, and how corrections work, since FBR’s API can’t edit an invoice. Then ask what records are kept, and who updates the tool when FBR changes its rules.

Related reading: connecting your ERP to FBR, integrator vs software and the eInvoicePro API.

Ready to simplify your FBR digital invoicing?

Join 2000+ businesses that use eInvoicePro to make invoices and send them to FBR.

Chat with us