Clients’ books, kept where the statements are built
A client’s books live in the client’s own Achekam books, and the firm works in them through its appointment. Bank statements arrive in whatever layout the bank produced, lines are coded by rules, by history or by an AI suggestion a person accepts, and the books flow straight into the statements.
Who uses it
- Bookkeeper
- Accountant
- Partner
- Business owner
What it does
- Bank statements as digital PDFs, scans, photos, spreadsheets or bank exports (CSV, OFX, QIF, MT940, CAMT.053), with the running balance checked as they are read.
- Bank rules by amount range, account and direction, learned rules, split lines and transfers between the client’s own accounts.
- “Suggest with AI” for what rules and history did not code: checked against the chart, and nothing posts until a person accepts it.
- Settling many invoices or bills from one bank line; reconciliation; multi-currency accounts with exchange differences.
- Guided workflows for monthly bookkeeping, management accounts, VAT returns and year-end close, each step checked against the books.
- Outsourced finance-office and fractional CFO desks for the clients the firm runs.
How it works
- The client appoints the firm; the firm’s access follows that appointment.
- Upload or import the bank statements; each is read and checked.
- Code the lines: rules first, history next, AI only for what is left — accepted by a person.
- Reconcile, close the period, and the statements are built from the books.
The controls that protect it
- The firm reaches only the books it is appointed to, and only as the appointment allows.
- AI on bank lines can be switched off per set of books; control and bank accounts are never suggested.
- Before a line is sent to AI it is reduced to its date, description, amount and direction, with numbers and recognised names masked.
What it does not do (yet)
- Bank feeds are in beta; statements can always be uploaded.
