Submission checks
How to Check an Accepted FBR Digital Invoice
Check the posting response, environment, FBR invoice reference and item results. Understand why a saved record, validation or QR code alone is not proof.
By Digital Invoice PK by Xinuty · Published · Updated
Begin with the submission record
To check an accepted FBR digital invoice, start with the record of the posting attempt for that sale. Identify the local invoice reference, the environment and the action. A saved invoice proves that the software has a record; it does not establish what the authority received.
Digital Invoice PK keeps invoice and submission information for operational review. Use the response and history together. If the screen shows a general status but the underlying result is missing or inconsistent, ask support to review it before treating the invoice as complete.
Distinguish validation, posting and test results
FBR's technical specification describes separate validation and posting operations. Its successful post example includes an FBR invoice number with a validation response and item results. Check those details together; an overall code alone can hide a line error in the documented response examples.
| Record or result | Meaning for your review |
|---|---|
| Local bill number | Identifies the software record; keep it distinct from the authority-issued reference. |
| Valid draft / validation response | Shows the outcome of a check; review the posting result separately. |
| Queued / pending | Needs a final result checked before closing the exception. |
| Sandbox post result | Evidence of a test; it is not production acceptance for a live sale. |
| Production post response | Review the FBR invoice reference and overall/item results against this sale. |
Official reference: FBR / PRAL: Technical Specification for DI API, version 1.12
A five-point acceptance review
Use the same short check for the first live invoice and the last one of the day. Checking a response is more useful than relying on a temporary success notification.
- Match the local bill reference and sale details to the record you intended to submit.
- Confirm that the response is for a production post, rather than validation or sandbox testing.
- Check the overall result and every returned item result for errors or an unresolved outcome.
- Record the returned FBR invoice number and confirm it is associated with this invoice.
- Keep the submission time and response with the invoice record; investigate missing or contradictory evidence with support.
What a QR code or public verification can establish
Treat a printed QR code as a way to access information and compare identifiers. Its presence alone does not prove production acceptance. Check that the receipt and saved response refer to the same sale and authority reference.
FBR publishes a Tax Asaan / SMS verification route for purchases from Tier-1 integrated retailers under POS integration. That page has a specific scope. Confirm the verification route appropriate to your DI integration with the onboarding team before applying POS instructions to every dealer invoice.
Official reference: FBR: POS Invoice Verification
Keep a monthly exception list
For a dealer making 10–50 invoices a month, a short daily review can prevent unresolved results building up. Keep pending, rejected and uncertain records visible until someone has recorded the outcome. Reconcile your sale records and accepted submission records with the person preparing your return.
An accepted response does not, by itself, determine the correct legal classification or complete your sales tax filing. Keep supporting records and resolve differences before return preparation. If an accepted invoice needs a later adjustment, agree the applicable process rather than issuing a second invoice for the same sale.
Official sources and review dates
The links below support the official guidance in this article. Product instructions describe the Digital Invoice PK workflow; examples are illustrative. Check the official material for updates relevant to your business.
- FBR / PRAL: Technical Specification for DI API, version 1.12
The API document linked by FBR's Technical Assistance page when checked. Document last updated 24 July 2025; check FBR for replacements before implementation. Checked .
- FBR: POS Invoice Verification
Explains Tax Asaan and SMS verification for purchases from Tier-1 integrated retailers. Confirm applicability to your integration. Checked .