A month of a client’s paper, read once and proposed as journal entries.
An accounting firm’s work is a pile of scans and somebody typing them into a ledger. Zala reads the scans — Arabic and English, vouchers, invoices, e-invoices and sheets of small receipts — and proposes the entry against that client’s own chart of accounts. A person still approves every one. That is the point.
Not a reader. A bookkeeper’s first draft.
Reading a page is the easy half. The work is turning a stapled envelope of paper into one entry that looks like the way that client’s books are actually kept, and refusing when it cannot.
Reads the paper you already have
Payment vouchers, supplier invoices, e-invoices and sheets of small receipts, in Arabic and English, from a scanner or a phone. No new forms for anyone to fill in.
One envelope, one entry
A voucher with its invoices stapled behind it — each invoice often twice, the supplier’s copy and the e-invoice — is joined back into a single entry. Duplicates are marked, never deleted.
Entries in the client’s own accounts
Journal lines are proposed against that client’s real chart of accounts. An account their books do not hold cannot be proposed, and the reviewer still has the whole chart.
It follows how that client posts
How this client posted this supplier last time is read out of their own past vouchers, so the proposal looks like their bookkeeping and not like a template.
A review screen built for a pile
One row per page, saying what is on it before anybody opens it. Open one and the scan sits beside its figures, so a number is checked against the paper, not retyped from it.
Back into the books
Approved entries go into the accounting system the firm already uses, or out as a file their accountant imports. Nothing is ever written to the file the books are read from.
What a reviewer is looking at.
Illustrative screens with invented companies, invented account numbers and invented figures.
A month’s uploads, and what is in each
One envelope, proposed as one entry
A figure the page contradicts is not a reading
A wrong number is worse than a missing one.
A blank gets filled in by somebody. A plausible wrong figure is read, believed, posted, and found a year later by an auditor. Most of this work is the checks that stand between the two.
An unbalanced entry is shown as unbalanced rather than quietly adjusted to fit.
And the implied rate is one the tax authority actually uses. A total with no tax stated is split, and the split is labelled wherever it appears.
A plausible account number that is not in the client’s chart is the easiest mistake to miss, and an accounting system will take it without complaining.
Their name is on every page they scan, so it is the name a reader reaches for first. A name that is theirs is replaced or emptied.
Thermal receipts print the amount twice. When the two readings disagree, the figure is dropped and the slip joins the ones a person has to look at — with the reason, and with no number invented in its place.
The reader lists the slips; the arithmetic is done by the program. A model asked to sum a page of numbers will usually get it right, and usually is not a standard for someone’s books.
When the slips read come to more than the voucher, the entry is refused outright and the reviewer is sent to the original.
Checked by invoice number — scoped to that counterparty, because parallel series repeat numbers — and by amount, for the entries whose description carries no number.
A batch holding both a purchase and a sale is not one entry. It names the pages that disagree instead of picking a side.
Everyone sees only what is theirs.
A firm holds several clients’ books at once, and a permission is a named thing a person has, never a rank that happens to include it.
- Drop a scan in, read it, correct it, approve it
- The scan beside the figures, at a readable size
- Search every document by supplier, number, amount or account
- Accounts offered are the ones this client actually uses
- A queue of only what needs a person
- Every field graded, and a blank said to be blank
- Each proposed line traces back to the page it came from
- Nothing reaches the books without an approval
- How much paper each client sends, and how far it has got
- What a document costs to read, recorded per document
- Named permissions per person, not a ranked admin
- An activity log of who approved and who posted what
- Their books stay in their own system
- Their voucher numbers stay in their own series
- They scan the way they already scan
- Nothing is posted that somebody at the firm did not approve
Somebody else’s books set the rules.
Only the page image leaves the office, to a reader that keeps nothing and trains on nothing. Everything read stays on the firm’s own machine.
The books are opened read-only. Anything written goes to a separate file, and reading and writing the same file is refused outright.
A voucher writes whole or not at all. A half-written entry balances to nothing and tells nobody.
Every write is logged with exactly what it wrote, so it can be found and taken back out again.
A blank is better than a guess. A field that could not be read comes back empty with a note, because somebody fills a blank in and nobody checks a confident wrong number.
What each document cost to read is recorded from the providers’ own reported usage, so the monthly bill is a measured figure rather than an estimate.
It works with the system you keep the books in.
Desktop accounting files, a shared database or an API. The chart of accounts, the clients and the posted history are read from where they live, so nothing is typed into a second system.
Where an invoice carries a signed code from the tax authority, that code is the best evidence on the page — its dates and amounts are checked against what was read, not re-read.
A spreadsheet or import file in the shape the books expect, for a firm that would rather post the batch itself than let anything write to their file.
A tool on a computer in the office, not a service on the internet: no database to host, no account to sign into, and client documents that never sit on somebody else’s disk.
Send us a month of real paper.
Not a demo file — the envelopes as your clients actually send them, handwriting and all. We read them against your own chart of accounts and show you what came back, including what it could not read. That is the only honest way to find out whether this is worth building for your firm.