How to Collect Entry Fees and Pay Out Prize Money

Every organizer who has run more than two events knows the real job isn't the tennis, padel, or pickleball — it's the money. Collecting entry fees, tracking who's actually paid, doing the prize-pool math, and getting winnings into the right hands without a spreadsheet meltdown is the unglamorous work that quietly decides whether you keep running events at all.

This guide is about that work specifically: why cash and Venmo collection breaks down, how to structure a prize pool that players trust, what a defensible refund policy looks like, the record-keeping you should keep at a high level, and how to take all of it off your plate with in-app collection and connected payouts.

The cash-and-Venmo problem

The default way most events get funded is the worst way. It looks like this: an organizer posts an event, players say they're in, money is supposed to arrive by cash on the night or a payment app beforehand, and the organizer becomes a part-time debt collector. The failure modes are predictable and they compound:

• Phantom commitments. "I'm in" is not "I've paid." You build a 16-player bracket around eight people who never sent money and three who drop the morning of, and you're rebuilding the draw in the parking lot.
• The chase. You spend the week before every event sending "hey, did you get a chance to send that over?" messages. This is the single biggest reason organizers burn out.
• Reconciliation by memory. Cash on the night means counting bills against a mental list while people want to start playing. Something never adds up, and the gap comes out of your pocket.
• Float risk. You front court costs, balls, and prizes assuming the money will materialize. Sometimes it doesn't, and you've personally subsidized the event.
• No record. When someone disputes whether they paid, it's your word against theirs with no ledger. There's no version of that conversation that ends well.

The structural problem underneath all of these: collection is decoupled from registration. A player can register without paying, so registration tells you nothing about who's actually funded. Every fix below comes back to recoupling those two things — no payment, no spot.

Designing a prize pool players trust

If you're running competitive events, prize money raises the stakes and the engagement — but only if the pool is transparent. The fastest way to lose a community's trust is an opaque prize pool where players suspect the organizer is pocketing the difference.

The principle: the split is published before anyone pays. Players should be able to look at the event and know exactly what happens to their entry fee. Two clean, defensible structures:

• Fixed prizes. "First place: a set amount. Runner-up: a set amount." You announce specific figures up front and guarantee them regardless of turnout. Simple, but you carry the risk if numbers are low.
• Pooled and split by percentage. A defined share of total entries forms the prize pool, distributed by a published percentage split (for example, the bulk to the winner, a smaller share to the runner-up, optionally a third). The pool scales with turnout, so you never owe more than was collected. This is the most common competitive structure and the easiest to defend.

For getting the entry fee and the operating-cost portion right in the first place — so the prize pool is generous and the event is sustainable — work through the pricing playbook for Americanos and leagues. The two decisions are linked: the prize split only makes sense once the entry fee covers your real costs.

A refund policy you can actually defend

Refunds are where good intentions meet operational reality. A player gets injured, work explodes, a family thing comes up — and you have a bracket built, courts booked, and prizes committed around their spot. You need a policy that's compassionate enough that people don't resent it and firm enough that it doesn't bankrupt the event.

A defensible structure most organizers can stand behind:

1. Set a cancellation cutoff

   A clear date or number of hours before the event. Cancel before the cutoff: a refund (full, or full minus a small processing portion — your call, stated up front). The cutoff exists because before it, you can still backfill the spot.

2. Define the after-cutoff rule

   After the cutoff the spot is committed — courts are booked, the draw is set, the prize pool is calculated on the headcount. The honest default is no refund after the cutoff, because the cost of that spot is already sunk. State it plainly so it's never a surprise.

3. Keep organizer discretion explicit

   You decide genuine hardship cases. Make it explicit that exceptions are at your discretion, not an entitlement — that protects you from "but you refunded her" arguments.

4. Handle event cancellation separately

   If you cancel the event, every player gets refunded in full. That's not negotiable and it should be stated as clearly as the player-cancellation rule.

The non-negotiable design rule: refunds are organizer-managed, not player self-serve. A player cannot click a button and claw their entry back out of a half-built event. You hold that control, because only you can see the bracket, the court bill, and the prize math. The policy is published; the execution is yours. For the operational details of how cancellations and payout timing interact, see the help guide on refunds, cancellations, and payout timing.

Record-keeping and taxes, at a high level

This is general operational guidance, not tax advice — talk to a professional about your specific situation and jurisdiction. But every organizer should keep, at minimum, a clean record of: total entries collected per event, prize money paid out per event, your operating costs (court, balls, equipment), and the net.

Why it matters even if you're "just running a friendly league":

• Money flowing through you — collected from players, paid out as prizes — may have reporting implications depending on volume and where you operate. You want a clean ledger long before that's ever a question, not reconstructed from a chat history afterward.
• A per-event record is what lets you actually answer "is this event making money or am I subsidizing it?" — which is the difference between a hobby that drains you and a program you can grow. The club-owner's guide to monetizing court time builds directly on having that data.
• If anyone ever disputes a payment or a payout, a system-generated record ends the conversation in seconds. Memory and screenshots don't.

The practical takeaway: you want collection and payout to flow through one system that keeps the ledger automatically, so record-keeping is a byproduct of running the event rather than a second job you do afterward.

How Skedge collects fees and handles payouts

Everything above describes a problem with one root cause — collection, payment tracking, prize math, refunds, and records living in five different places (a chat app, a payment app, your memory, a spreadsheet, your own bank account). Skedge collapses all of it into the event itself.

Here's how it works operationally. You create the event in the app (App Store or Google Play) or on the web, set the entry fee, and move the event from DRAFT to LIVE. Then:

• Entry fees are collected in-app at registration. Payment and a confirmed spot are the same action. There is no "registered but unpaid" limbo, which removes the chase and the phantom-commitment problem in one move. Players join with their phone number plus a one-time code via an event code or invite link.
• You connect a Stripe payout account. Skedge handles the collection and the payouts to you — you're not running money through your personal account or fronting costs hoping it comes back.
• The ledger is automatic. Who paid, how much, and what's owed is tracked by the system, not your memory, so reconciliation on event night is something you read, not something you do.
• Refunds stay with you. When a refund is warranted under the policy you published, you issue it as the organizer — players cannot self-serve a refund out of your event, which keeps the prize pool stable for everyone who's still in.
• Big-screen display and live scoring mean event night is about the competition, not a clipboard and a cash box.

This isn't about adding a payment feature. It's about recoupling the two things that should never have been separated — registering for your event and paying for it — and letting everything downstream (the ledger, the refund control, the payout) fall out of that automatically.

To set this up, walk through the help guide on setting up entry fees and payouts, and review the refunds, cancellations, and payout timing reference so your policy and your tooling line up. When you're ready to run a funded event without chasing a single payment, start here — and price it properly first with the Americano and league pricing guide.