Reconciliation
8 control checks · No statement imported
Tie
6
Attention
1
Not connected
1
Received
0.00
Unidentified
0.00
Every shilling accounted forReceived = allocated + credit balances + unidentified. Nothing else is possible.
ties
| Received (One Bill payments) | 0.00 | |
| Allocated to invoices | 0.00 | |
| Credit balances | 0.00 | |
| Unidentified | 0.00 | |
| Accounted for | 0.00 | |
| Held separately — not One Bill (0) | 0.00 |
Ties exactly. No unidentified money.
Bank closing balanceOpening + credits − debits must equal the balance the bank printed. Proves nothing was missed.
attention
No statement imported yet — import one to prove completeness.
No receipt over-appliedAllocations against a receipt can never exceed the receipt.
ties
0 receipts checked, all within their own value.
Invoice balances derive correctlyBalances are never stored — every one is amount minus its allocations.
ties
40 invoices checked. No invoice over-paid, every status consistent.
Intercompany positions net to zero"Due to X" in Developments must equal "Due from Developments" in X, every month.
ties
| Property Owners — collected on their behalf | 0.00 | 0% settled |
| Water & Sewerage — collected on their behalf | 0.00 | 0% settled |
Both sides are generated from the same allocation lines, so they cannot diverge inside this system.
Cash sitting in the right accountCustomer money that landed outside the One Bill Account. Already allocated — only the cash needs moving.
ties
| One Bill Account | 0.00 | clear |
| Main Account (not the One Bill account) | 0.00 | clear |
| Property Owners Account (not the One Bill account) | 0.00 | clear |
| Water & Sewerage Account (not the One Bill account) | 0.00 | clear |
All customer receipts are in, or have been swept to, the One Bill Account.
No double-countingEvery statement line carries an idempotency key, so a re-import or a repeated webhook cannot credit a customer twice.
ties
0 keyed receipts, no duplicates. 0 line(s) skipped on import as already seen.
Agreement with TallyReceivables per customer per company, compared against Tally. Catches a journal keyed directly into Tally.
not connected
Needs read-only access to Tally over ODBC or XML. This is the check that catches the two systems quietly drifting apart — worth having even if vouchers are never posted automatically.
Ingest sources
| Source | Status | Latency | Proves completeness |
|---|---|---|---|
| Statement upload | active | manual | yes — carries closing balance |
| Scheduled pull (cron) | not connected | 30 min | yes — carries closing balance |
| Bank callback (webhook) | not connected | real time | no — notification only |