Loading
Because the ledger is organised by account and the funder asks by fund. The join is done manually at deadline, against a coding decision somebody made months earlier and did not write down.
The result is defensible but slow, and confidence in it depends heavily on one person's memory.
Cost centres carry the fund, so every transaction is coded to it at the point it is entered rather than allocated afterwards. Budgets sit against each fund, so spend against budget is current.
Staff time allocated in Loop carries cost from Nest's personnel records, so payroll apportionment reconciles with the ledger rather than approximating it.
It does not manage donors, run appeals or handle gift aid claims — those belong to a fundraising system, and Books records what arrives from it.
And it will not decide your fund accounting policy. It applies the coding structure you define, consistently.
A funder report is a query with a date range and a fund, drawn from transactions already coded. Restricted balances are visible during the year rather than at the end of it.
Every change keeps its previous value with an actor and a date, which is what an audit actually asks for.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, through cost centres coded at entry rather than allocated later.
Yes, through Loop, carrying cost rates from Nest.
No. It is the ledger beside one.
Half an hour on your own numbers is usually enough to say whether Books is the right place to start.