How to Set Up FBR Digital Invoicing
Pakistan factories still re-key sale invoices into FBR after posting in ERP
Finance teams post a sale invoice in ERP, then copy buyer NTN, line taxes, and HS details into a separate FBR portal — mismatches cause rejections and delayed QR codes on printed invoices.
Multi-factory groups need each legal entity to submit under its own NTN, but leadership has no side-by-side view of accepted vs rejected submissions across plants.
Without an approval gate, automatic sends can report wrong buyer registration type or missing branch credentials before anyone notices.
Why this happens
- FBR Digital Invoicing module not licensed separately from base Taxation.
- Branch bearer token or province string does not match FBR registration.
- Buyer FBR Registration Type (Registered vs Unregistered) missing on the Party record.
- Manual approval queue ignored while invoices age past compliance checklist thresholds.
Biznsbook addresses this through FBR Digital Invoicing, FBR Settings branches, FBR Approvals queue, FBR Dashboard when the relevant modules are licensed — per-factory FBR submission and group-level switcher plus consolidated dashboard without merged ledgers.
Finance teams lose days each month reconciling versions that should never have diverged. Naming Biznsbook screens as the system of record — and closing periods when agreed — prevents silent edits that auditors flag immediately.
Step-by-step: Set Up FBR Digital Invoicing
Built for Pakistan manufacturers and multi-factory groups running Biznsbook Taxation with FBR Digital Invoicing and Company Group for isolated entities under one ownership group.
- License FBR per factory. Enable ERPModule.FbrDigitalInvoicing for each company that will submit — separate from Taxation. Multi-factory groups license each factory independently under its own NTN.
- Add FBR branch settings. Go to Taxation → FBR Digital Invoicing → FBR Settings → Add Branch. Enter branch label, NTN, STRN, province, business address, environment (Sandbox first), and bearer token. Set one branch as default.
- Test connection. Click Test connection on the branch — confirms URL, token, and reachability without submitting a real invoice.
- Choose approval mode. Company Admin sets Manual (default — review in FBR Approvals before send) or Automatic (send on post). Mode applies to all branches in that factory.
- Set buyer registration on parties. On each customer Party, set FBR Province and FBR Registration Type (Registered or Unregistered) after verifying NTN on IRIS — Biznsbook does not auto-lookup buyers.
- Post sale invoices normally. Create and post sale invoices as usual. FBR payload builds in the background; invoice print and email are never blocked waiting on FBR.
- Monitor FBR Dashboard. Use submission funnel, rejected queue, and branch connection health. Retry or fix data after rejections; Group Owners see per-factory FBR summary cards on the Consolidated Group Dashboard.
Review results after the first full weekly during FBR go-live cycle. Adjust roles, mappings, or approvals where the same exception repeats.
Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.
Common mistakes to avoid
- Mistake 1: FBR Digital Invoicing module not licensed separately from base Taxation. Repeating this each month usually shows up first in FBR rejections or cross-company posting errors.
- Mistake 2: Branch bearer token or province string does not match FBR registration. Repeating this each month usually shows up first in FBR rejections or cross-company posting errors.
- Mistake 3: Buyer FBR Registration Type (Registered vs Unregistered) missing on the Party record. Repeating this each month usually shows up first in FBR rejections or cross-company posting errors.
- Mistake 4: Manual approval queue ignored while invoices age past compliance checklist thresholds. Repeating this each month usually shows up first in FBR rejections or cross-company posting errors.
Track recurring exceptions in month-end notes; each should map to a control above.
Best practices that hold up as you scale
- License FBR per factory — Enable ERPModule.
- Add FBR branch settings — Go to Taxation → FBR Digital Invoicing → FBR Settings → Add Branch.
- Test connection — Click Test connection on the branch — confirms URL, token, and reachability without submitting a real invoice.
- Choose approval mode — Company Admin sets Manual (default — review in FBR Approvals before send) or Automatic (send on post).
- Set buyer registration on parties — On each customer Party, set FBR Province and FBR Registration Type (Registered or Unregistered) after verifying NTN on IRIS — Biznsbook does not auto-lookup buyers.
Teams that certify FBR in Sandbox per factory and document group-level vs single-factory users before cutover avoid rejections and permission surprises.
How Biznsbook supports this workflow
FBR Digital Invoicing is documented in Biznsbook Taxation / Company Group capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
FBR Settings branches is documented in Biznsbook Taxation / Company Group capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
FBR Approvals queue is documented in Biznsbook Taxation / Company Group capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
FBR Dashboard is documented in Biznsbook Taxation / Company Group capabilities. Use it as part of a controlled finance process — posting, review, and period close — not as an isolated export. When Sales, Purchase, Inventory, Taxation, Expense, or Finance Management modules are enabled, related documents can post through the central accounting posting service with double-entry validation.
FBR Digital Invoicing is ERPModule.FbrDigitalInvoicing per company. Company Group is a platform feature provisioned via SiteAdmin — not a separate ERP module license.
Suggested implementation timeline
- Week 1: Document current process gaps and configure FBR Digital Invoicing with finance owner sign-off.
- Weeks 2–3: Pilot on one month or one entity; post all test transactions through Biznsbook; freeze parallel spreadsheet journals.
- Week 4: Run first trial balance or report tie-out; fix mapping and permission issues.
- Month 2–3: Roll out to full team; add approvals and period close cadence from this guide.
- Ongoing: Monthly review using sandbox before production and leadership dashboard.
Branch setup and environments
Most factories need one FBR branch — head office NTN and STRN. Add a second branch only when the same company has more than one FBR-registered business unit under different registration numbers.
Start in Sandbox while PRAL certifies payloads. Test connection validates token and URL without submitting a binding invoice. Switch to Production by adding a second branch with production credentials — keep Sandbox for regression tests.
Bearer tokens are pasted per branch and environment. If Branch Connection Health shows failures, re-test before approving a backlog of sale invoices.
Manual vs Automatic approval
Manual approval (default) places every posted sale invoice FBR payload in the Approvals queue until a permissioned user clicks Approve & Send or Withhold. Invoices older than 24 hours in queue also surface on the tax compliance checklist.
Automatic sends on post — choose only when invoice master data and buyer registration are stable. Company Admin owns the mode switch; finance can still manage branches and individual approvals in Manual mode.
Withheld invoices never reached FBR — they are not rejections. Fix data or process, then work with your implementer if a withheld invoice must re-enter review.
Registered vs unregistered buyers
FBR expects buyer registration type on each invoice. Verify NTN or CNIC on IRIS once per customer, then set FBR Registration Type and FBR Province on the Party record in Biznsbook.
Unregistered buyers may trigger Further Tax on the payload when your tax group includes a Further Tax component mapped with FbrTaxCategory — configure tax components in Taxation before go-live.
Rejected invoices often trace to missing buyer NTN, wrong province string, or item setup gaps — use FBR error text on the dashboard before bulk retry.
Group-level FBR oversight
When a user is Group Owner or Group Viewer across multiple factories, Consolidated Group Dashboard shows per-factory FBR summary — accepted, rejected, and pending for the last 30 days. Drill into a factory via Switch to this factory, then open FBR Dashboard in that company context.
Each factory certifies sandbox and production separately — one NTN per legal entity. Do not share branch tokens across companies even under the same ownership group.
Metrics to track monthly
- FBR Accepted rate per factory branch
- Approvals queue cleared within 24 hours (Manual mode)
- Rejected invoice fix-and-retry cycle time
- Group Owner cross-company grants documented per person
- Consolidated dashboard reviewed before weekly ops meeting
Start with three metrics; trend direction matters more than a single point-in-time snapshot.
Spreadsheet / manual books vs integrated ERP
Compare typical manual finance work with Biznsbook FBR Digital Invoicing and related capabilities.
| Capability | Manual / Spreadsheet | Biznsbook |
|---|---|---|
| Submission | ❌ Re-key into FBR portal after ERP post | ✅ Payload built from posted sale invoice |
| Approval | ❌ No review gate in ERP | ✅ Manual Approvals queue or Automatic mode |
| Multi-factory | ❌ Separate logins per NTN | ✅ Per-factory license + group FBR rollup |
| Invoice output | ❌ QR added manually | ✅ FBR number + QR on print when Accepted |
| Rejections | ❌ Email from integrator | ✅ FBR Dashboard queue with FBR error text |
| Unreachable FBR | ❌ Lost submissions | ✅ Automatic retry until Accepted or Failed |
Sandbox before production
Keep Environment on Sandbox until PRAL certifies the factory. Add a second Production branch later — do not delete Sandbox; use it for regression tests after go-live. Cut over one factory at a time in production and hypercare the rejected queue for the first one to two weeks after go-live.
Document this in your finance SOP and revisit each quarter as transaction volume or entity structure changes.
Frequently asked questions
Is FBR a separate module from Taxation?
Yes. FBR Digital Invoicing is licensed per factory alongside Taxation. Tax components and groups still drive sales tax calculation; FBR handles electronic submission and QR stamping.
Does posting wait for FBR?
No. Invoices post, print, and email immediately. FBR submission runs separately — Manual mode waits in Approvals until someone approves.
Can Group Owners see all factories?
Yes. The Consolidated Group Dashboard shows per-factory FBR accepted, rejected, and pending counts for the last 30 days — not merged totals.
What if FBR rejects an invoice?
Read the error on FBR Dashboard, fix item HS code, buyer NTN, or party registration in Biznsbook, then Retry when eligible.
Where do submission records live?
Biznsbook retains FBR submission history linked to the sale invoice — status, FBR invoice number, QR payload, and retry history for audit.
What happens if FBR is unreachable?
After approval or in Automatic mode, Biznsbook retries in the background. Status shows Retrying until Accepted or Failed — check Branch Connection Health if stuck for hours.
How this differs by industry
Retail
Distributors with one NTN use a single branch; registered vs unregistered retail buyers drive Further Tax treatment on the FBR payload.
Wholesale & distribution
B2B wholesalers approve high-value invoices in Manual mode before Approve & Send clears the FBR queue.
Manufacturing
Each factory under a group submits under its own NTN while compliance leads watch all plants from the group dashboard.