What Is an ACH Trace Number? (And How to Use It to Track a Payment)

Last updated July 2026.

An ACH trace number is the 15 digit reference that uniquely identifies a single ACH payment in the network. The first eight digits are the routing number of the originating bank, and the last seven are a sequence number that bank assigns. In a NACHA file it sits at positions 80 to 94 of the entry detail record, the last field on the line.

It is the closest thing ACH has to a tracking number, and the comparison is useful as long as you know where it breaks down. A parcel tracking number gives you live status. An ACH trace number gives you a unique handle that a bank can use to look the payment up. There is no public tracker.

How is an ACH trace number structured?

Because the first eight digits are the originating bank's routing number, the trace number tells you which institution started the payment before you talk to anyone. That is genuinely useful when a payment arrives from a company using a payment processor, since the routing prefix identifies the bank behind the processor rather than the brand on the invoice.

The sequence portion is assigned in ascending order within a file, which is why trace numbers in a batch usually run consecutively. That property matters more than it sounds: a gap in the sequence is a fast way to spot that entries were dropped between the file you built and the file the bank processed.

Where do I find the trace number?

It depends which side of the payment you are on.

• If you originated the payment, it is in the ACH file itself at positions 80 to 94 of the entry detail record, and normally in your bank's online payment detail screen for the transaction.
• If you received the payment, ask the sender. Most banks do not surface the trace number to the receiving side in online banking, and it usually does not print on the statement.
• If you are looking at an addenda record, positions 88 to 94 hold the entry detail sequence number, which ties the addenda to its entry. That is the last seven digits of the related trace number, not a trace number in its own right.

If the file is what you have and reading character positions by hand is not appealing, the NACHA file to Excel converter pulls the trace number into its own column with the leading zeros preserved, which matters because Excel will silently mangle a 15 digit number into scientific notation if the column arrives as numeric.

How do I trace an ACH payment?

The originating bank runs the trace, not the receiving bank. The sequence is:

1. Get the trace number, the amount, the effective date and the receiving account details together before you call.
2. Contact the originating bank and ask specifically for an ACH payment trace, using that phrase.
3. The bank follows the entry through the network using the trace number and reports back where it landed or why it did not.

If you are the recipient chasing a payment that never arrived, you cannot start this yourself. You need the sender to either give you the trace number or open the trace on their end. That is an awkward conversation to have repeatedly, which is one reason companies chasing a lot of unpaid or unmatched inbound payments move the follow up into automated receivables chasing rather than handling each one by email.

What a trace number cannot tell you

This is where expectations usually go wrong. A trace number is an identifier, not a status. On its own it does not tell you whether a payment settled, was returned, or was posted to the right account. All of that has to come from your bank or from the returns file.

It also does not survive as a link between systems the way people assume. The receiving bank is not obliged to pass the trace number through to the receiver's statement, so matching an incoming deposit to a specific trace number often is not possible from the statement alone. You match on amount, date and the company name from the batch header instead.

And a trace number will not tell you why something bounced. When an entry is returned, the reason arrives as a return code in a separate return entry, and the ACH return codes list from R01 to R85 decodes those. The trace number is how you tie the return back to the original payment.

Is the trace number the same as a reference number or a confirmation number?

No, though they get used interchangeably in conversation. The trace number is defined by the NACHA format and is the same value everywhere in the network. A confirmation number is whatever your bank's online portal generated when you submitted the payment, and it usually has no relationship to the trace number at all. When a bank asks for a reference, ask which one they mean, because quoting a portal confirmation number to an ACH operations team wastes the call.

The identification number field at positions 40 to 54 of the entry detail record is a third thing again. That one is yours: an employee ID, an invoice number, or whatever reference you chose to carry. It is often the most useful field for reconciliation precisely because you controlled it, and it travels through to the receiver.

Do wires and ACH use the same trace number?

No. Wires travel over Fedwire or CHIPS and carry their own reference, commonly called an IMAD or OMAD on Fedwire. ACH trace numbers only exist inside the ACH network. If somebody sends you a 15 digit number and calls it a wire reference, it is worth checking which rail the payment actually used, since the timing, the cost and the ability to reverse it are all completely different. The differences are laid out in ACH file vs wire transfer vs RTP.

Using trace numbers to reconcile a batch

The practical use for most finance teams is not tracing a lost payment, it is proving a batch went out complete. Pull the trace numbers from the entry detail records into a spreadsheet, sort them, and check three things: the count matches the entry count in the batch control record, the sequence has no gaps, and no trace number appears twice. A duplicate trace number inside one file is a generator bug and the bank will reject the file for it.

That check takes a minute once the file is in columns, and it catches the class of problem that dollar totals miss entirely. The full field layout, including the trace number and the fields either side of it, is documented on the NACHA file format reference, and the bank file format converter covers the other formats your bank might send if what you are holding turns out not to be an ACH file at all.