Excel PivotTable omits new bank rows after refresh
Updated · 2 min read
Refreshing an Excel PivotTable does not prove that newly appended bank rows fall inside its source range. Check the configured range separately from refresh completion. This route applies to an ordinary table/range PivotTable, not every Data Model or external-connection PivotTable.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Inspect the actual source boundary
- On a working copy, select the PivotTable and open Analyze → Change Data Source.
- Compare the selected source with the complete current bank-data range or intended table. Record the old boundary and check the first and last event identities.
- If new rows lie outside a fixed range, select the intended complete source and confirm the change.
- Refresh again. Compare the underlying event membership with the retained transaction list, rather than accepting the visible total alone.
Use this route only for the source types covered by Microsoft’s change-source instructions.
Microsoft documents different handling for Data Model sources; the ordinary change-source route is not available there. External connections require their own source review, and substantially changed columns may require a new PivotTable. Do not apply a range fix to those cases without checking their actual configuration.
Use a zero-net omission control
The synthetic range exercise begins with two source events. Two newly appended rows, +40 and −40, sit outside the original fixed range. Refreshing that range leaves its net total unchanged, so the total alone falsely looks complete. Expanding the source includes all four event identities while retaining the same net.
| Synthetic source event | Amount | In fixed source A–B? | In expanded source A–D? |
|---|---|---|---|
| A | +100 | Yes | Yes |
| B | −20 | Yes | Yes |
| C | +40 | No | Yes |
| D | −40 | No | Yes |
| Event count / net | — | 2 / 80 | 4 / 80 |
The Python checks compare membership and counts before and after the stipulated boundary change; they do not run Excel. In your workbook, review the detail behind the PivotTable and compare its source membership with the retained transaction list after refreshing.
Keep the old range, new range and source version with the review. Missing IDs, ambiguous source tables or an incompatible source type remain unresolved. For aggregation design and preserving the rows behind totals, use the separate grouping guide rather than treating a successful Refresh message as a completeness certificate.
For a PDF-only bank source, download LocalExtract. It processes one PDF locally to date,description,amount CSV; it does not access platform accounts or synchronize accounting records.
Official sources and scope
Documentation checked October 16, 2026. Official reference 1 — excel-pivot-source · Official reference 2 — excel-refresh
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy