PRA-integrated courier software should connect service invoicing with the consignment lifecycle. Booking, origin, destination, weight, service type, customer account, COD, payment, delivery status and fiscal receipt should not live in disconnected systems.
The official PRA Software Fiscal Device specification lists courier among its sector examples. The exact registration, service treatment, branch scope and current requirements should be verified through the PRA portal and professional tax advice.
Core courier software workflow
- Book the consignment: capture sender, receiver, origin, destination, service and package information.
- Calculate charges: apply approved weight, zone, service, fuel or other configured rules.
- Create labels and references: generate a unique consignment number and barcode where required.
- Collect or approve payment: record walk-in payment or authorised account credit.
- Fiscalise the service invoice: send applicable invoice information through the configured PRA process.
- Print or share documents: preserve the business reference, PRA fiscal number and QR receipt.
- Track movement: record branch handovers, dispatch, arrival, out-for-delivery and delivery.
- Reconcile: compare bookings, invoices, cash, account receivables, COD and fiscal status.
Walk-in versus account customers
| Requirement | Walk-in customer | Account customer |
|---|---|---|
| Pricing | Published counter tariff | Approved contract or customer tariff |
| Payment | Normally immediate | Credit terms or periodic settlement |
| Approval | Counter permissions | Credit limit and account status |
| Reporting | Shift cash and daily sales | Customer statement and receivables |
| Invoice link | Individual booking/invoice | Configured invoice or statement workflow |
Rate and surcharge management
Courier prices can depend on origin, destination, weight slab, service speed, package type and customer contract. Rate changes should be dated, approved and traceable. Cashiers should not manually overwrite charges without a recorded reason and permission.
COD and settlement controls
Cash on delivery collected for a merchant is operational money that must be reconciled carefully. Keep shipment charges, COD collection, merchant payable, deductions and settlement references separate. PRA service invoicing should be configured according to the business's approved accounting and tax treatment.
- COD amount captured at booking;
- delivery confirmation and collection status;
- rider or branch cash handover;
- merchant-wise settlement batch;
- approved deductions and service charges;
- bank/payment reference;
- unsettled and disputed COD reporting.
Branch, hub and counter control
Courier operations may span booking counters, branches and hubs. Identify which locations create taxable service invoices and which only handle movement. Register and configure each applicable POS/branch according to current PRA requirements. Use individual user accounts instead of shared cashier passwords.
Corrections, returns and failed deliveries
A shipment correction is not automatically the same as an invoice return. Preserve the original booking, invoice and fiscal response. Define approved procedures for address correction, weight difference, cancellation, return-to-origin, refund and credit adjustment.
PRA receipt and fiscal-status monitoring
Every applicable fiscalised invoice should retain the PRA response and QR receipt. A daily exception report should show pending, failed or returned invoices so finance staff can resolve them without creating duplicates. Read the PRA eIMS invoice guide.
Questions to ask during a courier software demo
- Can prices vary by zone, weight, service and account contract?
- Can one consignment be traced across branches and hubs?
- How are COD collections and merchant settlements separated?
- Can staff correct operational information without rewriting fiscal history?
- How does the system process returns linked to original invoices?
- Can each branch reconcile bookings, cash and fiscal status?
- Can management view customer profitability and outstanding balances?
- What happens when the PRA fiscal service or internet is unavailable?
Frequently asked questions
What is the best PRA-integrated courier software in Punjab?
The best solution is one that demonstrates pricing, booking, labels, branch movement, accounts, COD, returns, payments and PRA fiscalisation as one traceable workflow.
Can NexZion support courier branches?
Yes. Scope can include branches, counters, users, tariffs, account customers, consignment tracking and consolidated reporting.
Can courier software handle customer credit?
Yes. Account limits, tariffs, statements, receipts and ageing can be configured according to approved business rules.
Can it integrate with an existing tracking system?
Potentially. NexZion first reviews the current system, identifiers, API/data access and required direction of data exchange.
Book a courier software workflow review
Send your branches, daily bookings, service types, account-customer process, COD volume and current software. NexZion Solutions will recommend an implementation scope.
Reviewed: August 2026. This guide provides operational information, not tax or legal advice.
NexZion Solutions publishes practical guides based on business-software, compliance-workflow, website and automation implementation experience in Pakistan.
