Working with data

Bank reconciliation

Two independent records of the same events, compared. Every match states the facts that produced it, every difference becomes an exception you can work through, and nothing is expressed as a confidence percentage.

What you need

01
A statement
The spreadsheet or delimited file your bank already produces. VLDTION recognises the columns by name, in Hebrew and English, and asks you to map anything it cannot.
02
A ledger
Any dataset already imported for the same client, CSV, Excel, a uniform file, or a Hashavshevet MOVEIN export.
03
The bank accounts
Which ledger accounts represent the bank. Only postings to those accounts are candidates; without them every posting is, and the run says so.

How a match is decided

Matching runs in passes, strongest first. A record matched in an earlier pass leaves the pool, so the result does not depend on the order the files were read in. The same two files always produce the same reconciliation.

Pass	Basis	What must hold
1	Amount and reference	Same amount, and a reference of at least four digits that appears in both records, including one found inside the bank narrative
2	Amount and date	Same amount, same date, exactly one candidate
3	Amount within the window	Same amount, within ±3 days by default, exactly one candidate
4	Several candidates	Reported as a possible match, never resolved automatically
n/a	Currency	Two amounts are compared only when the currency is known and either identical or reconciled through a rate in your own data. A converted match must also fall inside the date window.

No confidence percentage

A match carries the signals that supported it: “exact amount · reference 1842 in both records · same date”, or “exact amount · 2 days apart · one candidate in the window”. An accountant can check each of those. A number like “94% confident” cannot be checked at all, so VLDTION does not produce one.

The exceptions

Rule	What it reports
BANK-001	A bank movement with no ledger posting, with its share of period activity
BANK-002	A ledger posting to a bank account with no bank movement
BANK-003	Several ledger postings that could match one movement equally well
BANK-004	Bank movements sharing a date, an amount and a narrative
BANK-005	A running balance that does not follow from the previous row
BANK-006	A material difference between bank and ledger net movement for the period
BANK-007	A movement in a currency nothing in the data can reconcile

Each is specified in the repository under docs/rules/reconciliation/ with its conditions, its evidence and. As always. What it does not prove. A cheque presented late produces BANK-002 and is perfectly proper.

BANK-001, BANK-002 and BANK-006 are practice-backed: תקן ביקורת (ישראל) 500 holds that audit evidence is more reliable when it comes from a source independent of the entity, which is the objective these serve. The standard prescribes nothing about how the two records are compared, and the citation on each rule says so. The rest cite nothing, because nothing was found to cite.

Periods are checked before records

Comparable: the statement and the ledger cover the same dates.
Partial overlap. Only the overlap is reconciled, and the screen says so. Items outside it would look like exceptions when they are simply outside the file.
Mismatch. The two do not overlap at all, and nothing is reconciled.

Linking by hand

Where the engine refuses to choose, you choose. A manual link records who made it, when, why, and the automatic state it replaced. And it is stored against the pair of datasets rather than the run, so re-running the reconciliation re-applies your work instead of discarding it. The automatic result is never overwritten; it sits in the trail beside the link.

What reaches the working paper

The account, the period, and both source files.
The statement fingerprint and the ledger fingerprint.
The reconciliation run identifier, the matching methodology version and the currency methodology version.
Every conversion: the original amount, the rate, where the rate came from, and the difference that remained.
Matched, manually linked, possible, and unmatched counts on both sides, with amounts.
The difference for the period, and the balance-continuity result.
Every exception with its evidence, and the review trail.

What reconciliation is not

VLDTION does not connect to a bank, hold credentials, or move money. It reads a file you already have, on your machine. A reconciliation surfaces differences for professional review; it does not determine that anyone did anything wrong.