{"id":6893,"date":"2026-08-11T11:03:43","date_gmt":"2026-08-11T09:03:43","guid":{"rendered":"https:\/\/www.cloudmaven.com\/?page_id=6893"},"modified":"2026-08-11T12:22:02","modified_gmt":"2026-08-11T10:22:02","slug":"netsuite-and-datev-integration","status":"publish","type":"page","link":"https:\/\/www.cloudmaven.com\/en-uk\/integrations-middleware\/netsuite-and-datev-integration","title":{"rendered":"NetSuite > DATEV Integration"},"content":{"rendered":"\n
\"\"<\/span>
\n
\n
\n

NetSuite and DATEV, finally talking to each other. Fully automated accounting and payroll, built for German compliance.<\/h1>\n\n\n\n

Cloudmaven’s eUnify connector links NetSuite to DATEV natively, so accounting exports and payroll imports run without spreadsheets, manual re-keying, or year-end surprises. It’s the same finance-first approach we bring to every ERP engagement.<\/p>\n\n\n\n

\n
Book a demo<\/a><\/div>\n\n\n\n
Talk to an integration expert<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n
\n
\n
\n

Why eUnify, in one paragraph<\/h2>\n\n\n\n

eUnify isn’t a third-party tool bolted onto NetSuite from the outside. It’s a native NetSuite application, built and maintained in-house by the same Cloudmaven team that configures your NetSuite finance architecture, not handed off to a separate integration vendor once the ERP project ends. Your accounting and payroll data stay inside NetSuite; only the compliant DATEV file ever leaves the system.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

Cloudmaven in Figures<\/h2>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\n
\n\n

16+<\/h3>\n\n<\/div><\/div>\n\n\n

Locations worldwide (Europe, EMEA, America, Asia)<\/p>\n<\/div>\n\n\n\n

\n\n

30+<\/h3>\n\n<\/div><\/div>\n\n\n

Countries in which we operate<\/p>\n<\/div>\n\n\n\n

\n\n

120+<\/h3>\n\n<\/div><\/div>\n\n\n

ERP and EPM employees<\/p>\n<\/div>\n\n\n\n

\n\n

350+<\/h3>\n\n<\/div><\/div>\n\n\n

satisfied customers<\/p>\n<\/div>\n\n\n\n

\n\n

400+<\/h3>\n\n<\/div><\/div>\n\n\n

Successfully implemented projects<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Who this integration is a fit for<\/h3>\n\n\n\n

Finance teams running NetSuite alongside a German entity that reports through DATEV, and still moving accounting and payroll data by hand.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

German entities on NetSuite<\/strong>
Companies running NetSuite with a German entity, or a subsidiary, that reports through DATEV.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Manual monthly exports<\/strong>
Teams still exporting G\/L accounts, master data, or transactions to their tax advisor by hand every month.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Payroll in LuG or LODAS<\/strong>
Anyone processing payroll in DATEV Lohn & Gehalt (“LuG”, DATEV’s payroll module) or LODAS (DATEV’s alternative payroll system for larger or more complex payrolls) that needs to post into the NetSuite general ledger.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Multi-entity OneWorld setups<\/strong>
NetSuite OneWorld setups with several legal entities, each needing its own DATEV settings.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Legacy Tax or SuiteTax<\/strong>
Businesses on either of NetSuite’s two tax engines that want BU-Schl\u00fcssel (DATEV’s tax-treatment code, assigned to each transaction) resolved automatically instead of by hand.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Auditable review step<\/strong>
Finance teams that need a reviewable, auditable process before anything reaches their tax advisor, not just an email thread.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n

Companies that already rely on our portfolio<\/h2>\n\n\n\n
\n
\n
\n \n\n
\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n\n\n\n
\"Companies<\/figure>\n<\/figure>\n\n <\/div>\n <\/div>\n
\n
<\/div>\n
<\/div>\n <\/div>\n <\/div>\n\n<\/div>\n\n\n\n
\n
\n

eUnify, thought through from a finance perspective<\/h2>\n\n\n\n

A native NetSuite application with German accounting and payroll compliance built in, not bolted on afterward.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Runs inside NetSuite<\/strong>
It runs as an application inside NetSuite itself, so there’s no separate portal or login for the finance team to manage.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

One platform, both directions<\/strong>
Accounting export and payroll import run through one platform instead of two separate tools.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

German compliance handled natively<\/strong>
BU-Schl\u00fcssel (tax-treatment codes), Automatikkonten (DATEV’s automatic reconciliation accounts), Kirchensteuer (church tax) and Solidarit\u00e4tszuschlag (solidarity surcharge) withholding, and U1\/U2 (employer reimbursement schemes for sick pay and maternity pay) are all handled natively instead of bolted on afterward.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Review before submission<\/strong>
Before any DATEV file goes out, you get an account-level summary of original, correction, and net debit\/credit to check.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Per-entity configuration<\/strong>
Each legal entity keeps its own DATEV settings, account mappings, and booking configuration.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Automated payroll posting<\/strong>
Monthly or daily payroll runs post automatically, with gross-to-net validation before anything hits the ledger.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

A trail auditors can follow<\/strong>
Full request history, status tracking, and employee-level detail give finance teams, and their auditors, a clear trail.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

No third-party data silo<\/strong>
Accounting records stay in NetSuite. Only the compliant DATEV file goes to the tax advisor, so sensitive data never sits in a third-party silo.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Features<\/h3>\n\n\n\n

From a single accounting export to a fully automated close.<\/strong>
eUnify’s DATEV connector is built around two data flows, delivered as a phased rollout: most engagements start with accounting export, then add payroll import once the first close cycle is running smoothly.<\/p>\n<\/div>\n\n\n\n

\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Rechnungswesen: accounting export from NetSuite to DATEV<\/strong>
Export G\/L accounts, customer and vendor master data, and transaction postings in DATEV EXTF format (DATEV’s standard data-exchange format), ready for the tax advisor with no manual reformatting. It covers three export types (Accounts, Customers & Vendors, Transactions), works with both Legacy Tax and SuiteTax, resolves BU-Schl\u00fcssel automatically, lets you post journal corrections before submission, supports multi-subsidiary configuration, and keeps a full request history.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Lohn & Gehalt: payroll import from DATEV to NetSuite<\/strong>
Automatically post monthly payroll journal entries (wages, social security, taxes, and net pay) into the NetSuite general ledger. It supports three booking modes (Department, Company, Employee), scheduled automated runs, gross-to-net validation, LuG and LODAS payroll formats, cost center to Department\/Class\/Location mapping, a workflow report email after every run, and an employee-level audit trail.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n

eUnify, manual export, or a typical DATEV connector? An honest decision guide<\/h3>\n\n\n\n

Most companies arrive at this decision from one of three starting points. It’s worth naming them plainly instead of just comparing feature checklists.<\/p>\n\n\n\n

\n
\n

Rather keep manual export<\/h4>\n\n\n\n
\n\n\n\n
\n

Company profile<\/mark><\/strong>
One legal entity, low transaction volume, no payroll import need.<\/p>\n\n\n\n

Data volume & entities<\/mark><\/strong>
Low volume, infrequent postings.<\/p>\n\n\n\n

Compliance need<\/mark><\/strong>
Manual review is still manageable.<\/p>\n\n\n\n

Time to value<\/mark><\/strong>
No implementation needed, but ongoing manual effort every month.<\/p>\n\n\n\n

Payroll<\/mark><\/strong>
Payroll booked manually, entity by entity.<\/p>\n\n\n\n

Audit trail<\/mark><\/strong>
Email-based history, harder to reconstruct.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n

Rather a typical connector<\/h4>\n\n\n\n
\n\n\n\n
\n

Company profile<\/mark><\/strong>
Single-direction need (export only), limited compliance complexity.<\/p>\n\n\n\n

Data volume & entities<\/mark><\/strong>
Growing, but still a single entity or simple structure.<\/p>\n\n\n\n

Compliance need<\/mark><\/strong>
Basic EXTF export covers the requirement.<\/p>\n\n\n\n

Time to value<\/mark><\/strong>
Faster to set up, narrower scope.<\/p>\n\n\n\n

Payroll<\/mark><\/strong>
Usually not covered.<\/p>\n\n\n\n

Audit trail<\/mark><\/strong>
Varies by vendor; review step often missing.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n

Rather eUnify<\/h4>\n\n\n\n
\n\n\n\n
\n

Company profile<\/mark><\/strong>
Multi-subsidiary NetSuite OneWorld, or payroll import required alongside export.<\/p>\n\n\n\n

Data volume & entities<\/mark><\/strong>
Multiple legal entities, each needing independent DATEV settings.<\/p>\n\n\n\n

Compliance need<\/mark><\/strong>
BU-Schl\u00fcssel, Automatikkonten, Kirchensteuer, Solidarit\u00e4tszuschlag, U1\/U2 all in scope.<\/p>\n\n\n\n

Time to value<\/mark><\/strong>
Native NetSuite app; days to first live export once mapping is confirmed.<\/p>\n\n\n\n

Payroll<\/mark><\/strong>
LuG and LODAS payroll import with gross-to-net validation.<\/p>\n\n\n\n

Audit trail<\/mark><\/strong>
Full request history, journal corrections, and employee-level trail, native to NetSuite.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

In a joint discovery conversation<\/strong>, we assess your current export process and DATEV requirements without pre-committing you to a solution, and recommend the setup that fits your subsidiary structure, payroll needs, and compliance exposure.<\/p>\n<\/div>\n\n\n\n\n\n

\n
\n

We connect your relevant systems seamlessly<\/h2>\n\n\n\n

Cloudmaven connects eUnify to your existing system landscape: NetSuite OneWorld across multiple subsidiaries, DATEV Rechnungswesen and Lohn & Gehalt or LODAS on the tax advisor’s side, and any other Cloudmaven integrations you’re already running in NetSuite, such as Personio for HR data or Perk for travel and expense management.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n

Switching from an existing process<\/h2>\n\n\n\n

Typical starting points for a DATEV integration project differ quite a bit in effort and risk, so it’s worth setting expectations upfront:<\/p>\n\n\n\n

\n
\n
\n

Source process<\/h4>\n\n\n\n

Manual CSV\/Excel export<\/p>\n<\/div>\n\n\n\n

\n

Typical migration effort<\/h4>\n\n\n\n

Low to medium<\/p>\n<\/div>\n\n\n\n

\n

What matters most<\/h4>\n\n\n\n

Mapping the existing chart of accounts and cost centers to DATEV format and BU-Schl\u00fcssel logic.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Source process<\/h4>\n\n\n\n

In-house or custom-built script<\/p>\n<\/div>\n\n\n\n

\n

Typical migration effort<\/h4>\n\n\n\n

Medium<\/p>\n<\/div>\n\n\n\n

\n

What matters most<\/h4>\n\n\n\n

Assessing the existing mapping logic and tax key rules before cutover, so nothing gets lost along the way.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Source process<\/h4>\n\n\n\n

Another third-party DATEV connector<\/p>\n<\/div>\n\n\n\n

\n

Typical migration effort<\/h4>\n\n\n\n

Medium to high<\/p>\n<\/div>\n\n\n\n

\n

What matters most<\/h4>\n\n\n\n

Migrating historical mapping configuration and running a parallel-run period before switching over.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n

Cloudmaven & eUnify<\/h2>\n\n\n\n

Our principle holds for integration projects too: we start the conversation with your finance processes and subsidiary structure, not with the connector. Cloudmaven already supports complex, growing organisations as a NetSuite implementation partner across Switzerland, Germany, and beyond.<\/p>\n\n\n\n

eUnify was developed in-house specifically to close the gap between NetSuite and German accounting and payroll requirements: the same team that configures your NetSuite finance architecture also owns the DATEV connector, instead of handing you off to a third-party vendor.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

Companies that already trust our portfolio<\/h2>\n\n\n\n
\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n

Our services<\/h2>\n\n\n\n
\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Requirement analysis and DATEV mapping design<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Multi-subsidiary configuration, with per-entity DATEV and tax settings<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

BU-Schl\u00fcssel and tax key setup for Legacy Tax and SuiteTax<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Payroll import configuration for LuG and LODAS<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Tax advisor coordination and parallel-run testing<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n\t\t\t<\/span>\n\t<\/div><\/div>\n\n\n\n
\n

Ongoing support and monitoring<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

Our approach<\/h2>\n\n\n\n

Our approach is built on the Cloudmaven.ERP Methodology and its Target Operating Model (TOM) Framework.<\/p>\n\n\n\n

What is the Cloudmaven Integration Rollout?<\/h3>\n\n\n\n

The implementation of eUnify’s DATEV connector follows a structured, phase-based approach: a requirements and mapping workshop, DATEV and tax key configuration, parallel-run testing against the existing export process, go-live, and a hypercare phase alongside the first live monthly close.<\/p>\n\n\n\n

Implementation typically takes two to eight weeks, depending on how many subsidiaries are involved and whether payroll import is in scope alongside accounting export.<\/p>\n\n\n\n

\n
\n

FAQs<\/h2>\n\n\n\n
\n
\n