FBR E-Invoicing 2026: Connect Xero, QuickBooks Online, or Excel in Pakistan

If your business already keeps its invoices in Xero, QuickBooks Online, Excel, or another accounting system, FBR digital invoicing does not necessarily mean replacing that system. The practical challenge is connecting the structured invoice data you already have to the required FBR submission workflow.

This guide explains that connection layer: what your source system needs to provide, how PRAL fits into the route, what to validate and map before sending an invoice, and how to test, submit, and keep a useful history of the result. It is an operational overview, not tax or legal advice. Confirm current scope, dates, and procedures in the official FBR documentation and the applicable notifications before relying on this guide.

#What FBR digital invoicing changes

For a notified or otherwise covered taxpayer, an invoice is not only an accounting record. Relevant invoice data must be prepared in the format required by the applicable FBR digital invoicing documentation and submitted through the designated integration route. The exact fields, timing, taxpayer categories, and procedures can change, so do not treat a fixed industry list or a third-party checklist as a substitute for the current rules.

The important distinction is between:

• Your accounting system: where customers, products, invoices, tax codes, and totals are created.
• The FBR submission format: the structured data and validation rules that apply when covered invoices are reported.
• The connection layer: software that maps the first system to the second, validates the result, submits it, and records the response.

#PRAL's role in the workflow

PRAL (Pakistan Revenue Automation Limited) acts as the licensed integrator identified in the digital invoicing rules and provides the API connectivity route used for the submission exchange. FBR remains the tax authority: FBR notifications, rules, and official documentation determine who is covered and what taxpayers must do.

That distinction matters. PRAL's API response is part of the technical submission workflow; it is not a replacement for the taxpayer's responsibility to issue accurate invoices, apply the correct tax treatment, or confirm its obligations with FBR. Start with the FBR Digital Invoicing User Manual, the FBR Technical Documentation for the DI API, and the FBR IRIS portal.

#Connecting the accounting software you already use

The connection method depends on where the invoice data lives. In every case, the goal is to preserve the source invoice while producing a complete, correctly mapped FBR payload.

#Xero

With Xero, an integration can use an authorised connection to bring invoice data into the compliance workflow. The finance team can continue creating invoices in Xero while checking the fields needed for FBR submission in the connection layer. See the Xero to FBR integration page or the accounting connection guide for the setup sequence.

Before connecting, review your Xero contact details, item descriptions, tax rates, invoice numbering, and product classifications. A successful OAuth connection does not make incomplete source data compliant by itself; the invoice still needs review and mapping.

#QuickBooks Online

QuickBooks Online follows the same general model: authorise the connection, select or import the relevant invoices, review the mapped fields, and test representative cases before production submission. The QuickBooks Online integration page covers the product workflow, while the getting started guide provides the broader setup context.

Desktop accounting products and other ERPs can often use the export route instead. Confirm that the export contains the fields needed by the current FBR format rather than assuming that an accounting connection alone will supply them.

#Excel, CSV, and other structured exports

If your system can export a spreadsheet or CSV, you can use that structured data as the source for a submission workflow. This is different from uploading a screenshot or a PDF: each invoice field needs to be available as data that can be mapped and checked.

The Excel import workflow is useful when invoices are maintained in spreadsheets or exported from a system without a direct connector. Prepare consistent columns for seller and buyer details, invoice identifiers and dates, line descriptions, quantities, values, tax information, and product classifications. Use the CSV and accounting connection guide to check the expected import process.

#The checks to complete before submission

Connecting a source system is only the first step. A reliable workflow separates source-data review from submission and checks each invoice before it is sent.

#1. Business and party details

Verify the seller profile and the buyer information required for the applicable invoice type. This may include NTN, STRN, CNIC, registration status, addresses, and other identifiers. Use the current FBR schema and your tax adviser’s guidance to determine which fields apply; do not fill unknown values with placeholders.

#2. Invoice and line-item data

Check invoice number, issue date, quantities, unit prices, discounts, descriptions, totals, and the relationships between line totals and invoice totals. Product or service classifications, including HS codes where required, should be reviewed rather than copied blindly from an old template.

#3. Tax mapping

