HelperStable

Mark payment unmatched

Explicitly classifies an incoming Payment as unmatched when no business allocation should be retained.

Contexte financier
Mark payment unmatched
Finance
Typed result

Vue d’ensemble

Explicitly classifies an incoming Payment as unmatched when no business allocation should be retained.

Exemple

After reviewing a bank transfer that cannot be attributed, remove it from automatic matching while retaining the reason.

Parameters 2

paymentRequisPayment
Canonical received payment or payment to refund according to the operation.
reasonOptionnelstring
Business reason for the refund or applied classification.

Outputs 1

paymentPayment
Canonical payment in its updated state after the operation.

Behavior

The payment is preserved, but its reconciliation state explicitly indicates that it remains unmatched.

Key point Always distinguish the canonical object created by Ormuz from any external effect. A payment or refund intent in draft status does not prove that a provider executed the movement of funds.

Limits and responsibilities

  • This transition neither refunds nor deletes the payment.
  • Use it only when the process genuinely decides not to retain any allocation at this stage.