What Procure-to-Pay Covers
Procure-to-pay, usually shortened to P2P, is everything that happens between someone needing an item or service and the supplier being paid and the payment being booked. It runs from purchase requisition to approval, request for quotation where needed, purchase order, goods receipt or service acceptance, supplier invoice, matching, payment scheduling, payment, and finally the accounting entry and bank reconciliation.
In many mid-sized Saudi companies this cycle still moves through paper forms, WhatsApp messages, spreadsheets and signatures waiting for a manager to get back from a trip. The symptoms are familiar: an item runs out before anyone orders it, a supplier calls about an invoice nobody can find, site staff buy outside agreed contracts at higher prices, and an accountant spends days matching invoices line by line.
The "three clicks" in the title is not a promise that purchasing becomes magic. It describes what the routine path can look like once the system does the paperwork: one person raises or confirms a requisition, one person approves it, one person confirms receipt. Documents, postings and matching happen in between without re-keying. Exceptions still need human judgement; the goal is to make them rare and obvious.
The Stages and the Evidence Behind Each One
| Stage | Document | Must include | Owner |
|---|---|---|---|
| Need | Purchase requisition | Item or service, quantity, required date, budget code or cost center, estimated cost | Requesting department or warehouse |
| Approval | Electronic approval | Approver, timestamp, comments | Per authority matrix |
| Sourcing | RFQ and comparison | Three quotes above the policy threshold, selection rationale | Procurement |
| Commitment | Purchase order | Price, quantity, payment terms, delivery date, VAT | Procurement |
| Receipt | Goods received note or completion certificate | Quantity received, condition, quality, or service acceptance | Warehouse or user department |
| Invoice | Supplier tax invoice | Standard tax invoice fields, both parties' VAT numbers | Accounts payable |
| Payment | Payment run and voucher | Amount, due date, verified supplier bank account | Treasury |
Every automated step still needs evidence behind it. Automation that hides documents or skips receipt makes the cycle faster and weaker at the same time, which is the opposite of what you want.
Where a Manual Cycle Loses Time and Money
- Late discovery: the storekeeper notices a shortage only when someone asks for the item. With a seven-day supplier lead time, work stops or the item is bought urgently at a premium.
- Chasing approvers: paper requests sit on desks, or a photo is sent to a manager's phone with no formal record.
- Quote comparison in spreadsheets: every buyer builds a different sheet, and the reason for choosing a supplier is lost.
- Unrecorded receipts: goods arrive and get used, but the receipt is entered days later, so finance has no idea a liability exists.
- Manual matching: differences between order, receipt and invoice surface only when the supplier is already chasing payment.
- Unscheduled payments: invoices get paid according to who shouts loudest, not by due date, so early payment discounts are missed and some invoices are paid early for no benefit.
The Automated Cycle: Three Human Touchpoints
Click one: raise or confirm the requisition
Once each stock item has a reorder point and safety stock, the system can propose a requisition as soon as available stock drops below the threshold. The proposal shows suggested quantity, usual supplier and last purchase price; the buyer reviews and confirms. Non-stock purchases such as services or equipment use a short electronic form tied to a cost center or project.
Hypothetical example: an item is consumed at 40 units a day, the supplier lead time is 7 days, and safety stock is 120 units. Reorder point = 40 x 7 + 120 = 400 units. When available stock reaches 400, the system raises the proposal. Our guide to the inventory reorder point explains how to set these values.
Click two: approval by authority matrix
Approval routes are configured once by amount and spend type, then applied automatically. A hypothetical matrix:
| Request value | First approver | Second approver | Quotes required |
|---|---|---|---|
| Below SAR 5,000 | Department manager | None | One quote or contract price |
| SAR 5,000 to 50,000 | Department manager | Procurement manager | Three quotes |
| Above SAR 50,000 | Procurement manager | CFO | Three quotes plus comparison memo |
| Capital assets, any value | Department manager | CFO | By value |
The approver gets a notification with the request summary and remaining budget, and approves or rejects with a reason. If nothing happens within a set time, the request escalates to a delegate. Quote comparison can also run inside the system, as we describe in our article on RFQ comparison in ERP.
Click three: confirm receipt
When goods arrive, the storekeeper opens the purchase order and confirms the quantities actually received, or scans barcodes if items are labelled. Stock updates immediately and the system records a goods-received-not-invoiced liability before the invoice even arrives. For services, the user department confirms completion or attaches the completion certificate. Matching and payment scheduling follow from there.
Three-Way Matching and Tolerances
Three-way matching compares the purchase order, the receipt and the supplier invoice before an invoice is released for payment. If quantity and price agree within tolerance, the invoice is approved without anyone touching it. If not, it is held and routed to an owner.
Hypothetical example: a PO for 500 cartons at SAR 48 each, SAR 24,000 before VAT. The warehouse received 490 cartons. The supplier invoices 500 cartons at SAR 48.50. Policy tolerances are 1% on price and zero on quantity.
- Price variance: 0.50 / 48 = 1.04%, outside tolerance.
- Quantity variance: 10 cartons invoiced but not received.
- Outcome: the invoice is held, the supplier is asked for a corrected invoice or a credit note, and only what was received is paid at the agreed price.
Do not let the system settle exceptions on its own. It should flag the difference and its likely cause; a person decides. Over time the exception log also shows which suppliers make repeated errors, which feeds directly into supplier management and evaluation.
The VAT Angle: Supplier Invoices Under Phase 2
VAT in Saudi Arabia has been 15% since July 2020, and you cannot recover input VAT without a valid tax invoice from the supplier. Under Phase 2 e-invoicing, a supplier's standard B2B tax invoice is cleared by ZATCA before it reaches you, and it should carry your name, address and VAT number. That gives accounts payable clear checks:
- Is the buyer VAT number on the invoice actually yours?
- Is it a standard invoice rather than a simplified one? A simplified invoice may be used for B2B supplies of SAR 1,000 or less and does not need buyer details.
- Is VAT charged at the right rate on the right lines?
- Is there a credit note for every return or later discount?
VAT returns are monthly for businesses with annual taxable supplies above SAR 40 million and quarterly otherwise, due by the last day of the following month. An invoice that sits unmatched for weeks can miss its period, pushing the input VAT claim later than it needed to be.
Supplier Advance Payments
For equipment or made-to-order goods, suppliers often ask for an advance, say 30% when the PO is signed. The cycle has to handle this explicitly: the advance sits on the supplier account as a debit linked to that PO and is deducted from the final invoice on delivery. For VAT, an advance received before supply is taxable when the supplier receives it, so the supplier should issue a tax invoice for the advance and then a final invoice that nets off what was already invoiced. If the system does not tie the advance to the PO, you get the classic statement showing the supplier owed the full amount when a third was paid months ago.
Early Payment Discounts: Worth Taking?
Some suppliers offer terms like 2/10 net 30: 2% off if you pay within 10 days instead of 30. It sounds small. Annualized, it is not:
- You pay 98% of the amount 20 days early to save 2%.
- Return over 20 days = 2 / 98 = 2.04%.
- Approximate annual return = 2.04% x (365 / 20), roughly 37%.
If your cost of funds is well below that and you have the cash, take the discount. The problem in a manual cycle is that the invoice rarely reaches treasury approved within ten days. With receipts recorded on time and matching done instantly, the invoice is ready while the discount window is still open.
Off-Contract Spend
When you negotiate annual prices for a list of items and a site supervisor then buys the same item from a nearby shop at a higher price because the official route is slow, that is off-contract or maverick spend. Each purchase is small; the yearly total is not, and it weakens your negotiating position because the contracted supplier never sees the volume you promised.
Three tools address it: a catalogue of approved items linked to contract prices, so users pick from a list instead of typing free text; an alert when an entered price exceeds the contract or last purchase price by more than a policy threshold; and a firm rule that no invoice is paid without an approved PO, with a separate route for genuine exceptions such as utilities and telecoms.
Controls That Must Survive Automation
- Segregation of duties: whoever requests does not approve, whoever approves does not receive, whoever receives does not pay. System roles enforce it.
- Supplier bank detail changes: any IBAN change needs separate approval and a call-back to a known number. Changed bank details are one of the most common fraud routes.
- After-the-fact POs: a PO created after the invoice arrived defeats the control. Track the ratio.
- Budget visibility: approvers see remaining cost-center budget before they approve.
- Audit trail: every change to an order or invoice is stamped with user and time.
Metrics That Show Whether It Works
| Metric | How to calculate | What it tells you |
|---|---|---|
| Cycle time | Requisition to PO, and receipt to payment | Where requests really stall |
| System-generated requisitions | Proposals raised by the system / all requisitions | How far reorder rules are trusted |
| First-pass match rate | Invoices matched with no exception / all invoices | Quality of POs, receipts and supplier invoices |
| Spend under contract | Spend at agreed prices / total spend | Size of off-contract buying |
| After-the-fact PO rate | POs created after invoice / all POs | Policy compliance |
| Discounts captured | Discounts taken / discounts offered | Payment scheduling efficiency |
For a wider set of measures, see our article on procurement KPIs.
A Phased Rollout
- Map today's cycle (2 weeks): follow ten real requests from need to payment and log every wait.
- Clean item and supplier data (2 to 3 weeks): standardize item codes and units, update supplier VAT numbers and payment terms.
- Agree the authority matrix (1 week): signed off by management before it is configured.
- Set reorder points (2 weeks): start with the highest-consumption items.
- Pilot (4 weeks): one category or one branch, with a weekly exception review.
- Roll out: extend once the metrics hold steady.
Common Mistakes
| Mistake | Effect | Fix |
|---|---|---|
| Automating today's process as is | Unnecessary steps just run faster | Simplify the route before configuring it |
| Over-engineered approval chains | Requests stuck between five approvers | Two or three levels suit most companies |
| Stale reorder points | Wrong proposals that users learn to ignore | Review quarterly against actual usage |
| Auto-settling variances | Paying for goods never received | Hold exceptions for human review |
P2P Automation With Tranquil
Tranquil brings purchasing, inventory and financial accounting into one cloud system, so a requisition becomes a PO, a receipt and a posting without re-entry. Inventory supports multiple units of measure and central inventory, and e-invoicing covers Phase 1 and Phase 2 requirements. The team can configure multi-level approval chains, reports and screens to match your policy, with role-based training. Explore purchase management or contact us to review your current cycle.
Frequently Asked Questions
What is the difference between two-way and three-way matching?
Two-way matching compares the PO with the invoice and suits some services and small purchases. Three-way matching adds the receipt, so you only pay for what actually arrived. Use it for goods.
Can service purchases such as maintenance be automated?
Yes. Receipt takes the form of a completion certificate or service report confirmed by the user department. Do not release a service invoice without it.
What if the supplier invoice arrives before the goods?
Register it and keep it on hold until the receipt is posted, then it matches automatically. Only agreed advance payments on the PO should be paid before delivery.
How long does P2P automation take?
For a mid-sized company with reasonable item data, two to three months to a stable rollout. Cleaning item and supplier data usually takes the longest.
Does automation replace the procurement team?
No. It moves the team's time from chasing and data entry to negotiation, supplier evaluation and contract management, which is where real savings come from.