Financial statements built from the books — and able to prove every figure
The statements are built from the trial balance or straight from the client’s books in Achekam. The client reviews them in their portal, the directors sign, and the issued version is locked with a seal over the trail behind every figure.
Who uses it
- Accountant
- Manager
- Partner
- Client director
What it does
- Trial balances imported from files or read from the client’s books, mapped by type with last year’s mapping remembered.
- Statements and notes under IFRS and IFRS for SMEs, with the public interest score worked out from the client’s figures.
- A live link to the client’s books: journals posted after the statements were built are named, and never mixed into the issued figures.
- Client review of the draft and director sign-off; signing again after a change; outside accounting officers sign off where the entity has one.
- Proof of Figure: any figure opens its trail, and the issued version carries one seal that can be checked against the books later.
- iXBRL prepared from the issued statements for the CIPC submission.
How it works
- Bring in the trial balance or link the client’s books.
- Map the accounts; AI may propose a mapping, and a named person accepts it.
- Build and review the statements and notes; the client reviews in the portal.
- Sign and issue: the version is locked and sealed; prepare the iXBRL.
The controls that protect it
- An issued version is locked; a change makes a new version that is signed again.
- An AI-proposed mapping counts only once a named person accepts it, and the trail says who.
- A check that cannot run says “not checked” with its reason — never “passed”.
What it does not do (yet)
- Achekam prepares the iXBRL; the submission to CIPC is made by the firm.
- The notes’ own account tables are not yet traced by Proof of Figure; the trail starts from the statements’ tables.
