PRA Digital Invoicing Integration: Punjab eIMS, Credentials & POS
How Wise Digital Invoice supports Punjab Revenue Authority (PRA) eIMS: choose PRA instead of FBR per company, store POS ID and token, validate locally then PostData to sandbox or production, use services-oriented invoice forms, and one-tap submit from Point of Sale.
Not every Pakistani business posts sales invoices to the Federal Board of Revenue. Punjab service providers and POS-linked businesses can report through the Punjab Revenue Authority (PRA) eIMS path instead. Wise Digital Invoice also supports BRA and SRB. When you enable Digital Invoicing for a company, you pick one authority—FBR, PRA, BRA, or SRB.
This article is the plain-language tour of PRA integration: credentials, what gets sent, how invoices look different from the FBR screen, and how POS fits in.
One authority per company
At signup (or when an admin / reseller creates the company), Digital Invoicing includes a provider choice:
- FBR — federal goods / Digital Invoicing API path most of our older guides describe
- PRA — Punjab services / eIMS PostData path (this guide)
- BRA — Balochistan services / POS ID and bearer token
- SRB — Sindh cloud POS / POS ID, username, and password
That setting drives credentials, form fields, validation, and submission for every invoice in that company. If your group has both federal goods entities and Punjab service entities, keep them as separate companies with the right provider on each.
Credentials: POS ID, token, sandbox vs live
PRA companies store credentials in the same familiar credentials area as FBR users, but the fields match PRA’s model: a registered POS ID, an access token, and an environment (sandbox or production).
Sandbox is for practice—trials stay sandbox-only by design, same idea as our FBR trial. Production needs your real token and POS registration with PRA (including any IP allowlisting they ask for). Once live mode is on, successful posts return a PRA invoice number that we store on the invoice for audit and reprint.
What “validate” and “submit” mean for PRA
PRA’s integration does not mirror FBR’s separate remote validate API. In Wise Digital Invoice we still give you a clear gate:
- Validate builds and checks the PRA payload locally (buyer identifiers, PCT/HS lines, amounts, payment mode, and the rest of the PostData shape) and logs the result so you can fix problems before going live.
- Submit posts that JSON to PRA’s sandbox or production PostData endpoint and, on success, saves the authority invoice number on your record.
From the counter, if you use Point of Sale with Digital Invoicing on, a completed walk-in sale can run that validate-and-submit path in one step—so the till and the authority stay in sync.
Invoice screens that match services, not federal goods
PRA companies should not fight FBR-only fields every day. On create and edit, we hide federal-centric line options (sale-type pickers, SRO schedules, withheld-at-source style fields, and similar) and normalise lines for the PRA services-oriented payload. Products follow the same idea: keep PCT/HS and tax rate clean without dragging federal SRO baggage into a Punjab services invoice.
Prints show PRA eIMS branding where it matters, so the paper or PDF your customer sees matches the authority you actually filed with.
Bringing existing invoices in
PRA companies create invoices in the app, or import drafts from the standard spreadsheet on the invoice import page. Imported rows stay drafts until you review and submit. Counter sales usually start in Point of Sale.
Payment mode travels with the sale
PRA cares how the customer paid. Cash, card, and other methods map into PRA’s payment mode on the invoice—especially useful when the sale starts in POS and still needs a correct fiscal payload. Your counter workflow stays simple; the mapping happens in the submit path.
How this sits next to FBR content on our site
Most of our older public guides still talk about FBR, because that is what many national goods businesses need. PRA support does not replace those pages—it gives Punjab service businesses a first-class path in the same product. If you are still deciding which regime you fall under, talk to your tax advisor; then configure the matching provider in Wise Digital Invoice and practice in sandbox first.
Want to try it? Start the free trial, choose Digital Invoicing with PRA, optionally tick POS, and walk through a few sandbox posts before you go live.
PRA endpoints and registration steps can change when the authority updates eIMS. Behaviour described here matches Wise Digital Invoice’s PRA PostData integration, credentials, invoice forms, and POS one-step submit as shipped today.
Get a free demo
See Wise Digital Invoice on your use case: customers, products, and FBR validation in one walkthrough.
Request free demoNext steps (internal links)
Product overview: home, digital invoice software in Pakistan, FBR digital invoicing guide, and free trial (7 days). Contact us.