Shopify to FBR Field Mapping for Digital Invoices
Some FBR values come directly from Shopify; others need merchant configuration or tax approval. This mapping table shows the difference.
Map source and ownership together
A field map should name the Shopify source, transformation, FBR destination, fallback and approving owner. If a value is not present, fail visibly rather than inventing one.
Core mapping table
| FBR concept | Likely Shopify source | Control needed |
|---|---|---|
| Merchant invoice reference | Order name / immutable ID | Approved format and uniqueness |
| Invoice date | Payment, order or fulfilment event | Adviser-approved time-of-supply trigger |
| Buyer name and address | Billing or shipping profile | Choose source by documented rule |
| Buyer registration status | Controlled customer attribute | Verification; never infer from company name |
| Item description | Line title / variant | Preserve a clear commercial description |
| HS code | Product or variant mapping | Tax adviser approval and effective date |
| UOM | Product mapping | Current accepted FBR value |
| Quantity and price | Line item | Precision and refund handling |
| Discount | Line and order allocations | Reconcile allocated total |
| Rate / sale type / SRO | Tax mapping, not free text | Approved as one consistent set |
| FBR invoice number | FBR response | Never pre-generate |
Headers need decisions
Seller details belong to the configured legal entity, not the Shopify store display name. Invoice type, date, buyer type and scenario must match current documentation and the merchant’s facts.
Lines must reconcile
Allocate discounts deterministically and preserve shipping treatment. Sum taxable values and tax from lines using accepted precision, then compare the payload to Shopify’s gross, discount and tax totals.
Version the map
Store who approved each tax mapping and its effective date. When a code changes, future orders should use the new version while historical submissions remain explainable.
Test representative orders
Use sandbox cases for real product, buyer, payment and discount combinations. Preserve payload and response evidence and test failures as well as successful invoices.
Treat discounts and shipping explicitly
Shopify can represent line discounts, order discounts, discount codes, automatic promotions and free shipping differently. Decide how an order-level amount is allocated to lines, how rounding differences are handled and whether shipping is a separate line or part of another value under the approved tax treatment.
Test a multi-line order where only one item is discounted, a percentage discount with paisa rounding, a refunded shipping charge and a free gift. Reconcile the sum of mapped lines to Shopify’s commercial totals and explain any deliberate difference.
Plan for catalogue changes
Variants can inherit or override product mappings, bundles can represent several goods as one Shopify line, and staff can replace an SKU. Use stable product or variant IDs in addition to SKU, validate required mappings before an item goes live and alert on an unmapped product.
When the adviser changes a code or treatment, use an effective date and record the old and new values. Decide how open, unfulfilled orders are treated rather than automatically applying today’s mapping to an earlier commercial event.
Last updated: 2026-08-04
Not tax advice. Confirm registration scope, rates, deadlines, and filing obligations with a Pakistani tax practitioner against current FBR SROs and the Sales Tax Act. ComplyStream is not affiliated with FBR or PRAL.
Ready to connect Shopify to your invoice workflow?
Install ComplyStream, review the current product capabilities and follow the setup steps with your approved tax configuration.