FBR Digital Invoicing Buyer CNIC, NTN and Registration Type Guide

Quick answer

In FBR Digital Invoicing, buyer information is not handled through one universal rule for every transaction. The DI API requires the buyer registration type to be identified as Registered or Unregistered. The official API field description marks buyerNTNCNIC as required, but optional when the buyer is unregistered. Buyer business name, province and address remain required API fields.

There is also an important legal exception: FBR’s official Digital Invoicing FAQ states that when a manufacturer or importer supplies an unregistered distributor, the tax invoice must contain that distributor’s NIC or NTN under section 23(1)(b) of the Sales Tax Act, 1990.

What buyer fields does the FBR DI API use?

The official Technical Specification for DI API Version 1.12 lists these buyer-level fields:

• buyerNTNCNIC: buyer NTN or CNIC; optional in the case of an unregistered buyer.
• buyerBusinessName: required.
• buyerProvince: required and selected from the relevant reference data.
• buyerAddress: required.
• buyerRegistrationType: required, with Registered or Unregistered as the stated values.

This means that selecting “Unregistered” does not automatically remove every buyer-information field. The software still needs a complete buyer workflow that matches the current API rules and the actual transaction.

Registered buyer workflow

For a registered buyer, the invoice system should normally:

1. Select the registration type as Registered.
2. Enter the buyer’s correct NTN or CNIC in the buyer registration field.
3. Use the buyer’s correct business name.
4. Select the buyer province from the accepted reference data.
5. Record the buyer address.
6. Validate that the buyer identity and transaction scenario are compatible before submission.

A seller should not enter a random registration number merely to pass API validation. Buyer identity should come from reliable customer records and should be verified where appropriate.

Unregistered buyer workflow

For an unregistered buyer, the API documentation permits the buyer NTN/CNIC field to be optional. However, the buyer registration type, business name, province and address remain part of the required invoice structure.

The correct operational approach is:

1. Select Unregistered only when that accurately reflects the buyer’s status.
2. Complete the buyer name, province and address fields required by the API.
3. Check whether the business activity, buyer relationship or applicable law creates an additional NIC/NTN requirement.
4. Select the correct invoice scenario and sale type.
5. Validate the complete payload before posting the invoice.

Important exception for an unregistered distributor

FBR’s official FAQ addresses a specific situation in which an integrated enterprise sells to an unregistered buyer who does not provide particulars. It states that, for supplies by a manufacturer or importer to an unregistered distributor, the tax invoice must contain the NIC or NTN of that unregistered distributor, as applicable.

This exception is important because the API-level statement that buyer NTN/CNIC is optional for an unregistered buyer does not cancel transaction-specific legal requirements. The seller must consider both the technical API rules and the legal nature of the supply.

Is there a universal invoice amount above which CNIC or NTN is mandatory?

The official Digital Invoicing API field table and the FBR Digital Invoicing FAQ reviewed for this guide do not establish one universal invoice-value threshold that applies to every buyer, seller and transaction type. A business should therefore avoid publishing or applying a blanket amount rule unless it can identify the current law, notification, SRO or official instruction that creates that threshold for the specific transaction.

Buyer registration type is not the same as filer status

The API field buyerRegistrationType identifies the buyer as Registered or Unregistered for the Digital Invoicing transaction. Businesses should not automatically treat that field as identical to income-tax filer, late-filer or Active Taxpayer List status. These concepts may be relevant in tax administration, but they should not be mixed without confirming the applicable FBR rule and reference service.

Common mistakes that cause validation or compliance problems

• Selecting Registered while leaving buyer NTN/CNIC blank.
• Selecting Unregistered for a buyer who is actually registered.
• Using dummy CNIC or NTN values.
• Leaving buyer name, province or address incomplete.
• Applying a consumer workflow to an unregistered distributor without checking section 23 requirements.
• Assuming one buyer rule applies to every invoice scenario.
• Changing buyer type only to make an invoice pass validation.
• Mixing POS rules, Digital Invoicing rules and unrelated withholding-tax thresholds.

Recommended software controls

• Maintain separate customer records for registered and unregistered buyers.
• Make buyer registration type mandatory.
• Require NTN/CNIC automatically when Registered is selected.
• Show a warning for manufacturer or importer sales to an unregistered distributor.
• Validate province and other reference values before submission.
• Store the selected invoice scenario and sale type with the invoice.
• Keep request and response logs without exposing security tokens.
• Allow an authorized user to review exceptions before live submission.

Official references

• FBR Digital Invoicing Technical Assistance
• Technical Specification for DI API Version 1.12
• FBR Digital Invoicing FAQs
• FBR Digital Invoicing Legal Provisions

Related NexZion Solutions guides

• FBR Digital Invoicing Software in Pakistan
• FBR Digital Invoicing Error Troubleshooting Guide
• FBR Invoice Scenarios SN001–SN028
• FBR Digital Invoicing Readiness Checklist
• Request an FBR Digital Invoicing Demo

Frequently asked questions

Is buyer NTN or CNIC required for a registered buyer?

The official API field table treats buyer NTN/CNIC as required, with the stated optional treatment applying when the buyer is unregistered.

Can buyer NTN/CNIC be blank for an unregistered buyer?

The API documentation marks it optional for an unregistered buyer, but the business must still check transaction-specific legal requirements. For example, FBR’s FAQ states that a manufacturer or importer supplying an unregistered distributor must include the distributor’s NIC or NTN.

Are buyer name, province and address optional for an unregistered buyer?

No. The API field description lists buyer business name, province and address as required fields.

Should software automatically insert a dummy CNIC?

No. Dummy identification data can create inaccurate records and compliance problems. The system should apply the correct buyer workflow and require authorized review when information is missing.

Important: This guide summarizes official FBR technical documentation and FAQs available when reviewed. The Sales Tax Act, Sales Tax Rules, notifications, SROs and current FBR instructions prevail if any requirement changes or conflicts with this explanation.