Skip to content
← HomeWorkflowMonitoringUse casesE-invoicingThe starting pointDeploymentPricingDeutsch
Automation made simple

Your systems now work together.

Any format, any source, any destination: ahabFlow receives CSV, XML and e-invoices from workstations, business applications, mailboxes and database servers, then transforms, validates and delivers the data to your ERP, DMS, database, file storage or email system. No new ERP. No coding required. Monitored by the Hub outside your network.

Less manual work. Fewer data-entry errors. Greater visibility.

ONE PROCESS, END TO END Input Transformation Delivery Monitoring
Hub - Administration & designDESIGN WORKFLOWS, ADD MONITORING CHECKS AND CONFIGURE JOBS HERECENTRAL ADMINISTRATION - DESIGNWorkflow designerSTEPS - RULES - MAPPINGAdd monitoring checksSERVICES - PATHS - THRESHOLDSConfigure jobsSCHEDULE - TRIGGER - RETRY
click to select
YOUR NETWORK - ON-PREMISES OR CLOUDCONNECTOR REPORTS STATUS AND RETRIEVES WORKFLOWS, CHECKS & JOBSSOURCE SYSTEMSWorkstationCSV · XLSERPPOSTING - IDOCBusiness applicationXML · EDIMailbox / SFTPE-INVOICE · PDFDatabase serverSQL · VIEWOther sources…ConnectorCOORDINATES - DISTRIBUTES - CONTROLSWorker 1ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 2ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 3ahabFlowRECEIVETRANSFORMVALIDATEDELIVERDESTINATION SYSTEMSDMSPDF/A · INDEXDatabaseSQL · JSONFile storagePDF · JPGServices & APIsREST · JOBEmail deliveryE-INVOICE · CSVDATEV - SAP - Salesforce - MoreDATEV, SAP, Salesforce, SharePoint, M-Files, ECM, DMS, API endpointsahabFlow - distributed automation systemWORKERS IN YOUR NETWORK - CONNECTOR - EXTERNAL HUB FOR ADMINISTRATION & MONITORINGSTATUSCSVXLSPOSTINGXMLEDIE-INVOICEPDFSQLPDF/ARESTJSONJPGSQLE-INVOICEINDEX
Hub - Administration, design & monitoringCONFIGURE WORKFLOWS, CHECKS & JOBS - MONITOR OPERATIONS - NO CONNECTION TO WORKERSCENTRAL ADMINISTRATION - DESIGN - MONITORINGWorkflow designerSTEPS - RULES - MAPPINGAdd monitoring checksSERVICES - PATHS - THRESHOLDSConfigure jobsSCHEDULE - TRIGGER - RETRYLogsRUNS - ERRORS - RETRYMonitoring checksSERVICES - RUN TIMEConnectorsDB · MAIL · API · DMSWorker workflowsSTATUS · SLA · AUDIT
click to select
YOUR NETWORK - ON-PREMISES OR CLOUDCONNECTOR REPORTS STATUS AND RETRIEVES WORKFLOWS, CHECKS & JOBSSOURCE SYSTEMSWorkstationCSV · XLSERPPOSTING - IDOCBusiness applicationXML · EDIMailbox / SFTPE-INVOICE · PDFDatabase serverSQL · VIEWOther sources…ConnectorCOORDINATES - DISTRIBUTES - CONTROLSWorker 1ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 2ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 3ahabFlowRECEIVETRANSFORMVALIDATEDELIVERDESTINATION SYSTEMSDMSPDF/A · INDEXDatabaseSQL · JSONFile storagePDF · JPGServices & APIsREST · JOBEmail deliveryE-INVOICE · CSVDATEV - SAP - Salesforce - MoreDATEV, SAP, Salesforce, SharePoint, M-Files, ECM, DMS, API endpointsEACH WORKER MONITORS SYSTEMS THROUGH CHECKS - CONNECTOR REPORTS TO HUBahabFlow - distributed automation systemWORKERS IN YOUR NETWORK - CONNECTOR - EXTERNAL HUB FOR ADMINISTRATION & MONITORINGSTATUSOKRUN TIMEOKOKSLAOKOKSLACSVXLSPOSTINGXMLEDIE-INVOICEPDFSQLPDF/ARESTJSONJPGSQLE-INVOICEINDEX
Hub - MonitoringOPERATIONAL MONITORING - NO CONNECTION TO WORKERSMONITORING - LIVE OPERATIONSLogsRUNS - ERRORS - RETRYMonitoring checksSERVICES - RUN TIMEConnectorsDB · MAIL · API · DMSWorker workflowsSTATUS · SLA · AUDIT
click to select
YOUR NETWORK - ON-PREMISES OR CLOUDCONNECTOR REPORTS STATUS AND RETRIEVES WORKFLOWS, CHECKS & JOBSSOURCE SYSTEMSWorkstationCSV · XLSERPPOSTING - IDOCBusiness applicationXML · EDIMailbox / SFTPE-INVOICE · PDFDatabase serverSQL · VIEWOther sources…ConnectorCOORDINATES - DISTRIBUTES - CONTROLSWorker 1ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 2ahabFlowRECEIVETRANSFORMVALIDATEDELIVERWorker 3ahabFlowRECEIVETRANSFORMVALIDATEDELIVERDESTINATION SYSTEMSDMSPDF/A · INDEXDatabaseSQL · JSONFile storagePDF · JPGServices & APIsREST · JOBEmail deliveryE-INVOICE · CSVDATEV - SAP - Salesforce - MoreDATEV, SAP, Salesforce, SharePoint, M-Files, ECM, DMS, API endpointsEACH WORKER MONITORS SYSTEMS THROUGH CHECKS - CONNECTOR REPORTS TO HUBahabFlow - distributed automation systemWORKERS IN YOUR NETWORK - CONNECTOR - EXTERNAL HUB FOR ADMINISTRATION & MONITORINGSTATUSOKRUN TIMEOKOKSLAOKOKSLA
Click to enlarge
On-premises deployment availableMulti-tenantComplete audit trail

