Operations and Troubleshooting

This document covers production operations, monitoring, and common failure
paths.

Operational Checklist

Before production use:

• verify the company is using Production mode
• verify bearer tokens are valid
• verify items have HS codes and required sale type data
• verify customers that need DI are explicitly enabled
• verify tax mappings are correct
• verify DI Log is reviewed during rollout

Key Operational Records

The main records to watch during support are:

• DI Settings
• DI Log
• Sales Invoice
• Purchase Invoice
• POS Profile

DI Log Usage

Use DI Log to inspect:

• exact payload sent to FBR
• exact response returned by FBR
• failed validation details
• FBR invoice number assignment

Troubleshooting

Invoice did not post

Check:

• DI Settings.enabled
• Auto Post on Submit
• customer enablement for DI sales invoices
• missing HS code, PCT code, or SRO fields
• DI Log request and response payloads

Unauthorized response from FBR

Check:

• DI bearer token
• POS bearer token
• whether the token matches sandbox or production mode

Reference sync failed

Check:

• company context
• token validity
• DI Log entries with API type Reference

POS fiscalization failed

Check:

• POS Profile credentials
• PCT codes on items
• payment mode mappings
• DI Log entries with API type POS Fiscal

Buyer verification failed

Check:

• customer NTN/CNIC
• DI access token
• DI Log entries with API type STATL

Rollout Advice

• start with one company in sandbox
• use invoice preview and validation before live posting
• monitor DI Log after every configuration change
• move to production only after consistent sandbox success