# Bookkeeper · Day 14 — Two-minute trick: the gate report

**Subject:** Two-minute trick: the gate report
**Send:** Day 14
**Goal:** surface the gate tool — non-obvious, high-value once seen

---

Hi {{first_name}},

The tool inside DataTools that buyers find last is the **gate** — and it's the one that quietly does the most for you.

What it does: before any row gets written to the cleaned CSV, the gate runs a per-row pass-through check. Rows that fail get *quarantined* into a separate file (`<filename>.quarantine.csv`) instead of silently dropped or silently passed.

Default rules (you can add your own):

- Missing required fields (date, amount)
- Amount in unexpected currency without a flag
- Date outside the export's stated range (catches the "totals row" issue from Day 1)
- Duplicate of another row already in the file (per the dedupe pass)
- Confidence below your threshold on a field that got auto-corrected

The 2-minute workflow:

1. Run the pipeline as usual.
2. Open `<filename>.quarantine.csv`. (It'll be tiny — typically 0-5% of rows.)
3. Eyeball it. Anything that's a real transaction, fix-and-re-include manually. Anything that's a totals row / blank row / corrupt row — confirm it's correctly quarantined and delete it.
4. Re-run the pipeline on the fixed-up version (or just append the manually-fixed rows to the cleaned CSV).

The reason this matters: silent drops are the worst possible failure mode for a bookkeeper. You'd rather a row come out wrong (you'll catch it on review) than disappear (you won't catch it for months). The gate makes the silent-drop case impossible.

Set the gate's confidence threshold to `0.85` for client work. Lower (0.75) for personal / exploratory; higher (0.92+) only if you've spent time tuning your client's preset.

— Michael
{{support_email}}