Connect your systems through their existing interfaces.

APIsDatabasesFiles & SFTPEmailERP & DMS

We assess integration with your specific application based on its interfaces, access permissions and vendor terms. Ready-made connectors are only promised where they are available for your system.

See how it works

An event starts the workflow. ahabFlow takes it from there.

A closer look at two processes: from a database view to a ZUGFeRD invoice, email delivery and archiving; and from XML plus PDF, enriched with database values, to your archive system. Both are monitored throughout.

Process 1 - Invoice run DB view ZUGFeRD Email & archive Monitoring
Example process - Invoice runDB VIEW → ZUGFERD → EMAIL DELIVERY → ARCHIVEWorkflow monitoringWORKER CHECKS - HUB COLLECTS STATUS OUTSIDE THE NETWORKRUN TIME1.8 s per invoiceVALIDATIONSchema & required fields OKDELIVERYSMTP acknowledgement receivedSTORAGEArchive ID loggedDatabase viewSQL VIEW - OPEN ITEMSWorker - "Invoice run" workflowPROCESSING ON THE SERVER WHERE THE WORKER IS INSTALLED1.READQuery the view2.BUILD ZUGFERDXML + PDF/A-33.VALIDATERequired fields - schema4.DELIVEREmail - archiveEmail deliveryZUGFERD TO RECIPIENTArchiveAUDIT-READY - INDEXINVOICE LINESSQL VIEWZUGFERD XMLPDF/A-3DOCUMENT + INDEX

A schedule or database event triggers the process. The Worker reads the view, creates a valid ZUGFeRD invoice from it (structured XML plus PDF/A-3), validates the schema and required fields, emails it to the recipient and stores the indexed document in the archive.

Monitoring checks run alongside the workflow: run time, validation results, SMTP acknowledgement and archive ID are logged. If a step fails, it is retried or escalated, not silently skipped.

Process 2 - Archive XML with PDF XML + PDF Database enrichment Archive & backup Monitoring
Example process - Archive XML with PDFXML + PDF → READ CONTENT → ENRICH FROM DATABASE → ARCHIVE SYSTEM → BACKUP FOLDERWorkflow monitoringWORKER CHECKS - HUB COLLECTS STATUS OUTSIDE THE NETWORKRECEIVEFolder is monitoredENRICHMENTDatabase match loggedARCHIVINGArchive acknowledgementBACKUPFile move confirmedIncoming folderXML + PDF PER PROCESSDatabaseMASTER DATA - ADDITIONAL VALUESWorker - "XML archiving" workflowPROCESSING ON THE SERVER WHERE THE WORKER IS INSTALLED1.READ XMLFields from the XML2.ENRICHValues from the database3.VALIDATERequired fields - PDF present4.DELIVERArchive, then moveArchive systemDOCUMENT + METADATABackup folderFILES MOVEDXML + PDFMETADATADOCUMENTINDEX VALUESFILES MOVEDMASTER DATA

