0002·Buyer registration number is not in the correct format
Buyer & seller identityCommon
What this means
FBR validates the shape of the identifier before looking it up. A CNIC is thirteen digits and an NTN is seven, with no dashes, spaces, or other separators. This check runs before any registration lookup, so a correctly identified taxpayer still fails if the number is formatted.
Why it happens
- The number was stored with dashes as users typically write it.
- Leading zeros were lost by storing the identifier as a number rather than a string.
- Whitespace was left at either end by a paste operation.
- An old-format or differently-lengthed identifier was carried over from a legacy system.
How to fix it
- 1Store registration numbers as strings and strip all non-digit characters before submission.
- 2Validate length at data entry — thirteen digits or seven — and reject anything else at that point.
- 3Never store an identifier in a numeric column, which destroys leading zeros irreversibly.
How Ordyoo handles this
Registration numbers are stored as text with non-digit characters stripped on entry, and length is validated when the customer is saved rather than when an invoice is submitted.
Related errors
Stop debugging FBR payloads by hand
Ordyoo builds and submits compliant invoices so most of these rejections never reach you. Start free.