A practical guide to FBR Digital Invoicing

What FBR Digital Invoicing is

FBR Digital Invoicing brings reporting into the sales invoice workflow. The business reports structured sales invoice data to FBR alongside the document sent to the buyer. The invoice record, tax treatment and authority response become parts of the same operational process.

A readable PDF remains useful, but reporting needs individual fields: seller and buyer identity, scenario, classification, quantity, rate and amounts. These fields must describe the supply consistently. A correct-looking total cannot compensate for an incorrect identifier or sale type.

Readiness means knowing where invoice information comes from, who reviews it, how validation errors are corrected and where the acknowledgement is retained. Finance and IT teams need a shared view of what has been posted and what still needs action.

Check whether your business is in scope

FBR Digital Invoicing applies to sales-tax-registered businesses notified by FBR. Check current FBR notifications for applicability and dates. Have the person responsible for tax decisions confirm the scenario and required references for your supplies.

Collect representative invoices, including the fields that vary between transactions: registration type, province, quantity, rate and SRO reference. Review that set with your finance and tax teams before configuring a recurring workflow.

The invoice data model

Seller, buyer and supply

Start with the seller and buyer. Their names, NTN or CNIC, business details, province, address and registration type are part of the invoice information. In Fiskl One, reusable buyer and seller profiles hold these details. Reuse reduces repeated entry, but the profile still needs review: a saved address or registration type should describe the party on the invoice being prepared.

The scenario identifies the invoicing context. At item level, the HS code describes the classification, the unit of measure describes how quantity is expressed and the sale type and rate describe the selected tax treatment. These fields belong together. Review the code, UoM and quantity as one group, then review the sale type and applicable rate as another. Do not infer a rate solely from a familiar item description.

Line items also carry value excluding sales tax, fixed or notified value or retail price where applicable, sales tax and sales tax withheld at source. Further tax, extra tax, FED and discount are separate fields. An SRO schedule and item serial provide the reference where required. Invoice-level advance tax under sections 236G and 236H is recorded separately from the line-item fields.

The distinction between a quantity, a unit price and a tax amount matters when reconciling the invoice. Fiskl One stores monetary values as exact decimals with two decimal places and quantities with three. A reviewer should still trace each amount to its input. Exact storage preserves the recorded precision. Trace the recorded amount to the reviewed inputs.

Scenarios explain the supply context

Fiskl One supports selection of all 28 FBR scenarios, SN001 through SN028. The list includes standard-rate goods, reduced or special treatment, sector-specific supplies, services and retail scenarios. Each scenario has a description and a sale type. Use the scenario explorer to read the actual descriptions rather than relying on a shortened label in an internal spreadsheet or an old invoice template.

Scenario choice is a review decision, not simply a navigation step. Identify what is being supplied and the relevant buyer context, then confirm that the scenario describes that transaction. A business may need more than one scenario across its invoice register. A sector label is a useful entry point for a discussion, but it is not a substitute for checking the individual supply.

The industry pages map sectors to the supported scenario IDs and highlight fields to consider. These mappings help you gather the right questions: whether a notified value is involved, whether an SRO reference is needed or which tax fields deserve review. Keep a documented decision about each recurring supply alongside the process your team uses to prepare it.

Use current reference data

Fiskl One looks up seven groups of reference data live from FBR: provinces, transaction types, HS codes, units of measure, sale-type rates, SRO schedules and SRO items. These lookups bring the available reference choices into invoice preparation. The team selects the appropriate values while working on the invoice rather than assuming that every remembered code or rate remains suitable.

Reference data and business master data do different jobs. A buyer profile describes your counterparty. An HS code or SRO reference belongs to the reporting model. Both can appear on the same invoice, but they have different review responsibilities. Assign someone to verify counterparty details and someone to confirm the classification and tax treatment, even if one person performs both roles in a small team.

