FBR Digital Invoicing · Guide

FBR Digital Invoicing: Sandbox vs Production

FBR provides a sandbox environment for testing and a production environment for live invoices. Here is the difference, why you should test first, and how the two fit together.


Two separate environments

FBR's Digital Invoicing API exposes a sandbox environment for testing and a production environment for real, legally-filed invoices. Each is reached with its own access token.

Invoices posted to sandbox are for validation and practice only; they do not count as issued sales tax invoices.

Why you test in sandbox first

Sandbox lets you confirm that your business details, sale types, HS Codes and tax calculations all validate against FBR's rules before anything goes live.

Catching a configuration or data problem in sandbox is far cheaper than discovering it on a real invoice a customer is waiting for.

Moving to production

Once your invoices validate cleanly in sandbox, you switch to the production token and start posting live. Production returns the real FBR invoice number and QR code.

The invoice structure is the same in both environments, so a clean sandbox test gives you confidence the live post will succeed.

How Digi Invoice manages both

Digi Invoice supports both environments, so you can practise safely and then go live without changing how you work.

The same validation runs in both, meaning what passes in sandbox is what FBR accepts in production.

Start issuing FBR-compliant invoices today

Digi Invoice validates, posts and QR-stamps your sales tax invoices through FBR's Digital Invoicing API — no development required.