Core go-live
- GL, AP, AR and banking
- Workflow, RBAC and audit
- CEO/CFO dashboards
- SSO, MFA and monitoring
- Payroll parallel run
Pakistan Revenue Automation · ERP proposal
Augment ERP
for PRAL
Capability, differentiation and a 20-week delivery plan for PRAL’s complete Scope of Work.
Prepared for PRAL5 August 2026Four-week discovery · Four releases
The problem
PRAL is not buying a generic finance system.
It is asking one programme to unite eleven functional modules with public-sector procurement controls, Pakistani statutory law, sovereign data ownership, security, migration and long-term operational accountability.
11
Enterprise breadth
Finance, procurement, inventory, assets, payroll, documents, BI, workflow, migration, integration and controls.
§
Public-sector compliance
PPRA rules, segregation of duties, tamper-evident evidence and inspection-grade auditability.
PK
Pakistani law
FBR salary slabs, Section 149 withholding, EOBI and Provident Fund must work in the product.
↗
Data ownership
Unrestricted extraction, a database dump or equivalent, and full handover at no cost.
AI
Self-service
Users must build reports and ask questions without vendor intervention or a security side channel.
5Y
Operational commitment
A 99.5% uptime SLA, five-year support, training, migration, recovery and change management.
Discovery · Weeks 1–4
Four weeks on site, turning current work into the delivery baseline.
Augment works alongside PRAL process owners to map how work happens today—including exceptions, controls, data and handoffs—so R1–R4 are built and accepted against one shared operating picture.
01
Mobilise and align
Owners, decisions, workshops and source evidence.
02
Map current work
Processes, exceptions and handoffs as operated today.
03
Assess controls
Pain points, variants, PPRA and statutory rules.
04
Profile data
Systems, masters, documents, interfaces and quality.
05
Validate fit-gap
Target processes, traced requirements and decisions.
06
Baseline releases
Backlog, migration, training and acceptance criteria.
Outcome: One signed delivery baseline for R1–R4.
The delivery position
Production in week 8.
Full Scope of Work in week 20.
Four weeks of on-site discovery establish how PRAL works and what each release must prove. R1 then activates the accounting, control and platform spine, followed by accepted production increments.
First production useWeek 8Finance, controls, dashboards, security, documents and PRAL data live.
Full scopeWeek 20Discovery plus all four releases delivered, tested, accepted and documented.
Operational horizon5 yearsSupport begins at R1, with hypercare through week 28.
Discovery removes ambiguity before build. Incremental production release then keeps acceptance, migration, training and uptime evidence inside the delivery cycles.
Four production releases
Every four weeks, a larger working system.
Control & treasury
- Budget and commitments
- Fixed assets and depreciation
- Payroll cutover
- Payment files and cash flow
- Delegation and escalation
Source to stock
- Procurement end to end
- PPRA configuration pack
- Contract and vendor control
- Inventory and valuation
- Opening stock migration
Complete & extend
- Payroll completion
- Self-service and AI query
- KPI and drill-down
- Document unification
- Integration and history
Hypercare continues through week 28. Five-year support starts at R1.
Why the cadence is safer
Four short evidence cycles replace one late leap of faith.
01 · Acceptance
PRAL tests what it is already using
Users accept one release at a time. Defects surface inside the first release cycle, not month 8, while they are cheaper and easier to isolate.
02 · SLA
Uptime evidence accrues in production
By week 20, PRAL holds twelve weeks of measured availability, backup and recovery evidence from a live system.
03 · Scope
Changes have a structural home
Each release is frozen at its start. A change moves to the next release—four weeks away—without destabilising current acceptance.
04 · Payroll
Cutover follows proof
No salary disbursement occurs until one complete parallel cycle is reconciled against legacy. R1 proves; R2 cuts over.
What decides the evaluation
Requirements that expose the difference between a tick and a working control.
Capability position · 4 August 2026
One product. One status language. A dated release for every gap.
LivePartialPlanned
Finance & Accounting
LiveLedger, AP, AR, banking, statements and audit spine.
R1 · Extended R2Procurement
PartialPO and receipt base; planning, tender evaluation and PPRA complete in R3.
R1 · Complete R3Inventory
LiveMaster, locations, receipt and transfer; financial stock ledger completes in R3.
R3Fixed Assets
LiveRegister, tags, transfer and verification; depreciation and disposal complete in R2.
R2Payroll
LivePakistan payroll, approvals, reports and certificates; advanced cases complete in R4.
R1 · R2 · R4Documents & BI
PartialAttachments and executive dashboards live; repository and self-service complete in R4.
R1 · Complete R4Workflow & Controls
LiveMulti-level approvals, RBAC and audit; delegation and runtime configuration follow.
R1 · R2 · R3Platform & Support
PartialMigration, APIs, security, training and operations delivered by release.
R1–R4 · Year 1–5SoW §6 · Finance & Accounting
The accounting spine is the first production release.
Live
R1 establishes control
Multi-level chart of accounts, dimensions, journals, period close, AP with three-way matching, AR, banking, trial balance, balance sheet, profit and loss, audit, approvals and executive dashboards—on PRAL data.
SoW §7 · Procurement Management
R3 joins budget, tender, contract, receipt and vendor evidence.
The result is a continuous public-procurement record—from annual plan to purchase and performance—with the PPRA rule pack implemented as configuration.
SoW §8–9 · Inventory & Fixed Assets
Operational custody meets financial valuation.
Inventory · R3
Perpetual stock control
Item and warehouse masters, multi-location receipt and transfer, issuance, adjustment, barcode, physical count and reorder policy—joined to weighted-average and FIFO cost layers and general-ledger posting.
Operations liveLedger planned
Fixed Assets · R2
Whole-life asset accounting
Register, categorization, tagging, custody transfer, maintenance and verification—joined to capitalization, separate book/tax depreciation, disposal gain or loss, retirement and final catch-up.
Register liveAccounting planned
SoW §10–13 · People, documents, insight & workflow
Controls stay consistent across every operating surface.
AI remains advisory. It may surface anomalies, explain variances or draft material; it does not post a journal, approve a payment or award a contract.
SoW §14–20 · Platform and handover
The programme includes the operating system around the ERP.
Eight differences that matter here
Designed around PRAL’s actual requirement—not a generic checklist.
01
Take the data and leave
Schema-level export and no-cost handover satisfy the exit clause directly.
02
Pakistani law as code
Versioned FBR, Section 149, EOBI, PF and certificates.
03
Auditor-grade evidence
Hash chaining and enforced segregation, surfaced in compliance reporting.
04
AI within permission
Same authorized handlers, tenancy and audit path as the UI.
05
Configuration autonomy
Approval, forms, fields, roles and transitions belong to PRAL admins.
06
Residency choice
Public, private or PRAL data centre, implemented through R1 automation.
07
Inspectable architecture
One ledger writer, integer money, locks, guards and idempotency.
08
Fit-gap before contract
A code-verified baseline that exposes live, partial and planned scope.
Our assessment · PRAL-specific comparison
The global leaders are broader. The question is fit for this SoW.
| PRAL-relevant lens | Auxo | SAP S/4HANA | NetSuite | Odoo | Workday |
|---|---|---|---|---|---|
| Database dump / handover | Native PostgreSQL schema | Available on-premise; cloud terms vary | Closed SaaS export model | Self-hostable | Closed SaaS export model |
| Pakistan payroll law | Product capability | Localization project | Partner dependency | Community localization | Not native payroll coverage |
| PPRA rule set | Configured for PRAL | Customization | Customization | Customization | Outside core focus |
| Hosting choice | Public, private, on-premise | On-premise possible | Vendor cloud | Self-host anywhere | Vendor cloud |
| Client configuration | Forms, roles, workflow, states | Specialist configuration | SuiteScript often required | Python often required | Certified ecosystem |
| Source access / escrow | Available | No | No | Open source | No |
| First production use | Week 8 | Long enterprise programme | Mid-market implementation | Implementation-dependent | Enterprise programme |
| Beyond this SoW | Focused | Deepest breadth | Very broad | Broad, variable depth | Deepest in HCM |
A comparison that awards Auxo every line would not be credible. Product, licensing and localization terms should be verified in writing during evaluation.
The 20-week delivery plan
Discover first. Then build, test, accept and train inside every release.
Weeks 1–4Discover
Map current work, validate controls, profile data and baseline R1–R4.
Weeks 5–8R1 · Go live
Configure, migrate, secure, parallel-run payroll and accept.
Weeks 9–12R2 · Control
Budget, assets, payroll cutover, treasury, encryption and DR.
Weeks 13–16R3 · Operate
Procurement, PPRA, contracts, vendors and inventory.
Weeks 17–20R4 · Complete
BI, documents, integration, history, hardening and handover.
Week 21 onwardRun & support
Hypercare to week 28; statutory and operational support through year 5.
Discovery gives every pod the same signed baseline. Six functional pods, one platform pod and independent verification then run concurrently. The human gates remain human.
Why 20 weeks is credible
Engineering speed matters. Programme shape matters more.
01 · Discovery
Current work becomes one signed baseline
PRAL’s processes, controls, exceptions, data and acceptance criteria are agreed before they can become release rework.
02 · R1
Configuration, migration and production control
The first release activates the accounting and control spine, migrates agreed data and establishes the production platform.
03 · Parallel delivery
Agent fleets under senior review
Six functional workstreams run concurrently, with automated testing and independent fresh-context verification against each stated requirement.
04 · Programme mechanics
Human work moves inside the cycle
Acceptance, migration reconciliation, training and uptime evidence overlap with construction instead of forming one sequential block at the end.
Discovery resolves PRAL-specific interpretation before build. Agentic engineering then compresses specification-driven work without pretending to compress decisions, acceptance, reconciliation, training or recovery evidence.
Risks and named contingencies
The schedule risk is dependency latency and scope discipline.
Largest schedule risk
PPRA sign-off late
R3 ships with a provisional published-rules pack, then is reconfigured when PRAL signs off. The release date does not move.
Governance
Acceptance capacity
One empowered owner per module, about two days in each acceptance week, with a 48-hour decision turnaround.
Critical path
Legacy extracts late
The entity moves to the following migration wave while the software release still goes live on schedule.
Real rework
Hosting undecided
R1 uses the reference target; replatforming becomes an R3 workstream. This is why the decision closes during discovery.
Control
Scope enters mid-release
The release remains frozen. Impact analysis and approval place the change in the next four-week increment.
Operational safety
Payroll variance
No cutover until one complete parallel cycle reconciles. A failed proof holds payroll at legacy without holding the ERP go-live.
SLA
Penalty measurement
Measure from R2 after the witnessed recovery drill, while R1–R2 still accumulate operating evidence.
Data value
Five years of history
Monthly balances plus a read-only archive are standard; journal-level history is selected and priced during discovery.
Concentration
Regional vendor risk
Escrow, PostgreSQL, OpenAPI, complete export and engineering handover preserve PRAL’s ability to operate without us.
What the plan requires from PRAL
Six dated commitments on the critical path.
Hosting and residency
Public, private or PRAL data centre—closed by discovery exit.
PPRA rule pack
Thresholds, methods and delegation matrix—closed in discovery.
Approval authority
Roles and approval matrix—validated and signed in discovery.
Legacy extracts
Finance/HR for R1, assets week 9, inventory week 13.
Module decision-makers
Named in discovery, one empowered owner each.
Acceptance users
Allocated time in weeks 8, 12, 16 and 20.
Ask every bidder to demonstrate live: a complete export of its own database, and a Pakistani payroll run with Section 149 withholding that produces a tax certificate.