Procurement Process: The Steps a Purchase Goes Through Before You Get Paid

Procurement is the buyer's control system. Its purpose is to ensure that money is spent on approved things, at defensible prices, with suppliers who will not create legal, financial or security problems later. Sellers experience it as friction, which it is, but the friction is deliberate and directed at risk rather than at any particular vendor.

Understanding that changes how it is handled. Arguing that a process is unnecessary never works, because the process exists to protect the organisation from decisions made by people exactly like your champion. What does work is making each step easy to complete: answering the questionnaire fully the first time, providing documents in the format requested, and knowing which approvals apply before anyone asks.

Requisition and budget

Someone inside the organisation formally requests the purchase and it is checked against an approved budget line. This is where many deals actually die, invisibly, because the budget was allocated elsewhere and nobody wanted to say so. A champion who cannot name the budget line is not yet a champion.

Sourcing

The buyer identifies candidate suppliers and gathers information, proposals or quotes. Formality scales with value. A small purchase may need one quote; a large one may require a documented competitive process with a written rationale for the selection. The important thing for a seller is when this stage begins, because the evaluation criteria are usually written during it.

Evaluation and negotiation

Proposals are scored against criteria, a preferred supplier is identified, and commercial terms are negotiated. In software purchases, security review, data protection review and legal review commonly run in parallel with this stage rather than after it, which is worth confirming, since a sequential assumption can add a month to your forecast for no reason.

Approval

The purchase is routed through the organisation's delegation of authority. The number of approvals rises with contract value, and duration is often set by meeting schedules rather than by effort. A deal requiring the approval of a committee that sits on the first Tuesday of each month will take as long as that implies, however urgent everyone claims it is.

Purchase order and onboarding

Once approved, a purchase order is issued, and separately the supplier is onboarded into the payment system with bank details, tax registration and any compliance documentation. These are different processes with different owners, and a supplier can hold a valid purchase order and still be unable to be paid because onboarding has not completed.

Delivery, matching and payment

The supplier delivers, someone in the buying organisation confirms receipt, and the invoice is matched against the purchase order and that confirmation before payment is released. Mismatches stop the clock, and the supplier is usually the last to hear about it.

The pattern in the last column is the most useful thing on this page for a seller. Influence is front-loaded. A proposal written brilliantly against criteria shaped by a competitor is still a proposal written against someone else's criteria, and the polite thing to do on arriving late is to ask which requirements are genuinely fixed rather than to pretend the disadvantage does not exist.

The first place is discovery, or rather its absence. A seller who has never asked how purchases of this size are approved will forecast a close date based on the champion's enthusiasm, and will be surprised by a process the champion assumed everybody knew about.

The second is the questionnaire returned incomplete. Security and compliance reviews often run on a queue, and an answer that raises follow-up questions goes back to the end of it. Answering fully the first time, including the honest no where something is not supported, is usually faster than answering optimistically and being asked again.

The third is the invoice that cannot be paid. Submitting without the purchase order number, with an incorrect legal entity name, or before supplier onboarding completes, puts the payment into an exception queue that nobody monitors closely. In organisations running three-way matching, this is entirely predictable and entirely preventable by asking two questions before invoicing.

A purchase order is the authorisation document issued at the end of approval. Vendor onboarding is the parallel process of registering a supplier for payment. A master service agreement is the umbrella contract that individual orders or statements of work hang from. Net terms describe when payment is due once an invoice is accepted. A security review and a data processing agreement are two of the gates that commonly run inside a software procurement rather than after it.

Related pages on buying, comparing and switching systems:pricing, book a demo, compare alternatives, what a CRM is, features overview, and switching from Zoho.