The procurement cycle in Dynamics 365 F&O

Station three built the foundation. This is the first thing that runs through it.

The five documents and their journals

#	Document	The accounting entry
1	Purchase requisition	None — an internal request passing through approval
2	Purchase order	No financial entry — a contractual commitment
3	Product receipt	The first real entry: receipt debit, accrual credit
4	Vendor invoice	Accrual debit, inventory or expense settles, vendor credit
5	Vendor payment	Vendor debit, bank credit

Row three is the lesson.

The product receipt produces a journal before the invoice arrives, carried by an accrual account derived from the item posting group you designed in the previous station.

That account’s balance is the first thing an auditor opens. Its meaning is simple: goods entered the warehouse and their invoice has not arrived. A large, old balance means the cycle is not closing, rather than that the account is wrong.

The interview question: goods received 28 September, invoice arrived 6 October. Which month carries the expense, and which account holds it in between?

The matching policy

An invoice does not post because somebody approved it. It posts because it matched — and was then approved.

Level	What is compared
No match	Nothing — an exception rather than a habit
Two-way	Invoice price against purchase order price
Three-way	Plus the quantity on the product receipt

The policy is set at three levels: company, vendor and item. That gradation is the advantage: three-way on goods and two-way on consulting services, in one company, with no manual exception.

Tolerances decide the mood of the whole department.

Zero tolerance holds every invoice a halala out; a wide one passes real variances. The middle that works is a small percentage with an absolute cap. One percentage for every item is an error: 2% on a hundred-riyal item is nothing, and on a two-million-riyal item it is a meeting.

Holds, and who resolves them

When matching fails, the invoice is held and does not post. The loudest complaint on these projects is a queue of held invoices with no owner.

The hold	The real cause	Who resolves it
Quantity billed exceeds received	Goods arrived, receipt never entered	The warehouse
Price variance	A stale price on the order, or no agreement	Procurement
Item not on the order	The purchase happened outside the system	Management — a discipline problem
Closed period	Invoice dated into a closed period	Finance

Three of four are resolved outside the accounts department. Attacking the queue with an extra headcount in finance treats the symptom.

What this product ships in the purchase cycle, and what needs a further licence, is in the Dynamics 365 Finance & Operations guide.

Approvals — where the days accumulate

A purchase cycle does not stall at posting. It stalls at waiting.

Three settings decide its speed.

Setting	The common error	The effect
Number of approval levels	Four levels for a five-hundred-riyal request	A week for a small purchase
Delegation during absence	Not configured	Every holiday halts the cycle
Value-based authority limits	One for everybody	A manager approving what is not theirs

The second row exposes itself at the first public holiday. The system does not know the approver is travelling; the request sits in their queue until they return. A company with no pre-configured delegation stops purchasing for a week every Eid.

The working rule at design: start at the fewest levels the finance director will accept, not the most the workshop asks for. Adding a level later is a two-minute setting, and removing one people have got used to is a month-long political discussion.

And attach value limits to the approval level rather than to the person. People change; the level stays.

Settlement — the forgotten step that makes reports lie

Paying a vendor does not end when the money leaves. It ends when the payment is settled against the invoices it paid.

Pay without settling and you get: a correct vendor balance and an entirely wrong statement. The invoices show unpaid, the payment shows open, and then the vendor calls chasing an invoice that was actually paid.

The control rule: no month closes with unsettled payments on the books and no written explanation.

What you actually do in this station

• Run a full cycle — requisition, order, product receipt, invoice, payment — and read each journal.
• Run the hard case: a receipt in one period and its invoice in the next, and write the effect on both months.
• Set a three-way matching policy with tolerances, then break a match deliberately and diagnose it.
• Pay without settling, pull the vendor statement, and watch it lie.
• Finish the official “manage accounts payable” path — 9 hours 56 minutes.
• Revisit the procurement cycle for the general principle.

The three commonest mistakes

One: expecting the journal at the invoice. It surfaces at the first close, when the accrual is several times what anyone expected.

Two: one matching policy for the whole company. Service invoices get held for no reason, holds get released by hand, and the control dies by habituation.

Three: skipping settlement. Wrong statements, vendor calls, and cash decisions on numbers that are not right.

The acceptance test for this station

1. Name the five documents and their journals, and which carry none.
2. Explain the accrual account: where it is derived from, when it clears, and what a swelling balance means.
3. Explain the three levels of the matching policy and when they differ.
4. Show your tolerances and justify both numbers.
5. Explain how a vendor balance is right and its statement wrong.

What comes next

You have the outbound side. The next station is the inbound one: the sales cycle — order to collection, and the packing slip half of all projects ignore, losing the cost with it.