BankGuard
Checks 1C and client-bank exchange files before import: a truncated statement, a repeated document, totals that don’t add up. The source file is never changed.
A statement inspection bench
Statement sheets pass under a probe and are only read. A counter reconciles the balance: opening plus receipts minus payments must equal closing, and a repeated document raises a flag.
Why
If a statement is truncated, repeats a document or its totals don’t match the payments, the error lands in the books. BankGuard reads the file, reports an error code and the line, and fixes nothing itself. It needs no access to the bank or the 1C database.
What it checks
Section structure and file closing, format version and encoding, 20-digit accounts, dates and amounts, and repeated documents by account, type, date and number. Above all: the opening balance plus receipts minus payments must equal the closing balance.
Under the hood
- Formats 1.01, 1.02 and 1.03.
- A repeat across files is a warning, within a file an error.
- A mode for outgoing orders with no posting date yet.
- JSON output for automation.