Flitz.ai
← All articles
4 min read

Bank Reconciliation and Swiss Compliance: Closing the Audit Trail Gap

Manual bank reconciliation isn't just slow — it's a compliance risk under the Code of Obligations. Here's what Swiss law expects and how automated matching keeps your books audit-ready.

Bank Reconciliation and Swiss Compliance: Closing the Audit Trail Gap

Every Swiss business owner knows the phrase "ordnungsmässige Buchführung" even if they've never read Article 957a of the Code of Obligations (OR) word for word. In plain terms: your bookkeeping must be complete, traceable, and verifiable at any time. That sounds reasonable in theory. In practice, the weakest link in most SMEs' books is not the invoice, not the expense receipt — it's the bank reconciliation step that happens weeks later, often under time pressure, often by hand.

What the law actually expects

Under the OR, every business transaction needs a documented, traceable path from the original document (invoice, receipt, contract) to the booking in your accounts and ultimately to the bank statement. This is the essence of the "Prüfspur" or audit trail. If a tax auditor or your fiduciary asks "show me that this invoice was actually paid, on this date, for this amount," you need to answer in minutes, not days.

Add MWST (VAT) obligations on top: the Federal Tax Administration expects your VAT return figures to tie back cleanly to actual cash flows. A mismatch between invoiced amounts, booked revenue, and bank inflows is exactly the kind of discrepancy that triggers follow-up questions during a VAT review. The Kontenrahmen KMU structure your accounts follow is only as reliable as the reconciliation behind it — a perfectly organized chart of accounts means little if the underlying bank data was matched manually and inconsistently.

Where manual reconciliation creates risk

Manually matching bank statements to open invoices is tedious and error-prone for reasons that have nothing to do with how careful your bookkeeper is:

  • Reference numbers get mistyped or truncated when copied between systems.
  • Partial payments and rounding differences require judgment calls that aren't always documented.
  • Multiple invoices paid in one transfer are hard to split correctly without a clear audit note.
  • Time pressure at month-end leads to "parking" unclear items in suspense accounts that never get cleaned up.

Each of these creates a small gap in your audit trail. Individually they seem minor. Collectively, they're exactly what an external auditor or tax authority flags first — because they suggest the reconciliation process itself isn't systematic.

How automated matching closes the gap

Flitz.ai's bank reconciliation module is built around the idea that reconciliation should be systematic by design, not by discipline. You can connect your bank account directly via the PostFinance Open Banking API, or import statements as CSV from any Swiss bank, including full support for the ISO 20022 (camt.053) standard that Swiss banks are standardizing around.

Once statement data is in, Flitz applies three matching strategies in sequence:

  1. QR reference matching — using the QR-bill reference number, the most precise identifier available on a Swiss payment.
  2. IBAN plus amount matching — for payments without a QR reference, matching the sender's account and the exact amount against open invoices.
  3. Fuzzy matching — for edge cases like partial payments, combined transfers, or slightly rounded amounts, using probabilistic matching to surface the most likely invoice candidates.

Transactions matched with 90%+ confidence are reconciled automatically. Everything else is flagged for a quick human check — so you're never relying on blind automation for ambiguous cases, but you're also not manually reviewing hundreds of straightforward payments every month.

Why this matters beyond saving time

The time savings are real, but the compliance angle is arguably more important. Every automated match is logged with the strategy used and the confidence score, creating exactly the kind of traceable documentation Article 957a asks for. When your fiduciary prepares your annual financial statements, or when you're asked to support a VAT filing, you can show — not just claim — that bank inflows map cleanly to invoiced revenue.

This also matters for data protection. Because reconciliation happens within a single Swiss-operated platform rather than being exported into spreadsheets, emailed between bookkeeper and owner, or copied into ad hoc tools, you reduce the number of places where sensitive financial and customer data sits unprotected — relevant both for DSG (Swiss data protection law) and, where applicable, GDPR.

Practical takeaway

Bank reconciliation is often treated as a back-office chore. Under Swiss compliance rules, it's actually one of the clearest tests of whether your bookkeeping holds up to scrutiny. Automating the matching — with QR references, IBAN and amount checks, and fuzzy logic for the messy cases — doesn't just save hours each month. It builds the audit trail your business needs to have ready before anyone asks for it.

An audit-ready business isn't one that reacts well to an audit. It's one where the audit trail was already there.

Stop Juggling Tools. Start Running Your Business.

Start your free account in 2 minutes. No credit card required.

Create Free Account