Data Foundation: Can the Numbers Be Trusted?
Every Load and Apply changes ends by checking the figures it wrote. The Summary page, under Data Foundation in the project home, shows the result: where the project stands in one line, five assurances, how fresh each system is, and the months you have closed. This page explains what each one tells you and what to do when it isn’t green. For setting up the project, see Get Started With Data Foundation.
Where the Project Stands
Section titled “Where the Project Stands”The first line of Summary says where the project stands:
| Line | Meaning |
|---|---|
| “In balance through September 2026” | Every assurance that applies is green, up to that month. |
| “2 of 5 assurances need attention through September 2026” | That many assurances are red. |
| “No finance system yet” | No system has been added. |
| “Not loaded yet” | No month has loaded. |
| “Loaded through September 2026; the assurances could not be read just now” | Data is loaded up to that month, but the assurances couldn’t be read when the page asked. |
| “Loading NetSuite” | A run is in progress. |
The month is the latest one that is complete. For a group, that is the last month every entity has loaded, and The group card says how complete the group is, for example: “38 of 41 entities loaded. Complete through September 2026; October is missing SAP ECC.” An entity that hasn’t loaded the next month holds the group figures back to the month before it, and the line names the system it comes from.
The Five Assurances
Section titled “The Five Assurances”The Can the numbers be trusted? card on Summary lists five assurances, each checked for every system, entity and month:
| Assurance | What it tells you |
|---|---|
| In balance with each system | Every account’s closing balance equals the balance the system itself reports. Where a system reports no separate balance, its ledger is compared with its own trial balance, month by month, and the line says Ledger agrees with its own trial balance. |
| Nothing lost on the way | Every row each system landed is counted, kept (it belongs to another system or book) or held back waiting for an answer. |
| Each entity’s books balance | Each entity’s postings for a month net to zero, in its own currency: debits equal credits. |
| The group adds up | Each intercompany pair agrees within the Intercompany tolerance, on charges and on balances, every month; every entity has its exchange rates; and each entity’s balance sheet balances in the reporting currency. |
| Cash flow agrees | The change in cash on the cash flow statement equals the movement in the cash accounts, for each entity and for the group. |
Each assurance shows one of these:
| Shows | Meaning |
|---|---|
| Green | It passed, and the line beneath says what was compared. |
| Red | At least one system, entity or month fails. The count beside it is how many items fail. |
| Not applicable | Nothing could be checked, for example a month with no balance or trial balance to compare with. The line beneath says why. |
| Not checked yet | No load has run the assurance. |
A company with one entity doesn’t see The group adds up. A month in which an entity has no exchange rate leaves that entity out of the group figures, so its cash flow isn’t judged that month.
When an Assurance Is Red
Section titled “When an Assurance Is Red”A red assurance lists what fails: up to the 20 most recent items, in month order. An item of the first three names the system, entity, month, account and amount. An item of the last two is a sentence, such as “No EUR rate for October 2026: Paris SA is left out of the group figures that month”. Amounts are in the reporting currency.
| Assurance | What to do |
|---|---|
| In balance with each system | Compare the account in the system’s own balance report, or its trial balance, with its ledger lines, then run Load again. |
| Nothing lost on the way | Answer the questions waiting on the Questions page, so the rows held back are counted. |
| Each entity’s books balance | Load the month again, or fix the journal in the system. |
| The group adds up | For a pair that differs, book the missing side, or correct the amount in the entity that differs. For a missing rate, load that currency’s rate for the month. For a balance sheet that doesn’t balance, check the eliminations and the translation of the statement lines. |
| Cash flow agrees | Give the balance sheet account that has no cash flow line an account role. |
Ask Weave why beside a red assurance asks Weave why it is red and who needs to fix it.
The Intercompany tolerance, in the reporting currency, is a project setting with a default of 1000. It is the same amount as group_red in Intercompany Eliminations.
The Readiness Checks stay as the detail under the five assurances. On the CFM-Accounting - Close and assurance dashboard, Every check, by system, month chosen groups them under the assurance each one proves.
How Fresh Each System Is
Section titled “How Fresh Each System Is”The Systems page shows, for each system, when it last loaded and, if the last load failed, its last good load. When the project’s Refresh setting is Daily, Weekly or Monthly, it also shows Next refresh with the time the next load is due. A system becomes overdue a day after it was due, and its row then says Refresh overdue since that time, in red. With one system, its row is on Summary, under Your system, marked Overdue when it is. With Refresh set to On demand, a system is never overdue.
A system whose load failed shows Failed and says what to do, for example to open its connection, or to connect again when its access has expired.
Close a Month
Section titled “Close a Month”Closing a month fixes its figures: later loads still read the system, but they no longer change a closed month. On Summary, the Close a month card says Closed through the last month every entity is closed through, or No month is closed yet.
To close:
- In Close through, pick the month. The list starts on the month after the last one closed, or on last month when none is closed.
- Click Close.
Every entity that you can see is closed through that month, and History records who closed it and when. Closing needs a Manager or Architect of the project.
When a system’s own fiscal calendar shows a month closed for every entity it holds, and the month isn’t closed here yet, the card offers it, for example “NetSuite shows September 2026 closed. Close it here?”. Click Close it here to close it.
When a System Changes a Closed Month
Section titled “When a System Changes a Closed Month”If a system later reports a different figure for a closed month, the closed month keeps its figure, and the What changed card on Summary shows the difference, naming the system, entity, month, account and the amount it changed by. The project shows amber while a change waits.
Click Accept the change to take the system’s new figures for that month. It runs Apply changes, which restates the month, and History records a Restatement with each account’s value before and after. Accepting a change needs a Manager or Architect who can use every system’s connection.
The Close target day project setting, five days after month end unless you change it, is the day the CFM-Accounting - Close and assurance dashboard counts a month as closed on time in Entities closed by the target day.
On the Dashboards
Section titled “On the Dashboards”Each Data Foundation dashboard tab opens with a context line that says what you are looking at: the month, the entity, the system, whether it is loaded and closed, how many assurances pass, and the currency and unit.
Notifications
Section titled “Notifications”People who use the PlaidCloud mobile app get two counts-only notifications about Data Foundation projects. Neither names the project.
- When a load changes the project’s state. When a Load or Apply changes finishes and the project turns red, amber or green, whoever started it gets “A Data Foundation project needs attention.” or “A Data Foundation project is ready.” For a scheduled load, that is whoever last saved the schedule.
- The daily digest. Once a day, each Architect and Manager of a project gets one notification, “2 Data Foundation projects need attention.”, counting the projects that since the last digest turned amber or red, whose last load applied codes no earlier load had seen, or whose load failed in the last 24 hours. On a project open to every member, only the person who last saved the project gets it. A project still loading is counted the next day.
A project is red when its last run failed or an assurance is red, amber while a question or a change after close waits or when the last load ended with a warning, and green otherwise. The color is judged on the whole project, not on the rows a person can see.