Publishing scope: This article is not a formal accounting, tax or audit opinion. It explains IconVio's pre-decision-package data-control approach.
File structure is read first
If a trial balance or subledger file is going to be taken as a source before reporting, the date, voucher/document number, account code, debit, credit, balance and counterparty fields need to be distinguishable. Column names may differ; the critical point is matching the fields deterministically.
Chart-of-accounts class and the equation
The first digit of the account code forms the backbone of the decision package in asset/liability and income/expense readings. Unclassifiable accounts are not silently treated as clean — they remain flagged in the report.
VAT and bank trace
Input/output VAT, withholding VAT and bank movement can affect the report's conclusion. These fields must be labeled with a matching and confidence signal before entering the decision package.
Where does this connect inside IconVio?
This article supports the Accounting Manager solution page and the IV-FINANCE system page.