Resources · Make integration

Business OS - DATEV Make integrationAutomate Business OS - DATEV with Make.

Can Make post bookings and cash entries into DATEV without anyone retyping them? The Business OS - DATEV Make integration gives you 18 action modules, from booking proposals to cash book entries and exports. This guide shows bookkeepers and ops leads how to connect the account and build a first scenario.

Try the Business OS - DATEV integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Business OS - DATEV Make integration do?

The Business OS - DATEV Make integration lets a Make scenario (the automation you build, a chain of steps) write accounting data into Business OS - DATEV and read reference lists back from it. Every step is a module, one brick of the scenario, and all 18 modules here are actions: they run when an earlier step hands them data.

Cash sales that land in the cash book. A point of sale or a shop app records a payment, and Erstelle einen Kassenbucheintrag (einfach) adds the matching line to the cash book, with Kassenbücher auflisten helping you pick the right book.

Bookings prepared for review. When an invoice is approved in another tool, Erstelle einen Buchungsvorschlag drops a booking proposal that an accountant checks, while Erstelle eine Buchung is the direct route once the data is trusted.

Reports that leave DATEV on their own. SuSa exportieren and Buchungsdaten exportieren pull the SuSa (trial balance) and booking data out, so a spreadsheet or a report tool downstream always receives the same export.

What the page cannot promise: the app has no trigger, so Make never learns on its own that something changed in DATEV, and the official module descriptions are missing, so the notes below lean on the module names and tell you to check each one with a test run. If you also weigh n8n for this job, the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from scratch. When a run fails, start with Make troubleshooting.

Connect

How do you connect Business OS - DATEV to Make?

  1. 01

    Copy your API key

    You need an active Business OS - DATEV account and an API key. Open the dashboard of your Business OS - DATEV account, click API Keys and copy the key you will paste into Make.

  2. 02

    Open the connection window

    In your Make account, add any Business OS - DATEV module to a scenario and click Create a connection. A connection is your account linked to Make once, then reused by all 18 modules of the app.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when several clients or companies share one Make account. Paste the credentials you copied, or follow the on-screen instructions, then save.

First scenario

Your first scenario with Business OS - DATEV

GoalWhen a cash sale is recorded in another app, Make adds the matching entry to your Business OS - DATEV cash book.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where the sale is recorded, since DATEV has no trigger.

  2. 02

    Set up the starting app

    Search that app by name, pick the module that returns new sales, and click Create a connection to link its account. Each sale it returns becomes a bundle, one item passed to the next module.

  3. 03

    Add the cash book module

    Click the + on the right, search Business OS - DATEV and pick Erstelle einen Kassenbucheintrag (einfach). Connect it with your API key, then map the sale data into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bundles each module received and check in DATEV that the entry landed in the right cash book.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two runs.

Modules

What can the Business OS - DATEV modules do?

Business OS - DATEV gives you 18 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Business OS - DATEV1

Buchungsdaten exportieren

ActionIn the docs only

Its German name means export booking data: the module hands the bookings stored in Business OS - DATEV to the next step of your scenario, where a sheet or a report can use them.

When to use it
a controller wants the raw bookings in a spreadsheet without logging into DATEV.
Watch out
the documentation lists no fields for it, so read the bundles after a Run once before mapping anything.
Business OS - DATEV2

DUO Beleg bereitstellen

ActionIn the docs only

Going by its name, this module makes a receipt (Beleg) available in DUO, so a document from another tool reaches the accountant without a manual upload.

When to use it
receipts arrive by email or in a storage app and should end up in DUO.
Watch out
list the receipt types first with DUO Belegtypen auflisten, then test on one document before the whole flow.
Business OS - DATEV3

DUO Belegtypen auflisten

ActionIn the docs only

This one lists the receipt types available in DUO, which saves you from guessing the value another module expects when it files a document.

When to use it
right before DUO Beleg bereitstellen, when you set up the scenario and want to see which types your account knows.
Watch out
it returns a list, so each type may travel as its own bundle and multiply the operations Make counts.
Business OS - DATEV4

