After I put together the free Troop Dues & Event Payment Tracker, a few other volunteers asked me the same handful of questions — usually after they'd already typed in a week of data and hit something that didn't look right. This is the guide I wish I'd had before I started: what order to fill things in, the one rule that isn't obvious until it bites you, and how to handle the situations that don't show up in a quick-start list.
Fill these in first, in this order
- Roster — every scout, one row each. Patrol and parent contact are optional but worth having before you need them.
- Events — every fee your troop collects this year, dues included. List annual dues as its own row right alongside campouts and summer camp, so it all lands in one place. If adults pay a different rate (or nothing, if they bring their own food), fill in the Adult Fee column too.
- Only then start on Payments.
Skipping straight to Payments before Events exist is the single most common way people confuse themselves in the first ten minutes — the dropdowns have nothing to point to yet.
The rule that isn't obvious: a row is what makes something 'owed'
Here's the part that trips up almost everyone. The Dues Summary tab doesn't know a fee applies to a scout just because it exists in Events — it only counts what's actually logged as a row in Payments. That means if a scout hasn't paid anything yet, you still need a Payments row for them, with Amount Paid left blank or at zero. The row is what registers the amount as owed. Waiting to log it until money actually comes in means that fee never shows up as due at all.
If it isn't a row in Payments, it isn't owed — no matter what's sitting in the Events tab.
So the practical habit: the moment you decide a fee applies to a scout — new campout announced, dues due for the year — add the row right then, at $0 paid. Update Amount Paid later when the check or Venmo actually shows up.
Handling the situations that come up mid-year
- A new scout joins in March. Add them to Roster, then go back and add Payments rows for anything that already applied before they joined — annual dues, whatever's already been billed — even if it's $0 paid so far.
- You made a typo or double-logged a payment. Just edit or delete the row directly in Payments. Dues Summary recalculates instantly; there's no second place to fix.
- A scout's fundraiser payout (popcorn, mulch sale, whatever your troop runs) should reduce what they owe. Log it once in the Fundraising Credit tab. It isn't tied to a specific due — it reduces their balance across everything they owe, automatically.
- Dues Summary shows a negative "Cash Still Owed" for a scout. That's not an error — it means their fundraising credit is bigger than what they currently owe. The number is allowed to go negative on purpose, so the surplus doesn't just disappear.
When the year ends
Carryover is manual — there's no button for it. Make a copy of the whole spreadsheet for the new year, clear out last year's Payments and Events rows, but before you do, write down each scout's ending Fundraising Credit balance from the old sheet and re-enter it in the new copy's Fundraising Credit tab. Credit doesn't travel between files on its own, and it's easy to forget when you're focused on setting up the new year's events.
None of this is complicated once you've hit it once. It's just easier to hear it from someone who already made the mistakes than to find out the hard way at a committee meeting.