Blog · Updated for 2026

KPRA Digital Invoicing Integration: Khyber Pakhtunkhwa RIMS, POS ID & Key

How Wise Digital Invoice supports Khyber Pakhtunkhwa Revenue Authority (KPRA) Restaurant Invoice Monitoring System: choose KPRA per company, store NTN, POS ID, and key, validate locally, then post to the KPRA RIMS API and print a verification QR.

Restaurants in Khyber Pakhtunkhwa report sales through the Khyber Pakhtunkhwa Revenue Authority (KPRA) Restaurant Invoice Monitoring System (RIMS), not the federal FBR Digital Invoicing API. Wise Digital Invoice treats KPRA as its own company setting, alongside FBR, PRA, BRA, and SRB. A company uses one authority.

Who this is for

Choose KPRA when the restaurant is registered with KPRA for RIMS. Hotels and other service businesses in the province that are not on the restaurant invoice API should confirm their path with KPRA before selecting this provider. Invoice screens follow the services layout (no FBR scenario or SRO fields), and Point of Sale is included automatically.

Credentials: NTN, POS ID, and key

KPRA does not use an FBR or PRA bearer token. On KPRA credentials, save the three values from your RIMS registration. The official guide is the KPRA RIMS API documentation:

  • NTN — the taxpayer number KPRA issued for this POS
  • POS ID — the terminal id KPRA issued (letters are allowed)
  • Key — the authentication key for that POS

KPRA publishes one live invoice URL. Sandbox in Wise Digital Invoice means you are using KPRA’s published test user, not a separate host. Their documented test values are NTN K123456, POS ID K123456, and key KPRA@123a. Production uses the NTN, POS ID, and key KPRA issued for the restaurant. Trials stay on sandbox. The key is stored on the server and is not printed on the receipt.

KPRA also offers a Windows utility that queues invoices on the restaurant PC. Wise Digital Invoice posts directly to the public RIMS endpoint, so the till does not need that local utility.

Validate, then post

Validate checks that the NTN, POS ID, key, invoice number, tax-exclusive amount, tax rate, and total are ready. KPRA accepts one tax rate on the invoice. Submit posts that bill to https://kpra.gov.pk/api/rims-integration. A successful response (status 201) stores KPRA’s transaction id on the invoice.

The receipt QR encodes KPRA’s verification link, https://kpra.gov.pk/api/?pos_id=…&invoice_no=…, so a customer can scan the bill and see it on KPRA. Each invoice number can be sent once for a POS ID. Cash is payment mode 1 and card is payment mode 2. POS can validate and submit in one step at the counter.

Same idea as PRA, BRA, and SRB: one authority per company, local validate, then a live post.

Get a free demo

See Wise Digital Invoice on your use case: customers, products, and FBR validation in one walkthrough.

Request free demo