HS Code, UOM and Sale Type in FBR Digital Invoices

Many invoice rejections begin in product master data. HS code, unit of measurement, sale type and rate are related business classifications; selecting each from an isolated dropdown can create a combination that looks complete but is not valid for the transaction.

What an HS code does

An HS code classifies goods for tariff and reporting purposes. It is not simply a keyword attached to a product name. Two stock items may share an HS code while retaining different descriptions and SKUs, and a similar commercial description does not automatically justify the same classification.

Classification should be supported by the product’s nature, composition and use, plus the applicable official tariff material and professional advice. Do not allow staff to pick the first search result merely to complete an invoice.

Why UOM must match the product and reference data

The unit of measurement tells the receiving system how quantity is expressed—such as pieces, kilograms or another recognised unit. The technical documentation provides reference services for UOM and HS/UOM relationships. Store the approved value with the product record and review it when packaging or commercial practice changes.

Keep the commercial unit and reporting unit relationship documented. If sales teams sell cartons but the approved reporting unit is pieces, define a controlled conversion instead of asking every operator to calculate it manually.

Sale type carries tax meaning

Sale type describes the applicable transaction treatment, not the customer’s preferred label. It can affect which rates and conditional fields are expected. The selected sale type should be supported by the transaction, product and applicable law.

Rates, SRO schedules and item references may be date-sensitive. Avoid hard-coding a permanent rate into every product without an effective date and review process.

Create a governed product master

For every sellable item maintain:

• internal SKU and clear product description;
• approved HS code and classification evidence;
• standard UOM and any controlled conversion;
• usual sale type and permitted alternatives;
• tax rate source and effective dates;
• SRO fields where applicable;
• owner, reviewer and last review date.

Lock approved fields for routine users and create an exception process for new products or unusual sales. Changes should be logged because a master-data edit can affect many future invoices.

Validate combinations, not fields

Before submission, check that HS code and UOM are an accepted relationship, the rate is available for the sale type and date, conditional fields are supplied where required, and quantities and values reconcile. Show the user which combination failed.

The public DI API technical specification documents reference endpoints and validation examples. Confirm current tariff classifications and tax treatment with official material and a qualified adviser; software cannot make that legal determination for the business.