We are pleased to provide you with a summary of our November, 2010 release.
You may now override the Billing Day on subscription charges when creating a subscription or amendment. This is useful if you want a new charge to be billed on its own billing anniversary separate from the existing bill cycle on an account (e.g. this may cause 2 or more invoices to be generated to a customer).
For example, if a customer has a subscription that is billed monthly on the 1st of the month, who subsequently signs up for a new monthly subscription on the 15th of June, the default behavior would be for the new subscription to be billed for the partial month (June 15 – June 30), and then billed for the full month every 1st of the month thereafter.
With this new feature, you may override the new subscription charge’s billing day so that it bills the full monthly period upon signup (June 15 – July 14), and then monthly on the 15th of the month thereafter for the new subscription. The old subscription will continue to bill unchanged.
When creating a subscription or amendment, any recurring or usage charge now has the option to set the bill cycle day to the bill cycle date of the account, a specific day of the month, the subscription start date, or the trigger date of the charge (set when the subscription is activated). This value defaults to the value set in the product catalog.
To access this feature, create a subscription or amendment, edit a recurring or usage charge, and change the "Billing Day" field.
Subscriptions can now be set to default to evergreen instead of termed in the administration settings. This will make subscription entry easier and faster for those users who deal mainly with evergreen subscriptions.
To change your default subscription settings, go to Settings > Z-Billing Settings > Define Default Subscription Settings.
You may now configure custom fields on the Invoice, Payment, Invoice Item Adjustment, and Invoice Adjustment objects that may be created and maintained via the User Interface and the API. These custom fields can be used for reporting, and therefore can be modified regardless of the status of the transaction (for example, after an invoice is posted).
Note that custom fields do not affect any amounts on the transaction. To manage custom fields, go to Settings > Z-Payments Settings > Manage Custom Fields or Settings > Z-Billing Settings > Manage Custom Fields, depending on the fields required
You may now more easily track the statuses of each transaction with respect to your integration with your accounting system by using a new field that has been added to all transaction objects (including Invoices, Payments, Refunds, Invoice Item Adjustments, and Invoice Adjustments, and Credit Balance Adjustments). With this release, a transaction’s status may be set to Yes, No, Error, Ignore, or Processing, depending on whether it has been transferred to the accounting system.
In addition, special rules apply to any transaction that is set to “Yes”, that prevent users from making any changes to a transaction after it has been transferred (this rule may only be overridden by users whose profiles have been set up to have permission to override transaction).
Please note: you will need to create a user role that allows users to “Override Transferred to Accounting” for each transaction type in order to access this feature.
This field is displayed in the User Interface, but can be updated via the API.
The integrations with Quickbooks Online and Desktop will now upload Invoice Item Adjustments. The integration will create a Credit Memo for each invoice item adjustment in Quickbooks similar to how it has handled Invoice Adjustments.
With this release, Zuora has added an additional setup procedure to configure the Litle and Chase/Paymentech processors to simplify the onboarding process. If you would like to use either of these processors, please contact Zuora support and we will manage the onboarding process by associating your merchant ID to your tenant
We are rolling out the ability to manage the product catalog via the API. Specifically, we are introducing new API’s to allow you to create and update product catalog objects (including product, product rate plan, and product rate plan charges). For more information on this API, please refer to the API documentation.
You may now update subscriptions to modify key dates via the API, including the contract effective, service activation, and customer acceptance dates. These dates can be modified only if no amendments or invoices have been generated on the subscription. For more information on this API, please refer to the API documentation.
You may now override an account’s bill cycle day when creating a subscription or amendment via the API. Please see the "Greater Billing Control" feature under Z-Billing in these release notes for more information on how this functionality works. For more information on this API, please refer to the API documentation.
Custom fields are now supported on the Invoice, Payments, Invoice Adjustments, and Invoice Item Adjustments – these custom fields can be accessed through the Create(), Update(), and Query() calls on the respective objects, and changes may be applied to transactions in any state (including, for example, draft and posted invoices). For more information on this API, please refer to the API documentation.
The Transferred to Accounting field is now available on the Invoice, Payment, Refund, Invoice Adjustment, Invoice Item Adjustment, Credit Balance Adjustment objects. These fields can be accessed through the Update(), and Query() calls on the respective objects, and changes may be applied to transactions in any state (including, for example, draft and posted invoices). For more information on this API, please refer to the API documentation.
We’ve added additional API’s to support credit balance operations, including the ability to apply credit balances to or from invoices, to refund a credit balance, or to cancel a credit balance. For more information on this API, please refer to the API documentation.