Create supplier payment
Creates the supplier-payment instruction driven by Ormuz without fabricating an ERP accounting document or yet executing the bank movement.
Contexte financier
Create supplier payment
Finance
Typed result
Vue d’ensemble
Creates the supplier-payment instruction driven by Ormuz without fabricating an ERP accounting document or yet executing the bank movement.
Exemple
Prepare an approved EUR 12,500 supplier transfer with its date and end-to-end reference.
Parameters 9
supplier
Supplier receiving the supplier-payment instruction.
amount
Operation amount in minor monetary units. When optional, the node may use the residual amount defined by its contract.
currency
ISO 4217 currency used to interpret all amounts in the operation.
payment_method
Payment method planned for the outbound instruction.
status
Target or initial lifecycle state allowed by the operation contract.
payment_date
Business date planned for supplier-payment execution.
reference
Human-readable payment reference for teams and downstream systems.
end_to_end_reference
End-to-end bank reference that Ormuz asks the execution provider to propagate when supported.
metadata
Free-form integration metadata associated with the resource according to the flat
common.metadata contract.Outputs 1
supplier_payment
Canonical supplier-payment instruction after creation or cancellation.
Behavior
The node creates the canonical instruction with beneficiary, amount, payment method, and initial pending or scheduled state.
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
- Creating the instruction does not prove that the bank executed the payment.
- The supplier and details required for execution must be available through the mechanisms defined by the bank integration, not invented by this node.