When preparing a sample invoice for onboarding, include the item descriptions you actually use and the units in which you sell them. Show where the relevant rate and references are selected. A demonstration is more useful when it reveals a decision your team needs to make than when it simply produces a successful response using unrelated sample data.

Validate before you post

A valid response comes before submission

A validate-then-post flow prepares the invoice, checks it with FBR and submits it only when validation returns valid. In Fiskl One, every invoice is validated with FBR before posting. Validation and submission run through the FBR integration service. The validation response is a decision point in the workflow: correct rejected fields and validate again before proceeding.

Validation does not remove the need for internal review. Your team remains responsible for the identity, scenario and transaction data it provides. Review the invoice against the supply before requesting posting. The system can check submitted data and returned status, while the finance team confirms that the invoice describes the intended business transaction.

After a successful post, Fiskl One stores the FBR-issued invoice number with the record. The PDF includes a QR code that encodes that number, together with the FBR logo. The PDF is the readable document; the saved invoice number is the acknowledgement associated with the posted record. Keep those roles clear when explaining the process to staff or customers.

Read the posting state before taking action

FBR posting has four states: not-posted, posting, posted and posting-failed. The invoice workflow also has pending and completed states; these are tracked separately. Looking at one status without the other can leave an incomplete picture. The how-it-works page shows the transitions so a reviewer can see the meaning and the next allowed action for each FBR state.

A not-posted invoice can be reviewed and submitted after valid validation. While posting is in progress, another post is blocked. A successful response moves the invoice to posted and retains the FBR invoice number. Posted invoices are locked from editing. Treat that lock as a reason to review carefully before posting, rather than as a reason to postpone review until the PDF is downloaded.

A failed post can be retried, provided an FBR invoice number does not already exist. Review the failure and correct the invoice if needed before retrying through validation. Avoid treating every unsuccessful attempt as a new invoice. Keeping the record and its current state visible gives the team a basis for deciding whether to wait, correct or retry.

Common validation issues to review

Check relationships, not only empty fields

Review the returned validation result, then check the field relationships highlighted below. Compare identity data with confirmed counterparty details. Review HS code, UoM and quantity together, then check the selected rate against the sale type.

Trace base value, sales tax, further tax, FED and discount back to their inputs. Confirm the required SRO schedule and item serial. Correct the identified issue and validate again before requesting posting.

A readiness checklist

Before a walkthrough, gather enough information to explain how an invoice moves through your business. Identify who prepares it, who reviews the tax treatment and who requests posting. Include the person who will manage account access and the business’s FBR token. Clear ownership helps the team interpret an error and make the next decision without passing the invoice between people who lack context.

Use the checklist below as a discussion tool. It stores selections only while you remain on this page. Work through a representative invoice in the demo, including a review of its reference data and totals. Confirm what the team will look for after posting and how it will find the same record later.

How Fiskl One handles the workflow

Fiskl One brings reusable profiles, scenario selection and live FBR reference lookups into invoice preparation. Its calculation model uses quantity and unit price, or notified value for Third Schedule goods, to establish the base. Sales tax is calculated from the base and rate; the line total adds sales tax, further tax and FED and subtracts discount. Review the applicable inputs before relying on the result.

The posting flow validates first, stores the FBR invoice number after success and locks the posted invoice. The register makes the posting state available for review, and the PDF carries the FBR number as a QR code. Portal analytics provide totals, invoice volume, revenue trends, posting status and top buyers across the available periods. Those views support operational review of invoice activity.

The security page explains account access, ownership-scoped records, decimal storage and audit history in plain language. Audit records cover invoice creation, updates and deletion, user and admin changes, and logins. Read the controls alongside the workflow so your team understands what evidence exists.

Book a demo with your company name, monthly invoice volume and the sectors or scenarios you use. Your NTN is optional in the request. The walkthrough lasts 30 minutes and uses your sectors and scenarios. Onboarding provisions your account and configures your business’s FBR token. Start with a concrete invoice workflow and the questions your team needs answered.