The Suspicious Activity Report (SAR) validation process in SAS Anti-Money Laundering does not check the following FinCEN error codes correctly:

Note: FinCEN error codes are from the FinCEN SAR XML Schema User Guide (version 1.6).

Miscellaneous Errors

• A4 - The critical element is not recorded
• A6 - The element exceeds the maximum occurrence threshold

Document Errors

• B1 - The element is not recorded
• B2 - The element is recorded but with no value (i.e. the value is null)
• B19 - The value recorded does not equal 14 numeric characters
• B42 - The value recorded for the element is not in the required format
• B45 - The element is not recorded or does not contain
• B46 - The value recorded is not valid based on the type of cyber event
• B47 - The element is recorded for a cyber-event type that is not applicable to this data
• B49 - The element is recorded for a cyber-event type that is not applicable to this data
• B51 - The element is not recorded or does not contain a value
• B53 - The element is not recorded or does not contain a value and the <CyberEventIndicatorsTypeCode> is equal to "11" Other
• B54 - The element is recorded with a value and the <CyberEventIndicatorsTypeCode> is not equal to "11" Other

Subject Information Errors

• C41 - The element is not recorded or at least one indicator identifying the type of relationship is not recorded with a "Y" value
• C45 - The element is not recorded or does not contain a value and the status of the relationship is Terminated, Suspended/barred, or Resigned
• C55 - The element is recorded with a valid value but the status of the relationship is not equal to Terminated, Suspended/barred, or Resigned

Financial Institution and Branch Where Activity Occurred Errors

• D1 - The party type associated with the financial institution where activity occurred exceeds the maximum occurrence for the FinCEN SAR
• D38 - The party type associated with the branch where activity occurred exceeds the maximum occurrence for the FinCEN SAR

Filing Institution Errors

• E0 - The party type associated with the filing institution is not recorded
• E1 - The party type associated with the filing institution exceeds the maximum occurrence for the FinCEN SAR
• E5 - The element is not recorded

Transmitter Errors

• G0 - A required party associated with the transmitter is missing 
• G1 - The report contains more than one party associated with the transmitter 
• G16 - The Transmitter Control Code (TCC) specified in the file is not valid TCC.  For production, the TCC must begin with "P" and for User Test, it must be equal to "TBATEST"

Transmitter Contact Errors

• H0 - A required party associated with the transmitter contact is missing
• H1 - The report contains more than one party associated with the transmitter contact

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

Operating System and Release Information

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at