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.

Request
path Parameters
invoiceKey
required
string

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

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 should not set this header.

Zuora-Org-Ids
string

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.

zuora-version
string

The minor API version. For a list of available minor versions, see API upgrades.

Request Body schema: application/json
required
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 debit memo operation to post the debit memo.

billToContactId
string

The ID of the bill-to contact associated with the debit memo.

Note: This field is available only if you have Flexible Billing Attributes enabled for your tenant.

comment
string [ 0 .. 255 ] characters

Comments about the debit memo.

effectiveDate
string <date>

The date when the debit memo takes effect.

invoiceId
required
string

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

Array of objects (items) <= 1000 items

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

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.

soldToContactId
string

The ID of the sold-to contact associated with the debit memo.

Note: This field is available only if you have Flexible Billing Attributes enabled for your tenant.

soldToSameAsBillTo
boolean

Whether the sold-to contact and bill-to contact are the same entity.

The created debit memo has the same bill-to contact and sold-to contact entity only when all the following conditions are met in the request body:

  • This field is set to true.
  • The billToContactId field is specified.
  • The soldToContactId field is not specified.
taxAutoCalculation
boolean
Default: true

Whether to automatically calculate taxes in the debit memo.

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 Custom Fields for more information.

Responses
200
500

Internal Server Error

4XX

Request Errors

post/v1/invoices/{invoiceKey}/debitmemos
Request samples
application/json
{
  • "autoPay": true,
  • "comment": "the comment",
  • "effectiveDate": "2017-11-30",
  • "items": [
    ],
  • "reasonCode": "Charge Dispute"
}
Response samples
application/json
{
  • "accountId": "4028ab1f87121698018712fb22312b70",
  • "accountNumber": "AN_Test11679650660490",
  • "amount": 1,
  • "autoPay": true,
  • "balance": 1,
  • "beAppliedAmount": 0,
  • "billToContactId": null,
  • "billToContactSnapshotId": null,
  • "cancelledById": null,
  • "cancelledOn": null,
  • "comment": "the comment",
  • "createdById": "bd19d326bce5465c81df19d3262954c3",
  • "createdDate": "2023-03-24 15:08:37",
  • "currency": "USD",
  • "debitMemoDate": "2023-04-29",
  • "dueDate": "2023-04-29",
  • "einvoiceErrorCode": null,
  • "einvoiceErrorMessage": null,
  • "einvoiceFileId": null,
  • "einvoiceStatus": null,
  • "id": "4028ab1f87121698018712fc005a2ba7",
  • "invoiceGroupNumber": "N-0001",
  • "latestPDFFileId": null,
  • "number": "DM00000001",
  • "organizationLabel": "MS US",
  • "paymentTerm": null,
  • "postedById": null,
  • "postedOn": null,
  • "reasonCode": "Correcting invoice error",
  • "referredCreditMemoId": null,
  • "referredInvoiceId": "4028ab1f87121698018712fb2a3b2b91",
  • "sequenceSetId": null,
  • "soldToContactId": null,
  • "soldToContactSnapshotId": null,
  • "sourceType": "Invoice",
  • "status": "Draft",
  • "success": true,
  • "targetDate": null,
  • "taxAmount": 0,
  • "taxMessage": null,
  • "taxStatus": null,
  • "totalTaxExemptAmount": 0,
  • "transferredToAccounting": "No",
  • "updatedById": "bd19d326bce5465c81df19d3262954c3",
  • "updatedDate": "2023-03-24 15:08:37"
}