01
Bank statements arrive via bank API, EBICS or CAMT file, get reconciled against open items and booked. Claude also reads messy payment references and proposes a match for approval when it is unsure.
02
Invoices, delivery notes, contracts and forms are turned into structured data, checked against your rules and written straight into ERP, CRM or a spreadsheet. Even for scans and changing layouts.
- Claude
- JSON schema
- Validation
03
Customers, products, prices and orders stay in sync between CRM, ERP, shop and accounting. With a clear source of truth and conflict rules instead of a spreadsheet in between.
04
Numbers from bank, ERP and CRM land in your inbox every Monday as a short report with commentary from Claude. No dashboard nobody opens.
- Reporting
- Claude
- Email/Slack
05
EBICS, FinTS and bank APIs on one side, SAP via RFC, OData or IDoc on the other. Where there is no ready-made node, we write the integration in TypeScript.
- EBICS/FinTS
- SAP RFC/OData
- TypeScript
06
Validation, duplicate checks, idempotency and a log that makes every change traceable. So the automation survives the auditor too.
- Validation
- Idempotency
- Audit