A transaction code classifies the type or direction of a financial transaction, such as a debit or credit. In an ACH application, it becomes a practical link between file-generation rules, entry data, validation, and user-facing statistics. section 7.5.3 section 7.6
Use transaction codes to:
- Select the transaction direction while generating ACH entries; a debit-only setup assigns transaction code 27. section 7.6
- Aggregate debit, credit, and other amounts when computing batch totals; the implementation currently considers codes 22 and 27. section 8.8.2
Debit-only ACH file
A file-creation scenario requests one batch containing ACH debits only. The implementation chooses a matching service-class code and assigns transaction code 27, then validates the expected number of entries in the generated file. section 7.6
Listing 7.35 Sample for creating files
@given(
parsers.re(
r'I want to have (?P<batch_count>\d+)
➥ batch with ACH debits only and a standard entry
class code of "(?P<standard_entry_class>.*)"'
)
)
def set_number_of_debit_batches_to_create(
setup_info, batch_count, standard_entry_class
):
setup_info["batch_count"] = int(batch_count) #1
setup_info["service_class_code"] = "225" #2
setup_info["transaction_code"] = ["27"] #3
setup_info["standard_entry_class"] = standard_entry_class #3
Inspect the setup step that converts a debit-only requirement into service-class and transaction-code values. section 7.6
