What was declared vs what is owed, spot the difference

A tax return says what a company declared; however, the documents filed show what is owed.

Reckon reads every one of those documents, works out the tax each line should have attracted, and shows the officer where the two disagree: the figure, the document it came from and the tax rule applied.

Request a demonstration Explore Reckon

Tax computation: what was filed and paid against what Reckon found, ₦11.9bn surfaced and ₦8.9bn raised as findings

Most of what is missed was never looked for

A liability rarely hides in one document. It shows where the general ledger, the bank statement and the return disagree, and those three are seldom put side by side. Reckon compares every line of every document, so a check that takes an officer a week happens in seconds.

Checks comparing each figure with a second, independent record: ledger against return, trial balance against financial statements

Start with what the taxpayer already filed

Returns, general ledgers, trial balances, financial statements, schedules and bank statements, in PDF, Excel or scanned form. Reckon reads them into one chart of accounts and maps every line to the tax areas it falls under.

Coverage map: 54 examination areas mapped to the tax heads that apply, from trial balance review to fee income

Every line, tested

For each line Reckon classifies what it is, computes what the applicable rule expects, and compares that with what was declared and what was remitted. A fee posted to the interest ledger is still a fee, and is tested as one. Differences above the materiality threshold for the industry become exceptions.

Exception: ₦4.2bn of fees booked to interest income should have carried VAT, with the lines and the rule behind it

Patterns across years, not just lines

Reckon keeps the taxpayer’s history as one profile. A series of short agreements that together make one long borrowing, or receipts that reconcile within a year but not across years, are tested as a matter of course.

Exception: a ₦45bn facility renewed back-to-back as 364-day agreements, read as one borrowing, stamp duty unpaid

The officer decides

Reckon raises exceptions; it does not raise findings. Every exception is reviewed by an officer, who raises a finding or dismisses it with a reason. The rules that produce exceptions are configuration the administration maintains itself, so two teams examining the same taxpayer reach the same result. AI is used to read scanned and unstructured input, and the exception says where.

Exceptions awaiting the officer: raise a finding, query the taxpayer or dismiss with a reason

A finding that survives objection

Each finding keeps the document version, the line, the rule version, the officer’s review and the supervisor’s approval. The same record is produced at reconciliation or before a tribunal, and stays with the case when officers move.

Finding F-01: ₦24.6bn of treasury bill interest wrongly treated as exempt, tied to the ledger line and the rule version

One engine, desk review, audit, investigation

Desk review runs on every filing as it arrives and clears or escalates it without an officer’s time. Audit takes selected cases through evidence requests, fieldwork and findings. Investigation works at transaction level for enforcement. The rules and the taxpayer record are shared; the workflow, people and depth are not.

Cases across desk review, audit and investigation on one engine, with rules, stage, officer and variance

Who it is for

Built for those with a mandate to collect

Revenue administrations and large-taxpayer offices, state internal revenue services, tax audit and investigation units, and the audit firms acting for them. Reckon reads from existing systems of record; write-back is approved by a person and logged.

Tell us which filings you review and what your audits need to establish. We will run Reckon on records you select, against criteria you set.

Request a demonstration