Understanding the Procure-to-Pay (P2P) Cycle

The journey from purchasing requirement to vendor settlement is among the highest-risk workflows in business operations. Without a unified ERP, organizations suffer from duplicate invoice payments, unapproved price discrepancies, misplaced advance payments, and delayed financial closes.

In Novus ERP, the procurement cycle is enforced through strict state transitions that maintain data integrity and an immutable audit trail at each milestone.

The 5 Stages of the P2P Workflow

1. Purchase Order (PO) Creation & Approval

The process initiates when an approved requisition is converted into a formal Purchase Order. The PO specifies agreed quantities, unit pricing, payment terms, delivery schedules, and designated receiving warehouses. Crucially, the PO establishes the commercial ceiling: subsequent vendor invoices cannot exceed authorized rates without documented variation approvals.

2. Goods Receipt & Inventory Put-Away

When physical goods arrive at the warehouse, inventory personnel inspect shipments against the PO line items and log a Goods Receipt Note (GRN). This increments stock levels in real time and generates an interim accrual journal entry (Debit: Inventory, Credit: Goods Received Not Invoiced / GRNI).

3. Three-Way Matching & Vendor Bill Ingestion

When the vendor submits their tax invoice, the ERP performs automated three-way matching across:

  • Purchase Order: Authorizing quantities and contracted prices.
  • Goods Receipt Note: Verifying actual accepted physical units.
  • Vendor Bill: Matching billed unit rates, sales tax rates, and total amounts.

Any variance exceeding configured tolerance thresholds triggers an exception review, preventing unauthorized cost overruns from entering accounts payable.

Four-Eyes Payment Governance

In Novus ERP, creator self-approval is programmatically blocked above company-defined thresholds. A procurement clerk who raised a bill cannot approve the outgoing disbursement file. Approval must be granted by an independent authorized signatory.

4. Payment Proposal & Withholding Tax Deduction

Approved bills enter treasury queues. In Pakistan, payments to resident and non-resident vendors require withholding tax (WHT) deductions under Section 153 of the Income Tax Ordinance. Novus ERP calculates the appropriate withholding deduction based on the vendor's active tax filer status (Active Taxpayers List / ATL) and services vs. goods classification.

5. Bank Transmission & Reconciliation

Approved payments generate bank-compliant payment files (such as ISO 20022 pain.001 or proprietary domestic clearing formats). When bank statement files (CAMT.053, MT940, or electronic feeds) are imported, the reconciliation engine matches statement lines against clearing entries, closing out transit accounts and producing real-time cash flow statements.

Stage Document Primary Control Accounting Impact
Ordering Purchase Order (PO) Budget & vendor terms verification Commitment recorded (no ledger impact)
Receiving Goods Receipt (GRN) Physical QA & count check Debit Inventory / Credit GRNI Accrual
Invoicing Vendor Bill Automated Three-Way Match Debit GRNI Accrual / Credit Accounts Payable
Settlement Payment Voucher Four-Eyes Approval & WHT Calculation Debit Accounts Payable / Credit WHT Payable & Bank Clearing
Reconciliation Bank Statement Rule-based auto-reconciliation Debit Bank Clearing / Credit Bank Account