DFI Account Number & R43 Returns: What They Mean

A DFI account number is the receiver's account number at their depository financial institution — the bank or credit union that holds the account — as it appears in an ACH entry. You may have run into the term through return code R43, “Invalid DFI Account Number.” R43 applies only to Automated Enrollment (ENR) entries; on a regular ACH payment, a bad account number comes back as R03 or R04 instead. Here is what the term means, why the return happens, how to fix it, and why it carries more weight when your business is high-risk.

What a DFI Account Number Is

DFI stands for depository financial institution: a bank or credit union that holds deposit accounts. The DFI account number is the receiver's account number at that institution, carried in the ACH entry so the receiving bank knows where to post the funds.

The field is more flexible than most people expect. It can be up to 17 characters in a standard ACH entry (35 in international IAT entries) and is alphameric, meaning letters and numbers are both valid. It is not the same thing as the routing number, which identifies the institution itself rather than the account inside it. Mixing the two up is the root of most account-number errors.

Where the DFI Account Number Appears in an ACH Entry

Every ACH entry carries the receiver's account number alongside the receiving bank's routing number. When an entry comes back, the return notice also carries a trace number, and it helps to know how to read it: the first 8 digits are the originating bank's routing number without its ninth check digit, and the last 7 digits are a sequence number.

Keep the three straight and return notices get much easier to read. The routing number identifies the bank. The DFI account number identifies where the funds were supposed to post. The trace number identifies the transaction itself.

ACH Return Code R43: Invalid DFI Account Number

R43 means the account number in an ENR entry is not valid at the receiving bank. For regular payments, the same problem returns as R03 (no account found) or R04 (invalid account number structure), and the fixes below apply to all three. Either it fails format rules or it does not match an account the bank has on record.

ENR entries carry one extra requirement worth knowing: the receiver's account number in the addenda record must include at least one alphameric character. An entry that misses that requirement comes back regardless of whether the underlying account exists.

In practice, the causes are ordinary. A typo at intake, transposed digits, a formatting error in the file, or account details that were correct once and have since changed will each produce the same return.

How to Fix an R43 Return

An R43 return does not fix itself, so the path back is short and specific:

• Confirm the account number with the account holder directly. Do not guess at the correction, and do not re-run the data that just failed.
• Correct the entry. Check the account number, the routing number, and the format of the field itself.
• Resubmit as a new transaction. The corrected entry has to be originated again.

If the account holder cannot confirm a valid account, stop there and collect payment another way rather than resubmitting into a second return.

How to Prevent Invalid Account Number Returns

Prevention is cheaper than correction. Three habits cover most of it:

• Validate routing numbers and their check digits before you submit. An entry with a failed check digit comes back every time.
• Verify account details at intake, not at failure. Confirm the account number when the customer provides it, while they are still in front of you.
• Avoid manual re-keying. Every time a number is typed twice, the error rate goes up.

Why ACH Returns Matter More for High-Risk Merchants

For most businesses, an R43 is an annoyance. For a merchant in a high-risk category, it is a data point. Processors and sponsor banks watch ACH return rates, and administrative returns like R03, R04, and R43 count toward yours. A merchant whose file is already under closer review has less room for returns that come from sloppy data entry — the one category of return you can actually control.

Treat account-number validation as part of keeping your ACH payment processing healthy, the same way you treat dispute handling as part of keeping your card volume healthy. Clean entries mean fewer returns, and fewer returns mean fewer questions from the bank.

ACH Processing Built for High-Risk Merchants

We specialize in high-risk processing, and ACH is part of it. If you need ACH acceptance alongside a high-risk merchant account, or your previous processor exited and you are rebuilding, send us your statements and we will tell you where you stand. Start with our ACH payment processing page and apply from there.