Create a debit memo from a charge

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 a product rate plan charge. Zuora supports the creation of debit memos from any type of product rate plan charge. The charges can also have any amount and any charge model, except for discout charge models.

When debit memos are created from product rate plan charges, the specified amount with decimal places is now validated based on the decimal places supported by each currency.

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

Request
header Parameters
Idempotency-Key
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.

Accept-Encoding
string

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.

Content-Encoding
string

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.

Authorization
string

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

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

Zuora-Entity-Ids
string

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-version
string

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:

  • charges > amount
  • charges > memoItemAmount
  • charges > chargeId
  • charges > productRatePlanChargeId
  • charges > comment
  • charges > description
  • customRates > currency
  • customRates > customFxRate
  • customRates > rateDate
Request Body schema: application/json
accountId
string

The ID of the account associated with the debit memo.

Note: When creating debit memos from product rate plan charges, you must specify accountNumber, accountId, or both in the request body. If both fields are specified, they must correspond to the same account.

accountNumber
string

The number of the account associated with the debit memo.

Note: When creating debit memos from product rate plan charges, you must specify accountNumber, accountId, or both in the request body. If both fields are specified, they must correspond to the same account.

autoPay
boolean

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.

autoPost
boolean
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 a debit memo operation to post the debit memo.

Array of objects (charges) <= 1000 items

Container for product rate plan charges. The maximum number of items is 1,000.

comment
string [ 0 .. 255 ] characters

Comments about the debit memo.

Array of objects (customRates) <= 2 items

It contains Home currency and Reporting currency custom rates currencies. The maximum number of items is 2 (you can pass the Home currency item or Reporting currency item or both).

Note: The API custom rate feature is permission controlled.

dueDate
string <date>

The date by which the payment for the debit memo is due, in yyyy-mm-dd format.

effectiveDate
string <date>

The date when the debit memo takes effect.

reasonCode
string

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.

IntegrationId__NS
string <= 255 characters

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

IntegrationStatus__NS
string <= 255 characters

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

SyncDate__NS
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
any

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.

Responses
200
post/v1/debitmemos
Request samples
application/json
{
  • "accountId": "402890555a7e9791015a7f15fe44001c",
  • "autoPay": true,
  • "autoPost": false,
  • "charges": [
    ],
  • "comment": "the comment",
  • "customRates": [
    ],
  • "effectiveDate": "2017-10-17",
  • "reasonCode": "Correcting invoice error"
}
Response samples
application/json
{
  • "id": "402890555a87d7f5015a892f2ba10057",
  • "number": "DM00000006",
  • "accountId": "402890555a7e9791015a7f15fe44001c",
  • "debitMemoDate": "2017-10-17",
  • "targetDate": null,
  • "dueDate": "2017-11-16",
  • "postedOn": null,
  • "postedById": null,
  • "status": "Draft",
  • "sourceType": "Standalone",
  • "amount": 50,
  • "taxAmount": 0,
  • "totalTaxExemptAmount": 0,
  • "balance": 50,
  • "beAppliedAmount": 0,
  • "autoPay": true,
  • "comment": "the comment",
  • "referredInvoiceId": null,
  • "referredCreditMemoId": null,
  • "transferredToAccounting": "No",
  • "reasonCode": "Correcting invoice error",
  • "excludeItemBillingFromRevenueAccounting": true,
  • "createdDate": "2017-03-01 17:24:14",
  • "createdById": "402881e522cf4f9b0122cf5d82860002",
  • "updatedDate": "2017-03-01 17:24:14",
  • "updatedById": "402881e522cf4f9b0122cf5d82860002",
  • "cancelledOn": null,
  • "cancelledById": null,
  • "latestPDFFileId": null,
  • "taxStatus": null,
  • "taxMessage": null,
  • "billToContactId": null,
  • "paymentTerm": null,
  • "sequenceSetId": null,
  • "success": true
}