Financial Inspector

The Inspector runs a battery of sanity checks across the data you imported — bank, card, cash flow, wallet — and returns a list of findings with everything that looks off.

The point is to flag inconsistencies without you eyeballing every account: duplicate entries, transactions with impossible dates, balances that don't reconcile against the statement, assets sold without a priced buy, missing FX rates, and so on.

How to run it

The page lives under Tools → Inspector. The Run now button kicks off a full execution against your current data.

There's a per-user daily quota configured by the admin (default = a handful of runs/day). When you hit the cap, the next attempt returns 429 with the reset time. This protects the infra during peak hours — for intense audits, spread the runs out.

Each run executes in the background, and gets logged with started_at / finished_at + the finding count per severity. The history shows up right under the button.

Reading findings

Each finding carries:

• Severity:
  • Error — something is inconsistent and likely affecting your reports. Investigate.
  • Warning — worth a look, but nothing's broken.
  • Info — heads-up; no action required.
• Module — bank, card, cashflow, wallet, or consolidated.
• Title — one-sentence description of what was detected.
• Check ID — internal identifier for the check, useful if you need to report a bug.
• Status:
  • Open — newly detected, not yet reviewed.
  • Acknowledged — you saw it and chose not to act now (stays in the list but off your radar).
  • Resolved — you fixed it (e.g. removed the duplicate, imported the missing FX).

Use the row buttons to move a finding between statuses. You can reopen any time you change your mind.

Explain with AI (optional)

When the admin enables the AI module for the Inspector, each row gets an Explain button. Clicking opens a contextual analysis by Olívia: what the check measures, why that specific row tripped it, and what the typical root cause looks like.

The explanation consumes monthly AI quota — same pool as the wallet + spending insights.

Exporting a run

Each run in the history has an Export link that downloads the full finding list for that run. Useful to archive before mass-resolving.

Best practices

• Run the Inspector right after each batch of imports — it catches corrupted OFX / wrong-encoding CSV / duplicate rows much earlier than the audit tab.
• "Acknowledge" is not the same as "Resolve". Use Acknowledge for known false positives (e.g. two legitimate entries with the same date and amount) and Resolve for actual fixes.
• The run history is your audit trail — don't delete it.

Open in the app