Skip to content

Latest commit

 

History

History
19 lines (16 loc) · 3.2 KB

POSTRevenueScheduleByChargeType.md

File metadata and controls

19 lines (16 loc) · 3.2 KB
Raw

Zuora::POSTRevenueScheduleByChargeType

Properties

Name Type Description Notes
amount String The revenue schedule amount, which is the sum of all revenue items. This field cannot be null and must be formatted based on the currency, such as `JPY 30` or `USD 30.15`. Test out the currency to ensure you are using the proper formatting otherwise, the response will fail and this error message is returned: `Allocation amount with wrong decimal places.`
custom_field__c String Any custom fields defined for this object. The custom field name is case-sensitive. [optional]
deferred_revenue_accounting_code String The accounting code for deferred revenue, such as Monthly Recurring Liability. Required only when `overrideChargeAccountingCodes` is `true`. Otherwise, this value is ignored. [optional]
deferred_revenue_accounting_code_type String The type of the deferred revenue accounting code, such as Deferred Revenue. Required only when `overrideChargeAccountingCodes` is `true`. Otherwise, this value is ignored. [optional]
notes String Additional information about this record. Character Limit: 2,000 [optional]
override_charge_accounting_codes BOOLEAN When overriding accounting codes from a charge, `recognizedRevenueAccountingCode` and `deferredRevenue AccountingCode` must be in the request body and can have the empty value. [optional] [default to false]
recognized_revenue_accounting_code String The accounting code for recognized revenue, such as Monthly Recurring Charges or Overage Charges. Required only when `overrideChargeAccountingCodes` is `true`. Otherwise, the value is ignored. [optional]
recognized_revenue_accounting_code_type String The type of the recognized revenue accounting code, such as Sales Revenue or Sales Discount. Required only when `overrideChargeAccountingCodes` is `true`. Otherwise, this value is ignored. [optional]
reference_id String Reference ID is used only in the custom unlimited rule to create a revenue schedule. In this scenario, the revenue schedule is not linked to an invoice item or invoice item adjustment. Character Limit: 60 [optional]
revenue_distributions Array<POSTDistributionItemType> An array of revenue distributions. Represents how you want to distribute revenue for this revenue schedule. You can distribute revenue into a maximum of 250 accounting periods with one revenue schedule. The sum of the newAmount fields must be equal to the amount field. [optional]
revenue_event POSTRevenueScheduleByChargeTypeRevenueEvent [optional]
revenue_schedule_date Date The effective date of the revenue schedule. For example, the revenue schedule date for bookings-based revenue recognition is typically set to the order date or contract date. The date cannot be in a closed accounting period. The date must be in `yyyy-mm-dd` format.