In the second process, the Worker monitors an incoming folder. Each item consists of an XML file and its associated PDF. Content is read from the XML, not the PDF, and enriched with additional database values.

The document and its metadata are then sent to the archive system. Only after acknowledgement are the files moved to the backup folder. Every step is timestamped, helping to prevent duplicates and unnoticed backlogs.

Monitoring

When something happens, action follows.

ahabFlow monitors systems and workflows and responds according to your rules, before someone has to call.

Example - Monitor and recover a service Check Restart Email escalation Monitoring checks
Monitor a service, restart it, escalateSERVICE - RESTART - LOG + CONTEXT - EMAIL TO PROVIDER AND CUSTOMERService monitoringWORKER CHECKS - HUB COLLECTS STATUS OUTSIDE THE NETWORKSERVICE STATUSstopped → detected in 12 sAUTO-RECOVERYRestart, 2 attemptsESCALATIONEmail to provider + customerService on the serverWINDOWS SERVICE - TASK - PROCESSNOT RUNNINGahabFlow WorkerRULE: IF SERVICE IS DOWN, ATTEMPT RESTART; OTHERWISE ESCALATE1. CHECK STATUS60 s interval2. TRIGGER RESTARTService / task3. CHECK RESULT2 attempts4. ESCALATELog + emailRUNNINGAGAIN?YESNOService running againAUTO-RECOVERED - LOGGEDLogs & contextEVENT LOG - SERVICE LOG - SYSTEM DATAExternal service providerEMAIL WITH LOG ATTACHMENTCustomer notificationSTATUS - NEXT STEPSTATUS?RESTARTRESULTOKLOG + INFOEMAILEMAIL

The Worker checks the service at configured intervals. A rule approved in advance can attempt a restart, check the result and notify the relevant contacts. Appropriate permissions are required, and all attempts are logged.

If the service remains down after the attempts, the Worker collects log files and system context and emails them to the responsible external service provider. You receive an update at the same time, so everyone has the same information.

Ifan overnight import has not completed
Thenrestart it, check the result and notify the person responsible
Ifa server has less than 10% free disk space
Thenclean up temporary files, move older data and report the result
Ifan interface stops delivering data
Thenreconnect, retrieve outstanding data and log the gap
Ifan invoice is missing required fields
Thenput it on hold, notify the case handler and document the process

What is monitored

Monitoring checks available today

ServicesProcessesEvent logsDisk spaceCPU & memoryFiles & foldersDatabase queriesMailboxesWeb services & APIsCertificatesBackupsPrint queues+ more added regularly

What happens next

Actions a workflow can trigger

Restart a serviceRun a scriptMove a fileRetry an importDeliver dataGenerate a documentSend an emailCreate a ticketArchiveClean upRequest approval+ more added regularly

The catalogue grows with your needs. Need a check or action that is not listed? We can develop it on request. You are not limited to what is available today.

Use cases

Turn manual tasks into automated workflows.

Six typical processes from projects with medium-sized businesses, IT service providers and public-sector organisations.

Email → ERP

Incoming invoices without retyping

Email → recognise invoice → AI/OCR → validate data → ERP → DMS

From email to posting, without manual steps

File system → DMS

Documents file themselves

Monitor folder → classify → add metadata → import into DMS → clear source

No more folders waiting to be processed

Database → DMS

Bring records and documents together

Read query → transform → match document → import → write back status

The document and its data, together again

CSV → API

Connect other systems without developing your own integration

Detect file → read → generate JSON → call interface → log result

Setup scope agreed after an interface review

SFTP

Make data exchange with partners reliable

Check SFTP → retrieve files → process → deliver to target → archive successful files

Traceable, even months later

Monitoring

Spot failures before users call

Check system & service → detect fault → run approved response → check result and escalate if needed

Get alerts from your systems, not your users

In focus

E-invoicing: turn CSV, database views or JSON into invoices ready to send.

ahabFlow creates XRechnung or ZUGFeRD invoices from structured sources such as CSV files, database views, JSON or API responses. It reads the data, completes and checks required fields, generates the XML and sends it with the PDF/A-3 to the recipient through the customer's email system. The document and metadata are then archived.

Input

Receive e-invoices, extract their structured data and deliver it to the right system.

Outgoing

Generate the required format from structured invoice data and send it after the defined checks.

from 2028

Mandatory e-invoice issuance for almost all businesses, regardless of size.

ongoing

Archive sent invoices and retain the supporting records.

XRechnungZUGFeRDCSV / DB view / JSONRequired-field validationEmail deliveryGoBD-compliant storage
XRechnung and ZUGFeRD generated from structured invoice data
From data to e-invoice: read, validate, generate, send and archive - traceable down to individual fields.

