AccoPro

A supplier invoice as a PDF, or a photograph of a receipt, read into a finished draft: the party, the dates, the line items and the totals.

A line it is sure of is filled in; a line it is not offers its best three guesses instead of a blank box or a quiet wrong answer.

Drop in the register and every row is classified — first by the rules you have taught it, then by AI, then by matching names.

Correct a classification once and it is remembered for next time.

Chassis numbers, purchase-order references, delivery terms — the things no field is built for go into the note, and never overwrite what you wrote.

Bring your own AI provider and key, kept encrypted for your company alone. Leave it blank and the AI features simply switch off.

Whatever the AI produces walks the same road as anything typed by hand: draft, checked, approved by a second person.

Debits and credits must match exactly, checked on the server every time you save — so it holds for spreadsheet imports too.

Draft → checked → approved, and the writer cannot approve. Working alone still lets you through, and marks the entry so you can see it later.

An approved entry is locked; a fix is a reversal. Every change is logged with who made it and when.

A draft cannot quietly change a balance sheet — which is why the statements agree with the ledger.

Group accounts as deep as you like; only the bottom level takes entries, so nobody posts to a heading by mistake.

What each party owes you and what you owe them, with a statement for any one of them and ageing by how overdue.

Quantity and value can never drift apart, because one posting carries both — including the freight and duty loaded onto the unit.

Suits stock worth naming one by one — vehicles, machinery, serial-numbered goods — as well as boxes on a shelf.

Tag the line and the tax is calculated at the rate that applied on that date, posted to its own account and frozen onto the line for later proof.

Laid out the way your board reads them — your headings, your order, your wording, with numbered notes underneath.

A trial balance that always adds up, because the balance check runs at the point of saving.

An entry across two branches balances on both sides by itself.

Opening balances carried in once, and a closed period will not accept new entries.

Cash, bank and wallet balances grouped so owners see their purchasing power without running a report.

Combined branch statements with intercompany elimination.

Build the statements the way your board reads them. If an account is not included anywhere, the software tells you — so nothing goes missing from a total.

Start from a ready-made chart of accounts or bring your own in from a spreadsheet.

Build the roles your company actually has, then give or take away a single permission for one person.

Pick your country and the right codes and rates are set up. Rates carry dates, so last year's entry uses last year's rate.

Spreadsheets in, checked row by row before anything is written; Excel, CSV and PDF out, on your own letterhead.

Source deductions, tax voucher splitting, and Mushak 6.3 and 9.1 returns in the official formats.

A locally hosted model parsing messy logs from third-party POS or e-commerce webhooks into clean vouchers.

When an outside platform changes its field properties, the data map is repaired rather than crashing.

Short, unreadable local bank statement strings normalised into clear ledger categories.

Lightweight vision processing pulling dates and totals off scanned paper cash memos straight into draft entries.