A payout table is the rule that turns an event's pool into who gets paid what. You build one from Settings → Payouts with the Create a payout table button, then assign it to a division.
The button opens a chooser with three kinds. Start with the one closest to your habit.
Twelve players at $16 each is a $192 pool. If you already keep a per-field-size dollar sheet, choose Grid, choose Paste from a spreadsheet, paste the sheet, and save. Each row is a field size and the amounts paid for each place. A header row is recognised if you include one.
Under Saved Payout Tables, each table shows what every place wins, in dollars, for each division that uses it: one row per number of players, places across. The dollars come from the part of the division's price that goes to payouts, after the ace pot, club funds and any season feed the current season takes from each entry. With $20 entry less $3 ace pot and $1 club funds, that is $16 a player, so the row for 12 players shares out $192. Each row assumes everyone paid in full and nobody tied, and it is exactly what the payouts screen pays for a night like that.
Rows run to four past the division's biggest field so far, and at least to 12; Show all shows the rest. A Grid table shows no row for a field size it does not cover. A division with no price, in a league with no default price, has nothing to work the dollars out from, and links you to Divisions & prices. A table no division uses shows its percentages instead.
While you build a PDGA curve, Show full field-size table shows the same kind of table at the Payout per player you set.
A Grid table only pays field sizes it has a row for. If an event has a field size your grid does not cover, the payouts screen tells you and asks you to add the row or enter the payouts by hand; the app never guesses a row by blending the sizes on either side. While you build a Grid table, the editor warns you about gaps between your smallest and largest field size, but it does not stop you saving.
Two divisions can use the same table. When you edit a table that more than one division uses, the editor names those divisions, and you choose:
Renaming a table only changes its name; it never makes a copy.