PUT /v1/creditmemos/{creditMemoKey}/unapply

Note: This operation is only available if you have Invoice Settlement enabled. The Invoice Settlement feature is generally available as of Zuora Billing Release 296 (March 2021). This feature includes Unapplied Payments, Credit and Debit Memo, and Invoice Item Settlement. If you want to enable Invoice Settlement, see Invoice Settlement Enablement and Checklist Guide for more information.

Unapplies an applied credit memo from one or more invoices and debit memos. The full applied amount from invoices and debit memos is transferred into the unapplied amount of the credit memo.

You can unapply a credit memo from an invoice or a debit memo only if you have the user permission. See Billing Roles for more information.

When you unapply a credit memo, the total number of credit memo items and the items that credit memo items to be unapplied from must be less than or equal to 15,000.

If the limit is hit, you can follow the following instructions:

If the Proration application rule is used, when unapplying credit memos, the following quantity must be less than or equal to 15,000:

(number of invoice items + number of debit memo items) * number of credit memo items

Otherwise, the First In First Out rule will be used instead of the Proration rule.

Servers

Path parameters

Name Type Required Description
creditMemoKey String Yes

The unique ID or number of a credit memo. For example, 8a8082e65b27f6c3015ba45ff82c7172.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Content-Encoding String No

Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.

Zuora-Track-Id String No

A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue.

The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), and quote (').

Authorization String No

The value is in the Bearer {token} format where {token} is a valid OAuth token generated by calling Create an OAuth token.

Zuora-Entity-Ids String No

An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header.

Zuora-Org-Ids String No

Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.

The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails.

If the header is not set, the operation is performed in scope of the user's accessible orgs.

Accept-Encoding String No

Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.

If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.

Request body fields

Name Type Required Description
effectiveDate String No

The date when the credit memo is unapplied.

debitMemos[] Array No

Container for debit memos that the credit memo is unapplied from. The maximum number of debit memos is 1,000.

debitMemos[].debitMemoId String Yes

The unique ID of the debit memo that the credit memo is unapplied from.

debitMemos[].amount Number Yes

The credit memo amount to be unapplied from the debit memo.

debitMemos[].items[] Array No

Container for items. The maximum number of items is 1,000.

debitMemos[].items[].debitMemoItemId String No

The ID of the debit memo item that the credit memo item is unapplied from.

debitMemos[].items[].amount Number Yes

The amount that is unapplied from the specific item.

debitMemos[].items[].taxItemId String No

The ID of the debit memo taxation item that the credit memo taxation item is unapplied from.

debitMemos[].items[].creditTaxItemId String No

The ID of the credit memo taxation item.

debitMemos[].items[].creditMemoItemId String No

The ID of the credit memo item.

invoices[] Array No

Container for invoices that the credit memo is unapplied from. The maximum number of invoices is 1,000.

invoices[].amount Number Yes

The credit memo amount to be unapplied from the invoice.

invoices[].items[] Array No

Container for items. The maximum number of items is 1,000.

invoices[].items[].invoiceItemId String No

The ID of the invoice item that the credit memo item is unapplied from.

invoices[].items[].amount Number Yes

The amount that is unapplied from the specific item.

invoices[].items[].taxItemId String No

The ID of the invoice taxation item that the credit memo taxation item is unapplied from.

invoices[].items[].creditTaxItemId String No

The ID of the credit memo taxation item.

invoices[].items[].creditMemoItemId String No

The ID of the credit memo item.

invoices[].invoiceId String Yes

The unique ID of the invoice that the credit memo is unapplied from.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.