# Bank statement setup sheet · one per client

Fill this once per client. It becomes the folder, the format map and the first run.

| Field | Your entry |
|---|---|
| Client name and code | e.g. Shree Packaging Pvt Ltd · SPPL |
| Banks and account types | e.g. Demo Bank CA ·· 4471; Demo Bank OD ·· 9001 |
| Statement source | CSV export / text PDF / scanned PDF / Excel |
| Statement period | Monthly on the 1st / fortnightly / weekly |
| Who sends it | Client accountant on WhatsApp / bank email / portal download |
| Books | Tally Prime ledger export (Excel) / ERPNext / other |
| Review owner at the firm | Name, WhatsApp number |
| Client contact for questions | Name, WhatsApp number, language |
| Cash deposit review threshold | e.g. ₹2,00,000 |
| AI confidence threshold for auto | e.g. 0.90 |

## Folder layout

```
clients/
  SPPL/
    bank/
      demo-bank-4471/
        2026-08.csv            ← statement as received (never edited)
        2026-08.categorised.csv
        2026-08.exceptions.csv
        2026-08.brs.csv
    setup/
      bank-format-map.csv
      category-rules.csv
      masters.csv
    reports/
      2026-08-summary.md
```

## Naming rule

`<yyyy>-<mm>.<ext>` for the statement, same stem for every output. The original file is never edited; every output names the line it came from.

## First-run checklist

- [ ] Format map tested on one statement: dates parse, debit and credit never both filled, running balance matches every line
- [ ] Masters loaded from the Tally ledger export
- [ ] Rules file copied from the kit and edited for this client
- [ ] Review owner named; approval step switched on before any Tally import
- [ ] Client contact confirmed on WhatsApp and told what questions will arrive