FAQ

Questions accountants ask first

Short answers, with the detail in the pages behind them.

Questions

Does VLDTION change my books?: No. The export is read-only input. VLDTION stores its own normalised copy and never writes back to the accounting system.
Does my client data leave the machine?: No. Import, validation, storage and export all happen in the application process. The application makes no network requests.
Is there an AI model involved?: No. Every finding comes from a written rule with a version, and column mapping suggestions come from a fixed dictionary of header names. Nothing is inferred by a model.
Will the same file always give the same answer?: Yes. Given the same dataset, rule versions and configuration, VLDTION produces the same findings and the same finding identifiers. That is what makes an evidence export checkable.
What happens to my notes if I re-import the same period?: They are carried forward. Review state is keyed by the finding's content-addressed id, so a finding that still exists after a re-import keeps its status, note and suppression.
Do the thresholds reflect Israeli law?: Two rules do, and say so: the allocation-number regime and the standard VAT rate were written against dated documents published by the Israel Tax Authority, and each carries its source into the product and into every export. Every other rule is a development check: VLDTION's own heuristic, labelled as one wherever it appears, and not a statement of statutory requirements. VLDTION does not guarantee compliance and is not approved by the Tax Authority.
Which accounting systems are supported?: Any system that exports CSV or Excel, which in practice is all of them; the Israeli uniform file structure (BKMVDATA), read field by field against the Tax Authority specification; and the Hashavshevet MOVEIN interface, read against the MOVEIN.PRM that accompanies it. Priority has no public export specification, so Priority data comes in through the uniform file it is required to produce, or through Excel with a column mapping.
How large a ledger can it handle?: The importer reads up to 250,000 rows per file, and the benchmark harness exercises the whole pipeline at 100,000 records and beyond. Filtering, sorting and paging happen in the database, and the table is virtualised, so the number of rows rendered depends on the size of the window rather than the size of the ledger.
Can VLDTION reconcile the bank?: Yes, against a statement you export from your bank yourself. It matches on amount and reference, then amount and date, then amount within a date window, and it reports rather than resolves a movement that two postings could match equally well. It never connects to a bank and never holds credentials.
Does it work across several clients?: Yes, locally. Everything belongs to a client and an engagement, queries are scoped to one client, and a single-client export contains that client and nothing of any other. There is no cloud, no account and no sync.
Is VLDTION a website or a program?: A program. You download it and install it on the accountant's own machine, and it keeps everything in a database file on that computer. This website exists to explain it, document it and distribute it. It never receives an accounting file, and it contains no browser version of the application. What you see here are bounded previews of its screens, drawn from synthetic fixtures and labelled as such.
Does it need an internet connection?: No. Import, validate, reconcile, investigate, document, back up and restore all work with the machine disconnected. That is not a claim: the entire test suite was run inside a network namespace with no interface, no route and no DNS, and the installed application was launched the same way.
Where do exchange rates come from?: From your own records, or from a published table you import yourself. VLDTION never fetches a rate. When you import a table it records who published it, what the publication is, the dates, which way round the rates read and a fingerprint of the file, and every converted match names the rate it used and where it came from. A date the table does not cover is reported as insufficient data rather than filled in from a nearby day.
What about payments in dollars or euros?: They are reconciled properly. Every amount carries its currency, comparisons run in integer minor units, and a cross-currency pair is matched only through a rate your own files carry, from the statement, from the ledger posting, or one you enter yourself. The match shows the rate, where it came from and the arithmetic. VLDTION does not fetch exchange rates: a pair with no rate anywhere is reported, not guessed at.
Can it reconcile a control account?: Yes, debtors, creditors, VAT control, or any pair of account sets you name. It runs on the same matching engine as the bank reconciliation and reports the composition of the difference rather than only the difference. If one side of the comparison is not in the data, it says insufficient data rather than reporting agreement.
Do I have to set the next quarter up from scratch?: No. Carrying an engagement forward brings the bank account scope, the column mappings, the rule configuration, the control-account scopes, the reviewer and the counterparties you already know. It brings no transactions, no findings and no runs. And a finding you dismissed last quarter arrives as an explanation beside the new one, not as a decision already made. You see both lists before anything is created.
Does a finding mean fraud?: No. VLDTION raises exceptions for professional review. It does not determine fraud, tax evasion or any other misconduct, and its output should not be presented as if it did.