Assumptions

These are the assumptions for the validation scenario.

• The achval01 example map processes an ACH file with 13 batch records. The example map goes through each ACH record and verifies the format of the File Header, Batch Header, Entry Detail, Addenda, Batch Control and File Control record formats.

  The input file contains the following:

  • Standard Entry Class (SEC)
  • CCD (Corporate Credit or Debit)
  • CIE (Customer Initiated Entry)
  • CTX (Corporate Trade Exchange)
  • MTE (Machine Transfer Entry)
  • POS (Point of Sale)
  • PPD (Pre-arrange Payment and Deposit Entry)
  • RCK (Re-presented Check Entry)
  • SHR (Shared Network Transaction)
  • TEL (Telephone-Initiated Entry)
  • WEB (Internet-Initiated/Mobile Entry)
• The configuration file ach_config.xml can be edited for these actions:
  • Treat required field as optional. Default is 'YES.'
  • Generate a report for ACH fields that have exceptions. Default is 'YES.'
  • Enforce validation on an ACH field. Default is 'true.'
  Note: Note: Keeping the rest of the settings is recommended, since they are used internally by the maps to process ACH records as defined in the NACHA rule book.
• The achval01 example map generates an XML output document that consists of the following information about the ACH file:
  1. ACH record info
     • name
     • value
     • line number
  2. ACH field info
     • name
     • value
  3. ACH configuration info
     • column number
     • length
     • attribute type
     • validation flag
     • requirement attribute
  4. Exception info
     • description of reason of failure
     • status (Pass or Fail)