Whether a finance sheet is current depends on three separate processes:
- Collaboration synchronization: Changes made by connected editors usually appear for other active users without a manual refresh.
- Formula recalculation: Formulas generally recalculate when their dependent cells change, depending on calculation settings and workbook performance.
- External-data refresh: Imports, connectors, add-ons, and APIs follow their own refresh rules. They may not update immediately.
A visible formula result proves only what the current cells calculate. It doesn’t prove that imported data is complete, current, or free of duplicates.
What updates automatically?
Edits from collaborators
Google Sheets supports simultaneous editing. When 2 authorized users have the workbook open and working internet connections, a cell change made by one user will usually appear for the other. Google documents its sharing and simultaneous-editing behavior in Share files from Google Drive.
Still, “real time” doesn’t mean a guaranteed synchronization time. A weak or interrupted connection can delay when another user sees an edit.
Formulas that depend on edited cells
A formula such as =B2-C2 normally recalculates after either input changes. More complex formulas can take longer, particularly when a workbook contains:
- Large or repeated range calculations
- Whole-column references
- Long chains of dependent formulas
- Numerous volatile functions
- Multiple import functions
- Formula errors that affect downstream cells
For slow workbooks, see Google’s separate guidance for improving Sheets calculation performance.
Imported or connected data
External data follows a separate update path. As a result, a formula can be fully recalculated while still using stale imported values.
For example:
IMPORTRANGEfollows behavior documented specifically for IMPORTRANGE.- Connected Sheets has its own manual and scheduled refresh options, described in Google’s Connected Sheets documentation.
- Add-ons and third-party connectors can use different schedules or require a connector-specific refresh action.
There’s no universal refresh interval for every import function, connector, API, and add-on.
A controlled finance example
Use this illustrative workbook to distinguish collaborator visibility, formula recalculation, and source refresh.
All formulas use commas as argument separators. Some spreadsheet locales require semicolons instead.
Transactions sheet
Create a tab named Transactions and enter:
| Cell | Value |
|---|---|
| A1 | Date |
| B1 | Category |
| C1 | Amount USD |
| A2 | 2026-07-01 |
| B2 | Revenue |
| C2 | 12500 |
| A3 | 2026-07-31 |
| B3 | Revenue |
| C3 | 7500 |
| A4 | 2026-08-01 |
| B4 | Revenue |
| C4 | 9000 |
Store A2:A4 as dates, B2:B4 as text, and C2:C4 as numeric amounts.
Summary sheet
Create a tab named Summary and enter:
| Cell | Value |
|---|---|
| A1 | Month start |
| B1 | Revenue USD |
| C1 | Budget USD |
| D1 | Variance USD |
| A2 | 2026-07-01 |
| C2 | 21000 |
Store Summary!A2 as a date, not text, and store Summary!C2 as a numeric amount. If your locale doesn’t recognize 2026-07-01 as a date when entered, use the locale’s accepted date-entry format and confirm that the cell contains the date July 1, 2026.
Enter this formula in Summary!B2:
=IF(COUNT(Transactions!C2:C4)<>COUNTA(Transactions!C2:C4),NA(),SUMIFS(Transactions!C2:C4,Transactions!B2:B4,"Revenue",Transactions!A2:A4,">="&A2,Transactions!A2:A4,"<"&EDATE(A2,1)))
The COUNT versus COUNTA check returns #N/A when a populated amount is nonnumeric. Blank amount cells remain acceptable under this particular control.
Enter this formula in Summary!D2:
=IF(AND(ISNUMBER(B2),ISNUMBER(C2)),B2-C2,NA())
Expected result
Summary!B2 should equal 20,000 USD:
12,500 + 7,500 = 20,000
The August 1 transaction is excluded because the formula uses a half-open date range. July 1 is included, while August 1 is excluded.
Summary!D2 should equal -1,000 USD:
20,000 - 21,000 = -1,000
Together, these values provide the baseline. The workbook passes the check when B2 is 20,000 and D2 is -1,000 with the stated inputs.
Test each update path
The following are proposed checks, not claims that they were executed. Reset the workbook to the baseline before each test unless the test says otherwise.
| Test | Input change | Expected Summary!B2 | Expected Summary!D2 | What it checks |
|---|---|---|---|---|
| Baseline | Use the original rows | 20,000 | -1,000 | Formula and date-boundary setup |
| Collaborator edit | Another editor changes Transactions!C3 from 7500 to 8000 | 20,500 | -500 | Edit visibility and dependent recalculation |
| Zero amount | Change Transactions!C3 to 0 | 12,500 | -8,500 | Zero remains a valid numeric amount |
| Blank amount | Clear Transactions!C3 | 12,500 | -8,500 | The formula permits blanks |
| Malformed amount | Paste the text seven thousand into Transactions!C3 in an unvalidated test copy | #N/A | #N/A | The numeric-type guard |
| Invalid category | Change Transactions!B3 to Rev | 12,500 | -8,500 | Only rows matching the Revenue criterion are included |
| No matching rows | Change Transactions!B2:B4 to Expense | 0 | -21,000 | Behavior when no rows match |
| Lower date boundary | Confirm Transactions!A2 is 2026-07-01 | 20,000 | -1,000 | July 1 is included |
| Upper date boundary | Confirm Transactions!A4 is 2026-08-01 | 20,000 | -1,000 | August 1 is excluded |
| Duplicate row | Append 2026-07-31, Revenue, 7500 in row 5 and extend every formula range ending at row 4 to row 5 | 27,500 | 6,500 | Financial effect of a duplicate |
| Opening entry | Append 2026-07-01, Revenue, 1000 in row 5 and extend every formula range ending at row 4 to row 5 | 21,000 | 0 | Treatment of an opening or adjustment row |
The duplicate test reveals the duplicate’s financial effect, but it doesn’t identify or exclude the row automatically.
Because its date and category meet the formula criteria, the opening-entry test includes the additional row. Excluding opening entries would require another field, such as transaction type, and an explicit exclusion rule.
The Rev test concerns an incomplete category label, not case sensitivity. If exact capitalization is a required control, build and test an EXACT-based method separately.
Finally, a zero result in the no-matching-rows test means the formula found no matching numeric amounts. It doesn’t prove that the source loaded successfully.
Check whether collaboration is current
Use 2 authorized editors:
- Have both users open the same workbook while online.
- Confirm both see the baseline values of 20,000 in
Summary!B2and -1,000 inSummary!D2. - Have one user change
Transactions!C3from 7500 to 8000. - Have the other user observe
Transactions!C3,Summary!B2, andSummary!D2. - Confirm the final values are 8000, 20,500, and -500.
- Record whether the edit appeared and whether the formulas reached the expected results.
If you suspect delayed collaboration, repeat the check under stable and interrupted connectivity. The observation applies to that workbook session. It doesn’t establish a universal synchronization speed.
Check calculation settings
In the desktop version of Google Sheets, open:
File → Settings → Calculation
Google documents the available recalculation controls in Change a spreadsheet’s locale and calculation settings.
Review these items:
- Confirm recalculation occurs on change.
- If the workbook uses functions such as
NOW,TODAY,RAND, orRANDBETWEEN, review whether a periodic recalculation option is appropriate. - Remember that periodic recalculation settings don’t set the refresh schedule for external connectors.
- After changing a setting, repeat the controlled source-cell test and compare the result with the expected 20,500 and -500.
Re-entering a formula or reloading the browser can help diagnose a problem. Neither action proves that the underlying issue is resolved, though. A connector may still be stale, or the formula may still reference the wrong cells.
Test an external-data refresh separately
If Transactions is populated by an import or connector, use this test:
- Identify the exact import method or connector.
- Record its displayed last-refresh time, if one is available.
- Choose one source record that maps to a known destination cell.
- Change that source value.
- Use the refresh action documented for that specific import method or connector.
- Confirm the corresponding destination cell changes.
- Confirm
Summary!B2andSummary!D2reach the independently calculated expected values.
Don’t assume that every connected range is current just because one formula recalculated. Source freshness, successful transfer, and downstream calculation are separate controls.
Troubleshooting a stale finance sheet
Check the update paths in sequence.
1. Confirm the source cell
First, check whether the expected value is present in the actual source cell. If Transactions!C3 still shows 7500, a downstream formula cannot produce the expected result for an 8000 input.
2. Inspect formula errors
Next, check Summary!B2 and Summary!D2 for errors. A malformed amount should produce #N/A in this example rather than a misleading total.
3. Check data types
Make sure dates are stored as dates and amounts are numeric. A value that looks like a date or amount can still be text. This applies to both Transactions!A2:A4 and the month-start input in Summary!A2.
Although the example checks the amount column, it doesn’t validate the date column. If dates arrive through pasted or imported data, add a separate date-quality control.
4. Verify the formula range
Check whether the formulas cover every required row. New rows outside Transactions!2:4 aren’t included unless the range expands. Use bounded dynamic ranges or table designs carefully, since whole-column references may add unnecessary calculation work.
5. Review calculation settings
Then confirm that the workbook’s calculation settings match the formula design, especially when volatile functions are present.
6. Check the external source
Review the connector’s status, refresh history, permissions, and documented refresh action. A correct SUMIFS formula cannot compensate for an incomplete source extract.
7. Treat browser reload as a diagnostic
Reloading may restore a disrupted browser session. It doesn’t guarantee that an external source was refreshed or that a calculation design is correct.
Finance checklist for shared budgets and forecasts
Before relying on a shared budget, forecast, or reporting sheet, confirm:
- The relevant editors are working in the intended workbook and tab.
- The source cells contain the expected values.
- Dates and amounts use the intended data types.
- Formulas cover all required rows and periods.
- Boundary dates are included or excluded as designed.
- Formula errors are visible rather than converted silently to zero.
- Duplicates and opening entries have explicit treatment.
- Calculation settings match the functions used.
- External-data freshness is checked through the applicable connector or import method.
- A control total is reconciled to independently stated inputs.
- Zero is distinguished from blank, missing, and failed-to-load data.
If the sheet feeds a chart, see Do Google Sheets Charts Update Automatically From Source Data?.
How ModelMonkey can help inspect a stale sheet
ModelMonkey is an AI assistant for Google Sheets and Microsoft Excel. In Google Sheets, it can receive the active spreadsheet, sheet, and range context.
Its spreadsheet tools can read ranges and formula errors, search sheet content, scan tables, analyze data, and make spreadsheet changes. For the example above, a task-specific request could be:
Inspect
Transactions!A1:C4andSummary!A1:D2. Check for formula errors, nonnumeric amounts, incorrect date types, and rows excluded from the July revenue total. ReconcileSummary!B2to the transaction rows and explain any proposed changes.
When the workflow presents a preview, review the proposed changes before proceeding. ModelMonkey’s output still requires judgment because its formulas, analysis, and edits aren’t guaranteed to be correct.
The Google Sheets assistant starts sessions through a configured backend service, so offline AI operation isn’t established. It also shouldn’t be treated as the refresh mechanism for every connector.
You can ask ModelMonkey to inspect the two example ranges. Before accepting any proposed edits, verify that the resulting July revenue and variance match the stated 20,000 USD and -1,000 USD controls.