ACH Version
1.45.5
What were you trying to do?
We rely on the batch validation to make sure we're structuring our NACHA file with the correct format, using this validation call:
https://github.com/moov-io/ach/blob/master/batcher.go#L46
What did you expect to see?
We expected that call to validate the batch format catching all errors. More specifically, the addendaRecordIndicator and the number of addendas in the entry should match.
What did you see?
We accidentally set the addendaRecordIndicator field as 1 in the entry detail without actually having addendas set. This bad format led to entries being rejected by the Fed via return code R25.
How can we reproduce the problem?
Set the addendaRecordIndicator to a value that does not match the actual number of addendas in the entry. The batch validation will not catch that as an error.
ACH Version
1.45.5
What were you trying to do?
We rely on the batch validation to make sure we're structuring our NACHA file with the correct format, using this validation call:
https://github.com/moov-io/ach/blob/master/batcher.go#L46
What did you expect to see?
We expected that call to validate the batch format catching all errors. More specifically, the
addendaRecordIndicatorand the number of addendas in the entry should match.What did you see?
We accidentally set the
addendaRecordIndicatorfield as 1 in the entry detail without actually having addendas set. This bad format led to entries being rejected by the Fed via return code R25.How can we reproduce the problem?
Set the addendaRecordIndicator to a value that does not match the actual number of addendas in the entry. The batch validation will not catch that as an error.