VedronERP · Financial Statements
Bank Transaction Matching
During M2 normalization, bank transactions are automatically matched to ERP orders and invoices. This gives each transaction an ordernr, invoicenr, and enrichment_status (matched, unmatched, or cancelled).
Matching Strategies (S1–S6)
- S1 — External reference: Matches when the bank description contains an order reference (e.g., Amazon order ID like 302-xxx-xxx).
- S2 — Invoice number: Matches when the description contains an invoice number (e.g., RE-153-2026).
- S3 — Customer name + amount: Matches by normalized company/person name and transaction amount.
- S4 — Amount + date window: Matches by transaction amount with a ±7 to +30 day date window.
- S5 — Wire transfer orderamount: For bank transfer orders, matches using a wider tolerance (max(€30, 2% of amount)) to cover flat bank fees.
- S6 — Überweisung invoice amount: For orders paid by bank transfer (Überweisung), matches using the invoice amount within ±€0.02 and a -7 to +90 day window — handles B2B customers whose legal form text blocks name matching.
Viewing & Correcting Matches
- Go to the M2 tab for a bank platform.
- Filter by enrichment_status = "unmatched" to see unresolved rows.
- Click a row to open the detail panel.
- Manually set the ordernr if you know which order this payment belongs to.
- Save — the row is re-enriched and flows through M3→M4→M5 automatically.
Tip: Run "Auto-Match" after uploading new bank data to let the system apply all six strategies. Unmatched rows that have no matching order will show "unmatched" — review these regularly to catch missing invoices.