Skip to content
Fiskl One
Inside Fiskl One

Every invoice has a path. Every state has a meaning.

Follow an invoice from the portal through validation and FBR posting to its recorded invoice number. See the fields and controls behind each step.

Architecture

From your team to the tax authority.

  1. 01

    Your team

    Browser / installed app

  2. 02

    Fiskl One portal

    Invoice form and register

  3. 03

    Fiskl One API

    Auth, validation, tax, audit log, PostgreSQL

    Admin console → API
    Account provisioning, invoices and audit records.
    API → PDF service → Invoice PDF with QR
    The QR encodes the FBR invoice number.

  4. 04

    FBR integration service

    Validate and submit

  5. 05

    FBR Digital Invoicing

    Validation and invoice number

Your team prepares invoices in the portal. The API handles authenticated access and invoice records, calls the FBR integration service for validation and posting, and stores the returned FBR invoice number. The admin console and PDF service use the API.

Posting sequence

Validation is part of posting.

  1. 01

    Submit

    Send the prepared invoice for posting.

  2. 02

    Validate with FBR

    The integration service validates the invoice before it is posted.

  3. 03

    If valid → mark posting → post

    A valid response permits posting. An invalid response stops the submission.

  4. 04

    FBR invoice number → posted + locked

    Store the returned invoice number, complete the invoice and lock it from editing.

  5. 05

    Otherwise → posting-failed

    Review the error, correct the invoice and retry the failed attempt.

Duplicate posting is blocked while a post is in progress or after an FBR invoice number exists. A failed post can be retried.

FBR status model

Four states. Explicit next steps.

validFBR invoice numberfailedretry
validFBR invoice numberfailedretry

not-posted moves to posting after valid validation. Posting moves to posted with an FBR invoice number, or to posting-failed. Posting-failed can retry to posting.

Meaning
The invoice has not been posted to FBR.
What you can do
Review or edit the invoice, validate, then submit it for posting.
Allowed transitions
After valid FBR validation: posting.

The invoice workflow uses pending / completed. FBR posting status is tracked separately.

Reference data

Seven live lookups from FBR.

The form uses reference data from FBR rather than a separately maintained rate list.

Provinces
Set the seller and buyer province.
Transaction types
Select the sale type for the invoice scenario.
HS codes / item descriptions
Identify the goods on each line item.
Units of measure
Select the unit for the item quantity.
Sale-type rates
Select the FBR rate for the chosen sale type.
SRO schedules
Reference the applicable schedule for an item.
SRO items
Select the item serial within the chosen SRO schedule.
Tax model

Keep the tax fields with the invoice.

Line-level fields

Value excluding sales tax
The line’s base value before sales tax.
Fixed / notified value or retail price
The notified base used for 3rd Schedule goods.
Sale type and rate
The supply classification and rate looked up from FBR.
Sales tax
Calculated from the base value and selected rate.
Sales tax withheld at source
The withholding amount recorded on the line.
Extra tax
An additional tax field stored with the item.
Further tax
The further-tax amount added to the line total.
FED
Federal excise duty added to the line total.
Discount
The discount amount subtracted from the line total.
SRO schedule and item serial
The schedule reference and item serial for the supply.

Invoice-level fields

Advance tax · 236G
Invoice-level advance tax under section 236G.
Advance tax · 236H
Invoice-level advance tax under section 236H.

Money is stored as exact decimals with two decimal places; quantities use three. Tax treatment depends on the selected scenario and applicable FBR reference data.

Documents

An invoice PDF with the FBR record.

The invoice PDF carries seller and buyer details, line items, tax amounts and totals. Posted invoices include the FBR-issued invoice number, the FBR logo and a QR code encoding that number.

The coded preview shows illustrative invoice content. It is not a downloadable invoice.

Sale invoice

INV-184 · SN001

Posted

Seller

Northfield Traders

Sindh

Buyer

Crescent Steel Works

Registered · Sindh

Illustrative PDF line item
Item / HS codeQuantityValue · PKR
Steel plate

7208.5100

100 KG50,000.00
Value excluding sales tax
50,000.00
Sales tax · 18%
9,000.00
Total · PKR
59,000.00

FBR invoice number · sample

FBR-SAMPLE-000184

Illustrative PDF layout · decorative QR placeholder
Data and access

An account for each business.

Buyer and seller profiles

Reuse names, NTN/CNIC, business name, province, address and registration type. Set a default profile.

Per-user data access

The API scopes business data to the authenticated owner. Accounts use JWT access and refresh tokens.

Admin provisioning

An admin provisions the account. Admins see the users they onboarded; Super Admins can see the platform.

FBR token at onboarding

Each business’s FBR token is configured during onboarding for the integration service.

Security

Read the verified access controls and data handling.

Security →