An ACH credit pushes money: the payer instructs its own bank to send funds to your account. An ACH debit pulls money: you, with the payer's authorization, instruct your bank to collect funds from theirs. Payroll direct deposit is a credit, and a utility bill on autopay is a debit. For a business getting paid, the choice decides who sets the payment date.
An ACH debit is an ACH payment started by the party being paid, which pulls funds from the payer's bank account under the payer's authorization. An ACH credit is one started by the payer, which pushes funds from its own account to the payee's. Both run on the same ACH Network under the Nacha Operating Rules; what differs is whose bank sends the instruction.
Nacha's own explanation uses exactly those two examples, and they show the difference well. Your employer decides when your pay goes out, because it sends the credit. The electric company decides when to collect, within the authorization you gave it, because it sends the debit. Everything else in this guide follows from that.
ACH debit and ACH credit compared
| ACH debit (pull) | ACH credit (push) | |
|---|---|---|
| Who starts it | You, the business being paid | Your customer, from its own bank |
| What you need first | The customer's authorization and bank details | Nothing beyond giving the customer your bank details |
| Who picks the date | You, within the authorization's terms | The customer |
| How far ahead it can be dated | No more than one banking day (Nacha rule) | Up to two banking days |
| Can it be pulled back? | Yes: the payer's bank can return it, for example for insufficient funds or an unauthorized claim | Only by a reversal for specific errors, within five banking days |
| Who controls the remittance detail | You, because you create the entry | The customer's payables system |
| Common entry codes | PPD, CCD, WEB, TEL | CCD and CTX from businesses; PPD for payroll |
How each one reaches you when a customer pays an invoice
Paying you by ACH debit
The customer gives you permission and its account details, usually by entering them on your payment page, signing a form or agreeing on a recorded call. You (or your processor) create a debit for the amount due and send it through your bank. It settles on the date you set, and if anything is wrong with the account, it comes back to you with a return code. Nacha puts the burden of proving the authorization on you, so keep the record.
Paying you by ACH credit
The customer's accounts payable team adds your routing and account numbers to its vendor file, then schedules payment from its own banking system. The money arrives on the date the customer picks, carrying whatever reference its system sends. You don't need any agreement with your processor to receive it. You do need to recognize it when it lands.
A month of receivables, collected both ways
Say a wholesale food distributor has 40 trade accounts on net 15 terms, billing $310,000 a month. Twenty-five accounts, worth $190,000 a month, pay by ACH credit from their own systems. The other 15, worth $120,000, have signed authorizations for the distributor to debit them on each due date. All figures are hypothetical.
The credit-paying accounts
Suppose these customers pay, on average, 8 days after the due date, because they run payables once a week and the timing rarely lines up. That lag keeps extra money tied up in receivables all month:
- Daily sales to these accounts: $190,000 ÷ 30 = $6,333.
- Extra receivables carried: $6,333 × 8 days = $50,667.
Suppose also that 6 of the 25 monthly credits arrive without an invoice number, and each takes the AR clerk 20 minutes to match. That is two hours a month spent working out who paid for what.
The debit accounts
These payments settle on each due date, so they add nothing to the lag. The cost shows up elsewhere. Say 2 of the 15 debits come back in a typical month with R01, the code for insufficient funds. The distributor calls each customer, agrees a new date and sends the debit again a few days later. Those two payments arrive late, and there may be a return fee from the processor, but the other 13 arrive exactly on time with the invoice reference the distributor put on them.
The debit side is plainly easier to manage. Moving even a few credit payers onto debits would cut that $50,667, and the distributor's days sales outstanding with it.
The risks on each side
With debits, the risk is the return
A debit can bounce for lack of funds, or be returned because the customer says it wasn't authorized. A business customer has two banking days after settlement to make that claim, and a consumer has up to 60 days. Nacha watches how often your debits come back as unauthorized: the threshold is 0.5% of debits, measured over the preceding 60 days or two calendar months. The codes and what to do about each are in ACH return codes.
Some businesses protect their accounts with debit blocks or filters at their bank, which stop debits from companies they haven't approved. If a customer has one, a debit from you can come back even with a signed authorization. Ask new business customers whether they need to approve your company ID with their bank before the first collection.
With credits, the risk is fraud aimed at your customers
A credit is hard for the payer to reverse, which is good for you, and that is what makes credits attractive to fraudsters. The common scheme is an email, apparently from you, telling customers that your bank details have changed. The money goes to the fraudster's account, and your invoice stays unpaid. Nacha's newer rules respond to this: since 22 June 2026, every receiving bank must have risk-based processes to identify ACH credits sent as a result of fraud. Your own defense is simpler. Tell customers, in writing, that you will never change your bank details by email alone, and ask them to call a number they already have before they update their vendor file.
Which one to offer your customers
Most businesses that invoice should accept both, and steer customers toward debits where the relationship allows it.
- Recurring charges or retainers work best as debits under a standing authorization, so each payment arrives on the date in the agreement.
- Larger customers with strict payables policies may not allow vendors to debit their accounts at all. Accept their credits, and ask them to send invoice numbers with each one. Their systems can use the CTX format, which carries up to 9,999 addenda records, and our guide to remittance advice covers what to ask for.
- One-off invoices can go either way. A pay button on the invoice turns a would-be credit into a debit the customer authorizes in one step.
If you set up debits, store the authorization and payment method once and reuse it rather than collecting bank details for every invoice. PayLink can set clients up on a payment API that accepts ACH and includes both a Customer Vault for stored payment methods and a Recurring API for subscriptions and plans.
For the network basics behind both payment types, start with what an ACH payment is.
Sources
- Nacha: How ACH Payments Work, accessed 15 November 2026
- Nacha: The Significant Majority of ACH Payments Settle in One Business Day or Less (28 August 2023), accessed 15 November 2026
- Nacha: RMAG Originator Essentials (PDF, 2024), accessed 15 November 2026
- Nacha: How to Calculate Unauthorized Return Rate (PDF), accessed 15 November 2026
- Nacha: Risk Management Topics (Fraud Monitoring Phase 2), accessed 15 November 2026
- Nacha ACH Guide for Developers: ACH File Details, accessed 15 November 2026