Troubleshooting
FBR Invoice Rejection and Timeout: What to Do Next
Separate data rejection from an uncertain FBR submission timeout. Review the existing invoice, preserve the response and plan the next safe step.
By Digital Invoice PK by Xinuty · Published · Updated
First establish what kind of failure occurred
When an FBR invoice is rejected or a submission times out, pause and read the response before clicking again. A clear data rejection identifies a problem in the submitted record. A connection failure can leave you without enough information to know whether the receiving service processed it.
Keep the local invoice reference, time, environment, action taken and response text together. This gives support a specific record to investigate and avoids confusing a sandbox test with a live attempt.
| Observed result | Next step |
|---|---|
| Missing or inconsistent data | Correct the indicated buyer, product or line value; validate the corrected record. |
| Authority rejection | Review the full response and any line errors; establish the cause before another post. |
| Authentication / connection configuration error | Ask the onboarding or support team to check the configured environment and connection. |
| Timeout or missing final response | Treat the outcome as unresolved; investigate the existing attempt before deciding to resend. |
| Queued / pending | Check the queue and history before manually posting the same sale. |
Correct an invoice rejected for data
Read the exact field or item named by the error. Typical preparation problems include incomplete buyer details, an unsuitable HS-code/UOM combination, missing sale type or inconsistent totals. The right correction depends on the record; a generic retry cannot repair inaccurate data.
- Find the buyer, product or invoice line referenced by the response.
- Compare the submitted value with the confirmed business record.
- Correct the source information and review other invoices using that same record.
- Validate the corrected invoice and review the result before posting again.
Investigate a timeout before another submission
A timeout reports that your software did not receive a usable response in time. It is not, by itself, evidence that FBR rejected the invoice. Creating a new local bill for the same sale can make the investigation harder and may lead to a duplicate submission.
Digital Invoice PK records submission history and provides queue and reconciliation workflows. Remote reconciliation depends on the connection configured for your installation. Ask support to investigate unresolved attempts when a status lookup is unavailable or inconclusive; do not assume a lookup will always settle the outcome automatically.
- Keep the original record and avoid repeated manual posts while its outcome is unresolved.
- Check the submission history for the same local reference and environment.
- Check for a returned FBR reference and review the response, including any item results.
- Have support use the available reconciliation process or agreed PRAL support route.
- Record the conclusion and next action before an authorised retry is made.
A worked example of an unresolved result
Use a short incident note even if your business creates only a few invoices a day. It helps the next person continue the investigation without starting over.
Give support a useful, private problem report
Send the local reference, environment, approximate time, action, exact error and relevant line number through the agreed private support channel. Never paste a connection token or account password into a public post. Share only the customer information needed for investigation.
Keep unresolved records in a daily exception list until there is a documented conclusion. Once accepted, handle any later correction through the applicable invoice adjustment process rather than deleting the record and hoping to reset its status.
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 .