Incoming: turn XRechnung and ZUGFeRD into posted invoices

Invoices with structured data (XRechnung, ZUGFeRD) arrive by email, portal or file storage. The format and content are recognised, required fields are checked, and structured data is passed to the ERP. The file is renamed (for example: Supplier_InvoiceNumber_Date.pdf) and stored in a file system or an audit-ready DMS archive.

The starting point

Things work. Nobody quite remembers how.

Processes built up over the years keep the business running - until one fails, an employee leaves or a new requirement arrives.

“A script has handled that for years. The person who wrote it left long ago.”
Batch files, services and cron jobs scattered across servers. Nobody knows exactly what runs where.
“We only noticed when Accounts complained.”
An interface had been down for two days. There was no alert because nobody was watching.
“Export, check, rename, upload. Every morning.”
Repetitive tasks that take time, with errors discovered only by chance.
Tools

Everything that needs to happen between your systems.

One platform instead of a collection of standalone tools that only one person understands.

Workflows, not isolated scripts

Build each process from reusable components: visible, version-controlled and maintainable without coding.

Built-in monitoring

Run times, errors and failed systems in one interface. Notifications and escalations follow your configured rules.

Transform data

Convert between XML, JSON, CSV, databases and e-invoices. Rename, calculate, filter and validate fields.

Databases & interfaces

SQL Server, PostgreSQL and MySQL through queries or procedures. Connect modern systems using REST, HTTP and JSON.

Files, SFTP & documents

Monitor folders, transfer files, classify PDFs and TIFFs, extract metadata and archive documents.

Mailboxes & delivery

Process incoming emails, retrieve attachments and send status updates and approval requests automatically.

AI in the workflow

For us, AI is a step in the process, not the product.

Use it where fixed rules are not enough: recognise document types, extract suppliers and amounts, interpret free text and match data. The results then continue through your defined validation rules.

ClassificationData extractionCheckMatching
01New invoice in the mailbox
02AI identifies document type, supplier and amount
03Rule-based validation and approval
04Delivery to ERP and DMS
05Custom logic through your own scripts

Please note: You can connect your own AI models to a workflow or add optional AI processing billed by page volume. With external AI services, the processing location depends on the configuration and agreed terms.

Architecture & deployment

Your data stays where it belongs.

Three components, two deployment options and two responsibility models: cloud or on-premises, each managed by us or administered and monitored by you.

Workers in customer systems, Connector in the network and a central Hub
01

Worker

Each Worker is a complete execution node: it receives, transforms, validates and delivers data. It also monitors connected systems, services and processes through its monitoring checks. Processing runs directly on the server where the Worker is installed. Multiple Workers can run on a single server or across many servers.

02

Connector

Links the Workers in your environment to the Hub, distributes tasks, synchronises state and ensures each process runs in the right place.

03

Hub

The central administration component: design workflows, add monitoring checks and configure jobs, with monitoring, logs, roles and tenants in one place. Available in your environment or as a managed service.

CloudCloud deployment, managed by us or administered by you.
On-PremisesDeployment in your infrastructure, managed by us or administered by you.
Monitoring on your termsWe monitor your workflows for you, or you manage monitoring and alerts yourself.
Pricing

One price per automated process.

There are no individual charges per document or processing step. Your plan includes an agreed monthly document volume. Volume extensions are available if you need more.

Clear plan sizes: 1, 5 or 20 automated processes. The cards compare workflow counts, included monitoring checks and monthly document volumes. During the process review, we identify the components, interfaces, deployment and permissions your process needs and specify them in the quotation.

What counts as a workflow? An example

Receive an invoice → validate its data → deliver it to the DMS: this can form one connected workflow. Repeated runs of the same configured workflow are not charged as individual transactions. The precise treatment of variants, tenants and destination systems is agreed in the quotation. Custom setup and external services, such as AI usage, are listed separately.

How are documents counted?

A technical retry does not count the same document again. Monitoring-only activity does not use your document allowance.

Self-Service

Build and run your own workflows.

Updates and product support are included in the licence. You retain full control over Workers, workflows and monitoring.

The monthly equivalent applies with a 12-month minimum term and annual payment in advance.

Starter
—/ month

1 workflow50 checks included
  • One automated process
  • 50 monitoring checks included
  • Updates and product support included
  • 5,000 documents per month included
Get a free process review
Our recommendationBusiness
—/ month

