Optionaladdenda02Optionaladdenda05List of Addenda05 records
Optionaladdenda98Optionaladdenda98Optionaladdenda99Optionaladdenda99Optionaladdenda99OptionaladdendaAddendaRecordIndicator indicates the existence of an Addenda Record. A value of "1" indicates that one or more addenda records follow, and "0" means no such record is present.
Number of cents you are debiting/crediting this account
OptionalcategoryCategory defines if the entry is a Forward, Return, NOC, DishonoredReturn, or DishonoredReturnContested
Last digit in RDFI routing number.
The receiver's bank account number you are crediting/debiting. It important to note that this is an alphanumeric field, so it's space padded, not zero padded
OptionaldiscretionaryDiscretionaryData allows ODFIs to include codes, of significance only to them, to enable specialized handling of the entry. There will be no standardized interpretation for the value of this field. It can either be a single two-character code, or two distinct one-character codes, according to the needs of the ODFI and/or Originator involved. This field must be returned intact for any returned entry. WEB uses the Discretionary Data Field as the Payment Type Code.
OptionalidEntry Detail ID
OptionalidentificationInternal identification (alphanumeric) that you use to uniquely identify this Entry Detail Record
The name of the receiver, usually the name on the bank account
OptionallineLine number at which the record appears in the file.
RDFI's routing number without the last digit.
OptionaltraceTraceNumber is assigned by the ODFI or software vendor and used as part of identification. The format of trace numbers is the first 8 digits of the ODFI's routing number followed by 7 digits chosen by the ODFI or software vendor. Sequentual or random numbers can be chosen. The only requirement of Nacha is unique trace numbers within a batch and file. Trace Numbers are included in each Entry Detail Record, Corporate Entry Detail Record, and addenda Record. In association with the Batch Number, transmission (File Creation) Date, and File ID Modifier, the Trace Number uniquely identifies an entry within a given file. For addenda Records, the Trace Number will be identical to the Trace Number in the associated Entry Detail Record, since the Trace Number is associated with an entry or item rather than a physical record. Use TraceNumberField for a properly formatted string representation.
Based on transaction type: 21 - Return or NOC for a credit to checking account | 22 - Credit (deposit) to checking account | 23 - Prenote for credit to checking account | 24 - Zero dollar with remittance data (credit) to checking account | 26 - Return or NOC for a debit to checking account | 27 - Debit (withdrawal) to checking account | 28 - Prenote for debit to checking account | 29 - Zero dollar with remittance data (debit) to checking account | 31 - Return or NOC for a credit to savings account | 32 - Credit to savings account | 33 - Prenote for credit to savings account | 34 - Zero dollar with remittance data (credit) to savings account | 36 - Return or NOC for a debit to savings account | 37 - Debit to savings account | 38 - Prenote for debit to savings account | 39 - Zero dollar with remittance data (debit) to savings account | 41 - Return or NOC for a credit to general ledger (GL) account | 42 - Credit to general ledger (GL) account | 43 - Prenote for credit to general ledger (GL) account | 44 - Zero dollar with remittance data (credit) to general ledger (GL) account | 46 - Return or NOC for a debit to general ledger (GL) account | 47 - Debit to general ledger (GL) account | 48 - Prenote for debit to general ledger (GL) account | 49 - Zero dollar with remittance data (debit) to general ledger (GL) account | 51 - Return or NOC for a credit to loan account | 52 - Credit to loan account | 53 - Prenote for credit to loan account | 54 - Zero dollar with remittance data (credit) to loan account | 55 - Debit to loan account (reversals only) | 56 - Return or NOC for a debit to loan account
Export
EntryDetail