AutoAssignPaymentTransactionCommandRequestInput
Runs the automatic assignment for one payment transaction now, whatever the setting for automatic assignment says. It finds the document by the transaction ID of an existing payment, by the payment reference, the amount, the customer number and the name, and can assign to sales orders, sales invoices and incoming invoices, and confirm refunds. When several documents match about equally well, nothing is assigned. A payment of an incoming invoice it records cannot be removed with ‘UnassignPaymentTransaction’. A document that becomes fully paid starts its workflows. Errors: PAYMENT_TRANSACTION_NOT_FOUND (the payment transaction was not found); PAYMENT_ACCOUNT_HIDDEN (the payment account is hidden; show it with ‘ShowPaymentAccount’ first); PAYMENT_TRANSACTION_IGNORED (the transaction is ignored; unignore it first); PAYMENT_TRANSACTION_IS_FEE (the transaction is a fee; fees are attached to the sales order of the transaction they belong to); PAYMENT_TRANSACTION_NOT_COMPLETED (the transaction is not completed yet); NO_OPEN_AMOUNT (nothing of the transaction is left to assign). - Request
AutoAssignPaymentTransactionCommandRequestInputFields
The ID of the payment transaction.
Whether to suppress the automatic workflows this call would start: the events of the payment transaction and, when a sales order or a sales invoice becomes fully paid, its workflows. Events for other systems are still published. Defaults to false when omitted.
Client-supplied idempotency key. When provided, a repeated request with the same key and payload replays the original result instead of re-executing the mutation.
Was this page helpful?