5 workflows100 checks included
  • Five automated processes
  • 100 monitoring checks included
  • Updates and product support included
  • 10,000 documents per month included
Get a free process review
Enterprise
—/ month

20 workflows200 checks included
  • Fifteen automated processes
  • 200 monitoring checks included
  • Updates and product support included
  • 25,000 documents per month included
Get a free process review

A monitoring check tracks a service, port or incoming file, for example. Custom workflow setup starts at €249 as a one-off charge. Tiered terms are available for partners.

The plan cards show base prices for the included document volume. All prices exclude statutory VAT. Annual contract: 12-month minimum term, paid annually in advance. Flex contract: one-month minimum term, monthly billing and monthly cancellation. Setup is charged separately. Notice periods and renewal terms are specified in the quotation. This selection applies to Self-Service only, not Managed Monitoring.

Automate across multiple tenants

ahabFlow automates work and monitors systems across internal tenants, such as companies in the same corporate group, company codes or ERP tenants. Additional tenants are available on eligible plans.

A technically identical workflow counts once, even when several tenants use their own settings. Separate automation processes count separately. The agreed monthly document allowance is shared by all tenants under the licence.

IT service providers and systems integrators need a separate customer licence or an individual partner agreement for independent customer businesses.

The quote sets a fixed document limit. If you need more, we agree the extension in advance. See the licence terms for the document allowance and the terms and conditions.

Licence calculator

What counts as a document?

Each distinct business document or file that a workflow processes or creates counts as one document. Examples include an incoming PDF invoice or a newly generated e-invoice.

A multi-page document counts once. Converting, transferring or retrying the same document does not increase the count. Monitoring-only activity does not use the allowance.

Enter the total number of documents per month across all tenants.

Counting rules in the licence terms

Managed Monitoring

Prefer not to manage monitoring yourself?

With Self-Service, you configure and run your monitoring. With Managed Monitoring, we carry out the agreed setup, maintain rules and review relevant alerts during the agreed service hours. Troubleshooting operating systems and business applications is not automatically included.

Managed S
499EUR / month
up to 50 checksapprox. 5-8 servers2 standard workflows
Enquire about this plan
Managed M
899EUR / month
up to 150 checksapprox. 15-25 servers5 standard workflows
Enquire about this plan
Managed L
1,499EUR / month
up to 300 checksapprox. 30-50 servers10 standard workflows
Enquire about this plan
Enterprise Managed
bespoke
>300 checkslarger / critical environmentsbespoke
Enquire about this plan

Managed Monitoring has a 12-month minimum term, regardless of the Self-Service contract option. Standard setup and rule configuration for the agreed scope are included. We agree on scope, existing infrastructure and any special requirements in advance. Custom workflows and further troubleshooting are quoted separately.

Managed plans include the stated standard workflows and checks for the agreed monitoring scope. Additional workflows for other business processes are licensed separately. Full service scope and exclusions.

Free process review

Which task would you like off your desk?

Tell us about a process you currently handle manually or with your own scripts. We will explain how it could become an ahabFlow workflow, with no obligation.

  • Assessment by experienced DMS and integration consultants
  • We normally respond within one business day
  • Also for partners, IT service providers and systems integrators
AI-generated illustration of two people viewing a process diagram on a screen.
AI-generated
What are you interested in? (optional)

Your selection is non-binding. You can enquire without choosing a plan or change your selection at any time.

Annual contract: paid annually in advance. Flex contract: monthly billing with a one-month minimum term.

Plan and contract option are still open. We will advise you based on your process.

We use your information to respond to this enquiry. Learn more in our privacy notice. This does not sign you up for a newsletter.

* Required fields. Plan and contract option are optional. Do not include passwords or confidential document contents.

FAQs

Frequently asked questions

Do we need to replace our existing systems?+

No. ahabFlow does not replace your ERP, DMS or business applications. It connects them and handles the transfers you currently carry out manually or through scripts.

Can you connect custom systems too?+

Yes, provided there is an interface: a database, file storage, SFTP, email or an API. If a component is missing, we can develop it on request.

What happens to our existing scripts?+

You can keep them. Existing logic can be integrated as a workflow step, with monitoring, logging and central management added.

Does ahabFlow have to run in the cloud?+

No. Alongside managed deployment, ahabFlow supports operation in your own infrastructure, including central administration.

Is it only for documents?+

No. In addition to documents, ahabFlow processes structured data and monitors technical systems, services and interfaces.

How soon can the first process be running?+

Typical workflows start from a template. Custom workflow setup starts at EUR 249.