Details eines Geschäftsjahres

ActionIn the docs only

Fiscal year details, as the name says: the module fetches the information of one financial year so later steps can check that a booking falls inside it.

When to use it
a scenario that posts entries needs to confirm which fiscal year is open before writing anything.
Watch out
no field is documented, so run it once and note exactly what DATEV sends back before you build conditions on it.
Business OS - DATEV5

Erstelle eine Buchung

ActionIn the docs only

A booking goes straight into the books: judging by its name, this action creates the entry itself rather than a proposal, from the amounts and accounts you map from the previous module.

When to use it
the source data is clean and already approved, for example invoices validated in an approval tool.
Watch out
a posted booking is real accounting data, so prefer Erstelle einen Buchungsvorschlag while you are still testing the mapping.
Business OS - DATEV6

Erstelle einen Buchungsvorschlag

ActionIn the docs only

Safer than a direct posting: judging by its name, this module drops a booking proposal in DATEV for someone to review and accept, which keeps a human check between the scenario and the ledger.

When to use it
you automate invoice entry for a client but the accountant wants the final word.
Watch out
proposals pile up if nobody reviews them, so agree on who checks them before you switch the scenario on.
Business OS - DATEV7

Erstelle einen Kassenbucheintrag (advanced)

ActionIn the docs only

The advanced variant of the cash book entry is, as its label suggests, the one to open when a cash movement needs more detail than the simple form offers.

When to use it
the simple version does not show the option a particular cash entry requires.
Watch out
the documentation does not say which extra settings it adds, so open both variants side by side in the editor and compare the fields before choosing.
Business OS - DATEV8

Erstelle einen Kassenbucheintrag (einfach)

ActionIn the docs only

With this module, a cash sale or a petty cash expense becomes a line in your cash book, using the simple form of the entry.

When to use it
a shop, a café or a kiosk records cash payments in another app and the cash book should follow without retyping.
Watch out
pick the target book carefully; Kassenbücher auflisten shows which cash books the connection can reach.
Business OS - DATEV9

Kassenbücher auflisten

ActionIn the docs only

As its name says, this module lists the cash books the connection can see, which helps when a company runs one book per shop or per register.

When to use it
you build a cash scenario for several locations and need the right book for each entry.
Watch out
each book is likely to arrive as a separate bundle, so check the output of a Run once before chaining an entry module after it.
Business OS - DATEV10

Kontenplan abrufen

ActionIn the docs only

Retrieving the chart of accounts gives your scenario the account list of the company, so later modules can post to accounts that actually exist.

When to use it
you map categories from an expense or sales tool to DATEV accounts and want to check them.
Watch out
the module name is the only hint of what it returns, so read the result of a test run before relying on it.
Business OS - DATEV11

Make an API call

ActionIn the docs only

Anything the other modules leave out can still be reached here: this module calls any endpoint of the Business OS - DATEV API, with the connection you already created.

When to use it
the action you need has no dedicated module in the list.
Watch out
you write the request yourself, so keep the API documentation of Business OS - DATEV at hand and test with Run once.
Business OS - DATEV12

Personenkonto erstellen

ActionIn the docs only

A new customer or supplier gets its own personal account in DATEV through this action, ready to receive bookings later in the flow.

When to use it
a client signs in your CRM and should exist in accounting before the first invoice is posted.
Watch out
running it twice for the same person may create a duplicate account, so decide how the scenario knows an account already exists.
Business OS - DATEV13

ReWe Beleg bereitstellen

ActionIn the docs only

Its name says it provides a receipt (Beleg) to ReWe instead of DUO, which gives you a second place to deliver documents from your scenario.

When to use it
the person who keeps the books receives documents in ReWe rather than in DUO.
Watch out
confirm which of the two targets is really used before building, then call ReWe Belegtypen auflisten to get the matching receipt type.
Business OS - DATEV14

