From procurement exceptions to a recovery file

An exception is a question, not a recovery

Begin by defining what the analysis can identify. Similar invoice references, a difference between ordered and invoiced quantities, or an apparently unused credit can each raise a question. They do not establish the explanation, the amount available for recovery or the supplier's obligation. Give the analytical rule a stated purpose and record the records and conditions it examines.

Create a candidate register with a stable reference for each question. Include the client entity, supplier identifier, affected transactions, detection reason, evidence owner and current status. Preserve the rule version and source extract behind the candidate so that a later rerun does not silently change its basis. Keep the candidate reference independent of an invoice number that may itself be incorrect or incomplete.

Use statuses that distinguish discovery from disposition. A detected anomaly may need source reconciliation before an operational owner can explain it. A supported factual discrepancy may then require contractual interpretation or a client decision about raising it commercially. Record those dependencies separately. An item should not progress merely because a reporting cycle has ended or because its apparent value attracts attention.

Define the population before interpreting the results. Record which entities, systems, suppliers and transaction periods are represented, together with exclusions and inaccessible records. State whether the analysis examines transaction headers, individual lines or payment events. A rule operating on invoice headers cannot explain a quantity difference within a line it has not examined, and an incomplete extract cannot describe activity outside its coverage.

Separate the discovery queue from the potential-recovery portfolio. Retain candidates that are unexplained, excluded or resolved as data issues, with their reasons, instead of presenting every detected item as an opportunity. The portfolio should contain defined questions supported sufficiently for the next client-owned action, while showing the evidence and interpretation still missing. It is a work programme, not a statement of money owed.

Reconstruct the procurement evidence chain

Follow the selected transaction through requisition or order, receipt or service acceptance, invoice, payment event and subsequent adjustment. Record which links exist and which depend on information held elsewhere. A purchase order may have several receipts and invoices; an invoice may be associated with several payment events. Preserve those relationships rather than forcing the transaction into a single row that loses its history.

Establish identifiers at the right level. Keep the client entity, source system, supplier account, document reference and line reference together where they are needed to identify a record. Normalise spelling or formatting only in separate matching fields, preserving the original values. Removing a suffix from an invoice reference can conceal a distinction that the source owner needs to explain.

Check that the matching process has not created the anomaly. Joining invoice lines to receipts and payment events can repeat a source line in the analytical output. Trace a selected result back to its original records and examine how each relationship was formed. An invoice appearing repeatedly after a join is not evidence that it was issued or paid repeatedly. Record ambiguous matches without automatically merging them.

Preserve event meanings as well as identifiers. Distinguish a payment instruction from its recorded execution, cancellation or replacement, using explanations supplied by the client process owner. Link credit notes and other adjustments to the transactions they address where the sources support that relationship. Keep document time, service period and system-entry time distinct when comparing records; they describe different parts of the sequence.

Work from authorised extracts and retain a source manifest showing their coverage, extraction criteria and custodians. Keep analysis separate from live supplier-master changes and payment processing. Limit the working dataset to fields needed for the defined question, with access assigned to the relevant roles. The evidence chain should let an authorised client owner reproduce the candidate without giving an analyst authority to alter the transaction.

Explain the discrepancy before escalating it

Build an explanation worksheet around the precise difference detected. State what the available records show, what the rule expected and what information could distinguish the plausible explanations. For a price difference, locate the relevant order version, service period and client-supplied commercial instruction. Ask directly appointed qualified advisers to resolve questions about the meaning or applicability of contractual terms rather than treating a stored price as an entitlement.

Consider an illustrative scenario in which a supplier invoice appears under a scanned reference and a manually entered variant. Similar details trigger a suspected-duplicate rule. The payment extract also contains an instruction marked cancelled and a replacement instruction. The analyst must establish whether the records concern repeated source capture, separate invoices, replacement processing or an unexplained additional event.

Trace the relationship using source references and the client's explanation of system statuses. Check the cancellation record, the replacement link and the evidence available for the resulting payment sequence. Preserve contradictory records rather than selecting the version that supports the largest candidate. Where the sequence cannot be established, identify the missing source and responsible custodian. Similar descriptions alone do not resolve what happened.

Test adjustments and timing before carrying the question forward. A credit may be recorded outside the selected extract, a service acceptance may cover several deliveries, or a revised instruction may apply to a different period. Treat these as possible explanations to investigate, not reasons to dismiss the candidate without evidence. Route tax treatment, accounting classification and recognition questions to the client's directly appointed qualified providers.

Record the conclusion at the level supported by the work. A repeated import may explain the analytical duplication; it does not establish the status of unrelated supplier transactions. An unresolved discrepancy may justify a factual supplier question without establishing a recovery claim. Ask the client operational owner to confirm the explanation of their process, and retain any specialist dependency separately from that operational confirmation.

Build a portfolio without counting an issue twice

Group candidates by their underlying transaction relationships before presenting a portfolio. The same invoice could trigger rules for a repeated reference, a price difference and an unmatched adjustment. Preserve each detection reason, but connect them to a common case where the evidence indicates that they concern the same event. A rule hit is not an independent commercial question merely because a different test produced it.

