Bank Bonus ACH Requirements

How ACH credits, ACH debits and payroll direct deposit differ when a promotion requires electronic activity. The safest reading is the one you can verify from the current terms and your own account history. A few minutes of documentation at the beginning can prevent weeks of support calls later. The first two details to write down are whether the offer says ACH credit, direct deposit, recurring deposit or any electronic deposit and whether person-to-person or account-to-account transfers are excluded.

For this page, the working test is concrete: verify whether the offer says ACH credit, direct deposit, recurring deposit or any electronic deposit, whether person-to-person or account-to-account transfers are excluded, the minimum dollar amount per transaction or in aggregate, the required number of credits or debits, and the date on which the transaction must post. Do that before you count the reward as expected income. A promotion can be legitimate and still be a poor fit when the qualification path depends on activity you would not otherwise use, cash you cannot comfortably park, or a deadline with no room for ordinary processing delays.

What the requirement actually controls

ACH is a payment network, not a single transaction type. Payroll direct deposit is normally an ACH credit, but so are many transfers that a bank may exclude from a promotion. A bank can therefore require “qualifying direct deposit” even though several other incoming payments also travel through ACH. In practice, treat that statement as the rule you must be able to prove from the offer and your own account record.

For this page, the promotion should answer whether the offer says ACH credit, direct deposit, recurring deposit or any electronic deposit, while the ordinary account documents explain recurring fees and transaction mechanics. Put both sets of terms in the same file and separately confirm whether person-to-person or account-to-account transfers are excluded and the minimum dollar amount per transaction or in aggregate. That matters because a seemingly small issue—treating every ACH credit as payroll—can leave you with a valid account but no reward.

Build the verification file first

The pre-application check should cover whether the offer says ACH credit, direct deposit, recurring deposit or any electronic deposit, whether person-to-person or account-to-account transfers are excluded, the minimum dollar amount per transaction or in aggregate, the required number of credits or debits, and the date on which the transaction must post. Each item should have either a quoted sentence from the offer, an account disclosure, or a dated bank confirmation behind it.

Treat outside data points as context only. Your evidence is the current bank offer, especially on the question of whether person-to-person or account-to-account transfers are excluded. Keep that evidence with the application date so later changes do not erase the rules you relied on.

A numerical example makes the risk visible

Imagine a promotion requiring $1,000 of qualifying direct deposits within 90 days. Two $500 payroll credits can satisfy it if payroll is eligible. A $1,000 transfer you push from another bank may post through ACH but still fail because the bank classifies it as an external transfer rather than payroll.

Rework that scenario with your own dates, amounts and account behavior. Treat this as a separate checkpoint: the minimum dollar amount per transaction or in aggregate. The goal is to surface the assumption that can change the result before the promotion is underway.

Where otherwise good applications fail

The recurring failure points here are treating every ACH credit as payroll, counting a micro-deposit verification amount, assuming a pulled transfer and a pushed transfer are coded the same way, waiting until the final week to test qualification, and relying on crowdsourced data points when the live terms use narrower language. None of these problems requires a fraudulent or misleading offer; they are ordinary execution errors that the written terms may still treat as disqualifying.

One risk deserves its own checkpoint: relying on crowdsourced data points when the live terms use narrower language. A promotion is stronger when that problem can be spotted and corrected before the final deadline or payout decision.

A simple operating checklist

A practical control file should save the offer definition of qualifying activity, keep paystubs or benefit statements for qualifying deposits, record the posted description shown by the receiving bank, confirm progress with the bank if the activity is ambiguous, and leave enough time for another qualifying cycle if the first deposit is rejected. These records let you answer the three questions that matter later: was I eligible, did I complete the required activity, and has the bank reached the promised payout date?

Turn the notes into dated actions. First: save the offer definition of qualifying activity. Then keep watching this point: confirm progress with the bank if the activity is ambiguous. The final documentation step is equally important: leave enough time for another qualifying cycle if the first deposit is rejected.

The practical decision rule

When a promotion hinges on ACH, the transaction description matters less than the offer’s definition. Use payroll or government deposits when the terms call for direct deposit, and get confirmation before substituting another ACH source. Compare the net reward with the effort and liquidity the rule consumes, not just with competing headline bonuses.

A well-chosen bonus fits ordinary account use. Make sure this point has a provable answer: the required number of credits or debits. The same plan should also tolerate counting a micro-deposit verification amount without turning into a support dispute.