> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Date field changes in the WSDL

> Describes the date field changes and provides guidelines on how to check your SOAP API integrations.

Describes the date field changes and provides guidelines on how to check your SOAP API integrations.

In WSDL 68 and earlier, Zuora treats 56 SOAP API [date fields as dateTime fields](/docs/platform/system-management/additional-tenant-management-settings/dates-in-zuora/date-and-datetime-formats). From WSDL 69 and later, Zuora treats these fields as date fields. These fields are no longer compatible with dateTime values.

After checking and updating your integrations, you are ready to download and use [WSDL 69](/docs/platform/integration/apis/soap-api/zuora-wsdl) or later.​

## SOAP API

Before downloading and using WSDL 69, check your SOAP API integration to see if you are passing or receiving any dateTime values to or from date fields.

## AQuA API

The date field changes described in this article also apply to AQuA API versions 69 and later. This is because the API version of AQuA is based on the corresponding version of the Zuora WSDL—for example, API version 69 is based on WSDL version 69.

* If you want to use API version 69 or later, check your AQuA integration to ensure that you are not passing in or expecting to receive any dateTime values from date fields.
* If you don't want to use API version 69 or later, ensure that you specify the version you do want to use in the `apiVersion` field of your AQuA queries. Otherwise, AQuA will use the latest version by default, which will result in a different date field format and may cause your existing integration to break.

## Zuora CPQ

If you use Zuora CPQ, review the affected [date fields](/docs/platform/integration/apis/soap-api/date-field-changes-in-the-wsdl), and check and update your integration code.

## Changes in date fields since WSDL 69

To use WSDL 69 or later, check your Zuora SOAP API integration for date fields that send or receive dateTime values. The response from a date field will only be a date. The response from a dateTime field will only be a dateTime. If you try to pass a dateTime to a date field when using WSDL 69 or later, you will get an `INVALID_VALUE` error message.

To become compliant:

* Remove any time and time zone offset components from values you use with a SOAP API date field.
* Change your Zuora integration to expect that time and time zone offset components are not returned from a date field.

For example:

* 2015-02-28T23:23:23 becomes 2015-02-28
* 2015-02-28T23:23:23-08:00 becomes 2015-02-28

As an example, from WSDL 69 and later, `ContractEffectiveDate` is a date field and will only accept or return a date value:

![date](/_fern-img/9191cc85ab5a500ba03fa391f73cb176d45069e02049f3a1cd1172c8d5dbdd66.webp)

In WSDL 68 and earlier, `ContractEffectiveDate` is a dateTime field and will accept or return a dateTime value:

![datetime](/_fern-img/89ad7e6c35200aa966a78964f657dfc8cebc97fe17a54cf0c6e94b901d87c32a.webp)

## Date fields you need to check

After you change your date fields, you need to check the following fields in your SOAP API integration:

<table>
  <tr>
    <th>
      Object
    </th>

    <th>
      Field
    </th>
  </tr>

  <tr>
    <td>
      Account
    </td>

    <td>
      LastInvoiceDate

      TaxExemptEffectiveDate

      TaxExemptExpirationDate
    </td>
  </tr>

  <tr>
    <td>
      AccountingPeriod
    </td>

    <td>
      EndDate

      StartDate
    </td>
  </tr>

  <tr>
    <td>
      Amendment
    </td>

    <td>
      ContractEffectiveDate

      CustomerAcceptanceDate

      EffectiveDate

      ServiceActivationDate

      TermStartDate
    </td>
  </tr>

  <tr>
    <td>
      BillRun
    </td>

    <td>
      InvoiceDate

      TargetDate
    </td>
  </tr>

  <tr>
    <td>
      BillingPreviewRequest
    </td>

    <td>
      TargetDate
    </td>
  </tr>

  <tr>
    <td>
      BillingPreviewRun
    </td>

    <td>
      TargetDate
    </td>
  </tr>

  <tr>
    <td>
      ChargeMetrics
    </td>

    <td>
      UpToDate
    </td>
  </tr>

  <tr>
    <td>
      CreditBalanceAdjustment
    </td>

    <td>
      AdjustmentDate
    </td>
  </tr>

  <tr>
    <td>
      ExternalPaymentOptions
    </td>

    <td>
      EffectiveDate
    </td>
  </tr>

  <tr>
    <td>
      Invoice
    </td>

    <td>
      DueDate

      InvoiceDate

      TargetDate
    </td>
  </tr>

  <tr>
    <td>
      InvoiceAdjustment

      > **Note**
      >
      > This object is deprecated on Production in WSDL version 64.0.
    </td>

    <td>
      RevRecStartDate
    </td>
  </tr>

  <tr>
    <td>
      InvoiceItem
    </td>

    <td>
      RevRecStartDate

      ServiceEndDate

      ServiceStartDate
    </td>
  </tr>

  <tr>
    <td>
      InvoiceItemAdjustment
    </td>

    <td>
      AdjustmentDate

      ServiceEndDate

      ServiceStartDate
    </td>
  </tr>

  <tr>
    <td>
      InvoiceSplitItem
    </td>

    <td>
      InvoiceDate
    </td>
  </tr>

  <tr>
    <td>
      Payment
    </td>

    <td>
      EffectiveDate
    </td>
  </tr>

  <tr>
    <td>
      PaymentMethod
    </td>

    <td>
      MandateCreationDate

      MandateUpdateDate
    </td>
  </tr>

  <tr>
    <td>
      PaymentMethodSnapshot
    </td>

    <td>
      MandateCreationDate

      MandateUpdateDate
    </td>
  </tr>

  <tr>
    <td>
      Product
    </td>

    <td>
      EffectiveEndDate

      EffectiveStartDate
    </td>
  </tr>

  <tr>
    <td>
      ProductRatePlan
    </td>

    <td>
      EffectiveEndDate

      EffectiveStartDate
    </td>
  </tr>

  <tr>
    <td>
      RatePlanCharge
    </td>

    <td>
      ChargedThroughDate

      EffectiveEndDate

      EffectiveStartDate

      ProcessedThroughDate

      TriggerDate
    </td>
  </tr>

  <tr>
    <td>
      Refund
    </td>

    <td>
      RefundDate
    </td>
  </tr>

  <tr>
    <td>
      SubscribeInvoiceProcessingOptions
    </td>

    <td>
      InvoiceDate

      InvoiceTargetDate
    </td>
  </tr>

  <tr>
    <td>
      Subscription
    </td>

    <td>
      CancelledDate

      ContractAcceptanceDate

      ContractEffectiveDate

      ServiceActivationDate

      SubscriptionEndDate

      SubscriptionStartDate

      TermEndDate

      TermStartDate
    </td>
  </tr>

  <tr>
    <td>
      TaxationItem
    </td>

    <td>
      TaxDate
    </td>
  </tr>
</table>

## Querying SOAP API objects using ZOQL

Using WSDL 68 or earlier, you can filter date or dateTime fields with date or dateTime values.

When using WSDL 69 or later, you must use a dateTime value to filter a dateTime field. You can only use a date value to filter a date field.

For example you must use a date value to filter `ContractEffectiveDate` :

```
select AutoRenew from subscription where ContractEffectiveDate = '2015-02-28'
```

See [Zuora Object Query Language (ZOQL)](/docs/platform/data/legacy-query-methods/zoql) for more information.

## Data Source export actions

In WSDL 68 and earlier, the output format of dates and dateTimes in data source exports depends on how data was entered into Zuora. Integrations that use data source exports in WSDL 68 or earlier may need to accommodate both date and dateTime values for the same field.

From WSDL 69 and later, the output from dateTime fields is a dateTime and the output from date fields is a date. For example:

* A value of `2015-02-13T23:18:00-08:00` will be exported as `2015-02-13T23:18:00-08:00`
* A value of `2015-02-13` will be exported as `2015-02-13`

See Data Exports introduction for more information.