Before FBR turns on production posting, most businesses must prove they can submit real invoice shapes in the sandbox. Competitors talk about “all 28 scenarios.” This guide explains what FBR sandbox scenarios are for, which cases usually break, and how to prepare without turning your finance team into full-time API developers.

What sandbox scenarios actually are

Sandbox is a test environment that mirrors FBR validation rules without writing live tax records. Scenarios are prescribed test invoices - different buyer types, sale types, rates, and edge cases - that your registered activity is expected to cover. Pass them, then request production enablement.

Exact scenario lists and IDs live in FBR/PRAL technical documentation (DI API / user manual). Treat third-party “28 scenarios” blog posts as orientation, not as a substitute for the PDF assigned to your registration.

Why the happy path is not enough

Teams that only test a standard-rated B2B invoice often fail later on:

Unregistered buyers / further tax situations
Zero-rated or exempt lines
Third Schedule style goods where rates and fields differ
Reduced-rate / SRO-linked supplies
Returns, cancellations, or notes that reference a prior invoice

Those edge cases are exactly what production will throw at you in week one. See also debit & credit notes.

A practical prep checklist

Confirm which scenarios FBR/PRAL assigned for your business activity.
Clean HS codes and UOMs against reference APIs - mismatches fail validation fast.
Use software that shows readable validate errors (not only HTTP 400).
Keep evidence: scenario IDs, timestamps, success responses.
Only then chase the production token.

Sandbox vs production - do not mix tokens

Sandbox and production credentials are separate. Posting a “test” invoice with a production token is how accidents happen. Label environments in your software, and train staff which workspace is live.

How Taxora.pk fits scenario work

Taxora.pk is built around create → validate → post so you can rehearse real invoice shapes before go-live. Our go-live fee covers PRAL scenario / production onboarding support - it is required, not an optional upsell. Details on pricing; trial via WhatsApp.

FAQ

Do I need every scenario if I only sell one product?

You need the scenarios FBR assigns for your registered activity. If your real sales later expand into new sale types, you may need additional testing - plan masters accordingly.

Can my developer skip scenarios by calling the API directly?

Direct PRAL integration still requires the mandated sandbox path. Skipping it usually delays production, it does not accelerate compliance.

FBR Sandbox Scenarios Explained: What You Must Pass Before Production