
How to Manage Dual-Tier Dues Collection for Chapters and National
Table of contents
Key takeaways
- Centralised collection (one payment, automatic split) is the cleanest model for data accuracy and member experience
- Decentralised collection (chapters collect and remit) gives chapters cash flow control but creates reconciliation headaches
- Split collection (two separate payments) creates the most friction for members and the highest non-renewal risk
- Whichever model you choose, the system must show a single financial status per member - either they're financial or they're not
Your association charges $200 per year in national dues and each chapter charges $75 in local dues. The member owes $275. How that $275 gets collected, allocated, and reconciled is the difference between a clean financial operation and a quarterly nightmare.
The three collection models
Centralised collection
The member pays $275 to the national office. The system allocates $200 to national and $75 to the chapter. The chapter receives its portion on a regular schedule (monthly or quarterly).
Advantages: One payment for the member. One financial status. No reconciliation between national and chapter records. The national office has complete, real-time data.
Disadvantages: Chapters receive their revenue on the national office's remittance schedule, not immediately. Some chapters feel financially dependent.
Best for: Organisations where the national office has the infrastructure to manage collections and the chapter relationship supports centralised control.
Decentralised collection
The member pays $275 to the chapter. The chapter keeps $75 and remits $200 to national.
Advantages: Chapters receive full revenue immediately. Chapters maintain a direct financial relationship with members.
Disadvantages: Reconciliation between national and chapter records is constant and error-prone. Some chapters remit late, remit incorrectly, or forget entirely. The national office doesn't know who's financial until remittance data arrives.
Best for: Organisations where chapters are highly autonomous and have reliable financial management.
Split collection
The member pays $200 to national and $75 to the chapter separately.
Advantages: Clear separation of finances. Each level manages its own revenue.
Disadvantages: Two payment experiences for the member (higher non-renewal risk). Two renewal cycles. Ambiguous financial status (national-financial but chapter-lapsed, or vice versa).
Best for: Almost nobody. Avoid this model if possible.
Implementation steps for centralised collection
- Set up a single payment page where members pay the full amount ($275).
- Configure automatic allocation in your platform: $200 to national, $75 to the member's chapter.
- Establish a remittance schedule: monthly is preferable (better cash flow for chapters), quarterly is acceptable.
- Communicate clearly to members: "Your $275 membership covers both your national membership and your Chapter Name] chapter membership."
- Provide chapters with visibility: chapters should see their portion in real time, even if they receive the cash on a schedule.
Handling edge cases
Member joins mid-year: Pro-rate both portions. If joining in July (6 months remaining), the member pays $137.50 ($100 national + $37.50 chapter).
Member transfers chapters: Pro-rate the chapter portion. If the member transfers in October (3 months remaining), $18.75 transfers from the old chapter allocation to the new chapter.
Chapter-only membership: Some organisations allow chapter membership without national membership (or vice versa). If so, the system must support a la carte pricing alongside the bundled rate.
Discounted categories: Student members, retirees, or life members may pay reduced rates. The allocation split should apply consistently to discounted amounts.
Implementation checklist
Whether you're implementing centralised collection for the first time or transitioning from a different model, follow these steps:
For the national office
- Define the allocation. Determine the national and chapter portions. Document any variations (different chapter dues by region, discounted categories).
- Configure the platform. Set up the payment system to split payments automatically. Test with a small group before launching to all chapters.
- Establish the remittance schedule. Monthly remittance is preferable for chapter cash flow. Quarterly is acceptable. Communicate the schedule clearly.
- Create member-facing communications. Draft the renewal email, invoice, and receipt. Make sure the member understands that one payment covers both national and chapter.
- Prepare a reconciliation process. Even with automatic allocation, you'll need to reconcile at least quarterly: does the total collected match the total allocated? Are chapter remittances on schedule?
For chapters
- Confirm your chapter dues amount. If chapters set their own rates, confirm the current rate with the national office before the billing system is configured.
- Update your members. Let members know that the billing process is changing (if it is). Explain that one payment now covers both national and chapter membership.
- Verify the first remittance. After the first collection cycle, check that the chapter received the correct amount. Flag any discrepancies immediately.
When to reassess your model
Review your dues collection model every 3-5 years, or when:
- Chapter count changes significantly. A model that works for 10 chapters may not work for 50.
- Payment technology evolves. New payment platforms may offer better allocation and reconciliation features.
- Renewal rates change. If renewal rates drop after changing the collection model, the payment experience may be the cause.
- Chapters express dissatisfaction. If chapters consistently complain about cash flow delays (centralised) or reconciliation burden (decentralised), the model isn't working.
Frequently asked questions
What if chapters want to set their own dues amount?
Allow it, but implement it within the centralised system. Chapter A charges $75 local, Chapter B charges $50, Chapter C charges $100. The system calculates the total (national + chapter) based on the member's chapter affiliation. The member still makes one payment.
How do we handle chapters in different countries with different currencies?
This is where centralised collection gets complex. Options: collect in the national office's currency and remit in local currency (national bears the exchange rate risk), collect in the member's local currency and convert (chapter bears the risk), or use a multi-currency payment processor.
What if a chapter disagrees with the remittance amount?
The remittance calculation should be transparent: number of financial members x chapter dues rate = remittance amount. If the chapter disputes the member count, the shared platform's member database should be the authoritative source.
How TidyHQ helps
TidyHQ handles dues collection with automatic allocation between tiers. When a member pays through TidyHQ, the payment is split according to the configured allocation, and both national and chapter see the transaction immediately. TidyConnect provides the national view across all chapters. No manual reconciliation. No quarterly remittance disputes. One payment, one system, one source of truth.
The $275 question isn't about money. It's about data. Get the collection right and you have accurate membership data, clean financial records, and happy chapters. Get it wrong and you spend hours every quarter reconciling numbers that should have matched from the start.
Header image: by www.kaboompics.com, via Pexels
Don't miss these

How to Measure Chapter Engagement When Every Chapter Is Different
A 30-member rural chapter and a 300-member metro chapter can't be measured the same way. Here's how to build engagement metrics that account for context.

How to Transition Chapters to a New Management Platform Without Resistance
Moving chapters to a new platform fails when mandated from above. Here's the bottom-up approach that works: demonstrate value, remove barriers, and let momentum build.

How to Set Up Roll-Up Reporting Across Your Chapter Network
Roll-up reporting aggregates chapter-level data into a network-wide view. Here's how to define metrics, standardise collection, and build reports that inform decisions.