2.4.9 Validation Results

The purpose of the Validation Results section is to run validation checks against FinCEN error codes. The validation Results page has the following sections:

• Validation Errors:Displays those errors considered by FinCEN to be primary errors that would require refiling or which would result in the rejection of the eFile, which includes the CTR, on submission.
• Validation Warnings:Displays those errors considered by FinCEN to be secondary errors that may not require refiling.

  This section refreshes every time approval is requested for the CTR. If there are no errors, this section is blank.

  The CTR ID of the record that is causing the error or warning displays in the Involved Record column of the Validation Results grid.

  When a transaction is associated with multiple Open CTRs, a Validation Error displays. The error message displays a list of CTRs which share the current CTR's transactions refreshes to reflect the resolution of the overlapping transactions between the CTRs. For example, if the current CTR shares a transaction with another CTR the user can either remove the shared transaction from one of the CTRs or close one of the CTRs. Once the overlap is resolved, the list of CTRs refreshes to show no CTR IDs. The user is then able to validate the CTR and move it forward in the workflow.

• XSD Validation Errors: All information provided in the CTR is validated against the CTR XSD files. If any error is present in the CTR, the error will be listed in the XSD Validation.
• FinCEN Ack Errors: The FinCEN Ack Errors section will be populated once a file has been processed by FinCEN and the associated acknowledgment file uploaded and parsed for the BSA ID as well as any error messages. FinCEN Ack Errors displays two sections:
  • Primary Errors
  • Secondary Errors.

As with the Validation Results these sections correspond to those Primary Errors from FinCEN requiring refiling as well as the Secondary Errors which may not.