Create an overlap record showing which candidates share source lines, payment events or proposed adjustments. Distinguish alternative explanations from separate issues supported by separate evidence. Where the relationship remains uncertain, mark the overlap as unresolved and keep the candidates out of any combined presentation that assumes independence. Record the grouping decision and its source basis so that another authorised analyst can challenge it.

Keep amounts attached to their source context. Distinguish an invoice amount from the particular line or difference being questioned, and retain the source currency and adjustment status. Do not add the full invoice to a related line discrepancy as though they concern separate value. Any proposed financial valuation or accounting treatment belongs with the authorised client function or directly appointed qualified provider, not the analytical grouping rule.

Order the work by the next action it requires. A source-retrieval task, a factual question ready for client consideration and a question dependent on specialist interpretation need different owners. Expose dependencies that affect several candidates, such as a missing adjustment extract or an unresolved supplier-identity mapping. Resolving that shared dependency may be more useful than repeatedly examining individual candidates whose evidence remains incomplete.

Preserve exclusions when new data arrives. Link later extracts to the existing case history and identify whether they change the explanation, introduce a separate event or repeat evidence already examined. A resolved data artefact should not reappear as a fresh opportunity simply because the rule ran again. Retain the reason for exclusion and the condition that would justify reopening it rather than deleting the source history.

Prepare a client-led supplier discussion

Turn each supported question into a discussion file that the client relationship owner can use. Open with the transaction identifiers, the factual difference and the specific explanation or supporting record being requested. Separate observations from assumptions and avoid language asserting wrongdoing or entitlement. Include enough of the transaction chain to explain the question without disclosing unrelated supplier records or internal analysis.

Put relevant limitations beside the question. If an adjustment period is missing or a document cannot be matched reliably, state that boundary in the client file. Identify any interpretation the client's appointed advisers still need to supply. The relationship owner should know what the evidence supports before deciding whether to contact the supplier, seek more internal information or leave the item unresolved.

Reserve commercial action to client management. The client decides whether to raise the question, what position to take, who speaks for the organisation and whether to negotiate or settle. Analytical support can organise evidence, record responses and identify factual differences without making commitments on the client's behalf. Preparing a potential-recovery file does not authorise withholding payment, changing supplier instructions or moving funds.

Maintain a supplier-response log linked to the released question and attachments. Record the response, new source references and any explanation that changes the case. Distinguish a supplier acknowledging receipt from agreeing with the facts or accepting a proposed commercial resolution. Route new documents back through the same matching and overlap checks; a credit supplied during discussion may affect several candidates already in the portfolio.

Separate document exchange from operational change. A message requesting altered payment instructions belongs in the client's established supplier-change process, not as an incidental amendment by the analyst handling the case. Questions about competing contractual interpretations belong with directly appointed qualified advisers. Keep the discussion file focused on the evidence and the decisions assigned to each role, with the supplier's position recorded rather than predicted.

Close the record and change the process

Define closure by disposition, not by removing the item from a report. A candidate may be explained as a data issue, resolved through additional records, left without sufficient evidence or taken to a client-confirmed commercial outcome. Preserve the supporting source, responsible client role and remaining limitations. Management deciding not to pursue an item does not turn the underlying question into a resolved fact.

Keep the supplier's response distinct from subsequent execution. An offered adjustment, a credit document supplied and the client's confirmation of how it was processed are different events. Ask the authorised client function to provide the relevant status and source reference. Do not label an item recovered merely because the supplier agreed to discuss it or issued a document whose treatment has not been established.

Connect recurring explanations to a specific process change. In the illustrative duplicate scenario, an import routine might be presenting a cancelled instruction and its replacement as unrelated events. A matching-rule correction should preserve that relationship and be tested against both replacement processing and genuinely separate transactions. Where the gap lies in operating practice instead, assign the change to the client owner of that workflow.

Carry supported patterns into category governance without treating analytical volume as supplier performance. Distinguish supplier-originated discrepancies from internal ordering errors, incomplete acceptance records and extraction defects. Use the explanation to identify whether the category needs clearer commercial instructions, a changed receiving hand-off or a better source record. A high concentration of rule hits alone is not a reason to change the supplier strategy.

Test the corrective action against the failure that produced the case, and record what remains outside the test. Link subsequent evidence to the original candidate so that recurrence is visible. Hand over the open questions, retained exclusions, supplier exchanges and assigned process actions with their source references. The result is a maintained potential-recovery and improvement file with stated inputs and limitations, not a promise of supplier agreement or recovered value.

Where this connects to a mandate

Procurement value recovery connects procure-to-pay analysis to a potential-recovery portfolio for client-led commercial discussions. Strategic sourcing and category transformation connects recurring exceptions to priority-category design, supplier-market strategy and commercial governance. Mericad provides non-regulated analytical and operational support with stated inputs and limitations; client management decides, signs, pays and operates, while directly appointed qualified providers perform reserved work.