Finance & Accounting 6 min 2026-11-21

Forensic reconciliation of Modelo 303/130 and BTW-aangifte filings against real invoices before January

Deterministic pre-accounting protocol to surface missing recurring bills, booking_date vs issue_date shifts, and unverified ISO 4217 FX rates before annual close.

Why four filed quarters rarely match the real annual archive

Across single-entity SMEs (1 Tax ID) and freelancers still gathering paperwork via email threads and spreadsheets, quarterly tax filings (Modelo 303 and Modelo 130 in Spain; BTW-aangifte in the Netherlands) close under intense deadline pressure. When January arrives and annual summaries (Modelo 390, Suppletie BTW, or year-end pre-accounting) must reconcile, the sum of four filed quarters routinely diverges from the actual PDFs on disk.

Rarely is this caused by advisor negligence; it stems from four upstream data fractures happening before the advisor ever sees the files.

Pre-Accounting Engineering Rule: A filed tax return PDF proves what number was typed into an official box—it never proves which valid supplier invoices were still sitting unread in an inbox on filing day.

Four discrepancy vectors caught deterministically before January

When you drop the year's real invoices alongside official bank files (ISO 20022 camt.053, Spanish Norma 43, or SWIFT MT940) and your filed Modelo 303/130 or BTW-aangifte receipts, the engine runs four deterministic audits aligned with our Engineering Standards Baseline:

  1. Missing monthly recurring invoices: If a telecom, utility, commercial lease, or cloud vendor shows 11 SEPA direct debits (ISO 13616) on the business bank statement while only 9 invoice PDFs exist in the archive, the engine pinpoints the exact 2 missing months so you request duplicates before closing the year.
  2. issue_date vs booking_date period shifts: An invoice dated June 29 (issue_date in Q2) that arrived by email on July 22 and was deducted in Q3 (booking_date) breaks naive date-range totals. Tracking both ISO 8601 timestamps lets the engine reconcile true accrual dates against the quarter in which input VAT was claimed.
  3. Unverified ISO 4217 foreign-currency bills: SaaS or foreign supplier invoices in USD or GBP keyed at an estimated exchange rate that disagrees with the settled EUR bank debit. Under zero-float BCMath rules, any foreign-currency document lacking a verified settlement rate stops in the exception inbox.
  4. Sign-flipped credit notes and subtle duplicates: Supplier credit notes (CEN EN 16931 code 381) printed with unsigned positive numbers that inflated expenses instead of reversing them.
[Real Invoice PDFs + CAMT.053/N43 Bank File + Filed 303/130/BTW]
                               │
                               ▼
          [BCMath Scale-4 Reconstruction (0 float)]
          • 12-month recurring vendor completeness radar
          • Dual timestamp tracking: issue_date vs booking_date
          • ISO 4217 FX lock against settled bank amount
                               │
                               ▼
       [Box-by-Box Discrepancy Report · Exception Inbox]
                               │
                               ▼
       [SHA-256 Sealed Handover to Your Advisor / Sage]

Keep your current advisor—with crystal-clear legal boundaries

Across both SME Pre-Accounting & Advisor Bridge (49 € and 99 €/mo) and Freelancers & Mixed Income, our role is unambiguous: Sunnyface is never a licensed tax advisory firm and never signs official tax filings on behalf of clients.

We act as your upstream administrative and pre-accounting firewall. Your current accountant keeps working in Sage, A3, SnelStart, or Exact Online, receiving a cent-accurate discrepancy breakdown backed field by field with SHA-256 sealed visual traceability and a 1-click audit ZIP.

Associated production module

Deploy this workflow to production without building from scratch

Our plug-and-play modules and tailored workflows embed these battle-tested rules, ready to connect directly into Sage or your enterprise ERP.