Airtable rollup totals: why a filtered view does not change the sum

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose the population before the formula

Airtable rollups calculate over fields from linked records. A view filter on the source table does not, by default, constrain a rollup elsewhere. If a total should include only approved records, express that requirement in the rollup’s conditions rather than relying on which rows a teammate currently sees.

Worked reconciliation

Use an illustrative project with three linked expense rows: 40 approved, 15 draft and 5 approved, all in one currency. An unconditioned sum over those amounts is 60. The business question “approved expenses” expects 45. Seeing only the two approved rows in a filtered Expenses view does not prove that the project’s rollup has the same scope.

Build the smallest useful check

1. Record the project ID and the IDs of its three expense links.
2. Confirm the numeric amount field and that all example values use the same unit.
3. Configure a rollup on that relationship using SUM(values).
4. Add the explicit Approved condition if that is the intended population.
5. Compare the output with the hand-calculated fixture, then change the draft row’s status and repeat the comparison.

Investigate disagreement without hiding it

If the result is 45 but you expected 60, inspect the conditions and actual links. If it is 60 but you expected 45, check whether approval is only a view filter. If it is another number, inspect missing links, wrong projects and inconsistent amounts before changing aggregation functions. Do not round a disagreement away.

Define the reporting contract

Store the metric name, currency, included statuses and time boundary beside the report. A lifetime project total and this month’s approved total are distinct measures. For mixed currencies, define a conversion policy before adding the amounts. No calculation in this example supplies exchange rates or accounting advice; it demonstrates how to make the included population explainable.

Continue with Airtable junction tables: store facts about a relationship when that next step matches your workflow.