"Missing Stmt" on the Check Match Screen

A check item on the TO MATCH tab shows an "X" in the Missing Stmt column. Hovering it
reads "Statement data may be missing for this time period" — but the statement for that period is
uploaded, processed, and reconciled. The flag is wrong, and it's worth understanding why before
you go looking for a missing statement that isn't actually missing.

Missing Stmt only appears on the TO MATCH tab — you won't see it on TO APPROVE or
MATCHED, because the flag only has meaning for items that haven't been resolved yet.

It does not test whether a matching statement exists, and it does not test reconciliation status.
It reads a cached, per-account snapshot computed by a separate background job, and that job only
checks two things:

1. Whether the last four digits of the check item's extracted account number match an account
   already configured in the project.
2. Whether the check's date falls inside a recorded period for that account.

If either check fails, the flag is set — even when the correct statement for that account and
period is sitting in the system, fully processed and reconciled. The flag has no idea whether a
matching statement line exists; it only knows whether the account and period the check item
thinks it belongs to look plausible.

Several distinct things can leave you looking at a flag that doesn't reflect reality:

• The check was never re-checked after your fix. This check does not run automatically — not
  on upload, not when a statement is reconciled, not on a schedule. It only runs when someone
  clicks Statement existence, and that button only appears on the TO MATCH tab. Fixing and
  reconciling the statement, by itself, does nothing to the flag until this is re-run.
• The account match is only on the last four digits. If two accounts in the project share the
  same last four digits, or the extracted account number is garbled in a way that still happens
  to end in the right four digits, the flag can be cleared or set for the wrong reason.
• The account number or date was misread on the check item itself. If either was extracted
  incorrectly, the flag will be set regardless of what's actually been uploaded.
• An unreconciled period is enough to trigger it, on its own — a period existing and having
  data isn't the same as it being reconciled, and reconciliation status is not what this flag
  measures either way. It's simply another way the same cached snapshot can be out of step with
  what's true right now.
• The flag clears automatically the moment the item matches or unmatches — so the state you
  see on a long-unmatched item can be very stale relative to everything that's happened since.

The button that re-runs this check is called Statement existence. Nothing about that name
suggests "re-check my Missing Stmt flags," and it isn't the same as checking whether a statement
exists in any general sense — it only re-evaluates account-number-suffix and date-range matching
for check items still in TO MATCH. If you've been looking for a way to make the flag reflect
reality and didn't think to try this button because of its name, that's a reasonable thing to
miss.

Don't rely on the flag by itself. To confirm whether a statement genuinely covers a check item's
period:

1. Check the account and period directly in the statements area, rather than trusting the icon.
2. If you've since fixed the account number or date on the check item, or uploaded a statement
   that wasn't there before, click Statement existence on the TO MATCH tab. You'll see a
   notification that the system is checking statement periods for all check items — this
   re-evaluates every item still in TO MATCH, not just the one you're looking at, so expect a
   short wait.
3. If the flag still doesn't match what you can see in the statements area after re-running it,
   double-check the account number and date on the check item itself — a mismatch there is the
   most common cause.