Getting started

Airtable expense base not working: fixes for formulas, syncs and views

If your Airtable expense base is not working, check the field types, linked records, filters and automations in order, and know when a sheet is enough.

Editorial illustration for Airtable expense base not working: fixes for formulas, syncs and views

When an expense base in Airtable misbehaves, the culprit is almost always a field type, a filter on a view, a broken link between tables or an automation that was switched off. Start with what you can see on the screen: is the data missing, wrong or just hidden? The answer tells you where to look.

Is the data missing or only hidden?

Open the table in its grid view and look for an active filter, a hidden field or a grouping that collapses rows. A base often has several views, and one may filter on a month that has passed. Switch to an unfiltered view of the same table to see whether the records are there.

Why are my totals wrong?

Common reasons are an amount stored as text, a rollup that points at the wrong linked field, and records with an empty link that never join the total. Say your table has five expenses of ₹1,200, ₹850, ₹2,400, ₹300 and ₹1,000. The total should be ₹5,750. If the rollup shows ₹4,750, one record is probably missing its link or has a blank amount. Count the records first, then find the odd one.

SymptomLikely causeWhat to check
Total too lowRecord not linked or amount blankFilter for empty link or empty amount
Amount will not addField stored as textField type should be currency or number
Month view emptyDate stored as text or wrong formatDate field type and format
Form entries missingForm points at a different tableThe form settings and target table
Automation silentIt was turned off or ran out of its allowanceThe automation list and its run history

What if a formula returns an error?

  • Check that every field name in the formula still exists, because a renamed field breaks it.
  • Look for empty fields feeding a division.
  • Make sure text and numbers are not being mixed.
  • Rebuild the formula in a new test field and compare.

For the exact function behaviour, use the maker's help pages, since features and limits are theirs to state and may change.

Should I rebuild or move away?

A base is flexible, and that flexibility is also the weakness: every column, link and view is something you built, so every fault is yours to find. If you only want to know where your money went, ask whether you need a custom database at all. Entering each expense by hand is the part people drop after a few weeks.

What is a lighter alternative for personal spending?

If your records mostly come from bank and card statements, an expense tracker that imports them removes the typing. SpendixAI takes statements as PDF, CSV or Excel, lets you review rows before saving, and categorises them with your rules first. Cash can still be added by hand. It is not a database builder, so if you need custom relations between tables, keep Airtable for that.

How do I stop the base breaking again?

  • Give each field one purpose and one type, and do not reuse a text field for amounts.
  • Keep one master table of expenses and build views from it, instead of copying data into several tables.
  • Write a small note in the base saying what each view filters.
  • Check totals against your statement at month end, so a quiet fault shows up within weeks and not at year end.

A base that nobody has checked against a bank statement for four months is a base you cannot trust, however well it is built.

A short troubleshooting order

  1. Remove filters and look at the raw grid.
  2. Check field types for amount and date.
  3. Count records against the paper or statement.
  4. Test the formula in a fresh field.
  5. Check automation history.
  6. Export a backup before bigger changes.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports