Create a debit memo from an invoice

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.

Creates an ad-hoc debit memo from an invoice.

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

path Parameters

The ID or number of an invoice that you want to create a debit memo from. For example, 2c93808457d787030157e030d10f3f64 or INV00000001.

header Parameters
string <= 255 characters

Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types.

With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident.


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.


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.


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

string <= 64 characters

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 (').


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.


The minor version of the Zuora REST API. See Minor Version for information about REST API version control.

This header affects the availability of the following request fields:

  • items > comment
  • items > description
Request Body schema: application/json

Whether debit memos are automatically picked up for processing in the corresponding payment run. By default, debit memos are automatically picked up for processing in the corresponding payment run.

Default: false

Whether to automatically post the debit memo after it is created. Setting this field to true, you do not need to separately call the Post debit memo operation to post the debit memo.

string [ 0 .. 255 ] characters

Comments about the debit memo.

string <date>

The date when the debit memo takes effect.


The ID of the invoice that the debit memo is created from.

  • If this field is specified, its value must be the same as the value of the invoiceId path parameter. Otherwise, its value overrides the value of the invoiceId path parameter.
  • If this field is not specified, the value of the invoiceId path parameter is used.
Array of objects (items) <= 1000 items

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


A code identifying the reason for the transaction. The value must be an existing reason code or empty. If you do not specify a value, Zuora uses the default reason code.

Default: true

Whether to automatically calculate taxes in the debit memo.

string <= 255 characters

ID of the corresponding object in NetSuite. Only available if you have installed the Zuora Connector for NetSuite.

string <= 255 characters

Status of the debit memo's synchronization with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.

string <= 255 characters

Date when the debit memo was synchronized with NetSuite. Only available if you have installed the Zuora Connector for NetSuite.

property name*
additional property

Custom fields of the Debit Memo object. The name of each custom field has the form customField__c. Custom field names are case sensitive. See Manage Custom Fields for more information.

Request samples
  • "autoPay": true,
  • "comment": "the comment",
  • "effectiveDate": "2017-11-30",
  • "items": [
  • "reasonCode": "Charge Dispute"
Response samples
  • "id": "402890555a87d7f5015a89251edc0045",
  • "number": "DM00000003",
  • "accountId": "402890555a7d4022015a7dabf5f60088",
  • "billToContactId": "2c93808457d787030157e031bb3de684",
  • "paymentTerm": "Net 30",
  • "debitMemoDate": "2017-11-30",
  • "targetDate": null,
  • "dueDate": "2017-12-30",
  • "postedOn": null,
  • "postedById": null,
  • "status": "Draft",
  • "sourceType": "Invoice",
  • "amount": 0.01,
  • "taxAmount": 0.01,
  • "totalTaxExemptAmount": 0,
  • "balance": 0.01,
  • "beAppliedAmount": 0,
  • "autoPay": true,
  • "comment": "the comment",
  • "referredInvoiceId": "402890555a7d4022015a7dadb3b300a4",
  • "transferredToAccounting": "No",
  • "reasonCode": "Charge Dispute",
  • "referredCreditMemoId": "402881e522cf4f9b0222cf5d82860002",
  • "excludeItemBillingFromRevenueAccounting": true,
  • "createdDate": "2017-03-01 17:13:15",
  • "createdById": "402881e522cf4f9b0122cf5d82860002",
  • "updatedDate": "2017-03-01 17:13:15",
  • "updatedById": "402881e522cf4f9b0122cf5d82860002",
  • "cancelledOn": null,
  • "cancelledById": null,
  • "latestPDFFileId": null,
  • "taxStatus": null,
  • "taxMessage": null,
  • "sequenceSetId": null,
  • "success": true