Fees and payouts

Money is where clan events go wrong, and it goes wrong quietly: a fee somebody swears they paid, a pool nobody can reconcile, a prize split argued about after the winners have logged off. This is the path that leaves a record at every step.

2 signatures settle a fee, by defaultPool = added + fee × approved entries1 row per person paid

Step 1

Setting the fee

The entry fee lives on the event, set when you create it or edited from its Sign-ups tab. A fee of nothing is a perfectly good answer — plenty of events run on a host-added pool alone.

Two settings decide what the fee actually means, and they are easy to skip past:

Per person or per accounton an event where people may enter several accounts, this decides whether they pay once or once each. Get it wrong and you will be refunding people.

Payment deadlineafter it passes, unpaid sign-ups stop being your problem to chase and start being a decision. Set it earlier than you think — the day before the event is too late to replace someone.

The pool follows the entries

The displayed prize pool is whatever you added by hand, plus the entry fee times the number of approved entries. It moves as sign-ups are approved and excluded, so the number on the page is always the one you could actually pay out.

Step 2

Collecting

Fees are collected the way your clan already collects money — in game, in Discord, however you do it. Anvil’s job starts the moment it arrives: somebody with staff access marks it paid, and that stamps who says they took it and when.

Players have a say too. A member can report who they paid and attach a screenshot, which is what turns “I definitely paid” into a record with two ends. When the player’s report and the collector’s claim name different people, that is a dispute the site can show you rather than one you find out about in an argument.

The proof is deleted on purpose

A payment screenshot is kept only until the fee is settled, then removed. It exists to resolve a disagreement, not to sit in storage for a year.

Step 3

The second signature

A fee sits at collected until a different staff member confirms it arrived. Whoever handled the money cannot also be the person who signs off that it turned up — that is the whole control, and it is why the site refuses a collector’s own confirmation rather than merely discouraging it.

How many signatures a fee needs is a clan setting, from zero to five. Zero exists for a real reason: in a clan where the treasurer is the owner, there is nobody else to sign, and “34 fees waiting on a second signature” becomes a queue that can never be cleared and permanently the loudest thing on the dashboard. At zero, marking a fee paid is the sign-off.

Set it to one — the default — if you have two people. Set it to zero if you honestly do not, and set it higher only if your clan has both the staff and the reason.

Step 4

Paying out

When the event ends, the event’s Payouts tab turns the pool into a list of people. Generate it and you get one row per recipient, not per team: a winning team’s prize divides equally across its members so that paying out is a list of names and numbers rather than an arithmetic problem at midnight.

Amounts start from a suggested split — winner-heavy, and the more paid places you set the flatter it gets — and every row is editable. The suggestion is a starting point, not a policy.

Then pay them, ticking rows off as you go. The point is that a week later anybody can look at the list and see who was paid what, rather than reconstructing it from Discord scrollback.

Announce it once, from here

Payouts post to your Discord channels from the event itself, so the announcement and the record are the same thing. A prize announced by hand is a prize somebody will later claim never arrived.

Step 5

When the numbers disagree

The four you will actually meet:

They say they paid, nobody marked itask them to report the payment with a screenshot. That puts a named collector and a timestamp on the record, and the named person can confirm or deny it.

Two staff both think they took itthe player’s own report is the tiebreak — it names who they handed it to. Fix the collector, then settle it.

A fee is stuck waiting on a signatureeither it is genuinely waiting on someone else, or your clan has fewer staff than the required-confirmations setting assumes. Lower the setting rather than confirming your own collection.

The pool changed after you told peopleit tracks approved entries, so approving or excluding a sign-up moves it. Quote the pool at the moment sign-ups close, not the moment they open.

Fees and payouts are the treasurer’s surface. A treasurer can do everything a moderator can, plus this; a moderator can mark a fee collected but never settle one.