HOA dues autopay: the treasurer's setup guide

Updated Aug 19, 2026 · ~1,200 words · For volunteer boards · Not legal advice

If you're still sending payment reminders by hand before every billing cycle, autopay is the fix. For most self-managed boards, switching to ACH autopay cuts treasurer time by 60–80% on payment collection — the cycle becomes: post assessments, let autopay run, handle the 10–15% who didn't enroll or whose payments failed.

How HOA dues autopay works

HOA autopay uses ACH — the same bank-debit network behind your mortgage payment and insurance premium. The flow:

1. Resident logs into the payment portal and enters their bank routing and account numbers.
2. They authorize recurring ACH pulls on the due date each billing cycle.
3. On the due date, your HOA software initiates the debit through Stripe or a similar processor.
4. The funds transfer from the resident's bank to the HOA bank account over 2–5 business days.
5. The unit ledger is updated automatically when the payment settles.

The treasurer sees one of three outcomes per unit: autopay succeeded, autopay failed (returned), or unit is manually scheduled to pay. No manual entry required for the autopay units.

What autopay requires from the board

Before you can offer autopay, you need:

• An HOA bank account connected to the payment platform — Stripe Connect or equivalent. Money should settle directly to the association account, not a platform balance.
• A unit ledger with due dates configured — autopay drafts on the due date per the assessment schedule. If the due date isn't in the system, there's nothing to pull against.
• A resident portal for enrollment — owners need a secure place to enter bank details. Never ask residents to email account numbers.
• A late-fee policy entered in the software — if an autopay fails and the resident doesn't pay manually before grace ends, the late fee should post automatically from the same settings that govern manual-payment delinquencies.

Resident enrollment: how to get to 80%+

Autopay adoption doesn't happen automatically. The steps that work:

1. Email all owners with a portal invite when you launch — a direct link to their unit portal, not a generic homepage. Explain autopay in plain language: "Log in, enter your bank account, never think about it again."
2. Show the late-fee math — for a $150 quarterly assessment with a $25 late fee, autopay is worth 16% of the assessment to avoid. Make that concrete.
3. Send one reminder cycle later for anyone who didn't enroll. After two billing cycles, most hold-outs either pay manually on time or become your delinquency list.
4. Help outliers individually — a 10-minute video call with a resident who's confused about the bank account form converts almost every time.

Most boards reach 70–85% autopay adoption within two billing cycles after launch.

Handling failed autopay payments

Failed ACH is the main edge case in autopay management. Common causes: insufficient funds, closed account, wrong account number at enrollment, or the bank's fraud filter blocking an unfamiliar debit.

When a payment fails:

• The platform notifies the treasurer and the resident by email (most platforms do this automatically).
• The unit ledger reverts to unpaid for that cycle.
• The board's collection policy takes over — typically a returned payment fee and a manual payment request before the grace period ends.
• The resident should update their payment method in the portal before the next retry or cycle.

Configure your returned payment fee in the software if your governing documents allow one. Make sure it's the same amount as your board-adopted policy — don't invent a number in the app that the board never approved.

Edge cases: ownership changes and variable assessments

Ownership changes: When a unit sells, cancel the previous owner's autopay and send the new owner a fresh portal invite. Most software ties autopay mandates to a user account — resetting is a 2-click operation. Failure to do this is how the old owner gets charged after closing.

Special assessments: Standard autopay mandates cover regular assessments. Special assessments (roof replacement, paving) typically require a separate authorization or manual payment from the owner. Communicate special assessments clearly — residents don't expect extra pulls.

Variable assessment amounts: If your assessments change quarterly (unusual but possible), configure the new amount before the cycle runs. Some platforms require owners to re-authorize when amounts change beyond a threshold — check your software's policy.

Autopay vs cards for HOA dues

ACH is the right default for recurring assessments. Stripe ACH costs roughly 0.8% per transaction. Credit and debit cards cost 2.9% + $0.30 per transaction — for a $300 quarterly assessment, that's $9 vs $2.40. On 30 units × 4 quarters, the difference is $792/year in processing costs alone.

Allow cards as an optional catch-up method (ownership changes, one-time makes), but set ACH as the autopay default and disclose card costs explicitly in the portal so residents understand why ACH is recommended.

Frequently asked questions