Airtable can handle a shared expense tracker, but the right plan depends first on how you model each expense. The published limits are 1,000 records per base on Free, 50,000 on Team, and 125,000 on Business. Enterprise Scale lists a higher ceiling, but confirm its current terms on Airtable's plans overview.
Those records are rows in a base, not people in the group. Six roommates can share one grocery record. Six separate share rows would count six records. Collaborator permissions and base limits are separate checks.
Airtable record limits by plan
A base can contain several tables, but the record allowance applies to the base as a whole. Adding Expenses, People, and Settlements tables does not create three separate Free allowances.
| Plan | Record allowance | Practical shared-expense fit |
|---|---|---|
| Free | 1,000 records per base | One-off trips, small households, or short histories |
| Team | 50,000 records per base | Ongoing household, club, or team tracking |
| Business | 125,000 records per base | Large or long-running expense systems |
| Enterprise Scale | 500,000 records per base, subject to plan terms | High-volume data that needs plan confirmation |
These figures come from Airtable's current plan information. Limits can change, so check the official plans overview before upgrading or redesigning your base.
The cap is per base. A second table does not add another allowance.
Count rows before choosing a plan
Start with projected rows, not the number of people in the group.
Projected records = expense rows + share rows + settlement rows
Use these examples:
| Tracking design | Calculation | Approximate records |
|---|---|---|
| Four household bills logged once per month for two years | 4 x 24 | 96 expense rows |
| Three people logging 10 personal purchases per month for one year | 3 x 10 x 12 | 360 expense rows |
| One trip with 200 cost entries | 200 | 200 expense rows |
| Four separate share rows for each of 200 expenses | 200 x 4 | 800 share rows, plus the 200 expense rows |
Turns out, group size only affects the count when your base stores a separate row for each person's share. If participants live in a linked field on the expense record, the same 200-person trip can still have 200 expense rows.
That design choice changes the plan calculation.
A household with four recurring bills per month would use 96 expense records over 24 months if each bill gets one row. A group that logs individual purchases will grow faster.
A practical shared-expense base design
Keep the base understandable to someone who did not build it.
| Table | One record represents | Useful fields |
|---|---|---|
| Expenses | One bill, receipt, purchase, or deposit | Date, merchant, amount, category, payer, participants, receipt, status |
| People | One participant | Name, contact label, household or group |
| Shares | One person's portion of one expense | Expense, person, amount owed, split rule, settlement status |
| Settlements | One repayment or adjustment | Payer, recipient, amount, date, status, confirmation note |
A simple roommate tracker can skip the Shares table. Store participants and split details on the expense record instead.
Use a separate Shares table when each person's amount needs its own formula, status, or history. It creates more records, but it also makes uneven splits easier to review.
Airtable's expense tracking template can provide field ideas. Adapt it to your group's rules rather than assuming a template decides who owes what.
Collaborators and permissions
An expense tracker needs an access plan before it needs more storage. Airtable's permissions overview describes controls across workspaces, bases, interfaces, and administrative areas.
Use the smallest access level that still lets someone do their job:
- People who add receipts or correct records need editing access.
- People who only review balances should use a lower-access option when available.
- One or two organizers should control field definitions, split rules, and closeout changes.
Not every participant needs to edit the base. A controlled view or lower-access sharing option may be enough for someone checking what they owe.
Exact collaborator counts, role names, and sharing options depend on the current plan and workspace settings. Do not rely on a fixed number from an old pricing summary. Check Airtable's current plan information before inviting a large group.
If your workspace uses user groups, review Airtable's user group documentation. Keep bank details, account numbers, and unrelated personal information out of the tracker.
One base or several?
One base usually works best for one household, one trip, or one club fund. Keep expenses, people, and settlements together so totals stay easier to check.
Separate bases make sense when groups should not see each other's receipts, different organizers own the data, or a closed project needs its own access rules. Splitting a single household into one base per month usually creates more maintenance.
Treat base creation and record volume as different planning questions. Do not rely on a fixed base-count number from an old roundup; check the current plan documentation for workspace and base allowances.
Picking a plan for shared expenses
Free works when the active base stays under 1,000 records and its available sharing controls fit the group. A short vacation, a small household, or a single event may never need more.
Team makes sense when the group will keep records for years, use separate share rows, or approach the Free record ceiling. It provides room for up to 50,000 records per base.
Business is relevant for a much larger history or a more structured organization. Its published allowance is 125,000 records per base.
Enterprise Scale requires a direct check of the plan terms. To be honest, most roommate and travel groups should first improve their record model before considering that tier.
A spreadsheet may be simpler for a few one-time costs. Airtable becomes more useful when the group needs linked participants, repeatable fields, filtered views, or controlled access.
A workable monthly routine
Separate tracking from payment. Airtable can record who paid, who owes, the amount, and whether the balance is settled; the actual transfer should happen through the payment method your group has chosen.
- Add the expense soon after purchase. Include the payer, amount, category, and receipt.
- Apply the agreed split rule. Write down whether the group uses equal, usage-based, per-person, or reimbursement-after-proof splits.
- Let participants review the row before closeout. Correct errors while the receipt is still easy to find.
- Record the settlement status after payment is confirmed. Keep the request and transfer process separate from the tracker.
- Close the period with a short review. Look for missing receipts, duplicate rows, and unpaid balances.
A useful reminder is: "Please review this month's shared expenses by the agreed date. Add missing receipts and mark your share paid after the transfer is confirmed."
What to do near the record limit
First, confirm that the count includes only records you actually need. Duplicate imports, unnecessary share rows, and repeated settlement entries can make a base grow faster than expected.
Next, keep open balances in the active base and move closed history only after you have a verified copy. Preserve the receipts and split explanation needed to resolve later questions.
Thing is, a 1,000-record ceiling is rarely the first problem for a single short trip. It can arrive quietly through recurring utilities, personal purchases, and separate share rows.
Attachment storage, automation allowances, and other plan limits may matter too. Check Airtable's current plan page before assuming that more records alone will solve the problem.
FAQ
Does each roommate create a record?
No. A record represents whatever your table defines, such as one bill or one purchase. A roommate creates an additional record only if your design stores that person's share or transaction separately.
Do multiple tables bypass the record cap?
No. The allowance applies to the base, not to each table inside it. Adding a Shares table can make the system clearer, but it does not create extra record capacity.
Are collaborator limits the same as record limits?
No. Record capacity measures stored rows. Collaborator rules govern access, roles, and sharing. Check the current Airtable permissions documentation for the controls available to your plan.
Can Airtable handle the payment itself?
Use Airtable to track the obligation and its status. Keep the actual payment request, transfer, and confirmation in the payment method your group already uses.
Where should I confirm current Airtable limits?
Start with Airtable's plans overview, then review the permissions documentation for sharing questions. Plan details can change.
Create five sample expense rows, add separate share rows only where you need them, and compare the projected count with your plan before inviting the group.