Manual cross-check ERP vs banking tool
Master data in the ERP, IBAN in the banking tool — every change requires tab-switch and visual comparison.
Case study · Accounting
Invoice verification in under 30 seconds.
Mid-market accounting verifies inbound invoices with SigID — IBAN against supplier account, signer authorization, audit evidence for the year-end audit.
Pilot pattern · Four-eyes principle · Audit-ID per transaction
Compliance & hosting
Starting point
Manual IBAN verification eats 8–12 minutes per transaction.
Before SigID, the accounting team verified every invoice above 5,000 EUR manually across two systems. Error-prone, slow, no cryptographic proof.
High error rate on IBAN changes
On average two wrong payouts per year due to CEO-fraud emails with forged bank details.
No audit trail for the year-end audit
ERP logs show click history, not whether the IBAN was actually verified — IBAN findings every year.
How SigID helps
Four steps — Audit-ID at the end of every transaction.
Accounting stays in the familiar ERP, the verification runs cryptographically in the Trust Layer.
Import invoice
Via ERP connector, mailbox or upload. SigID extracts supplier, amount and IBAN automatically.
Check IBAN against membership
Is the IBAN linked to the supplier? If not, a challenge starts in the Trust App.
Four-eyes signature via passkey
Two authorized people sign in the Trust App — with dynamic linking on amount and IBAN.
Audit-ID back to the ERP
The approval lands as Audit-ID in the ERP — re-verifiable by external auditors.
Outcome
Median 28 seconds, zero IBAN findings.
Pilot pattern from the accounting program. All values are architecture targets for the GA phase, not representative customer data.
- Median time per check
- 28 s
- IBAN audit findings
- 0
- Wrong payouts
- 0
vorher: 8–12 min
vorher: 3 / year
vorher: 2 / year
Pre-launch — architecture targets from pilot patterns, no comprehensive customer data yet.
Example scenarios
How accounting uses SigID concretely.
IBAN change on a key supplier
“Supplier reports new bank details. SigID opens a challenge in the Trust App. CEO and accountant both sign. Only then the new IBAN is active.”
Example scenario · Mid-market · 45 employees
- Verification time
- ≤ 5 min
- Four-eyes principle
- 2 signatures
Example scenarios based on module functionality. SigID is pre-launch — no representative customer data yet.
Accounting FAQ
Answers for CFO and external auditors.
Does SigID work with our ERP?
SigID provides webhooks and SDKs for TypeScript, Python and Go. Direct connectors for SAP, DATEV and Lexware are on the roadmap. The existing ERP stays the system of record, SigID returns the Audit-ID.Do auditors accept the audit evidence?
Audit events are stored immutably in line with GoBD, with timestamp and cryptographic proof. Re-verification is always possible — including by external auditors.Do we need to switch banking software?
No. SigID sits between ERP and banking. The banking tool still sees the payout, SigID attaches the Audit-ID to the transaction.What happens to the invoice PDF?
SigID stores hash and metadata — the PDF can be deleted after extraction. Data minimization is the default.
Test the accounting workflow with SigID?
Free plan, no credit card. First IBAN check ready to start in under 5 minutes.
- DSGVO-konform
- eIDAS-bereit
- Made in Germany