Create a payment using Zuora UI
Create payments for invoices, debit memos, or as standalone transactions in Zuora, with options for full, partial, or unapplied payments.
You can create a payment in the following scenarios:
-
A full or partial payment on an invoice or debit memo
-
A full or partial payment on several invoices and debit memos
-
An unapplied payment
-
A reserved payment - For more information, see Prepaid Cash with Drawdown .
-
A standalone payment - If you only need to create and process an electronic payment in Zuora through a Zuora gateway integration but will settle the payment outside of Zuora, you can create a standalone payment. For a standalone payment, you can specify a currency different from the payment currency in the customer account settings.Note: The support for standalone payments is in the Early Adopter phase. If you want to use this feature, submit a request at Zuora Global Support to enable it.
After creating a payment on an invoice and debit memo, the related payment transactions are displayed on the invoice or debit memo detail page. You can find payment details about the invoice and debit memo on this page.
When creating a payment, the total number of invoices and debit memos that the payment will apply to must be less than or equal to 1,000.
If the Proration application rule is used, when creating a payment, the following quantity must be less than or equal to 10,000:
(number of invoice items + number of debit memo items) * number of payment items
Otherwise, the First In First Out rule will be used instead of the Proration rule.
Zuora provides you with two ways to create a payment: external payment and electronic payment.
To create a payment from the REST API, see POST Create Payment .
Points to note while customizing payment numbers
-
The
Payment numberfield is only available in the request body to create external and electronic payment operations through both the UI and API. -
Updating payment numbers is not supported. For example, if you set the value of payment number to P-00001, you cannot change this value once the payment record is saved.
-
When a payment with a custom payment number is deleted, the system will change the value by adding a random suffix. For example, if your payment number is PAY-ECS-001, it will be changed to PAY-ECS-001_14230a434ea. This behavior ensures that if you use the same payment number in the future, it will still be unique.
-
Avoid using system default prefixes , prefixes for internal use , or any customized prefixes you have configured . This may cause a numbering conflict while naming the payment numbers. If the conflict occurs, you can change the prefix on the payment number, or change the starting number to a value greater than the current value.