Procurement card merchant split transaction approval

What is being tested

Did split card transactions bypass a purchase approval threshold for one underlying order? The boundary for this investigation is procurement card merchant split transaction approval. Begin with the disputed transaction or population, then identify which merchant transaction detail establishes the observed position and which underlying order supports the comparison. A difference in totals should not replace this question.

Evidence: merchant transaction detail

For procurement card merchant split transaction approval, merchant transaction detail must be linked to underlying order. Preserve the source owner, transaction reference, period and accepted version. Explain which field answers the financial question and which facts still require confirmation. Incomplete supporting records should create a named evidence gap rather than an assumed quantity, price or entitlement.

Evidence: underlying order

For procurement card merchant split transaction approval, underlying order must be linked to approval threshold. Keep the accepted version, covered scope and relationship to earlier documents. Identify whether it adds, replaces or transfers an obligation. A newer document should not be assumed to govern an earlier transaction unless its scope and effective period support that conclusion.

Evidence: approval threshold

For procurement card merchant split transaction approval, approval threshold must be linked to card approval record. Preserve the authorized sender, accepted scope and event timestamp. Distinguish a request from its acceptance and check whether the approver had authority for this change. Later approval should remain visible as a separate event rather than rewrite the original sequence.

Evidence: card approval record

For procurement card merchant split transaction approval, card approval record must be linked to merchant transaction detail. Preserve the authorized sender, accepted scope and event timestamp. Distinguish a request from its acceptance and check whether the approver had authority for this change. Later approval should remain visible as a separate event rather than rewrite the original sequence.

Reconciliation logic

Aggregate related purchases using order evidence before comparing the authorized limit. Build the comparison at the level identified by merchant transaction detail and retain the governing version from underlying order. Show intermediate classifications and excluded items separately; a net total can hide an unsupported component or a correctly offset correction.

Exception conditions

Separate legitimate orders can share a merchant and date. Treat the item as an unresolved exception only when the comparison described here cannot be supported by the linked merchant transaction detail, underlying order, approval threshold, card approval record. Document the conflicting input or rule. A plausible operational explanation requires validation, but it should not be discarded to maximize an apparent financial difference.

Human review and outcome

AP and procurement validate order relationship and policy exceptions. Route a supported approval exception without labeling all split payments improper. Keep the reviewer's reason and source references with that disposition. A supported correction should be followed to the revised record or settlement; an accepted explanation can close the question with no adjustment. Missing authority or evidence should remain an open task rather than a confirmed recovery.

Limitations and processing boundary

A PO, acceptance record or supplier credit request alone cannot prove a complete recovery. The authoritative supplier, contract, PO, invoice and receipt processor is not complete. Treat commercial interpretation, authorized acceptance and final credit application as separate validation steps. In this scenario, absence of merchant transaction detail or underlying order limits whether the comparison can be completed. The review method describes what people should validate, not a promise that AuditRes automatically detects or executes this specific outcome.

AuditRes pathway

Discuss procurement card merchant split transaction approval in the Procurement workspace. Review current plans, the shared platform and secure evidence requirements; use the existing contact path to confirm the sources and validation this scope requires.

AuditRes Procurement: Available for onboarding. Public previews use synthetic demonstration data; production processing remains gated until applicable customer sources and authoritative processors are connected and validated.

Neighboring financial questions

Procurement resource hub · All guides in this evidence collection