Documentation

VLDTION, in detail

VLDTION reads a ledger export you already produce, checks it against deterministic rules on your own machine, and shows the evidence behind every finding. These pages describe exactly what it does and where it stops.

What it is

A desktop application for accounting practices. You import an export, VLDTION normalises it into one internal model, runs a written rule set over it, and records what failed, with the records and the reasoning attached. Everything is stored on the machine it runs on.

Deterministic: the same file, rule set and configuration always produce the same findings and the same finding identifiers.
Evidenced: every finding names the rule and version that produced it, the attributes compared, and the source row and column behind each value.
Local: analysis, storage and export all happen in the application process. There is no account and no server component.

What it is not

VLDTION raises exceptions for professional review. It does not determine fraud, tax evasion or any other misconduct, it does not file anything, and it never writes to your accounting system. The export is read-only input.

Verified and development rules are not the same thing

Two rules in this build. The allocation-number regime and the standard VAT rate. Are marked verified: each was written against a dated document published by the Israel Tax Authority, and carries that source into the product and into every export. Every other rule is a development check: VLDTION’s own heuristic, useful for review and labelled as such wherever it appears. A development threshold is not a statement of Israeli law, and VLDTION does not guarantee compliance or claim any approval by the Tax Authority.

Where to go next

The desktop application

The product, the website, and where data goes

Getting started

Install, open, and run a first validation

How it works

The seven stages, end to end

Supported formats

Every export VLDTION reads, and what it does with it

Imports

Column mapping, rejected rows, partial data

BKMVDATA

Uniform file structure, read field by field

Findings

Severity, status, notes and suppression

Evidence

Provenance, fingerprints and exports

Bank reconciliation

Comparing a statement against the ledger

Foreign currency

The currency model, rate provenance and rounding

Rate register

Supplying published rates, with provenance

Subledgers

The ledger against the records behind it

Control accounts

A control balance against the records behind it

Working papers

The document that goes in the file

The rule contract

Result states, versions and configuration

Israeli rules

Allocation number, VAT rate, and their sources

Cross-period analysis

Materiality context and the forensic rules

Withholding tax

What is checked, and what is deliberately not

Clients and engagements

How work is organised, and how clients stay apart

Carrying forward

Starting the next period from the last one

Completion

When an engagement is finished, and who says so

Data handling

Where data lives and what leaves the machine

Keyboard

Every shortcut in the application

Troubleshooting

What to do when an import or a run refuses

Release notes

What each build changed

FAQ

Questions accountants ask first