For small charities, mosques, churches and community groups

Books nobody has to take your word for.

Charity Ledger keeps two books, donations in and bills out, checks them against the bank every week, and keeps every correction on the record. A week's figures take five minutes on a phone. "Where did the money go?" takes one print.

No passwords. No spreadsheets. Nothing to install.

Why

Two questions every treasurer gets asked

Paper and a spreadsheet can answer the first on a good day. Neither can answer the second, and it is the second one that gets asked in the meeting that matters.

Where is the money?

The books say what the bank should hold, on any date. Once a week, somebody confirms that it does.

How do we know nobody changed it?

Because nobody can. Every figure ever entered stays on the record, and the database will not let the app rewrite one.

How a week works

A week in five minutes

The only routine the product asks for. It fits the evening the figures come in, and it fits on a phone.

  1. CountVolunteers count the collection and empty the boxes, as they do now. They never need a login.
  2. EnterDate, source, method, amount. The week's total updates as you type.
  3. Bank itOne line moves the cash from the tin to the bank. The tin's arithmetic is shown.
  4. CheckType the balance from your banking app. It matches, or you say why not.
  5. PrintA statement for any two dates, with your charity's name and number on it.
Corrections, never edits

There is no Edit button.

There is Correct, and there is Void, and both ask for a one-line reason.

  • The corrected line stays on every print, struck through, next to the line that replaced it.
  • The app itself has no permission to change or delete a book line. That is a rule in the database, proven by tests, not a promise in a manual.
  • So "how do we know you didn't change it later?" has an answer that does not depend on trusting anyone.
Cash is an account

Money is in the tin or in the bank. Never nowhere.

Cash counted on Friday sits in the tin until a banking line moves it. Bills paid from the tin come out of the tin.

  • Because every pound is in one place or the other, the books can say what the bank should hold on any date. That is arithmetic, not opinion.
  • Card and bank-transfer donations go straight to the bank, on their own date.
  • A bill is on the books from the day it arrives and in "still to pay" until it is paid. Money moves on the paid date.
The weekly bank check

The glance at the bank on your phone, written down.

The product shows what the bank should hold and asks what it does hold.

  • A difference cannot be saved without a reason.
  • A check is never edited. A wrong one is followed by a right one, and both are on the record.
  • Every check, with its tick or its named difference, prints on the statement for the period.
card takings not yet settledcheque not yet clearedcounted wrong, correctedbank charge, not yet entered
Prints the committee can read

One page for the meeting. A pack for the year end. A file for the accountant.

  • Statement between any two dates: money in by method, money out by method, opening and closing balances, the checks in between, "still to pay" as one line.
  • Ledgers by source, by payee and by method, with every correction shown.
  • Year-end pack: cover, statement and every ledger in one print, with page breaks where they belong.
  • CSV for each book, so the accountant works in their own tools and never needs a login.
  • Your registered name and charity number at the top of every page. It is your system, not a costume on someone else's.
No passwords, anywhere

Your face or fingerprint, on your own phone.

Nothing to remember, forget or steal.

Each device is named

A phone, a tablet, the office laptop. Each one can be removed on its own, without touching the others.

The treasurer adds people

No sign-up form, no "forgot password" email, and no way in that was not deliberately given.

Committee members see everything

They print anything and change nothing. Their sign-ins are on the record like everyone else's.

Your data

Your books, kept safe and kept yours.

One charity, one database. Nobody's books share a table with anyone else's.

Hosted in the UK, copied twice

Replicated to a second site within seconds, and backed up off-site every night with ninety days kept.

Restores are rehearsed

Before go-live and every year after. A backup nobody has restored is a hope, not a plan.

Bills stay on your server

Photographed bills are read on your own server. They are not sent to a cloud service unless your trustees choose that.

Never locked out. If a subscription ever lapses, the books go read-only with export. A charity's records are never held hostage.

What it deliberately is not

Two books, a bank check, a handful of prints. Everything else was left out on purpose.

  • Not double-entry bookkeepingNo nominal codes, no journals, no budgets.
  • Not fund accountingIf you must report restricted funds, you need an accountant's package, and we will tell you so.
  • Not a Gift Aid claimIt records what a claim would need, so nothing has to be backfilled later.
  • Not a bank feedThe check is you, once a week, and that is the point.

It speaks your words. Donation, source, payee, banking, bank check. Nothing on any screen was borrowed from a warehouse.

Who is behind it

Built and supported by Modcoms.

A small software company in Belfast, and part of the Fruitful family of products.

  • A person answers. The same people who built it set it up with you and enter the first month alongside you.
  • A flat annual subscription, invoiced, so a committee approves one known figure.
  • Your books are yours: printed statements, ledgers and CSV files at any time, including if you leave.
Ask for a walkthrough

See a week entered, live.

Twenty minutes on a call, with a pretend month. Bring the questions your committee asks.

Or email hello@modcoms.com. Forward it to your committee; it reads the same way to them.

If a subscription ever lapses, the books go read-only with export. A charity's records are never held hostage.