Local-first accounting validation · Built for Israeli practice
Validation, with the vowels removed
VLDTION is a desktop application you install. It reads the exports your accounting system already produces, checks them against deterministic validation and forensic rules, and shows the evidence behind every finding. Your accounting data stays on your computer: there is no workspace to log into, nothing to upload, and no model deciding what matters.
Each one names the rule, the records and the attribute that differed
The errors that matter are not the ones that break the balance. They are the ones that survive it.
Twice
A supplier sends a copy, a colleague keys it again two days later, and the input VAT is claimed on both. Nothing in the trial balance objects.
₪1
A rounding difference and a genuine keying error look identical in a report. Only arithmetic over every line separates them.
21:47
A material manual journal on the last day of the quarter is not evidence of anything. It is evidence that somebody should look.
A quarter of a mid-sized client can carry thousands of lines. Reviewing all of them by hand is not a discipline problem; it is an arithmetic one. VLDTION does the arithmetic and hands back the exceptions, with the reasoning attached.
The application
This is the desktop application, drawn from synthetic data. Move through its surfaces: each one is a different answer to the same question. What is wrong here, and how would you show somebody that you are right?
Synthetic data
Two postings carry invoice 4471-B for the same supplier and the same amount, eleven days apart. The allocation numbers differ; nothing else does.
Attributes compared · 7
Chain of custody
Exceptions worth a reviewer's attention, ranked by severity and named by the rule that raised them.
How VLDTION works
An export goes in, field mappings normalise it, rules run in a fixed order, and a bank statement is matched against the result. Every stage is deterministic and every stage happens on the accountant’s own machine.
Import
Records read from the export you already produce
Normalise
13
Source fields mapped to one internal model
Validate
21
Deterministic rules, evaluated in order
Reconcile
7
Bank statement matched against the ledger, differences raised
Analyse
Findings raised with full provenance
Evidence
Individual observations recorded and exportable
Carry forward
1
Configuration and explanations to the next period; no findings
Evidence
One finding, attribute by attribute
Two supplier invoices. Five attributes identical, one absent, one different, which is the finding, stated as a comparison rather than as a score.
What a re-run would have to match
Give VLDTION the same file and the same rule version and it reaches the same finding, with the same identifiers. That is the difference between a result a reviewer can check and one they have to take on trust.
Nothing here is a score · every figure is a fact about the records
Bank reconciliation
Matched
The facts agree, and the match records which
Manual
A person matched it, and is named
Possible
More than one candidate; reported, not guessed
Unmatched
One record has no counterpart
Insufficient
No rate, no data, so no claim
The same engine reconciles a control account against the records behind it. CTRL-001 to CTRL-005 above, because the populations differ and the arithmetic does not. An account the data cannot support returns insufficient data rather than agreement.
A match carries the facts that produced it. Exact amount, reference in both records, two days apart, one candidate in the window. And never a confidence percentage, because a percentage cannot be checked. Every exception states what it does not prove. How reconciliation works.
Give it the export you already produce
Nobody should rebuild their bookkeeping around a review tool. VLDTION sits above the accounting system: you export what you already export, and it reads it, including the uniform file structure every registered Israeli system is required to produce.
BKMVDATA, uniform file structure
SupportedRecords classified, structure validated against the file, and fields read at the positions specification 1.31 declares.
Hashavshevet, MOVEIN interface
SupportedFixed-width journal transactions read at the positions the accompanying MOVEIN.PRM declares, including the allocation-number field.
Delimited text (CSV, TSV)
SupportedAny delimited export, with columns mapped once from a dictionary of English and Hebrew header names.
Excel workbook (XLSX)
SupportedWorkbook values as the spreadsheet stored them. Formulas are never evaluated.
Bank statement (CSV, XLSX)
SupportedThe export your bank already produces, with columns recognised by name in Hebrew and English, including a currency column and a rate column where the statement carries them. Bank-specific fixed-width interchange files are not implemented: no bank publishes their record layout.
Priority. Native export
Not supported nativelyPriority exports are user-configurable form exports, and no public specification defines their columns. Priority data reaches VLDTION through the uniform file structure that every registered Israeli accounting system must produce, or through Excel with a column mapping.
Every row above is generated from the adapters in this build, and each states what it does not do as plainly as what it does. Supported formats, in detail.
Built for Israeli practice
VLDTION is shaped around the documents Israeli practices work with: allocation numbers, VAT arithmetic per document, invoice series integrity, and the uniform export formats. Shipped areas are marked; the rest are on the roadmap and are not claimed as working.
VAT
Arithmetic and rate consistency per document
5 rules shipped
Allocation numbers
Presence and format on qualifying invoices
3 rules shipped
Invoice integrity
Series continuity and credit note sourcing
2 rules shipped
Duplication
Repeated documents and repeated postings
2 rules shipped
Journal integrity
Materiality, timing and dormant accounts
5 rules shipped
Period controls
Cut-off, backdating and negative expense
2 rules shipped
Counterparty identity
Duplicate and conflicting master records
2 rules shipped
Reconciliation
Bank statement against ledger, in one currency or across two: unmatched both ways, ambiguity, balance continuity
7 exception rules shipped
Cross-period
New counterparties, dormant accounts, repeated adjustments
2 rules shipped
Withholding
The statutory rates, and a deduction recorded where the specification does not permit one
2 rules, both verified
Control accounts
A control balance against the records that support it, and the composition of the difference
6 exception rules shipped
VLDTION is a review tool, not a statement of statutory requirements. It does not guarantee compliance and is not approved or endorsed by the Israel Tax Authority. Every threshold it applies is shown on the finding it produced, so it can be judged by the professional using it.
Local-first architecture
Accountants hold other people's financial records. That is the constraint the product is designed around, not a feature added to it. VLDTION is built to do its work inside the application process, on the machine holding the export.
Accounting data
The export already on your machine
VLDTION
Normalisation and deterministic rules
Local analysis
Evaluated in the application process
Findings
Evidence you can read, keep and export
No cloud processing
Analysis runs where the data already is
No external model
Rules are written, versioned and inspectable
No data upload
The product has no reason to transmit ledger data
No writes to the books
Source records are read, never modified
The engine is complete and tested: imports, validation, reconciliation, evidence, working papers, backup and restore all work, and the whole suite runs with no network namespace at all. What is not finished is distribution. Only Linux has been built, and nothing is signed, which the download page states per platform.
The rule engine
RULE-001
Two or more purchase documents share the same supplier, document number and net amount. A duplicated purchase invoice overstates expense and over-claims input VAT.
Development rule, VLDTION's own analytical procedure, not a statement of Israeli law.
Match conditions
RULE-004
The VAT recorded on a document does not equal the net amount multiplied by the declared VAT rate, beyond the configured rounding tolerance.
Development rule, VLDTION's own analytical procedure, not a statement of Israeli law.
Match conditions
RULE-012
A supplier invoice above the configured threshold carries no allocation number in the export. The threshold is configuration, not a legal determination.
Development rule, VLDTION's own analytical procedure, not a statement of Israeli law.
Match conditions
The contract every rule implements
interface RuleDefinition {
id: string
name: string
category: RuleCategory
severity: Severity
version: string
conditions: readonly string[]
evaluate(ctx: RuleContext): readonly FindingDraft[]
}Rules are pure functions over a fixed context. No clock, no network, no hidden state, so a run can be reproduced exactly, which is what makes a finding auditable.
Rules in this build
Finishing the work
Every requirement is a question about what the engagement holds, answered from stored state. Anything required and unmet blocks completion until it is done, or until a named person records why it does not apply, which is written into the review trail rather than making the warning disappear.
Derived, not declared
Every requirement is a question about stored state. Is there a ledger, did a run happen, is anything still open, answered by reading the engagement rather than by asking the accountant.
An override is not a tick
A requirement that does not apply is overridden by a named person with a written reason, and stays visible as overridden. It never becomes met.
No progress percentage
A number would average a missing bank reconciliation together with a reviewer's name. Completion is a state with a list behind it, not a score.
A desktop application
Windows
Built · unsignedmacOS
Not testedNever compiled, so it is not offered.
Linux
Built · unsignedNothing is signed yet, so nothing is published for download. The download page lists exactly what was built, for which platform, with its SHA-256, and says plainly where a platform has nothing. The screens shown on this website are bounded previews drawn from synthetic data: this site has no version of VLDTION you can run in a browser, accepts no accounting files, and holds no accounting database.
Product philosophy
01
The same export, the same rule set, the same answer. A finding that cannot be reproduced cannot be defended.
02
The product never asks to be trusted. It shows the records it compared and the attribute that failed.
03
VLDTION raises exceptions and ranks them. It does not close them, and it does not touch the books.
VLDTION is a desktop application. This website documents it, shows what its screens look like and hands you the installer; it holds no accounting data, processes none, and has no version of the product you can run in a browser. The application on your machine is the only thing that reads a ledger.