Diagnosing and Fixing Date Gaps in an Account

The gap check only fires when the break between one period's end date and the next period's
start date is more than 24 hours. A start date exactly one day after the prior end date is
fine. A start date two days after the prior end date is enough to be flagged — this is a
common, deceptively small case: the dates aren't obviously wrong, they just leave one calendar
day uncovered.

Hovering the warning icon on the date field shows one of two distinct messages:

The difference between them is whether the ending balance on the earlier period and the starting
balance on the later period actually tie out.

• "Date Gap (No Balance Difference)" means the balances line up across the gap — the money
  is accounted for, only the dates leave a hole. This is usually a date typo or a misread date,
  not a missing statement.
• "Statement GAP (BALANCE difference)" means the balances don't tie out either. That's a
  stronger signal that a statement covering that stretch is genuinely missing — if it existed and
  were loaded, the running balance would connect.

Use this distinction before you do anything else: it tells you whether you're hunting for a typo
or a missing document.

The inline warnings on a statement's date fields are state-dependent. While a statement is
unreconciled, they check for overlaps with neighboring periods — the condition covered in
"Resolving a Date Overlap Error on a Statement".
The moment a statement becomes reconciled, the same warning switches to checking for
gaps instead, and keeps checking indefinitely afterward.

That means a statement can reconcile cleanly and then sit there with a persistent amber
highlight — that's the gap check finding a real 24-hour-plus break to its neighbor, not a sign
the reconcile failed or needs to be redone. If you just reconciled a statement and it's still
highlighted, look at the gap between it and the next period before assuming something went wrong.

Use "Fix Date Gaps" first — it's the direct answer for most of these. This is a single,
project-wide action, not something you run per statement. It walks every account's periods and,
for each adjacent pair, closes the gap only when it's small — roughly one to four days — and
only when the balances on either side of it tie out exactly. It moves only the later
period's start date; it never touches an end date, a transaction date, or a balance. If the
balances don't match, it leaves that pair alone rather than guessing.

After nudging a date, it re-checks the affected period automatically: a period that had been
reconciled and now fails the check drops back to unreconciled, and a period that had been
unreconciled and now passes cleanly is promoted to reconciled — either can happen as a result of
running this. It requires the more senior of the two engagement roles; the more junior role
cannot run it.

If the gap is larger than a few days, "Fix Date Gaps" will skip it, and that's a real signal:
the gap means a statement covering that period is genuinely missing. The fix is to upload it, the
same way you would load any other evidence.

Editing dates manually is also available, on the reconcile screen, only while the statement
is unreconciled. This changes the period's own start or end date only — it does not move the
dates on any transactions underneath it, which keep whatever dates they were originally read
with. Use a manual edit when the transactions themselves are dated correctly and only the stated
period boundary is off.

If a whole year was misread, use "Change Year" instead of retyping a date. "Change Year"
moves the period and every transaction inside it together, keeping them in sync — a plain date
edit would leave the period looking right while the transactions underneath still carry the
wrong year. Change Year also clears any existing matches on the affected transactions, which a
plain date edit does not.

None of these fixes affect matches by themselves except Change Year (noted above). Editing a
date field and saving, or letting Fix Date Gaps nudge a start date, does not delete or disturb any
transaction or match on the statement — only the period's own dates and, where the check finds a
new problem, its reconciled/unreconciled status.

The action requires the more senior of the two engagement roles. If you don't have it, either ask
someone on the engagement who does, or use the manual per-statement fixes above, which work at
any role level that can edit statement dates.