Which FBR integrations does E-Khata Cloud support?

Three, each configured separately: FBR Digital Invoicing for sales-tax-registered businesses selling goods, FBR Tier-1 POS for large retailers with per-outlet POS IDs, and Punjab Revenue Authority (PRA) invoicing for services. Other provincial bodies are not integrated today.

Can it check whether my buyer is an active taxpayer?

Yes. Enter the buyer's NTN or STRN on the party record and E-Khata looks up their registration with FBR and checks the Active Taxpayer List. Filer status is shown on the party and used when tax is calculated.

Where do HS codes and units of measure come from?

From FBR. The product form searches FBR's HS code list directly, and the unit picker offers the 32 units FBR publishes, narrowed to the ones FBR permits for the chosen HS code. SRO schedules, SRO items, sale types and provinces are resolved from FBR's reference endpoints as well.

What happens if FBR rejects an invoice?

The invoice moves to failed in the queue with FBR's response and a plain-language explanation of the error mapped from FBR's error code. You fix the invoice and file again. Most rejections are caught before filing by the preflight checklist on the invoice.

Can I test against the FBR sandbox first?

Yes. Each integration holds separate sandbox and production credentials, and Test Connection is built so it can never file a real record. You can also try the free FBR Scenario Tester on this site, which runs the same payload builder against FBR's sandbox.

Can a filed invoice be edited?

Once FBR has accepted an invoice it locks in E-Khata, and an attempt to edit it explains why and what the correct path is. Corrections go through a return or credit note, which is filed to FBR through the same queue.

Are sales returns reported to FBR?

Yes. A return recorded against a filed invoice is reported as a credit note referencing the original, through the same preview and confirmation. Your Sales Tax Register (Annexure-C) and output tax stay consistent.

Does it produce the sales tax annexures?

Yes. The Sales Tax Register (FBR Annexure-C), Purchase Tax Register (Annexure-A), WHT Statement and a tax-wise summary are all in the report library and built from the same posted documents.

Tax & compliance

FBR Digital Invoicing That a Person Approves Before It Files

E-Khata Cloud is wired into FBR's own APIs, not just the posting endpoint. It looks up HS codes, checks whether your buyer is an active filer, narrows units to what FBR allows, and lists every reason FBR would reject an invoice before you send it. Then it shows you the exact payload and waits for you to press File. Nothing is filed behind your back.

Book a free demo See it in action

FBR Digital Invoicing in E-Khata Cloud is a review-then-file system. Sales invoices are prepared with the tax metadata FBR requires, checked against FBR's live reference data, and placed in a queue where a person opens the payload preview, passes a disclaimer, and files. The returned Invoice Reference Number and QR code print on the invoice, returns file as credit notes, and every attempt is logged against the document. Three integrations are supported, each configured on its own: FBR Digital Invoicing, FBR Tier-1 POS, and the Punjab Revenue Authority.

Updated September 2026

Three integrations, one queue

FBR is not one thing. Federal Digital Invoicing, the Tier-1 POS integration for large retailers, and provincial invoicing for services under the Punjab Revenue Authority are three separate systems with three separate endpoints, credentials and rules. E-Khata treats them as three integrations, each with its own settings card, its own token, its own POS ID where one is required, and its own sandbox. What they share is the review queue, so your team learns one screen.

FBR Digital Invoicing (DI) for sales-tax-registered businesses selling goods.
FBR Tier-1 POS for retailers integrated under the Tier-1 regime, with per-outlet POS IDs.
PRA for services taxed by the Punjab Revenue Authority, configured separately from federal filing.
Sandbox URL and token per integration, so you practise against the right environment.

Nothing is filed behind your back

Saving an invoice does not send it to FBR. It appears on the File with FBR screen as ready. A person opens the payload preview and sees the exact data that will go to FBR, field by field. A disclaimer gate asks them to confirm they have checked it. Only then is the invoice queued, and only rows a person explicitly queued are ever sent. Every business we have spoken to wanted this, because a wrong filing is far more expensive than a delayed one.

Queue statuses: ready, queued, posting, posted, failed. Only queued and posting move on their own.
Single or bulk filing, both behind the same preview and confirmation.
A timeout does not auto-retry, because FBR may already have received the filing. You decide.
Filing is a separate permission from creating invoices, so a junior can bill and a senior can file.

We check the buyer with FBR before you bill them

Type a buyer's NTN or STRN on the party record and E-Khata asks FBR who they are and whether they are sales-tax registered. It also checks the Active Taxpayer List, so you know whether the buyer is a filer before the invoice is raised, which changes the tax that applies. Buyer identity follows Pakistani rules exactly: an NTN is seven characters and can contain a letter, a CNIC is thirteen digits, and neither is silently mangled.

Registration lookup against FBR for NTN and STRN.
Active Taxpayer (filer) status, shown on the party and used in the tax calculation.
Unregistered buyers are handled correctly, including the further tax cases.
Buyer province resolved from FBR's own province list.

HS codes, units and SROs come from FBR, not from a spreadsheet we typed

The product form searches FBR's HS code list directly, so every item carries a code FBR recognises. Units of measure are pulled from FBR and, once an HS code is chosen, the unit picker narrows to only the units FBR permits for that code and fills the unit in automatically when only one is legal. SRO schedules and SRO items, sale types, provinces and published tax rates are all resolved from FBR's reference endpoints.

HS code search across FBR's published list, from inside the product form.
32 FBR units of measure, narrowed per HS code, with a product-level override.
SRO schedule and SRO item pickers for exemptions and notifications.
Sale type resolved from FBR's transaction type list, per line, with the scenario taking precedence.

Preflight: every rejection reason, before you submit

Before an invoice can be queued, E-Khata runs the same checks FBR will run and lists what is missing or wrong as a checklist on the invoice: an item without an HS code, a unit FBR does not accept for that code, a buyer ID in the wrong shape, a missing province, a scenario mismatch. Each issue links to the field that fixes it. You correct the invoice, not the rejection.

Issues shown on the invoice and in the queue, with plain-language help for each.
FBR's own error codes mapped to explanations your staff can act on.
The payload builder reproduces 27 of FBR's 28 published scenarios field for field.
The free FBR Scenario Tester on this site runs the same builder against FBR's sandbox.

Practise on the sandbox, then go live

Each integration holds a sandbox token and a production token separately. Test Connection is built so it can never file a real tax record, and the sandbox and production endpoints are kept apart structurally, not by a checkbox someone could tick by mistake. A business can run its first weeks of filings against the sandbox, compare the responses, and switch to production when the accountant is satisfied.

Separate sandbox and production credentials per integration.
Test Connection verifies the credential without filing anything.
Tokens are stored encrypted and are write-only once saved.

Filed invoices lock, and every attempt is logged

Once FBR accepts an invoice, it locks. An attempt to edit it explains why and what the correct path is, instead of failing silently or letting the books drift from what FBR holds. Every filing attempt, every FBR response and every error is recorded against the document in a filing log, with the status shown on the invoice list and in the queue.

Filed-invoice guard with an explanatory dialog.
Per-document filing log: attempt, response, error, user, time.
FBR status badge on the invoice list, refreshed while a filing is in flight.

Returns file as credit notes so your annexures tie

A sales return recorded against a filed invoice is reported to FBR as a credit note through the same queue, with the same preview and confirmation. Your output tax, the Sales Tax Register (Annexure-C) and the return itself all agree, because they come from the same posted documents.

Credit notes reference the original filed invoice.
Sales Tax Register (Annexure-C) and Purchase Tax Register (Annexure-A) built from the same data.
WHT statement and tax-wise summary alongside.

How a filing happens

Set up the integration
Settings, then Integrations, then FBR. Enter the sandbox and production tokens, the default scenario, seller identity, and, for Tier-1 POS, the POS ID. Test Connection confirms the credential without filing anything.
Prepare products and parties
Give each product an HS code and an FBR unit from the Tax tab. Add NTN, STRN or CNIC to each buyer and let E-Khata check registration and filer status with FBR.
Bill as normal
Raise the sales invoice the way you always do. The preflight checklist on the invoice tells you if anything FBR needs is missing.
Review and file
Open File with FBR. Preview the exact payload, confirm the disclaimer, and file, singly or in bulk. Watch the status move to posted.
Print and report
The IRN and QR code print on the invoice. Returns file as credit notes. The Annexure-C register is ready for the return.

27 of 28

FBR's published Digital Invoicing scenarios reproduced field for field by the payload builder

Who it is for

Sales-tax-registered wholesalers

High invoice volume with registered and unregistered buyers mixed. Filer status per buyer, bulk filing from the queue, and credit notes for returns.

Tier-1 retailers

Per-outlet POS IDs, the Tier-1 integration configured separately from DI, and receipts that carry the returned reference.

Manufacturers and exporters

HS codes on every finished product, SRO items for exemptions, and the scenario coverage that manufacturing invoices need.

Service businesses in Punjab

PRA invoicing for services, configured on its own token and endpoint, reviewed in the same queue as everything else.

Frequently asked questions

No, by design. Saving an invoice places it in the File with FBR queue as ready. A person previews the exact payload, confirms a disclaimer, and files. Only invoices someone explicitly queued are ever sent, and a timeout is never retried without a person deciding, because FBR may already have received it.

Explore more of E-Khata

FBR Digital Invoicing: who must comply and why Free FBR Scenario Tester Guide: FBR Digital Invoicing Guide: FBR Tier-1 POS integration Guide: PRA invoicing for services Sales Accounting and tax registers Pricing

See how your business runs on E-Khata.

30-min Zoom or WhatsApp call. We'll walk you through E-Khata with examples that match your business type.

Zain Gohar

Co-founder, E-Khata Cloud

“I or my co-founder personally join every demo call.”

Book a 30-min call →

Or message us on WhatsApp: +92 300 1676722 (we reply within 1 hour).