Good dues billing ties every payment to membership status, handles late payers in stages, lets members renew and pay on their own, and gives companies an invoice when they need one. When those four things work, renewal season is mostly members serving themselves. When they don't, it's exports, reconciling and reminder emails sent to people who already paid.
This guide walks through what dues billing actually has to do, what a member portal should handle, and how to tell whether your current process is costing you renewals. It's written for membership directors, finance staff and anyone who has built a renewal report at 9pm.
A dues payment isn't just money in. It changes who someone is in your database. Here is what has to happen around the charge itself:
In Cannolai, each of these is a setting your staff configures, not a custom build. Turn on bill later, auto-pay with a stored card, or installments per product. Set calendar or anniversary terms. Define grace stages and which benefits each stage removes. Control eligibility with a list. For a sample 90-day grace structure, see our guide to renewal automation; this post is the billing half of that story.
Most dues problems don't show up as one big failure. They show up as small gaps between the payment and the member record, repeated a few hundred times every renewal season.
| Billing job | When it runs on workarounds | When it's built into your AMS |
|---|---|---|
| Updating status after payment | Someone matches payments to records, often days later | Status changes the moment the payment lands |
| Renewal reminders | Lists exported before each send; paid members still get reminders | Reminders go only to members whose status says they owe |
| Grace periods | One cutoff date, or benefits removed by hand | Benefits step down by stage, automatically |
| Corporate memberships | Seats tracked in a spreadsheet; staff add people by email request | Company admins assign their own seats |
| Invoices for companies | Built in a separate tool and re-keyed when paid | Created, sent and paid against the same record |
| Board reporting | Numbers rebuilt each quarter and rarely match | Renewal and revenue reports read from one member record |
The pattern is the same in every row: the more places a payment has to travel, the less anyone trusts the numbers. Fewer hand-offs means fewer reminder emails to people who already paid.
A good member portal lets members finish the whole renewal without emailing your staff. When you evaluate one, log in as a member, on a phone, and try these:
Cannolai's portal covers all seven, and it works against one member record. When a member renews and pays online, the membership shows as active on their record right away, so nobody has to update status by hand. Ask every vendor you evaluate the same question: does a portal payment update membership status immediately, or does someone update it later? That gap is where renewal reports stop matching reality.
Renewal campaigns work best when they know who's in grace, who's on auto-pay and who has an open invoice. That data lives in your AMS, so the question is how it reaches whoever sends the emails.
In Cannolai, you build a list, and lists can be static (a fixed group) or active (updating as data changes). For associations that use HubSpot, Cannolai is built to pair with it: contact and company records sync automatically, and any list you choose syncs too, on an hourly, daily, weekly or monthly schedule. Billing data doesn't sync on its own, so your marketing tools only get what you decide to send.
| List | What marketing does with it |
|---|---|
| Members in grace, days 1 to 30 | A friendly reminder sequence |
| Members in grace, days 31 to 60 | A "you're about to lose your discounts" message |
| Auto-pay members renewing next month | A heads-up so the charge isn't a surprise |
| Company admins with unassigned seats | A nudge to put those seats to use |
Not on HubSpot? Cannolai sends automated renewal reminders on its own, and every list is also available through Cannolai's API.
If two or more of these sound familiar, the problem is probably your billing setup, not your staff.
Fixing these usually doesn't need a new process. It needs billing rules that live with the member record, so the system does the matching instead of your team. Get that right and renewal season stops being the time of year everyone dreads, and maybe becomes the season you celebrate with cannoli.
Slides can't tell you whether your grace stages, company seats and invoice rules will actually work. The Cannolai Taste Test can. We set up your real dues structure in a working sandbox so your team can renew, invoice and pay before you sign anything.
Book a Taste Test and bring your messiest membership type. We like a challenge.
Dues billing is how an association management system (AMS) invoices, collects and records membership payments. Unlike general billing, each payment also sets membership status, which controls benefits, member pricing and access.
Look for payments that update membership status immediately, staged grace periods tied to benefits, invoice, auto-pay and installment options, organizational seats, and a self-service portal where members see and pay open invoices. Then check how billing and renewal data reaches your marketing tools.
At minimum: see open and paid invoices, pay online, renew, choose a payment option, update their profile and view their history. Company admins should also be able to assign membership seats to their staff.
HubSpot can bill recurring subscriptions, either by charging automatically or by sending recurring invoices. Dues also need membership status, staged grace periods, benefits and organizational seats, which an AMS manages. Many associations let the AMS own dues and use HubSpot for renewal marketing.
Offer both. Many companies need an invoice their finance team can approve, while individuals often prefer auto-pay. In Cannolai you can allow bill later, auto-pay or installments for each membership product.
Cannolai is independent of HubSpot, Inc. and is not sponsored or endorsed by HubSpot.