> ## Content Index
> Fetch the complete content index at: https://notionsolutions.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Notion Rollup Sum Wrong? Reconcile the Linked Project Amounts
- URL: https://notionsolutions.net/notion-rollup-sum-wrong/
- Published: 2026-10-30T10:17:10.000Z
- Updated: 2026-10-30T10:17:12.000Z
- Description: Trace one client's linked project budgets to the rollup, distinguish a wrong sum from an incomplete subtotal, and keep integration discrepancies separate.
- Author: Kevin Turner
- Tags: fix, client-work

A Notion rollup can show a valid number and still total the wrong work. Start with the **exact pages linked to the client**, check the amount on each page, then confirm that the rollup uses the intended relation, numeric property, and **Sum**. A project elsewhere in the workspace does not join the total just because it has the same client name.

I would reconcile one client before changing formulas or rebuilding databases. That gives you a small, visible set of inputs to compare with the result. This guide covers a populated numeric total inside Notion; for a blank result or unavailable source property, start with the [source, relation, and access checks](https://notionsolutions.net/notion-rollup-not-working/).

## Identify which total you are reading

A rollup on a client page and a calculation across the Clients database answer different questions. The first totals the projects linked to that client. Notion also supports [aggregating a rollup column across a table or board](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#aggregate-rollups), such as summing every client's project total. Reconcile the individual client row first, before investigating that second aggregation.

Also compare the result in Notion itself with the result you are questioning. If Notion shows the expected total but an integration shows another value, preserve that distinction. For example, [NotionApps documents its own recalculation, related-database access, and sync checks](https://docs.notionapps.com/troubleshooting/why-are-my-rollups-on-notionapps-showing-zero-0-value-or-an-incorrect-value?ref=notionsolutions.net). Those controls belong to NotionApps; they are not settings for a native Notion rollup.

## Check the linked projects, not a similar-looking list

Open the client record and inspect the relation selected by the rollup, such as **Projects**. Open each linked page from that property. [A rollup reads a chosen property from those related pages](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#rollups), so this list defines the inputs you need to reconcile.

Check for a missing project, an unintended project, or a similarly named page with a different amount. A client label stored in a Text or Select property does not establish the relation. If the client has several projects but you can only select one, check the relation's limit: Notion offers [1 page or No limit](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#view-and-remove-related-pages). Choose the limit that matches the actual client-project rule.

Do not use a filtered project view as a substitute for this check. Notion's [view filters control which records that view displays](https://www.notion.com/help/views-filters-and-sorts?ref=notionsolutions.net#filters); the rollup's documented inputs are its related pages. Inspect the relation directly rather than assuming that an “Active projects” view defines the budget total.

## Confirm the source property and calculation

Click a cell in the rollup column to inspect its configuration. Check these choices in order:

1. **Relation:** Projects, rather than a separate Invoices or Tasks relation.
2. **Property:** the intended Budget field on those project pages.
3. **Calculate:** Sum, rather than a count or a list of original values.

For a straightforward budget total, use a numeric source. Notion's [Number property accepts numbers and can display them as currency](https://www.notion.com/help/database-properties?ref=notionsolutions.net#types-of-database-properties), and its [Sum calculation adds numeric properties on related pages](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#rollup-types). A budget written in the page body is not the selected Budget property.

If the source is a Formula instead, inspect that formula's inputs and result type before applying this numeric reconciliation. Do not change the original property's type merely to make Sum appear. A list, formatted text, or a formula error needs its own diagnosis; Notion's [formula-error guidance distinguishes type, reference, and empty-value problems](https://www.notion.com/help/common-formula-errors?ref=notionsolutions.net).

The rollup also has [number-format and decimal-placement settings](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#rollups). Compare the entered source amounts and the intended precision, not just rounded labels. Use one agreed currency for the reconciliation; a dollar-looking format is not evidence that amounts originally recorded in different currencies have been converted.

[![North Studio budget total checked against Projects relation, Budget Number property in US dollars and Sum calculation](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/rollup-check-three-inputs.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/rollup-check-three-inputs.webp?ref=notionsolutions.net)

Confirm all three inputs: Projects, the numeric Budget field and Sum. A familiar-looking total can still read the wrong source.

## Reconcile one client's project budget

In this fictional example, North Studio's Projects relation contains Brand refresh, Content update, and Discovery. Each Budget value is a Number in US dollars. The client rollup reads **Projects → Budget → Sum**.

__Example inputs for North Studio's linked-project total__
| Project         | Budget | Linked to this client? |
| --------------- | ------ | ---------------------- |
| Brand refresh   | $1,200 | Yes                    |
| Content update  | $450   | Yes                    |
| Discovery       | $300   | Yes                    |
| Additional work | $600   | No                     |

The linked amounts add up to **$1,950: $1,200 + $450 + $300**. Additional work's $600 is outside this record set. Whether it *should* be linked is a budget decision; finding it elsewhere in Projects is not enough to include it.

A result of $1,500 would prompt you to check Content update's link and Budget value. A result of $2,550 would prompt you to look for the additional $600 among the linked inputs. A result of 3 would prompt you to check whether a count was selected. These are arithmetic clues, not unique diagnoses: inspect the configuration and source pages before changing anything.

### Change only a confirmed cause

Use the discrepancy to choose the next inspection, then correct only the mistake you have confirmed:

1. **If the known amounts total $1,500:** check whether Content update is actually present in North Studio's Projects relation. If it is missing and belongs to this client's budget, select that exact project page in the relation. If it is already linked, open it and inspect its Budget value; adding another similarly named project would not repair a missing amount.
2. **If the total is $2,550:** inspect whether Additional work is linked. If the budget rule excludes that project, remove that relation entry rather than deleting the project itself. Notion's [related-page control removes a link with the **–** action](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#view-and-remove-related-pages).
3. **If the output is a count:** confirm that the source is the intended numeric Budget and the calculation is Sum. Keep any useful count as a separate completeness check; do not treat the number of linked projects as their dollar total.

After the confirmed edit, reopen the same client and reconcile the same inputs. The target is a total whose linked membership, entered amounts and calculation match the budget rule, not simply a larger number.

## Separate missing amounts from a wrong sum

A correct sum can still be an incomplete budget. If a linked project's amount has not been agreed, label the result as a known-budget subtotal until that input is resolved. Do not turn an unknown amount into an agreed zero simply to make the table look complete.

Add a separate check using [Count empty on the same Budget property](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#rollup-types). It counts related pages without a value. **Count values** counts non-empty values, while **Count all** counts values instead of adding their amounts. Keep these checks distinct from the budget Sum so a missing input stays visible.

The same $1,500 of known amounts can arise from different incomplete inputs. With only Brand refresh and Discovery linked, the relation contains two projects and **Count empty** is 0 if both Budget fields have values. With all three intended projects linked but Content update's Budget empty, [Count empty is 1](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net#rollup-types). The first case needs a membership decision; the second needs an amount to be agreed and entered. Neither is evidence that the Sum calculation itself is wrong.

[![Two North Studio input sets both have $1,500 of known budgets, but a missing link has Count empty 0 and a linked empty Budget has Count empty 1](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/rollup-same-subtotal-different-cause.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/rollup-same-subtotal-different-cause.webp?ref=notionsolutions.net)

Check membership before missing values. An unlinked project and an empty Budget need different corrections, even when the known subtotal is the same.

Change one confirmed cause at a time, then reconcile the same record set again. If the links, numeric inputs, property, and calculation all match but the result still differs, record the exact pages, amounts, settings, and discrepancy for the workspace owner or support. Keep the existing databases intact while that unexplained result is investigated.