Data automation · Finance · Documents

Data that arrives on its own, exactly where it is needed.

Bank statements, invoices, orders, master data: we connect bank, SAP, ERP, CRM and shop so nobody types, copies or reconciles by hand anymore. With Claude wherever documents and messy data are involved.

The problem

The data is there. It is just in the wrong system, the wrong format or a spreadsheet.

In most companies the same manual steps run every day: open the bank statement, type in the invoice, export the list, copy numbers together. Every step costs time and is a source of errors. Almost all of it can be automated.

  • Spreadsheets as the interface

    Numbers from bank, ERP and CRM are collected by hand every Monday. The report is finished when it is already outdated.

  • Documents someone has to type in

    Invoices, delivery notes and contracts arrive as PDF or scan in the inbox. By the time the data is in the system, someone has touched it twice.

  • Systems that do not know each other

    CRM, ERP and shop each have their own truth about customers, products and orders. Reconciliation happens when things already creak.

  • Errors that show up at year end

    Double-booked payments, missing receipts, wrong VAT. Without validation and an audit trail, this only surfaces months later.

Services

What we actually automate. Each item is a good starting point for a pilot.

01

Match incoming payments

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.

  • Banking APIs
  • CAMT
  • SAP
  • DATEV
02

PDF extraction with Claude

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

Keep systems in sync

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.

  • CRM
  • ERP
  • Shop
  • Webhooks
04

Reporting for management

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

Bank and SAP integration

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

Data quality & audit trail

Validation, duplicate checks, idempotency and a log that makes every change traceable. So the automation survives the auditor too.

  • Validation
  • Idempotency
  • Audit

Process

One data flow first, then the next.

We start with the process that eats the most manual work and build it for production. Then the next one. That is how weeks deliver what would otherwise be a year-long project.

  1. 1

    Data map

    Which systems, which formats, which manual steps. We map where data flows today and where it gets stuck.

    30 minutes · free

  2. 2

    Pilot

    One data flow end to end, in production, with validation and alerting. For example payment matching or invoice capture.

    2 weeks · fixed price

  3. 3

    Rollout

    More data flows by priority, monitoring, audit trail, documentation. We build and stay hands-on.

    Iterative · sprint rhythm

  4. 4

    Handover

    Your team takes over operations and further development. With training and a support model that fits.

    Enablement · optional retainer

Recently built

Payment and account data from bank interfaces automatically into SAP

Account transactions arrive through the bank interface, are matched against open items, presented for approval when unsure, and then booked into SAP and downstream systems. Idempotent, with a clean audit trail and monitoring. Self-hosted on AWS.

  • Banking APIs
  • SAP
  • Approval
  • Audit trail
  • AWS

From the blog

Hands-on knowledge about n8n, data automation and AI in the enterprise. A new article every two days.

The first articles are coming soon.

All articles

FAQ

Frequently asked questions

Does our data have to leave the building?

Not necessarily. n8n runs self-hosted on your infrastructure. For Claude we use providers with EU processing and a data processing agreement, and we only send the fields the step needs.

Which systems can you connect?

Anything with an API, a file interface or a database. SAP, DATEV, Microsoft Dynamics, HubSpot, Salesforce, Shopware, Shopify, banks via EBICS, FinTS or API. Where there is no ready-made node, we write the integration.

How reliable is Claude at reading documents?

Very good on clean documents, good on scans and changing layouts. What matters is the validation behind it: totals must add up, numbers must exist. Anything uncertain goes to approval instead of into the system.

What happens with errors?

Every data flow gets retries, an alert and a place where unclear cases land. Nothing disappears silently. Every change in the target system is traceable.

What does it cost?

A pilot for one data flow is a fixed-price project over two weeks. We name the price after the intro call, once systems and scope are clear.

Which data flow costs you the most manual work today?

30 minutes, no pitch. We look together at what can be automated, what a pilot costs and how fast it can run.

Prefer writing?

Send an email

Book an intro call · 30 minutes

Calendar not showing? Open it directly: calendar.app.google