Cross-Validation Rules
Overview
Cross-Validation Rules enable companies to enforce or prevent transactions from posting unless they follow specific configurations. For example, if a Journal Entry has a debit to Account ABC, then the credit must be to Account Type Income; or if a Vendor Bill has the Deparment: Marketing, then the Entity must be "Marketing Solutions Inc, Advertising Agency 1, or Event Planner" This gives accounting teams the peace of mind that everything posted in NetSuite is following the Company's Accounting Policies.
Step-by-Step Process
The walkthrough below demonstrates the configuration and functionality of Cross-Validation Rules (CVR).
Click here to view this walkthrough in full screen.
To create Cross-Validation Rules, a user needs to fill out the three aspects of each rule: Main Information, Filters, and Requirements. Each of these is explained below.
Main Information
The Main Information of the CVR explains how the rule should behave. Below is an explanation of each field
| Field | Description | Example |
| Name | The name you want to give the CVR. | Marketing Spend |
| Transaction Type | The NetSuite Transaction Types that you want the rule to apply to. | Journal, Vendor Bill, Invoice |
| Status | If the rule is in effect or not. | Active |
| Action | The two options are Error or Report. If Error is selected, then Cross-Validation Rules will prevent a transaction from posting by throwing an error when a user tries to save it. If Report is selected, then Cross-Validation Rules will allow the transaction to post but it will log the transaction in a report of violating transactions. | Error |
| Description | A description of the rule. | This rule will prevent a Vendor Bill with the Department: Marketing if the Vendor is not one of our marketing-related suppliers. |
| Error Message | This is the message that a user will see when the CVR prevents a transaction from posting. The Name of the rule will be appended at the end of the Error Message with a hyperlink to the CVR. | You cannot post a Vendor Bill with the Department: Marketing to that Vendor because they are not marketing related. |
Filters
A Cross-Validation Rule can have as many filters as a company needs. When a CVR has more than one filter, a transaction must meet all the filters to be evaluated; if a transaction only meets some of the filters on a CVR then it will not be evaluated for the CVR requirements. CVR filters have three fields: Field, Operator, and Value.
| Field | Description | Example |
| Field | This is the transaction field that the filter Operator and Value will relate to. | User, Account, Amount, Department |
| Operator | This is the method by which the Value is considered on the specific Field. | Equal, Not Equal, Includes, Any of, Greater Than |
| Value | This is the Value that the Field must match or not match to qualify for the filter. | John Smith, 1000 Checking, $1000 |
Requirements
Cross-Validation Rule Requirements are what the user is trying to enforce or prevent on a transaction. When a user tries to create a transaction, the Cross-Validation Rule script will first evaluate if it meets any CVR filters. If the CVR finds that the transaction does qualify for certain filters, then the transaction will be evaluated against the CVR requirements. If the transaction passes the requirement, it will be allowed to post; if it fails then it will fail to post or be added to the Cross-Validation Rule Report. CVR Requirements have the following fields: Field, Enforcement Direction, Operator, Value.
| Field | Description | Example |
| Field | The transaction field you want the CVR to evaluate. | Amount, Account Type, Role, Custom Segment |
| Enforcement Direction | This is whether the value on the transaction must be or cannot be a specific value based on the CVR. | Must Be or Cannot Be |
| Operator | This is the method by which the Value is considered on the specific Field. | Equal, Not Equal, Includes, Any of, Greater Than |
| Value | This is the Value that the Field must be or cannot be to pass the requirement. | $-10000, AP Clerk, Cost of Goods Sold |