Review Split Purchase Orders Without Approving Spend

Define the review unit and authority boundary

Treat split-purchase review as a bounded evidence lane, not a procurement role. The unit is one purchase request and every order created from it, linked to the requesting department, the approved catalog, the amount, the approval threshold in force, and the owner authorized to commit spend. Write the lane brief before access is granted so a coordinator knows which fields may be prepared and which conclusions belong to procurement.

The central risk is a coordinator deciding that two orders are really one purchase and approving the combined commitment. That is a procurement judgment.

The outsourced role may group records by the identifiers the company supplies, calculate the combined amount, and flag a pattern. It may not select a vendor, approve an exception, or tell a requester that a workaround is acceptable.

Capture request lineage before comparing orders

Start from the originating request or requisition, not from the order list. Record the request identifier, requester, cost center, business reason, requested delivery date, and the exact catalog version used. Then attach every order that cites the request, including cancelled and revised orders, because a cancelled order can still reveal an attempt to divide a commitment.

Preserve the order version, creation time, currency, and the approval record attached at the time. A later reclassification must be appended, never used to overwrite the earlier state.

When two systems disagree about the amount or the requester, keep both values and name the system of record for each field. A clean comparison begins with an honest lineage, not with a tidy spreadsheet.

Detect split patterns with explicit rules

Write the detection rule before running it. A common rule flags consecutive orders from the same requester, vendor, and cost center within a defined window where each order sits below the threshold but the combined value exceeds it.

The rule should name the window, the matching keys, currency treatment, and whether cancelled orders count. The company owns those choices.

Run the rule as a reproducible query and keep the query version with the result. Report matches, near misses, and suppressed cases separately.

A near miss might share a vendor but not a business reason, and suppressing it without a note hides the judgment. The coordinator documents what the rule returned and routes the interpretation to procurement rather than writing a conclusion into the case.

Separate clerical checks from procurement judgment

Clerical checks confirm that fields are present, identifiers match, totals add up, and the approval record covers the order as written. Procurement judgment covers whether the business reason justifies the purchase, whether the vendor is appropriate, and whether the combined commitment should be approved. Keep these in separate fields so a reviewer can see which part was mechanical.

A neutral summary is more useful than a recommendation. State the orders, the combined amount, the threshold, the matching keys, and the open question.

Do not write that the case looks like an attempted split unless the company has approved that language for the lane. The owner needs the facts and the uncertainty, not a borrowed conclusion that could later appear in an audit as the company's position.

Document stop states and owner escalation

Stop when the request lineage is incomplete, the threshold version is unknown, currencies cannot be converted on an approved rate, or an order was changed after approval. Each stop needs a reason code, the missing evidence, the named owner, and the safe interim state. A stopped case is not a failed case; it is the control doing its job before an unauthorized commitment is made.

Escalation should be short and attributable. Include the case identifier, the orders, the rule that matched, the evidence already checked, the specific decision requested, and the last safe time to act.

Record the owner's response closely enough to preserve the decision, then link it to every affected order. Silence is not approval, and a verbal go-ahead should be converted into a written record by the owner.

Measure detection quality and close the loop

Report how many requests were reviewed, how many matched the rule, how many were confirmed by procurement, and how many were closed as legitimate. Include the cases where evidence was missing and the cases that were reopened.

A high match count may mean the rule is noisy, while a low count may mean intake is incomplete. Neither number is a performance score on its own.

Close by reconciling the request, every linked order, the approval record, and the final commitment. Verify that the owner's decision reached the procurement system, not just the review queue.

When the rule produces repeated false positives, revise the matching keys with the owner and keep the old rule version for comparison. The lane improves when the evidence changes the rule, not when the queue looks quiet.