Station 4 of 10
Procure to pay in Oracle Fusion
What you leave this station with
Running a full purchase cycle or simulating it in writing, reading the journal each document produces, and diagnosing a held invoice from its cause rather than its symptom.
Station three built the structure and the master data. This station is the first thing that runs through it.
Start with a commercial note that explains half of what you are about to see: procurement in Oracle Fusion is priced separately from the financials core — US$625 per user per month, exactly the same as the core, as set out in the system guide. So when you read about procurement features and cannot find them in an environment, the reason is usually that they were not bought, rather than that you failed to look.
The five documents and their journals
| # | Document | Who creates it | The accounting entry |
|---|---|---|---|
| 1 | Requisition | Whoever needs the thing | No entry — an administrative commitment |
| 2 | Purchase order | The buyer | No financial entry — a contractual commitment shown as encumbrance |
| 3 | Receipt | The warehouse | The first real entry: inventory or expense debit, accrual credit |
| 4 | Supplier invoice | Payables | Accrual debit, supplier credit, the difference to a variance account |
| 5 | Payment | Treasury | Supplier debit, bank credit |
Rows three and four are the whole lesson.
The journal is not born at the invoice, which is what everybody arriving from a simple accounting package expects. It is born at receipt. And the suspense account carrying the gap between the two moments — received-not-invoiced accrual — is the most important account nobody looks at on a balance sheet. A swelling balance on it is the first sign that the purchase cycle is not closing.
The interview question, put plainly: goods were received on 28 September and the invoice arrived on 6 October. Which month carries the expense, and what holds it in between? Answer that and you understand the cycle. Fail to and you have memorised screens.
Blanket agreements — what marks this tier out
Small systems raise a purchase order per transaction. There is a layer above it here that changes how the work is done.
- A blanket purchase agreement fixes price and terms with a supplier for a period; releases are drawn against it.
- A contract purchase agreement fixes terms with no items or prices, and orders reference it.
Their value is control rather than administration. Once prices are governed by an agreement, a price variance on an invoice becomes an exception to be investigated rather than a daily event. That is the state in which the system becomes a control instrument rather than a data entry log.
The practical test during implementation: if most of your spend is repeat business from known suppliers and you hold not one agreement, you are running an enterprise system the way a daybook is run.
Three-way matching and its tolerances
An invoice is not paid because somebody approved it. It is paid because it matched.
| Match type | What is compared | When it is used |
|---|---|---|
| Two-way | Invoice against purchase order | Services with no receipt |
| Three-way | Plus the receipt | The default for goods |
| Four-way | Plus inspection | Items subject to quality inspection |
Tolerances are the setting that decides the mood of an entire department. Zero tolerance holds every invoice a fils out. Wide tolerance passes real variances that nobody ever sees.
The middle that works: a small percentage tolerance with an absolute cap. One percentage for every item is the common error — 2% on a hundred-riyal item is nothing, and on a two-million-riyal item it is a meeting.
Holds — the commonest operational failure in this system
When matching fails, the system puts a hold on the invoice and it is not paid.
The loudest complaint on projects at this tier is not a technical fault. It is a queue of held invoices that nobody owns. Procurement says it belongs to finance, finance says the receipt was never entered, and the warehouse says the goods were delivered a month ago.
Four causes cover most of the queue:
| The hold | The real cause | Who resolves it |
|---|---|---|
| Quantity billed exceeds received | Goods arrived and were never entered | The warehouse, not finance |
| Price variance | An order at a stale price, or no agreement at all | Procurement |
| Closed purchase order | The transaction happened outside the system and is being regularised | Management — it is a discipline problem |
| Closed period | An invoice dated into a closed period | Finance |
Read the last column: three of four are resolved outside the accounts department. Anyone attacking a hold queue by adding a headcount in finance is treating the symptom.
What you actually do in this station
- Run a full cycle — requisition, order, receipt, invoice, payment — or simulate it in writing with the expected journal for each document.
- Read the receipt journal specifically and know the name of the accrual account in your own design.
- Run the hard case: a receipt in one period and its invoice in the next. Write out the effect on both months.
- Break a match deliberately, then diagnose the invoice from its cause.
- Write a proposed tolerance policy with a percentage and an absolute cap, and justify both numbers.
- Reread the procurement cycle to separate the general principle from this product’s specifics.
The three commonest mistakes
One: expecting the journal at the invoice. It surfaces at the first month end, when the accrual balance is several times what anyone expected and nobody can source it.
Two: operating with no blanket agreements. Price variance becomes a daily event and matching loses its control meaning entirely.
Three: clearing holds by release. The hold is lifted by hand, again and again, and the system’s control turns into a ritual with no effect — which the auditor finds on the first pass.
The acceptance test for this station
- Name the five documents and each journal, and which carry none.
- Explain the accrual account: when it fills, when it empties, and what a swelling balance means.
- Explain two-way, three-way and four-way matching and when each is used.
- Show your tolerance policy and justify both numbers.
- Diagnose a held invoice and name the department that actually resolves it.
What comes next
You have the side money leaves by. The next station is the side it arrives by: order to cash — sales order to customer collection, and why the customer balance is wrong every time invoicing is separated from delivery.