For a sports team, start with a Transactions table linked to Categories. Add a Month Key formula so Airtable can group records by month.
This gives you a useful monthly summary. You won't need a report row for every expense. Add a persistent Monthly Summary table only when you need saved category-month totals or budget comparisons. Rollups total linked records. They don't automatically find every transaction that belongs to a month.
Choose the lightest setup that works
Turns out, most teams do not need a second table on day one. A grouped view of Transactions is faster to audit and often answers the monthly question by itself.
| Need | Recommended setup |
|---|---|
| Monthly totals by category | Transactions view grouped by Month Key, then Category |
| Saved category-month records | Monthly Summary table with one row per month and category |
| Player balances and reimbursements | People table, plus Contributions records when shares vary |
A spreadsheet may be faster for a team with fewer than 10 members, equal splits, and occasional expenses. Airtable earns its setup time when you need linked players, categories, receipts, or several people entering records. Headcount is only one factor.
If you want a visual starting point, Airtable's expense-tracking template is a generic reference. Adapt its fields to team reimbursements instead of copying a business layout unchanged.
Build the base structure
Use three tables first: Transactions, Categories, and Monthly Summary. Add People when you need to track who paid or who should be reimbursed.
Transactions table
| Field | Type | Why it belongs |
|---|---|---|
| Expense | Primary text field | Names the purchase, such as Spring tournament registration |
| Date | Date | Places the expense in the correct month |
| Amount | Currency | Stores the full cost of the receipt or bill |
| Paid By | Linked record to People | Identifies the person who fronted the money |
| Category | Linked record to Categories | Connects the transaction to Travel, Gear, Dues, or another category |
| Receipt | Attachment | Keeps a photo or file with the transaction |
| Reimbursement status | Single select | Tracks stages such as Not requested, Requested, and Reimbursed |
| Notes | Long text | Records split details, approval notes, or exceptions |
| Month Key | Formula | Groups records by month |
For the Month Key formula, use:
IF({Date}, DATETIME_FORMAT({Date}, "YYYY-MM"), "")
Make Amount a currency field and Date a real date field. Free-typed dates create messy filters.
Categories needs a Name field and, optionally, a Budget field. Its linked Transactions field lets you add a Total Spent rollup using the Amount field and SUM(values).
People can store players, coaches, parents, or organizers who pay team costs. If one base holds multiple teams or seasons, add Team and Season fields to Transactions. Filter those fields before reading monthly totals.
Create the simple monthly summary view
Start here before building a separate summary table.
- Add a few category records, such as Uniforms, Travel, Dues, Gear, Snacks, and Tournaments.
- Enter sample transactions with a date, amount, category, payer, and receipt.
- Create a grid view in Transactions named
Monthly summary. - Group the view first by Month Key and then by Category.
- Set the Amount summary to Sum. You can also show a record count.
- Add a Team or Season filter if the base contains more than one group.
- For a single month, filter Month Key to an exact value such as
2026-03.
The group totals update as transactions change. Compare one displayed month with a manual total before sharing it. Airtable's custom reports guidance also describes views and rollups as ways to summarize linked data.
Airtable calls this a view rather than a separate tab, but it works as the team's monthly summary area. Keep the underlying Transactions table available for review.
Add a persistent Monthly Summary table
Use this option when the team wants saved report rows, budget comparisons, or a clean record for each closed month.
One row should represent one category in one month. That rule keeps the math visible.
| Field | Example | Setup |
|---|---|---|
| Summary name | 2026-03 \| Travel |
Primary field |
| Month Key | 2026-03 |
Single line text or a consistent month date |
| Category | Travel | Linked record to Categories |
| Transactions | March travel records | Linked records to Transactions |
| Total Amount | 450 | Rollup of Transactions > Amount using SUM(values) |
| Transaction Count | 3 | Rollup using the count-all option |
| Budget | 500 | Optional currency field |
| Variance | 50 | Optional formula using Budget minus Total Amount |
Create 2026-03 | Travel. Link only the March travel records. Total Amount then rolls up those linked Amount values.
Manual links are fine for a small team. For a busier base, use a stable key such as 2026-03|Travel; an automation can find the matching summary row and write that link back to Transactions. Test a few records first. Duplicate keys can create bad totals.
An Airtable Community budgeting example uses intermediate records for nested rollups. Treat it as a design pattern, not official sports-team instructions.
Thing is, a rollup cannot guess which records belong in the row. A Categories rollup can show all linked transaction totals, but it does not know which month you are viewing. To show persistent totals by month, group Monthly Summary by Month Key and sum Total Amount.
Keep team costs separate from reimbursements
Do not confuse the full expense with one person's share.
A tournament fee may be paid by one parent while several players owe different amounts. A uniform may belong to one player. Travel may depend on attendance, nights stayed, or another rule the group agrees to in advance.
| Record or field | What it means |
|---|---|
| Amount | Full cost of the receipt or bill |
| Paid By | Person who paid upfront |
| Owed Amount | Amount a person should repay |
| Reimbursement recipient | Person who should receive repayment |
| Status | Whether the request is pending, requested, or reimbursed |
For a simple one-person reimbursement, Owed Amount and Reimbursement recipient can sit on Transactions. For several people, create a Contributions table with Expense, Person, Share Amount, Status, and Notes fields. Roll up contribution amounts when calculating balances, not the original expense amount.
Equal splits can work for shared snacks or dues. Player-specific gear usually needs a player link. Record the chosen rule in Notes so the same expense is not recalculated differently later.
Airtable records the decision and status. It does not send or settle the payment.
Share the record without opening the whole base
Keep data entry separate from review. A form can collect a new expense and its receipt, while a filtered view can show approved monthly totals.
If parents or players need to update an existing record, that is different from submitting a new one. Airtable's support page on updating records using a form documents a workaround for that situation.
| Audience | Practical access |
|---|---|
| Treasurer or organizer | Edit access to the working base |
| Players or parents | A form for new submissions and a read-only review view when available |
| External reviewer | A filtered view containing only the fields they need |
Before sharing, remove private notes and internal approval fields from the review view. Open the shared view yourself first. Check that receipts, payer names, and reimbursement statuses show what you intend.
Sharing records is not the same as collecting money. Keep the payment step in whatever method the group already uses, and use Airtable as the supporting record.
Check the numbers before trusting them
The date is right, the category is right, the receipt is somewhere in a phone camera roll, but the record still lands in the wrong month because the Date field was text. It happens.
| Common mistake | Better fix |
|---|---|
| Category is a single select, but you need linked rollups | Use a linked Categories record |
| Month is typed into notes | Use a Date field and Month Key formula |
| Categories rollup is expected to show one month | Use the grouped view or category-month links |
| Full expense is used as everyone's reimbursement | Track Contributions or Owed Amount separately |
| Automation is turned on before the design is tested | Check several records manually first |
| Receipts live only in messages or camera rolls | Attach them to the transaction record |
Log purchases soon after practices, registrations, or tournament events. Once a month, check the receipts, payer, category, and reimbursement status before sharing totals.
The summary is only as reliable as its links. Start with five sample expenses and one month, compare the grouped total with the receipts, and add the persistent Monthly Summary table only if the team needs saved category-month records.