Accounting software tax codes are not automatically the same as the categories expected by FBR. Map each source tax code or rate to the applicable FBR value, and document how you handle zero-rated, exempt, withholding, or other special cases that apply to your business. The tax mapping guide covers this configuration step in more detail.

TaxConnect can help surface missing fields, unsupported values, and inconsistent calculations before submission, but the taxpayer or its adviser remains responsible for deciding the correct tax treatment. Keep the mapping under review when FBR guidance, products, or rates change.

#4. Schema and calculation validation

Pre-submit validation should check required fields, formats, identifiers, line calculations, tax calculations, totals, and the shape of the payload. It can catch avoidable errors before the invoice reaches the submission endpoint. It cannot guarantee that FBR will accept every invoice or decide whether the underlying transaction is correctly treated for tax purposes.

#Sandbox testing before production

Use the available sandbox or test environment before switching to production. A useful test set includes:

• A normal taxable sale with several line items.
• Different customers and identifier types used by your business.
• Discounts, multiple tax codes, and rounding cases.
• Exempt or zero-rated transactions where relevant.
• An intentionally incomplete invoice, to confirm that errors are visible and actionable.
• An Excel/CSV import if your live workflow uses exported data.

Compare the returned response with the source invoice, correct mapping or data issues, and repeat the test. Sandbox acceptance is evidence that a test payload passed the test route; it is not a blanket approval of every future invoice. The sandbox testing guide explains the practical sequence, and the official FBR API documentation remains the authority for technical requirements.

#Production submission and audit history

After the business profile, mappings, and test cases are ready, configure the production credentials described in the current documentation. The connection layer should make it clear whether an invoice is awaiting validation, ready to submit, submitted, accepted, or rejected, and should preserve the response when the submission route provides one.

TaxConnect sits between your accounting source and the FBR/PRAL submission route. It is software for importing or connecting invoice data, validating it, submitting it through the configured route, and keeping the workflow history. It does not replace FBR, PRAL, IRIS, your accounting system, or your responsibility for the invoice.

An audit history is most useful when it lets your team trace:

• The source invoice and the time it entered the workflow.
• The mapping and validation result used before submission.
• The submission timestamp, environment, and returned status.
• Any error code or message that needs correction and resubmission.

Keep your own accounting and tax records as required. A submission log helps explain what happened technically; it does not by itself prove that every tax position or record-keeping obligation has been satisfied.

#How TaxConnect fits

TaxConnect is a software layer for businesses that want to keep their existing accounting workflow while preparing invoices for FBR digital invoicing. Depending on your source, you can:

• Connect Xero or QuickBooks Online instead of re-entering every invoice.
• Import Excel or CSV data from a desktop system or structured export.
• Map source fields and tax codes to the required submission fields.
• Validate data and calculations before sending it to the configured FBR/PRAL route.
• Test representative invoices in sandbox before using production credentials.
• Review submission statuses and maintain an audit history for the integration workflow.

If you are comparing approaches, the FBR e-invoicing comparison sets out the trade-offs between manual filing, custom development, other integrators, and a connection layer. For implementation steps, start with getting started, then review IRIS setup, sandbox testing, and production token setup.

#A practical readiness checklist

Before production submission, confirm that you have:

1. Checked whether the business is currently notified or otherwise covered, using the latest FBR guidance.
2. Confirmed the seller profile, buyer fields, invoice numbering, dates, classifications, and tax mappings.
3. Connected Xero, QuickBooks Online, or an export with the required structured fields.
4. Validated representative invoices and corrected the errors found.
5. Tested the real workflow in the available sandbox environment.
6. Configured production credentials only after the test results and business review are complete.
7. Confirmed how your team will monitor responses, correct rejected invoices, and retain accounting and tax records.

#Sources and limitations

• FBR Digital Invoicing User Manual
• FBR Technical Documentation for DI API
• FBR website
• FBR IRIS portal
• PRAL

This article is informational only. It does not constitute tax, legal, or regulatory advice, and it does not guarantee acceptance, compliance, availability, or a particular response time. FBR requirements, technical documentation, scope, deadlines, and procedures can change. Confirm the current position with FBR and the official documentation before submitting live invoices.

---

Published 13 July 2026. Last reviewed 15 August 2026 by TaxConnect Team. Tax regulations and technical requirements are subject to change.