Collector content validation rules
These validation rules compliment the standard content validation rules by providing a way to validate counts, sums, and unique values using multiple records. During collector content validation, values are collected across multiple records before a comparison is performed to determine the correctness of a field value. The term collector refers to the cross-record nature of the rules. The rules are maintained using the Business Rules user interface edit function.
- Activation
- During activation, the collector is enabled and initialized. Activation occurs when a specific record is received. Source fields in the collector are used to identify the record that activates the collector. In most cases, only the record type is needed. NACHA has an additional requirement to include the SEC code and addenda fields.
- Execution
- Execution begins after a collector is activated. Target fields in the collector are used to identify a target record for the collector. During execution, the records up to, and including, the target record are collected. The records are either counted, accumulated, or retained for unique verification. Zero or more records are processed in this phase.
- Evaluation
- Evaluation occurs when the target record is received. The comparison or test that is used to determine the correctness of the fields is performed. If the validation is not successful, an error code is assigned.
Each of these phases can be run conditionally. A condition that fails during activation disables the collector completely. During execution, an execution condition might selectively add records to the collection. A collector can be activated and then execute, only to be ignored in the evaluation phase because the evaluation condition fails.