A non-profit cannot record “we spent $1,938 on rent”. It has to record which pot of money that rent came from — which grant, which contract, which programme, which office. Funders audit it. Get it wrong and the money goes back.
So the practices that keep those books spend days a month applying labels by hand. Agent501 is built for those practices: multi-tenant from the start, one trained model per client, and nothing about any one firm baked into it.
| Stage | What happens |
|---|---|
| Ingest | Bank downloads, card statements and payroll runs land in one workbook, one tab per account. |
| Code | Agent501 proposes a full coding for every row from precedent — and states what it matched on, how many times it has seen that pattern, and how consistent it was. |
| Gate | Quality checks run before anything leaves. A hard failure blocks the accounting export outright. |
| Review | A human corrects only what the agent flagged. It never guesses at a vendor it has not seen. |
| Learn | The correction is kept and reused. Next month it does not ask again. |
| Deliver | Fifteen files, including the import file the accounting system actually wants — balanced, truncated to spec, ready to post. |
| Area | Detail |
|---|---|
| Learning | A backoff rulebook over vendor / card / amount-band / memo tiers, retrained per client from its own approved corrections. One client's lesson never reaches another. |
| Explainability | Every suggestion carries its evidence. The reviewer asked for this directly: “it’s telling me there’s a problem; if I can’t see it, I don’t know what to fix.” |
| Safety | A corruption tripwire, invalid-GL and direction-flip checks, and a gate that blocks the export rather than posting something wrong. |
| Multi-tenant | One database and one trained model per client, provisioned by script. |
| Least privilege | Non-admins never see a filesystem path, an internal panel or a raw exception. Pinned by a test that walks the templates. |
| Delivery | Push to master; a timer on the server notices within 60s and redeploys. Measured push-to-live: about 45 seconds. |
| Question | Answer |
|---|---|
| Who is it for | Accounting practices doing the monthly close for non-profit clients — anywhere the coding is repetitive and the segments matter. |
| Multi-tenant | One database and one trained model per client, created by script. A lesson taught on one client never reaches another. |
| Accounting system | Writes the import file MIP Fund Accounting expects. The export layer is a module, so another ledger is a new writer rather than a rewrite. |
| Branding | Product name, tagline and firm name are environment settings. A practice puts its own name in the header without touching the source. |
| Deployment | One Ubuntu box behind nginx. Push to the branch and a timer redeploys within a minute. |
Nothing here is real. The organisation, its vendors, its funders and every person named are invented for this demo — the software is the real part.
Watch the 90-second walkthrough See the monthly flow Open the working screen