Scope of Audit Trail
- Last updated
- Save as PDF
Zuora Audit Trail supports the following capabilities:
- Track, log, and report on a user’s login history
- Track, log, and report on setting changes. Changes on the following settings can be audited:
- Billing
- Default Subscription and Order Settings
- Define Billing Rules
- Manage Tax codes
- Define Discount Settings
- Manage Revenue Recognition Codes
- Configure Tax Dates
- Payment Terms
- Payment
- Configure Application Rules
- Payment Method Type
- Commerce
- Synchronize Salesforce.com Data
- Finance
- Configure Accounting Codes
- Configure Accounting Rules
- Manage Currency Conversion
- Set Revenue Automation Start Date
- Configure Revenue Event Types
- Manage Revenue Recognition Models
- Configure Segments
- Configure GL Segmentation Rules
- Manage Revenue Recognition Rules
- Manage Chart of Accounts
- Audit Trail
- Billing
- Track, log, and report on activities in user management settings. Changes on the following user management settings can be audited:
- User
- Role & Permission
- Track, log, and report on changes of the following business objects. For more information about tracking subscription and billing document histories, see View financial transaction histories.
- Account
- Contact
- Custom Object (see Data Model of Audit Trail for supported objects)
- Notification (see Data Model of Audit Trail for supported objects)
- Order Line Item
- Product Catalog (see Data Model of Audit Trail for supported objects)
- Payment
- Payment Method
- Payment Gateway (Only available to Chase Orbital payment gateway)
- Refund
- Workflow (see Data Model of Audit Trail for supported objects)
- Google Cloud Enterprise credentials used for Payment Page reCAPTCHA Enterprise configuration (represented as the
HpmCaptchaCredential
object)
- Audit Trail supports the Custom Field Definition object, which represents a custom field that has been defined on a business object.
- Audit Trail retrieves jobs performed through Deployment Manager.
- Administrators can enable or disable auditing the above objects through Manage Audit Trail Settings.
Authorized users can generate the Audit Trail reports through Data Query. The Audit Trail records are stored in the following tables:
auditloginevent
for login historyauditsettingchangeevent
for user management and other settings changesauditobjectchangeevent
for business object changes
Additionally, you can contact Zuora Global Support for advanced auditing requirements.
View financial transaction histories
As a financial system of record, Zuora’s object model for financial transactions, such as subscriptions and billing documents, is natively versioned and designed with an immutable and append-only structure, which ensures that historical data remains intact and auditable. Consequently, you should track financial transaction histories via Data Query or on dedicated pages in the UI instead of Audit Trail.
- Versioned subscription change histories: As a change is made to a subscription, a new version of the subscription is created. The corresponding order action or amendment type of each subscription version indicates the change made to the subscription. You can view subscription change histories in one of the following ways:
- On the subscription detail page. See View Versioned Subscription Change History for more information.
- Query the SubscriptionStatusHistory object in Data Query or Data Source Exports. See Query data through Subscription Status History data source for more information.
- Single version subscription change histories: If the Single Version Subscription feature is enabled for your tenant, there is only one version for each subscription. The SubscriptionChangeHistory object provides a clear record of key orders-related changes made to the single version subscription. You can view the change history of a single version subscription in one of the following ways:
- On the subscription detail page. See View Single Version Subscription Change History for more information.
- The Subscription Change History API operations.
- Billing document histories: You can query the InvoiceHistory or MemoHistory object in Data Query to view billing document histories.
- InvoiceHistory: Tracks changes made to invoices, such as creation, posting, cancellation, deletion, edit, email activities, PDF generation, reversal, and more.
- MemoHistory: Tracks changes made to credit and debit memos, such as creation, posting, cancellation, deletion, edit, as well as special actions for credit memos, such as applied, unapplied, and refund.
- CreditMemoApplication
- CreditMemoApplicationItem
- PaymentApplication
- RefundApplication
The Audit Trail feature has the following limitations:
- Audit Trail reports are retrieved through Data Query. All the Data Query limitations are applicable when you generate Audit Trail reports. See Data Query Limitations for the details.
- The usage-based charges with the following charge models are not audited even if the Product Catalog auditing is enabled, including:
- Multi-Attribute Pricing
- High Water Mark Volume Pricing
- High Water Mark Tiered Pricing
- Pre-Rated Pricing
- Pre-Rated Per Unit Pricing
- Auditing the changes of business objects has performance impact.
- To audit custom field changes of a custom object, you must set the custom field as an auditable field. One custom object can have a maximum of five auditable fields. For more information, see Create a new custom object definition.
Delete or anonymize audit log data
According to the applicable privacy laws, if you want any of your audit trail data/records deleted, Zuora recommends you open a ticket with support. We will assist you in logging into AWS and manually deleting it all.
According to the applicable privacy laws, if you want any of your audit trail data/records deleted, Zuora recommends you open a ticket with support. We will assist you in logging into AWS and manually deleting it all.