ReWe Belegtypen auflisten

ActionIn the docs only

Before sending a receipt to ReWe, this module shows which receipt types exist on that side, so the filing step uses a value DATEV accepts.

When to use it
during setup of a scenario built around ReWe Beleg bereitstellen.
Watch out
these types are not necessarily the same as the DUO ones, so never reuse a value from DUO Belegtypen auflisten without checking the output.
Business OS - DATEV15

Rechnungsordner auflisten

ActionIn the docs only

Invoice folders are listed by this module, handy when documents must be sorted into the right folder instead of one shared pile.

When to use it
incoming and outgoing invoices go to different folders and the scenario has to choose one.
Watch out
the documentation says nothing about what each folder bundle contains, so read the test output and map the identifier you see there.
Business OS - DATEV16

Steuersätze auflisten

ActionIn the docs only

Tax rates available in DATEV come back from this module, which keeps VAT choices consistent between your source tool and the books.

When to use it
a booking scenario must attach the right tax rate to each line instead of a hard-coded value.
Watch out
map the rate from this list rather than typing it by hand, and recheck the result in DATEV after the first Run once.
Business OS - DATEV17

SuSa exportieren

ActionIn the docs only

SuSa is the usual German shorthand for the trial balance (Summen- und Saldenliste), and this action exports it so a report, a sheet or a message can carry the current figures.

When to use it
management wants the trial balance in its reporting tool after the books are closed for a period.
Watch out
the export format is not documented, so inspect the file or data it returns before feeding a dashboard.
Business OS - DATEV18

Zahlungsbedingungen auflisten

ActionIn the docs only

Payment terms stored in DATEV are listed here, so new accounts or bookings can reuse the terms your accountant already set up.

When to use it
you create personal accounts with Personenkonto erstellen and want each one to carry the right terms.
Watch out
a list module can return many bundles; keep the one you need with a filter so the next module does not run once per term.
Need help

Need help automating Business OS - DATEV with Make?

A person reads every message.

FAQ

Questions about Business OS - DATEV and Make

01Is the Business OS - DATEV Make integration free?
Yes, on the Make side. Business OS - DATEV is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the limit on active scenarios. Usage is counted in operations, one execution of one module on one item. Your Business OS - DATEV subscription is separate: its own pricing page gives the details.
02What is needed to connect Business OS - DATEV to Make?
An active Business OS - DATEV account and an API key. You find the key in the dashboard of your account, under API Keys. In Make, add any module of the app to a scenario, click Create a connection, give the connection a name if you like, and paste the key or follow the on-screen instructions. The connection is then shared by every module of the app, so you only do this once per account. If several companies are involved, one connection per account with a clear name keeps things readable.
03Can Business OS - DATEV start a Make scenario in real time?
No. The app has no trigger module, so nothing in Business OS - DATEV can start a scenario by itself. You start it another way: with a trigger from another app, such as a shop, a CRM or a form, or with the schedule on the first module, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes, on paid plans 1 minute. If the source app offers an instant trigger, which calls Make through a webhook as soon as something happens, the DATEV modules run right after it.
04What if a Business OS - DATEV module is missing in Make?
Use Make an API call. It reaches any endpoint of the Business OS - DATEV API with the connection you already have, so an action that the other modules do not cover stays possible. You write the request yourself, so keep the API documentation of the vendor open. Also note that the Make documentation for this app is marked as AI-generated and may contain mistakes: verify important details in a test run, and contact Business OS - DATEV directly if the vendor documentation leaves a question open.
05Should Business OS - DATEV be automated with Make or n8n?
It depends on where your team already builds automations. On Make, this app gives you 18 action modules, including a generic API call, from the Free plan and without writing code. The same app often has an n8n node as well, so check whether one exists and what it covers before choosing. Compare the modules you actually need, the way your team prefers to work and the tools already connected on each side, rather than a general ranking of the two platforms.
Same platform

Other docs you might need on this stack.

Browse all integrations