Expense management for amateur cricket clubs — who paid, who's owed, settled fairly

Ask any cricket club treasurer what the worst weekend of the year is, and they’ll tell you: end-of-season reconciliation. Dues collected here, expenses paid there, a folder of receipts, a column of Venmo screenshots, and the slow, awkward work of figuring out who’s square and who isn’t. It’s the part of running a club that quietly burns people out.

CrickTeams treats club money as a system, not a spreadsheet you reconcile by hand. This post walks through how expenses, fees, and your club balance fit together — and how the whole thing settles up fairly without a weekend of detective work.

Two kinds of money, one ledger

A cricket club has money flowing in two directions, and most tools only handle one of them.

• Money in — fees. Members owe the club. CrickTeams separates the kinds of fees a real club charges: annual or seasonal club membership, a per-tournament fee that only the roster pays, and one-time charges for things like kit or a club dinner. Every active member gets the right rows, automatically.
• Money out — expenses. Members and managers spend on the club’s behalf: equipment, travel, meals, umpiring fees, ground costs. Each expense is submitted with a receipt, categorized, and approved.

Keeping these in separate documents is exactly why reconciliation is painful — the in and the out never line up without manual cross-referencing. CrickTeams keeps both in one place so the club’s true position is always visible.

Submitting an expense: receipt first

When a player spends money for the club, they submit the expense themselves rather than DMing you a photo. They pick a type (equipment, travel, meals, umpiring, ground), a scope (the club, a tournament, a match, or a practice), enter the amount, and attach the receipt — a JPEG, PNG, or PDF from their phone.

Club expenses land in a pending queue for a manager to review. You approve or reject from one screen, and every approved expense carries its receipt with it. No more “I’m sure I paid for the balls, I just can’t find the proof.”

The part that saves the weekend: crediting expenses against dues

Here’s the mechanic that makes CrickTeams different from a payments app or a plain expense log.

When a manager approves a player’s expense, that approved amount can be credited directly against what the player owes — applied to their oldest outstanding fees first, then the next, and so on. If a player who owes dues pays for something the club needed, the system applies their out-of-pocket spend to those dues automatically.

A worked example: a player owes $80 in dues and submits a $100 expense for new equipment. On approval, $80 of that expense clears their dues, and the remaining $20 is flagged as owed back to them. You no longer do that subtraction by hand for every player, every month — the math that used to live in an Excel formula happens on approval.

Reimbursing what’s left over

When an approved expense is bigger than what the player owed — or the player owed nothing at all — there’s a residue: real money the club needs to pay back. CrickTeams keeps that residue visible and lets the manager record the reimbursement when it’s paid, noting the method (cash, Venmo, Zelle, PayPal, bank transfer) and attaching a confirmation if you want one.

The result is a clean trail: the expense, the receipt, what it cleared in dues, and what was paid back — nothing relies on anyone’s memory.

Club balance: where the club’s cash actually stands

In a lot of clubs, one person — the manager or treasurer — holds the club’s funds in their own bank account, so club money and their own dues get commingled. CrickTeams has a club balance for exactly this. When a manager pays out of the shared pool it debits the balance; dues coming in top it back up.

Spending ahead of collections is normal, not an error. If the treasurer fronts a cost the balance can’t yet cover, the balance simply goes negative — shown as “the club owes you,” a receivable that heals itself as dues arrive. The system never refuses to record a real obligation, which is the whole point of keeping honest books.

Fairness is just transparency, applied

“Settling up fairly” sounds like a values statement. In practice it’s a data problem, and it’s solved the moment everyone can see the same numbers:

• Players see their own position — what they owe, what they’ve paid, and what the club owes them back — without asking the treasurer.
• Managers see the club-wide picture — outstanding dues, approved expenses, what’s reimbursable, and the running balance.
• Every entry has proof — fees are recorded against payments; expenses carry receipts; reimbursements note how and when they were paid.

When the numbers are shared and sourced, the awkward conversations mostly disappear. There’s nothing to argue about when everyone is looking at the same ledger.

Why this matters when you’re comparing tools

A payment app moves money but doesn’t track it against fees. A spreadsheet tracks it but only one person can maintain it, and the players never see it. A generic team app schedules matches but has no idea what a tournament fee is, let alone how to credit an expense against one.

CrickTeams is built for the cricket-club version of this problem specifically — separate fee types, expense-to-dues crediting, a shared club balance, receipts on everything. Expense tracking is available to grow into as your finances get more involved, alongside the scheduling, availability, and reminders the rest of the club already runs on. If your end-of-season reconciliation currently costs you a weekend, this is the part of CrickTeams worth trying first.