Cross-Validation Rules Report
Overview
Netgain Tools provides two reports for monitoring cross-validation rule exceptions across your NetSuite account: the Reported Exceptions report and the Outstanding Exceptions report. Together, these reports give teams the tools to enforce internal controls, track policy compliance, and identify transactions that need corrective action.
The Reported Exceptions report displays a historical record of every transaction that has triggered a cross-validation rule at the time they were saved. Each exception has a status — Open, Prevented, Cleared, or Ignored — allowing teams to track which violations are open and still need attention, which were successfully prevented, which have been corrected, and which have been acknowledged and dismissed. The system automatically updates the status from Open to Cleared when a previously violating transaction is corrected.
The Outstanding Exceptions report runs a live query against your transactions to find those that currently violate one or more selected rules. Unlike the Reported Exceptions report, which captures a snapshot at the time of each transaction save, the Outstanding Exceptions report reflects the current state of your data — showing you what is in violation right now, regardless of when the transaction was originally saved.
Prerequisites
- Cross-validation rules must be configured and active.
- Users must have the appropriate role permissions to access the Cross-Validation Rules app.
Accessing the Reports
Navigate to either report through the Netgain Side Navigation Bar or via Netgain > Cross-Validation Rules.
- Reported Exceptions: Netgain > Cross-Validation Rules > Reported Exceptions
- Outstanding Exceptions: Netgain > Cross-Validation Rules > Outstanding Exceptions
Both the Reported Exceptions and Outstanding Exception reports have resizable and movable columns. When rearranging columns, once you have them in your preferred order, refresh the page and Cross-Validation Rules will remember that order for future visits to the report.
Reported Exceptions
The Reported Exceptions report shows transactions that were flagged by a Cross-Validation Rule at the time they were saved. Each time a transaction is saved and violates a rule — whether the save was blocked (Prevent) or allowed (Detect) — the system logs an exception record. This report displays those records along with a status indicating whether the violation is still active, has been corrected, or has been acknowledged by a user.
When to use it:
Use this as your primary working view. Come here first to review, investigate, ignore, or resolve flagged transactions. Each exception record reflects the exact error message generated at save time and retains its status (e.g., ignored) so you can track what's been addressed. This report will give a full audit trail of prevented/detected transactions and if/how they were resolved.
Exception Statuses
| Status | Description |
|---|---|
| Open | The violation has been reported and has not yet been resolved or ignored. Open exceptions represent active violations that may require corrective action. |
| Prevented | The violation was successfully prevented by the system. This is applicable only to Prevent rule types. |
| Cleared | The transaction has been corrected and no longer violates the rule. The system automatically changes an Open exception to Cleared when it detects that the violation has been resolved — for example, when the transaction is re-saved and passes the rule. |
| Ignored | A user has acknowledged the violation but chosen not to correct it. Ignoring an exception removes it from the default Open view without deleting the record. |
Managing Exception Statuses
Each row in the report includes an action button on the right side, depending on the current status:
- Open exceptions display an amber eye icon with a slash through it. Click it to mark the exception as Ignored. This acknowledges the violation without requiring a correction.
- Ignored exceptions display an undo arrow icon. Click it to restore the exception to Open status.
- Cleared exceptions do not display an action button, as they have already been resolved by the system.
Outstanding Exceptions
The Outstanding Exceptions report runs a live query to find transactions that currently violate one or more selected rules. This report scans your transaction data as it exists right now, identifying violations regardless of when the transactions were originally saved. It is useful for periodic compliance checks or for identifying violations that may have been introduced through data changes outside the normal transaction save process.
This report is essential if you have transactions created by User Event scripts. NetSuite prevents User Event Scripts from triggering Cross-Validation Rules and other scripts, which means transactions created by User Event scripts that violate a Prevent type Cross-Validation Rule will not be prevented and will not appear on the Reported Exceptions report; instead, they will appear on the Outstanding Exceptions report.
When to use it:
Use this as your audit and completeness check — especially after creating or modifying a rule mid-period. Because this report queries historical data dynamically, it will surface violations on transactions that existed before a rule was activated and have never been re-saved.
Common scenarios:
You added a new rule partway through the fiscal year and want to see all prior transactions that would violate it.
You want to identify scripted or system-generated transactions that may have bypassed save-time validation.
You want line-level detail across all violations, not just a summary by transaction.
Tips for Using the Reports
- Audit reviews: Use the Reported Exceptions report filtered by date range and export the results to provide a list of cross-validation exceptions for a given period.
- Compliance checks: Use the Outstanding Exceptions report to run periodic scans and verify that no transactions are currently in violation of your active rules.
- Tracking remediation: Filter the Reported Exceptions report by Status = Open to see which violations still need attention. As transactions are corrected, their status changes to Cleared automatically.
- Acknowledging known exceptions: Use the Ignore action on the Reported Exceptions report to acknowledge violations that do not require correction — for example, one-time exceptions that have been approved by management.
- User training: Filter by a specific user to identify whether a team member is repeatedly triggering the same rule, which may indicate a need for additional training.