How ByarInvoice works
From empty workspace to FBR-ready invoices.
FBR Digital Invoicing is not a single button — it is an onboarding path plus a careful submit loop. ByarInvoice mirrors that reality: prepare your business data early, connect the fixed IP when you are ready, prove sandbox scenarios, then post production invoices only when FBR says you can.
Get ready
These steps unlock the product in the same order FBR expects — without blocking you from organizing customers and invoices while IP approval is still in flight.
- 01
Create your business workspace
Sign up once. ByarInvoice creates your login, your organization, and your membership in one step — so you land in a dashboard that already belongs to your business.
- 02
Set up the work FBR will later receive
Add your business profile details, customers, and products while FBR access is still pending. Dashboard use and FBR submission are separate: you can prepare clean data before the first live post.
- 03
Allowlist the ByarInvoice IP in FBR
Digital Invoicing is tied to a fixed public IP. You register ByarInvoice’s server IP in your FBR portal. FBR’s validation can take roughly a day to a week — we track that wait as an explicit onboarding status, not a mystery spinner.
- 04
Prove the flow in sandbox, then go live
When sandbox opens, run the scenarios that match your activity and sector. After FBR signs off, production credentials unlock. Only then can real invoices be posted — never by guessing which token or URL to use.
Every invoice, the safe way
Live submission is always two-phase: validate, then post. That protects you from “success” responses that still hide line-item errors — and keeps sandbox tokens away from production endpoints.
- 1Draft
Build the invoice from your customers and catalog with the fields FBR expects — amounts, tax, and document shape included.
- 2Validate
We call FBR’s validate endpoint first. HTTP 200 is not enough: we read header and line-item status so soft failures surface before you commit.
- 3Submit
Only after a clean validation do we post. Sandbox and production use separate tokens and URLs; the app keeps those environments from mixing.
- 4QR & record
A successful post returns an FBR invoice number. We store the raw exchange for compliance and generate the required QR for the printed invoice.
What stays under the hood
Your FBR bearer tokens never ship to the browser. Every validate or post attempt keeps a structured audit trail (without secrets) so support and compliance can see what FBR actually returned. If a submit fails, you retry deliberately from the dashboard — no silent queue guessing for MVP.