Validation of invoices for missing charges and spending outliers
Use the invoice summary variance validator to compare draft invoices to their latest posted versions, flagging missing expected charges and spending outliers based on a configurable spending threshold.
The invoice summary variance validator compares each draft invoice with its most recent posted counterpart in the same billing group. It checks for missing expected charges and spending outliers, then combines the results into a single audit outcome.
Detection rules
For this validation, the previous posted invoice is the most recent posted invoice in the same billing group with an invoice date earlier than the current draft invoice date. Invoices are in the same billing group when they share all of the following billing attributes:
Account ID
Currency
Sequence Set ID
Invoice Group Number
The validator uses that previous posted invoice as the baseline for identifying missing expected charges and spending outliers.
The validator checks for the following conditions:
-
Missing expected charge:
Condition
Outcome
Reason
No previous posted invoice in the billing group
Pending Triage
First-Time Billing
One or more charges from the previous invoice are absent
Pending Triage
Missing Expected Charge
All prior charges are present
(no flag)
—
New charges that did not exist on the previous invoice are not flagged — only removals are checked.
-
Spending outlier:
Condition
Outcome
Reason
No previous posted invoice in the billing group
Pending Triage
No Spending History
Current invoice total exceeds previous total × spending threshold
Pending Triage
Spending Outlier
Otherwise
(no flag)
—
The default spending threshold is 2.5×. For example, if the previous invoice was €20,000, any current invoice above €50,000 is flagged. The check applies even when the previous invoice amount is zero or negative.
Run a summary variance validation
To validate a bill run or invoice, describe your request to Zuora AI. The agent confirms the spending threshold and custom field names before processing.
Examples:
-
Validate bill run BR-00019597 for missing charges and spending outliers -
Validate bill run BR-00008774 for missing charges and spending outliers, use 3x spending threshold -
Validate invoice INV00049470 for missing charges and spending outliers, saving validation status to my_status__c and validation reason to my_reason__c
Configuration parameters
Parameter | Description | Default |
|---|---|---|
spending_threshold | Multiple of the previous invoice amount above which the current invoice is flagged (e.g. 3.0 = 3×) | 2.5 |
validation_status_field | Invoice custom field to store the validation outcome | validation_status__c |
validation_reason_field | Invoice custom field to store the anomaly reason | validation_reason__c |