---
title: "Create debit memos"
method: POST
path: "/v1/debit-memos/bulk"
tags: ["Debit Memos"]
---

# Create debit memos

`POST /v1/debit-memos/bulk`

**Note:** This operation is only available if you have [Invoice Settlement](https://docs.zuora.com?resourceId=billing-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](https://docs.zuora.com?resourceId=billing-invoice-settlement-migration-checklist-and-guide) for more information.

Creates multiple debit memos from invoices or product rate plan charges. You can create a maximum of 50 debit memos in one single request. 

- If you set the `sourceType` request field to `Invoice`, you can create multiple debit memos from invoices.
- If you set the `sourceType` request field to `Standalone`, you can create multiple debit memos from product rate plan charges.

The debit memos that are created are each in separate database transactions. If the creation of one debit memo fails, other debit memos can still be created successfully.

You can create  debit memos only if you have the user permission. See [Billing Roles](https://docs.zuora.com?resourceId=platform-billing-roles) for more information.

## Headers

- `Idempotency-Key` string
- `Accept-Encoding` string
- `Content-Encoding` string
- `Zuora-Track-Id` string
- `Zuora-Entity-Ids` string
- `Zuora-Org-Ids` string
- `Zuora-Version` string

## Request body

- union
  - BulkCreateDebitMemosFromInvoiceRequest
    - `sourceType` 'Invoice', required — The type of the source where debit memos are created. This enum field has the following values: - `Invoice`: By setting this field to `Invoice`, you can create multiple debit memos from invoices. - `Standalone`: By setting this field to `Standalone`, you can create multiple debit memos from product rate plan charges. The specific schema of the `memos` object field in the request body depends on the value of the `sourceType` field. - To view the `memos` schema applicable to debit memo creation from invoices, select `Invoice` from the following drop-down list. - To view the `memos` schema applicable to debit memo creation from product rate plan charges, select `Standalone` from the following drop-down list.
    - `memos` DebitMemoFromInvoiceRequest[] — The container for a list of debit memos. The maximum number of debit memos is 50.
      - `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 — 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](https://developer.zuora.com/api-references/api/operation/PUT_PostDebitMemo) 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 <a href="https://docs.zuora.com?resourceId=billing-attributes-for-flexible-billing" target="_blank">Flexible Billing Attributes</a> enabled for your tenant.
      - `comment` string — Comments about the debit memo.
      - `effectiveDate` string, date — The date when the debit memo takes effect.
      - `invoiceId` string, required — The ID of the invoice that the debit memo is created from.
      - `items` DebitMemoItemFromInvoiceItemType[] — Container for items. The maximum number of items is 1,000.
        - `amount` number, double, required — The amount of the debit memo item.
        - `description` string — The description of the debit memo item. **Note**: This field is available only if you are on the latest Zuora API version, or you set the `Zuora-Version` request header to `257.0` or a later available version.
        - `financeInformation` object — Container for the finance information related to the debit memo item.
          - `deferredRevenueAccountingCode` string — The accounting code for the deferred revenue, such as Monthly Recurring Liability.
          - `recognizedRevenueAccountingCode` string — The accounting code for the recognized revenue, such as Monthly Recurring Charges or Overage Charges.
          - `revenueRecognitionRuleName` string — The name of the revenue recognition rule governing the revenue schedule.
        - `invoiceItemId` string — The ID of the invoice item.
        - `quantity` number, double — The number of units for the debit memo item.
        - `serviceEndDate` string, date — The service end date of the debit memo item.
        - `serviceStartDate` string, date — The service start date of the debit memo item.
        - `skuName` string, required — The name of the charge associated with the invoice.
        - `taxItems` DebitMemoTaxItemFromInvoiceTaxItemType[] — Container for taxation items.
          - `amount` number, double, required — The amount of the debit memo taxation item.
          - `financeInformation` object — Container for the finance information related to the source taxation item.
            - `salesTaxPayableAccountingCode` string — The accounting code for the sales taxes payable.
          - `jurisdiction` string — The jurisdiction that applies the tax or VAT. This value is typically a state, province, county, or city.
          - `locationCode` string — The identifier for the location based on the value of the `taxCode` field.
          - `sourceTaxItemId` string — The ID of the source taxation item.
          - `taxCode` string — The tax code identifies which tax rules and tax rates to apply to a specific debit memo.
          - `taxCodeDescription` string — The description of the tax code.
          - `taxDate` string, date — The date that the tax is applied to the debit memo, in `yyyy-mm-dd` format.
          - `taxExemptAmount` number, double — The calculated tax amount excluded due to the exemption.
          - `taxName` string — The name of taxation.
          - `taxRate` number, double — The tax rate applied to the debit memo.
          - `taxRateDescription` string — The description of the tax rate.
          - `taxRateType` 'Percentage' | 'FlatFee' — The type of the tax rate applied to the debit memo.
        - `taxMode` 'TaxExclusive' | 'TaxInclusive' — The tax mode of the debit memo item, indicating whether the amount of the debit memo item includes tax. **Note**: You can set this field to `TaxInclusive` only if the `taxAutoCalculation` field is set to `true`. If you set `taxMode` to `TaxInclusive`, you cannot input tax amounts for debit memo items. The corresponding invoice item must use the same tax engine as the debit memo item to calculate tax amounts.
        - `unitOfMeasure` string — The definable unit that you measure when determining charges.
      - `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 <a href="https://docs.zuora.com?resourceId=billing-attributes-for-flexible-billing" target="_blank"> Flexible Billing Attributes</a> 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 — Whether to automatically calculate taxes in the debit memo.
      - `IntegrationId__NS` string — ID of the corresponding object in NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
      - `IntegrationStatus__NS` string — Status of the debit memo's synchronization with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
      - `SyncDate__NS` string — Date when the debit memo was synchronized with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
  - BulkCreateDebitMemosFromChargeRequest
    - `sourceType` 'Standalone', required — The type of the source where debit memos are created. This enum field has the following values: - `Invoice`: By setting this field to `Invoice`, you can create multiple debit memos from invoices. - `Standalone`: By setting this field to `Standalone`, you can create multiple debit memos from product rate plan charges. The specific schema of the `memos` object field in the request body depends on the value of the `sourceType` field. - To view the `memos` schema applicable to debit memo creation from invoices, select `Invoice` from the following drop-down list. - To view the `memos` schema applicable to debit memo creation from product rate plan charges, select `Standalone` from the following drop-down list.
    - `memos` DebitMemoFromChargeRequest[] — The container for a list of debit memos. The maximum number of debit memos is 50.
      - `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 — 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](https://developer.zuora.com/api-references/api/operation/PUT_PostDebitMemo) operation to post the debit memo.
      - `charges` DebitMemoFromChargeDetailType[] — Container for product rate plan charges. The maximum number of items is 1,000.
        - `amount` number, double — The amount of the debit memo item. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `224.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
        - `excludeItemBillingFromRevenueAccounting` boolean — The flag to exclude the debit memo item from revenue accounting. **Note**: This field is only available if you have the Billing - Revenue Integration feature enabled.
        - `description` string — The description of the product rate plan charge. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `257.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
        - `financeInformation` object — Container for the finance information related to the product rate plan charge associated with the debit memo.
          - `deferredRevenueAccountingCode` string, nullable — The accounting code for the deferred revenue, such as Monthly Recurring Liability.
          - `recognizedRevenueAccountingCode` string, nullable — The accounting code for the recognized revenue, such as Monthly Recurring Charges or Overage Charges.
          - `revenueRecognitionRuleName` string, nullable — The name of the revenue recognition rule governing the revenue schedule.
        - `productRatePlanChargeId` string, required — The ID of the product rate plan charge that the debit memo is created from. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `257.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
        - `quantity` number, double — The number of units for the debit memo item.
        - `serviceEndDate` string, date — The service end date of the debit memo item. If not specified, the effective end date of the corresponding product rate plan will be used.
        - `serviceStartDate` string, date — The service start date of the debit memo item. If not specified, the effective start date of the corresponding product rate plan will be used.
      - `comment` string — Comments about the debit memo.
      - `currency` string — The code of a currency as defined in Billing Settings through the Zuora UI. If you do not specify a currency during debit memo creation, the default account currency is applied. The currency that you specify in the request must be configured and activated in Billing Settings. **Note**: This field is available only if you have the <a href="https://docs.zuora.com?resourceId=billing-multiple-currencies-overview" target="_blank">Multiple Currencies</a> feature enabled.
      - `customRates` DebitMemoFromChargeCustomRatesType[] — 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. - You cannot set the custom rates, if both the **Automatically include additional Currency Conversion information in data source exports** option and **Fx data** feature are enabled. - DebitMemo, DebitMemoItem, and DebitMemoItemTax will utilize the provided custom Fx rate to convert amounts from the transactional currency to the home currency.
        - `currency` string, required — The currency code for either Reporting or Home currency. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `224.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
        - `customFxRate` number, required — The Custom FX conversion rate between home currency and transactional currency items. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `224.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
        - `rateDate` string, date — The date on which a particular currency rate is fixed or obtained on. **Note**: This field is available only if you are on the latest Zuora API minor version, or you set the `Zuora-Version` request header to `224.0` or [a later available version](https://developer.zuora.com/v1-api-reference/api-versions/#minor-version).
      - `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.
      - `number` string — A customized debit memo number with the following format requirements: - Max length: 32 characters - Acceptable characters: a-z,A-Z,0-9,-,_ The value must be unique in the system, otherwise it may cause issues with bill runs and subscriptions. If not provided, Zuora will generate a unique number per the sequence set on the account level. If the account-level sequence set is not specified, the system default sequence set is used. For more information, see <a href="https://docs.zuora.com?resourceId=billing-config-of-prefix-and-number-for-billing-docs" target="_blank">Configure prefix and numbering for billing documents</a>.
      - `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 — ID of the corresponding object in NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
      - `IntegrationStatus__NS` string — Status of the debit memo's synchronization with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
      - `SyncDate__NS` string — Date when the debit memo was synchronized with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).

## Response `200`

OK

- BulkDebitMemosResponseType
  - `memos` GETDebitMemoType[] — The container for a list of debit memos.
    - `accountId` string — The ID of the customer account associated with the debit memo.
    - `accountNumber` string — The number of the customer account associated with the debit memo.
    - `amount` number, double — The total amount of the debit memo.
    - `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.
    - `balance` number, double — The balance of the debit memo.
    - `beAppliedAmount` number, double — The amount that is applied to the debit memo.
    - `billToContactId` string, nullable — The ID of the bill-to contact associated with the debit memo. The value of this field is `null` if you have the [Flexible Billing Attributes](https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes) feature disabled.
    - `billToContactSnapshotId` string, nullable — The ID of the bill-to contact snapshot associated with the debit memo. The value of this field is `null` if the bill rule [Preserve snapshot of bill-to and sold-to contacts when billing documents are posted](https://docs.zuora.com?resourceId=billing-billing-rules-billing-document) is disabled.
    - `cancelledById` string, nullable — The ID of the Zuora user who cancelled the debit memo.
    - `cancelledOn` string, nullable — The date and time when the debit memo was cancelled, in `yyyy-mm-dd hh:mm:ss` format.
    - `currency` string, nullable — The currency of the debit memo. **Note:** By default, the currency on a billing document matches the default currency set on the associated account. However, Zuora now offers a Multiple Currencies feature to support different currencies for billing documents, allowing flexibility beyond the account-level currency. For more information, see <a href="https://docs.zuora.com?resourceId=billing-multiple-currencies-overview" target="_blank">Multiple Currency</a>.
    - `comment` string, nullable — Comments about the debit memo.
    - `createdById` string — The ID of the Zuora user who created the debit memo.
    - `createdDate` string — The date and time when the debit memo was created, in `yyyy-mm-dd hh:mm:ss` format. For example, 2017-03-01 15:31:10.
    - `debitMemoDate` string, date — The date when the debit memo takes effect, in `yyyy-mm-dd` format. For example, 2017-05-20.
    - `dueDate` string, date — The date by which the payment for the debit memo is due, in `yyyy-mm-dd` format.
    - `einvoiceErrorCode` string, nullable — The error code returned when the e-invoice file status is `Failed`. This code can either be a Zuora-generated error code or one returned by a third-party e-invoicing service provider. **Note**: This field is available only if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/e-invoicing/e-invoicing-overview" target="_blank">E-Invoicing</a> feature in **Early Adopter** phase enabled.
    - `einvoiceErrorMessage` string, nullable — The error message returned when the e-invoice file status is `Failed`. This message can either be a Zuora-generated error message or one returned by a third-party e-invoicing service provider. **Note**: This field is available only if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/e-invoicing/e-invoicing-overview" target="_blank">E-Invoicing</a> feature in **Early Adopter** phase enabled.
    - `einvoiceFileId` string, nullable — The ID of the e-invoice file generated for the debit memo. **Note**: This field is available only if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/e-invoicing/e-invoicing-overview" target="_blank">E-Invoicing</a> feature in **Early Adopter** phase enabled.
    - `einvoiceStatus` 'Processing' | 'RetrieveTimeOut' | 'Generated' | 'Success' | 'Failed' | 'ConditionalSuccess' | 'ApprovedByAuthority' | 'Rejected', nullable — The status of the e-invoice file generation for the debit memo. - If e-invoice file generation succeeds, this field is either `Generated` or `Success`, and both the error code and message are empty, and the `eInvoiceFileId` field stores the ID of the generated e-invoice file. - If the responses from tax vendors such as Sovos or Avalara are taking too long, this field becomes `RetrieveTimeOut`. Once the vendor responds successfully, you can use the 'Resync E-Invoice Status' action to update the status automatically. You can view these updates in System Health telemetry. - If a failure occurs during e-invoice file generation, this field is `Failed` and an error code and an error message are returned respectively in the `einvoiceErrorCode` and `einvoiceErrorMessage` fields. - If e-invoice file generation conditionally succeeds, this field is `ConditionalSuccess` and an error code and an error message are returned respectively in the `einvoiceErrorCode` and `einvoiceErrorMessage` fields. - If the e-invoice file has been approved by the tax authority, this field is `ApprovedByAuthority`. The next status will be either `Success` or `Rejected`. - If the e-invoice file has been rejected by the government, this field is `Rejected`. You cannot resend this e-invoice; you must create a new invoice instead. **Note**: This field is available only if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/e-invoicing/e-invoicing-overview" target="_blank">E-Invoicing</a> feature in **Early Adopter** phase enabled.
    - `excludeItemBillingFromRevenueAccounting` boolean — The flag to exclude the debit memo item from revenue accounting. **Note**: This field is only available if you have the Billing - Revenue Integration feature enabled.
    - `id` string — The unique ID of the debit memo.
    - `invoiceGroupNumber` string, nullable — The number of the invoice group associated with the debit memo. The value of this field is `null` if you have the [Flexible Billing Attributes](https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes) feature disabled.
    - `latestPDFFileId` string, nullable — The ID of the latest PDF file generated for the debit memo.
    - `number` string — The unique identification number of the debit memo.
    - `organizationLabel` string — The organization that this object belongs to. Note: This field is available only when the Multi-Org feature is enabled.
    - `paymentTerm` string, nullable — The name of the payment term assoicated with the debit memo. The value of this field is `null` if you have the [Flexible Billing Attributes](https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes) feature disabled.
    - `postedById` string, nullable — The ID of the Zuora user who posted the debit memo.
    - `postedOn` string, nullable — The date and time when the debit memo was posted, in `yyyy-mm-dd hh:mm:ss` format.
    - `reasonCode` string — A code identifying the reason for the transaction. The value must be an existing reason code or empty.
    - `referredCreditMemoId` string, nullable — The ID of the credit memo from which the debit memo was created.
    - `referredInvoiceId` string, nullable — The ID of a referred invoice.
    - `sequenceSetId` string, nullable — The ID of the sequence set associated with the debit memo. The value of this field is `null` if you have the [Flexible Billing Attributes](https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes) feature disabled.
    - `communicationProfileId` string, nullable — The ID of the communication profile associated with the debit memo. **Note**: This field is available in the request body only if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes" target="_blank">Flexible Billing Attributes</a> feature turned on. The value is `null` in the response body without this feature turned on.
    - `soldToContactId` string, nullable — The ID of the sold-to contact associated with the debit memo. The value of this field is `null` if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes" target="_blank">Flexible Billing Attributes</a> feature disabled.
    - `soldToContactSnapshotId` string, nullable — The ID of the sold-to contact snapshot associated with the debit memo. The value of this field is `null` if you have the <a href="https://docs.zuora.com/en/zuora-billing/bill-your-customer/leverage-advanced-capabilities/flexible-billing/flexible-billing-attributes/overview-of-flexible-billing-attributes" target="_blank">Flexible Billing Attributes</a> feature disabled.
    - `sourceType` 'Subscription' | 'Standalone' | 'Order' | 'Consolidation' | 'Invoice' | 'CreditMemo' — The type of the debit memo source.
    - `status` 'Draft' | 'Posted' | 'Canceled' | 'Error' | 'PendingForTax' | 'Generating' | 'CancelInProgress' — The status of the debit memo.
    - `success` boolean — Returns `true` if the request was processed successfully.
    - `targetDate` string, date, nullable — The target date for the debit memo, in `yyyy-mm-dd` format. For example, 2017-07-20.
    - `taxAmount` number, double — The amount of taxation.
    - `taxMessage` string, nullable — The message about the status of tax calculation related to the debit memo. If tax calculation fails in one debit memo, this field displays the reason for the failure.
    - `taxStatus` 'Complete' | 'Error' | 'UnknownError' | 'DuplicateDoc' | 'InvalidRequest' | 'InvalidResponse' | 'TaxEngineError' | 'ConcurrentModify' | 'InternalServerError' | 'TaxCodeTemplateError' | 'Voided', nullable — The status of tax calculation related to the debit memo. **Note**: This field is only applicable to tax calculation by third-party tax engines. Also, the `Voided` status indicates that the tax transaction is successfully canceled on the tax vendor's side. If a tax transaction was successfully committed to the third-party tax engine but the invoice failed to post, Zuora automatically detects the issue and voids the tax transaction on the vendor's side.
    - `totalTaxExemptAmount` number, double — The calculated tax amount excluded due to the exemption.
    - `transferredToAccounting` 'Processing' | 'Yes' | 'No' | 'Error' | 'Ignore' — Whether the debit memo was transferred to an external accounting system. Use this field for integration with accounting systems, such as NetSuite.
    - `updatedById` string — The ID of the Zuora user who last updated the debit memo.
    - `updatedDate` string — The date and time when the debit memo was last updated, in `yyyy-mm-dd hh:mm:ss` format. For example, 2017-03-02 15:36:10.
    - `IntegrationId__NS` string — ID of the corresponding object in NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
    - `IntegrationStatus__NS` string — Status of the debit memo's synchronization with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
    - `SyncDate__NS` string — Date when the debit memo was synchronized with NetSuite. Only available if you have installed the [Zuora Connector for NetSuite](https://www.zuora.com/connect/app/?appId=265).
  - `success` boolean — Returns `true` if the request was processed successfully.

## Other responses

- `500` — Internal Server Error
- `4XX` — Request Errors

---

[API](https://skmtc.dev/zuora/apis/api-reference.md) · [All operations](https://skmtc.dev/zuora/apis/api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/zuora/api-reference/revisions/d11e237f3e54/schema)