Punjab Revenue Authority provides eIMS services, including an eIMS guide, installer and invoice search. An applicable implementation connects the business billing or POS workflow with the current PRA mechanism using registered business, branch and invoice information. Scope and eligibility must be confirmed through PRA guidance before configuration.
Availability, authentication and technical scope depend on the external platform, current requirements and approved access.
Authority-specific guidance
What this workflow means for the relevant jurisdiction
PRA administers Punjab sales tax on services and provides eIMS facilities through its taxpayer portal. This is distinct from federal FBR workflows and should be scoped around the business's service activity and Punjab registration.
Businesses that may need this workflow
Applicable restaurants and service businesses in Punjab
PRA-registered businesses instructed to use eIMS
Businesses connecting an existing billing or POS workflow
Multi-branch operations that need branch-level setup
Typical implementation sequence
1Confirm PRA registration and whether eIMS applies
2Review the current PRA guide and installer requirements
3Register or verify the relevant branch and POS information
4Map service invoice and tax fields
5Test invoice creation, response handling and invoice search
Status and verification note
PRA applicability, credentials, rates and the current technical process must be confirmed directly through PRA. This page does not claim PRA certification, approval or partnership.
How it works
From assessment to a supported workflow
STEP 01
Assess
Confirm the business workflow, external-system access and required data.
STEP 02
Configure
Set up the supported connection, credentials and field mapping.
STEP 03
Map Data
Align products, customers, transactions and required references.
STEP 04
Test
Validate sample records, responses and exception handling.
STEP 05
Deploy
Move the agreed workflow into the production environment.
STEP 06
Monitor
Review records and maintain the configured integration.
Registered business, branch, POS and service-invoice fields
Status
Implementation and access required
Who may need it?
Businesses with a relevant connected workflow
This integration may be relevant where a business uses Asaan POS or Asaan Restro and needs to exchange registered business, branch, pos and service-invoice fields with PRA eIMS Integration. Eligibility, access and final scope must be confirmed before implementation.
Common implementation issues
Plan for access, data and exceptions
Credentials or platform access are not available before configuration starts.
Required product, customer, tax or transaction fields are incomplete.
Test scenarios do not cover corrections, failures or unusual records.
External API rules or platform requirements change after implementation.
Integration flow
A clear path between your systems
Your Asaan Product
Secure Integration Layer
PRA eIMS Integration
Validated Records
Frequently asked questions
Common questions about PRA eIMS Integration
What is PRA eIMS Integration?+
Punjab Revenue Authority provides eIMS services, including an eIMS guide, installer and invoice search. An applicable implementation connects the business billing or POS workflow with the current PRA mechanism using registered business, branch and invoice information. Scope and eligibility must be confirmed through PRA guidance before configuration.
How does Asaan Solutions support PRA eIMS Integration?+
Our team can assess requirements, configure supported workflows, map required data and assist with testing and deployment.
Which Asaan products are relevant?+
Asaan POS, Asaan Restro may be relevant depending on the business workflow and agreed implementation scope.
What information is required?+
Business registration information, External-system credentials or access, Relevant business and transaction fields, Required API or platform information, A testing environment where available may be required. Exact requirements depend on the external system.
How long does implementation take?+
Timing depends on platform access, data mapping, testing requirements and the agreed scope. The team confirms a plan after assessment.
