Important: FBR rules, tax rates, scenario requirements and API behavior can change. Always use the latest applicable FBR requirements when configuring live transactions.
01
Product Overview
A complete digital invoicing workspace designed around FBR workflows.
FBR Invoice Software helps businesses prepare invoice data, validate it against FBR requirements, submit it, and retain the resulting invoice ID, QR code, status and audit information.
The workspace keeps important relationships visible—including HS Code, sales type, tax rate, FBR Unit of Measurement, request payload and FBR response—so users can understand why an invoice is accepted or rejected.
From registration to a production-ready environment.
Create the customer account and business profile, configure seller information and FBR environment details, then connect and verify the Sandbox environment.
Identify applicable business scenarios, complete testing, resolve data issues, configure Production, and prepare customer and product master data before live invoicing.
A daily snapshot of invoicing, package usage and compliance activity.
Use the dashboard to review the current package, renewal details, FBR environment, business identifiers, invoice statuses, customer and product counts, invoiced value, sales tax and recent activity.
Review rejected invoices and invoices waiting for submission before starting additional work.
Create reusable buyer profiles and avoid repeated data entry.
Maintain the information required for Sales Tax Registered and Sales Tax Unregistered buyers. When creating an invoice, search for a saved customer and select it to fill the available buyer information automatically.
Save products once and reuse them across invoices.
Product records can store a name, HS Code, default unit price, discount, sales type, tax rate, commercial UOM, FBR UOM and quantity conversion. Default price and discount remain adjustable at invoice level.
Reduce classification errors and make quantity reporting easier.
Enter a product name to review relevant HS Code suggestions and the related FBR UOM. Suggestions support the decision; the business remains responsible for selecting the correct classification.
Use a fixed conversion when a stable relationship exists, such as one plate equaling 0.100 KG. Use manual FBR quantity when a fixed conversion is unsuitable.
A central view of draft, validated, rejected and submitted invoices.
Use Sales Invoice for a new sale and Debit Note for an eligible adjustment to a previously verified invoice. Your internal invoice number is a business reference; the official FBR Invoice ID is returned only after successful submission.
Prepare and review invoice data before communicating with FBR.
Choose the invoice type and date, enter or generate an internal number, select the applicable sales category, choose a saved customer, and add one or more products.
Review quantities, prices, discounts, UOMs, sales type, tax rate and scenario-specific fields, then save the invoice as Draft. Draft status gives you a quality-control step before FBR validation.
Validation and final submission are separate actions.
Validate with FBR to identify incompatible HS Code/UOM combinations, tax-rate issues, missing fields or scenario-specific problems without completing final registration.
After successful validation, mark the invoice FBR Ready and submit it. A successful submission returns the official FBR Invoice ID and makes the QR code available. Request payloads and responses remain visible for troubleshooting.
Statuses distinguish Draft, Validation Pending/Failed/Success, Ready for Submission, Submission Pending, Rejected/Failed and Submitted invoices.
Invoice logs retain relevant request payloads, responses, timestamps and retry history. Retryable FBR service errors can remain pending for automatic retries after 1, 3, 8, 10, 15, 20 and 30 minutes, with manual retry where appropriate.
Turn an accepted submission into a customer-ready invoice.
After successful submission, view the FBR Invoice ID and QR code, generate or print the invoice PDF, save it for records, and share invoice information through the configured customer communication workflow.
The customer-facing invoice should use the commercial UOM while FBR reporting can use the separately configured FBR UOM.
Import larger invoice volumes with a validation step.
Download the specimen Excel file, retain its column structure, add the invoice data, upload it, and run the validation scan. Correct every highlighted issue and scan again before importing the validated records.
Use important FBR information available inside the software.
Reference data includes FBR-recognized provinces, more than 7,500 HS Codes, sales types, units of measurement and business scenarios. These references help users understand field relationships that can otherwise cause validation errors.
Identify applicable scenarios, prepare test invoices, validate and submit them in Sandbox, review each result, correct data relationships, and repeat until the required scenarios succeed.
Keep test transactions and live invoices clearly separated.
Use Sandbox for configuration, scenario testing and data-mapping checks. Use Production only for live business invoices after testing is complete. Always confirm the environment indicator and selected company before submitting.
Understand invoice consumption, validity and renewal position.
Review package name and status, renewal or validity date, invoice consumption, recent activity, environment and business-profile information on the dashboard. Confirm commercial terms from the current package or written quotation.
Confirm the company and environment, review rejected and pending work, maintain master data, create or import drafts, and review customer, product, HS Code, UOM, tax rate and quantity information.
Validate first, correct all errors, mark the invoice FBR Ready, submit it, confirm the returned Invoice ID and QR code, then generate and share the PDF as required. Use Invoice Logs for failed or pending invoices.
Use the FBR response details to fix the data instead of guessing.
For HS Code/UOM mismatches, review product mapping and reference data. For tax errors, review sales type, rate and scenario requirements. For buyer or quantity errors, check registration type, identifiers, province, UOM and conversion.
If FBR is unavailable, keep the invoice in the retryable workflow instead of creating a duplicate. For support, share the internal number, FBR Invoice ID when available, current status, response message and environment.
Use the platform as a controlled business process.
Use individual authorized accounts, restrict FBR credentials and Production access, confirm the company profile, require validation before submission, review unusual logs and maintain backups under your deployment policy.
Treat FBR payloads and responses as business and tax records. FBR Invoice Software is an independent commercial solution and is not an official FBR-owned application.
Get help with onboarding, configuration and digital invoicing.
The team can assist with onboarding, IRIS Sandbox configuration, Production configuration, scenario testing and operational guidance. Use the verified contact details on this website when requesting assistance.
