Blog · Finance metrics and formulas · Procurement
Cost per purchase order divides procurement processing spending by the purchase orders handled in the same period. Calculate it by business unit and processing route, reconcile the cost pools, and separate a process difference from a change in order mix.
Cost per purchase order is procurement processing cost divided by the purchase orders handled in the same period. It measures the administrative cost of buying, using a defined scope from preparation through the activities your company chooses to include. The purchase value of the goods stays outside this processing measure.
Cost per purchase order = In-scope procurement processing cost / In-scope purchase-order count
The numerator can include buyer labor, approval time, purchasing-system costs and external exception-handling charges. If receiving or accounts payable work belongs in your measure, include both its cost and the matching workload consistently. Otherwise keep those activities outside it.
The denominator is a count of purchase-order headers, not order lines, invoices or units purchased. One order can contain several items and lead to multiple invoices. Federal purchase-order guidance, for example, distinguishes the order document from its specified quantity or scope of services. A private company's counting policy should reflect its own process and be documented just as clearly.
This is different from customer fulfillment cost per order, which follows an outgoing sale. It is also different from the cost per unit of goods produced or purchased. A processing rate cannot substitute for either measure.
Use a PO register with order ID, business unit, issue or completion date, status, and processing route. A route might distinguish an order that follows an established buying arrangement from one requiring manual review. Define the labels from actual process records, rather than assigning them after seeing which unit looks expensive.
Use time records or an approved activity study for labor. Keep employee or role, activity, hours, approved loaded hourly rate and the cost center receiving the cost. Add a separate spending export for purchasing systems and outside processing services. Confirm that an outside service is not already included in a shared allocation.
The allocation discipline matters more than the label. Federal contracting rules on direct costs prohibit charging the same-purpose cost directly when it is also treated as an indirect cost in like circumstances. Those rules have a specific federal scope, but the duplicate-charge check is useful for this management calculation too.
Maintain a bridge from ledger spending to the in-scope numerator: included amount, excluded amount and reason. Costs used in the rate must reconcile to that bridge. A time study can allocate payroll; it should not add a second payroll expense on top of the ledger amount.
A US distributor reviews one quarter. Its North and South business units use the same cost boundary and a loaded labor rate of $40.00 per hour. System allocations are approved for this period; exception-service costs are separate third-party charges, with no overlap with employee time.
| Unit and route | POs | Hours | Labor: hours × 40 (USD) | System allocation (USD) | Exception service (USD) | Total processing cost (USD) | Cost per PO (USD) |
|---|---|---|---|---|---|---|---|
| North, routine | 800 | 200 | 8,000 | 4,000 | 0 | 12,000 | 15.00 |
| North, manual | 200 | 300 | 12,000 | 2,000 | 4,000 | 18,000 | 90.00 |
| South, routine | 400 | 100 | 4,000 | 2,000 | 0 | 6,000 | 15.00 |
| South, manual | 600 | 900 | 36,000 | 6,000 | 12,000 | 54,000 | 90.00 |
| Total | 2,000 | 1,500 | 60,000 | 14,000 | 16,000 | 90,000 | 45.00 |
For North's routine orders, 200 hours × $40.00 = $8,000 of labor. Add $4,000 of systems and no exception service to get $12,000. Divide by 800 POs to get $15.00 per PO.
For South's manual orders, 900 × $40.00 = $36,000 of labor. Adding $6,000 and $12,000 gives $54,000, and $54,000 / 600 = $90.00 per PO. The same steps produce every other row.
The company result is $90,000 / 2,000 = $45.00. Dollar rates are shown to two decimal places; these example rates divide exactly.
First reconcile the numerator. Labor of $60,000 plus system costs of $14,000 plus exception services of $16,000 equals $90,000. The cost bridge must explain that entire amount against payroll and spending records.
Then reconcile the denominator. The four non-overlapping groups contain 800 + 200 + 400 + 600 = 2,000 distinct POs. A PO must belong to one unit and one processing route in this table. If an order moves between routes during processing, apply a documented classification rule and retain the original order ID.
Finally, rebuild cost from the rates:
| Processing route | POs | Cost per PO (USD) | Rebuilt cost (USD) |
|---|---|---|---|
| Routine | 1,200 | 15.00 | 18,000 |
| Manual | 800 | 90.00 | 72,000 |
| Total | 2,000 | 45.00 | 90,000 |
The weighted rate is (1,200 × $15.00 + 800 × $90.00) / 2,000 = $45.00. Multiplying it back by 2,000 returns $90,000. Averaging the four displayed group rates instead would give $52.50, because it assigns equal weight to groups with unequal workloads.
North processes 1,000 POs for $30,000, or $30.00 each. South processes 1,000 for $60,000, or $60.00 each. The gap looks large until the two routes are compared: both units have exactly the same routine rate and exactly the same manual rate.
South's higher average comes entirely from more manual orders. Across the company, manual work represents 800 / 2,000 = 40.0% of POs but $72,000 / $90,000 = 80.0% of processing cost. These percentages use counts and costs from the tables, respectively.
If South had North's mix of 800 routine and 200 manual orders, its calculated cost at the unchanged route rates would be 800 × $15.00 + 200 × $90.00 = $30,000. That is a mix illustration, not a promised saving: someone must establish whether the manual work can actually become routine and which expenses would change.
Keep shared-cost allocation stable as well. The federal guidance on indirect costs describes logical cost groupings and allocation bases that reflect benefits received. A changing allocation base can move the rate without changing the purchasing process.
Use an annual ordering cost comparison when the next question is how frequency affects the yearly total. A purchase order dashboard has a different job: keeping the ongoing purchasing picture visible.
Bring a PO register, your processing-cost workbook and the approved allocation assumptions. Covirage maps the columns, and its tools compute and check costs, counts and weighted rates; the external AI model explains the comparisons with every figure traced to its rows. Create a free Covirage account, then set up your business and bring a sample of your own data.
See Covirage for procurement teams for the purchasing context.
The processing measure normally excludes the purchase value of the goods or services. It measures the effort and resources used to administer the order. Include procurement labor and agreed support costs, and state whether receiving or invoice matching falls inside the boundary.
Canceled orders can consume real purchasing effort. Either count them in an explicitly defined handled-order measure or show them separately with their associated costs. Do not remove them from the denominator while leaving all the work they caused in the main cost pool.
It may handle more complex orders, exceptions or approval steps, or it may allocate more shared costs to procurement. Compare processing routes and cost definitions before treating the difference as poor performance. The mix of routine and manual orders can explain the entire gap.
Use a frequency that matches the decision and the availability of reliable cost records. A monthly trend can reveal changing order mix, while a longer measurement period may better represent labor and system costs. Refresh the assumptions when staffing, responsibilities or contracts change.