Customer Deposit

A customer deposit transaction records the funds received when a customer makes an advance payment for an order. This payment is recorded in the general ledger as a liability until the goods or services are delivered, and does not affect the customer's accounts receivable balance. After the order is filled, the deposit is applied against the invoice.

For more details about this type of transaction, see Customer Deposits.

The customer deposit record is defined in the tranCust (customers) XSD.

Supported Operations

Note:

You can also use the asynchronous equivalents of SOAP web services list operations. For information about asynchronous operations, see SOAP Web Services Asynchronous Operations. For more information about request processing, see Synchronous Versus Asynchronous Request Processing.

Field Definitions

The SOAP Schema Browser includes definitions for all body fields, sublist fields, search filters, and search joins available to this record. For details, see the SOAP Schema Browser’s customer deposit reference page.

Note:

For information about using the SOAP Schema Browser, see SOAP Schema Browser.

Usage Notes

Working with Credit Card Data

When working with credit card data, be aware of the following security features:

When adding a transaction that uses a credit card number, you cannot identify the credit card number using a masked value such as ************5151. You must enter the full 16-digit number, or you can identify an existing credit card record through a RecordRef. (You can identify the full number using the ccNumber field. You can reference an existing record using the creditCard field.)
Searches do not work if they include the operator is or isNot in conjunction with the ccNumber field. The only search operators that can apply to this field are empty and notEmpty.

Creating a Customer Deposit based on a Sales Order

As of the 2012.1 endpoint, the salesOrder field is exposed for customer deposit transactions, so that customer deposits can be based on other types of sales orders in addition to cash sales, typically from invoices. Note that only sales orders with the same customer as in the customer deposit can be used.

The following example shows the creation of a customer deposit based on a sales order:

HTTP Request

          <platformMsgs:add
          xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
          xmlns:xs="http://www.w3.org/2001/XMLSchema"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns:platformMsgs="urn:messages_2017_1.platform.webservices.netsuite.com"
          xmlns:s0="urn:customers_2017_1.transactions.webservices.netsuite.com"
          xmlns:platformCore="urn:core_2017_1.platform.webservices.netsuite.com">
         <platformMsgs:record xsi:type="s0:CustomerDeposit">
            <s0:customer internalId="199" />
            <s0:salesOrder internalId="7818" />
            <s0:payment>214.0</s0:payment>
         </platformMsgs:record>
      </platformMsgs:add>

HTTP Response

          <addResponse xmlns="urn:messages_2017_1.platform.webservices.netsuite.com">
         <writeResponse>
            <platformCore:status isSuccess="true" xmlns:platformCore="urn:core_2017_1.platform.webservices.netsuite.com" />
            <baseRef internalId="7828" type="customerDeposit" xsi:type="platformCore:RecordRef"
              xmlns:platformCore="urn:core_2017_1.platform.webservices.netsuite.com" />
         </writeResponse>
      </addResponse>