Outstanding to
Developments959,582.0573%
Property Owners104,540.858%
Water & Sewerage242,460.3019%
Aug 2026

Reconciliation

8 control checks · Last import 02/09/2026, 09:19

Tie

6

Attention

1

Not connected

1

Received

1,167,790.61

Unidentified

250,000.00

Every shilling accounted forReceived = allocated + credit balances + unidentified. Nothing else is possible.
1attention
Received (One Bill payments)1,167,790.61
Allocated to invoices917,790.61
Credit balances0.00
Unidentified250,000.00
Accounted for1,167,790.61
Held separately — not One Bill (2)1,501,240.00
Ties, but some money is still unidentified.
Bank closing balanceOpening + credits − debits must equal the balance the bank printed. Proves nothing was missed.
ties
One Bill Account · 31/07/20264,666,530.61ties
1 statement tie to the bank's own closing balance.
No receipt over-appliedAllocations against a receipt can never exceed the receipt.
ties
6 receipts checked, all within their own value.
Invoice balances derive correctlyBalances are never stored — every one is amount minus its allocations.
ties
16 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 behalf104,540.850% settled
Water & Sewerage — collected on their behalf216,466.150% 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 Account2,669,030.61clear
Water Collection Account (not the One Bill account)0.00clear
Electricity Collection Account (not the One Bill account)0.00clear
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
6 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 its XML/HTTP gateway. This is the check that catches the two systems quietly drifting apart — worth having even if vouchers are never posted automatically.

Ingest sources

SourceStatusLatencyProves completeness
Statement uploadactivemanualyes — carries closing balance
Scheduled pull (cron)not connected30 minyes — carries closing balance
Bank callback (webhook)not connectedreal timeno — notification only