Working with data
Control accounts
A control account is meant to be the summary of the detail behind it. Where it is not, the difference is a number, and a number on its own tells you nothing. This part of the product is about its composition.
The same engine
A control reconciliation compares ledger against ledger, where a bank reconciliation compares statement against ledger. The populations differ and the questions differ; the arithmetic does not. VLDTION runs both through one matching engine, so a control match is decided in the same passes, carries the same signals, and is as reproducible as a bank match.
What you configure
| Setting | What it is |
|---|---|
| Control accounts | The general-ledger codes that carry the control balance |
| Supporting accounts | The population that should explain it |
| Materiality | The difference at or below which the account is reported as reconciled |
| Date window | How far apart two records may be and still be the same event |
Nothing is recognised from an account name. No two charts of accounts in Israel number these the same way, and a product that guessed would be guessing about a figure somebody is going to sign.
What it will not do
Half a reconciliation is not a reconciliation
Nor does it decide which side is right. Every exception states what it does not prove, and “the control account is wrong” is never one of those things.
The rules
| Rule | What it reports |
|---|---|
| CTRL-001 | The control balance and the supporting total do not agree, beyond materiality |
| CTRL-002 | A supporting entry with no control-account posting |
| CTRL-003 | A control-account posting with nothing behind it |
| CTRL-004 | The two populations do not cover the same dates |
| CTRL-005 | A duplicated supporting entry |
Each is specified in the repository under docs/rules/control/ with its conditions, its evidence, its ordinary false positives and what it does not prove. A control account posted in monthly totals produces CTRL-002 for every invoice and is perfectly proper.
Assurance, stated exactly
Every control rule is development. The control objective. Testing a summary against its detail. Is ordinary professional practice. What no authority does is prescribe this comparison: this window, this reference length, these passes, this materiality. That is VLDTION’s own analytical procedure, and the rule says so rather than citing a standard that does not mandate it.
- Law is not regulation.
- Regulation is not an auditing standard.
- An auditing standard is not professional practice.
- Professional practice is not a VLDTION analytical procedure.
- The product never collapses those five into one another.
What reaches the working paper
- The control accounts and the supporting accounts, by code.
- Both balances, both counts, and the difference.
- The matched and unmatched counts on each side.
- Every exception with its evidence.
- The run identifier, the methodology version and the ledger fingerprint.