The procure-to-pay cycle

The whole purchasing flow on one page, and who does what.

Baca dalam Bahasa Indonesia

On this page
  1. The cycle in seven steps
  2. Who does what
  3. What the ledger sees
  4. Where P2P goes wrong
  5. In Voltrus
  6. Checklist

Procure to pay, usually shortened to P2P, is everything between "we need something" and "the supplier has been paid". In a spreadsheet company it is often a chain of WhatsApp messages, a PO typed in Word, a delivery note in a drawer and a bank transfer made from the supplier's invoice alone. Each link works, but nothing checks that the company paid for what it ordered, at the price it agreed, and only for what actually arrived.

An ERP turns that chain into linked documents, and each link is a control. This article gives the whole cycle on one page. The articles after it go through each step in depth.

The cycle in seven steps

StepDocumentWhoWhat it proves
1. NeedPurchase requisition, MRP suggestion or reorder alertRequester, plannerSomeone needed it, for a reason
2. SourceSupplier quotationBuyerThe price and lead time were compared
3. OrderPurchase order (PO)Buyer, approverThe company committed to buy, at an agreed price
4. ReceiveGoods receiptWarehouseThe goods physically arrived, in this quantity
5. InspectQuality inspection (when required)QualityThe goods are fit to use
6. InvoiceSupplier billAccounts payableThe supplier claims payment, matched to PO and receipt
7. PayPayment, often in a payment runTreasuryMoney left the bank for a matched, due bill

The most important idea is that steps 3, 4 and 6 are recorded by different people and checked against each other. That check, the three-way match, is what stops paying for goods that never came or at a price nobody agreed. See Supplier invoices and the three-way match.

Who does what

Good practice separates four roles, even in a small company where one person may hold two of them:

  • Requester or planner decides what is needed and when.
  • Buyer chooses the supplier, negotiates and issues the PO.
  • Receiver (warehouse) counts what arrives and posts the receipt. The receiver should not be the buyer: a buyer who can also confirm receipt can approve a delivery that never happened.
  • Accounts payable enters the supplier's invoice and prepares payment. AP should not be able to create suppliers or change their bank details: that combination is the classic route for paying a fake supplier.

See Internal controls and segregation of duties for how to arrange these roles in Voltrus.

What the ledger sees

Every step that moves goods or creates an obligation posts to the general ledger by itself. For a PO of 100 units at Rp 50,000, plus 11% PPN on the bill:

EventDebitCreditAmount
PO approved(nothing: a commitment, not a transaction)
Goods receivedInventoryGoods received not invoiced (GRNI)5,000,000
Bill issuedGRNIAccounts payable5,000,000
PPN Masukan (input PPN)Accounts payable550,000
PaymentAccounts payableBank5,550,000

GRNI is a liability that means "we have the goods and owe for them, but the invoice hasn't come yet". A healthy GRNI account only holds recent receipts. Old items in it mean bills that were never entered, or receipts that were posted by mistake. How operations post to the general ledger covers every entry in detail.

Where P2P goes wrong

The same handful of problems show up in almost every company:

  1. Buying without a PO. The invoice arrives first and the PO is created afterwards to make the paperwork fit. This destroys the control: nobody approved the purchase before it was made.
  2. Receipts posted late. Goods sit in the warehouse for a week before anyone posts the receipt, so stock reports, MRP and GRNI are all wrong in the meantime.
  3. Paying from the invoice alone. The bill is paid without checking it against the receipt. Short deliveries and price increases go unnoticed.
  4. Supplier master data maintained by everyone. Duplicated suppliers, bank details changed without a second check.
  5. No payment discipline. Bills are paid when the supplier calls, not when they are due, so cash planning is guesswork.

In Voltrus

Each record shows its Next steps for its current status, so a received PO offers Create supplier bill, and its linked documents (receipts, bills, returns, payments) appear on the record.

Voltrus does not have a purchase requisition document. Needs come from MRP, reorder points, or a person creating a draft PO directly; a draft PO plays the role of the requisition, and approving it is the commitment. Purchase orders and approval explains how to run approvals with that model.

Checklist

  • Write down the rule: no purchase without an approved PO, except a short list of exceptions (utilities, petty cash).
  • Assign the buyer, receiver and AP roles to different people where you can.
  • Post receipts the same day goods arrive.
  • Review the GRNI balance every month-end; anything older than 30 days needs an answer.
  • Pay suppliers in a weekly payment run, not on request.

Run it in Voltrus ERP

Everything in these guides is built in: documents that post to the ledger as they happen, Indonesian tax, MRP and costing, with AI agents that propose and people who approve.

See Voltrus ERP