What sits between NetSuite and DATEV is not a file, it is a translation: your chart of accounts onto SKR03 or SKR04, your tax codes onto DATEV keys, your customers and vendors onto DATEV number ranges. DATEV Mapping defines that once — after which the batch is produced at the push of a button, or on its own.
It fails on the translation. NetSuite thinks in its own chart of accounts, DATEV in SKR03 or SKR04 — and in between sits somebody with a spreadsheet, every month. The result only shows at the tax firm, when the import rejects rows.
Export, rebuild, sort columns, fix formats — every month again, and every time by hand. The routine is so established that nobody asks why it exists.
One new NetSuite account without a counterpart in the chart breaks the whole batch. The person who notices is usually the accountant — and they bill the rework.
NetSuite tax codes and DATEV keys are two systems. Without a fixed mapping, revenue ends up in the books under the wrong key.
Customers and vendors need DATEV-compliant numbers. Create them in NetSuite and that is exactly what is missing — so the document stalls.
Whatever fails on import comes back as a question: a week later, in the middle of the close, to the same person who built the export.
The delivery to the tax firm has a date. If the person who knows the export is away, the date slips — knowledge in one head is the real risk.
Three mappings carry the entire process. They are set during onboarding, live as records in NetSuite, and are only touched again when the chart of accounts actually changes.
An assistant walks through the base configuration: entity, chart of accounts, period, target folder. No project, no interface, no second platform.
Accounts, tax codes and master data are linked once. Whatever is added later is reported by the validation on its own.
The monthly run starts at the push of a button — or runs automatically once scheduled, validation log included.
All entries of a period in DATEV format, strictly per the official specification.
NetSuite accounts onto the matching DATEV accounts, for instance SKR03 or SKR04.
Tax codes are assigned to the correct DATEV keys — set once, constant afterwards.
Customers and vendors in DATEV format, in the same run as the postings.
Missing mappings, implausible amounts and gaps are named before the file is created.
Once scheduled the export runs by itself — with a log, so nobody has to guess whether it did.
An assistant walks through the initial configuration step by step, validating at each stage.
Runs in every edition of Oracle NetSuite — no additional module required.
Data leaves NetSuite only as a finished file. No external service, no copy in transit.
The mapping is made for accounting and controlling teams in German NetSuite accounts that hand all or part of their bookkeeping to a tax firm — and for NetSuite owners whose monthly export currently depends on a single person.
Native SuiteScript inside the account — no middleware, no data replication.
SuiteBundle 597578 — installation and updates through NetSuite’s bundle mechanism.
DATEV format per the official specification, including the header with entity, chart of accounts and period.
SKR03 and SKR04 — or a custom chart if your tax firm uses a different one.
Files in the NetSuite file cabinet, ready to hand on without rework.
Manual run or scheduled monthly run, each with a log.
Because that is where the difference lies. Exporting a file is easy; the work sits in the mapping — translating chart of accounts, tax keys and master data cleanly from NetSuite into the DATEV world. Function and scope are unchanged.
SKR03 and SKR04 are the standard case. If your tax firm uses a different chart, the mapping is set accordingly — it is a table, not a hard-wired chart of accounts.
The validation triggers before the file is produced: you see which account has no DATEV counterpart yet and complete the mapping. No incomplete batch reaches the tax firm.
Yes. Once set up, the monthly export runs on schedule, including validation and log. The button stays available for interim runs.
Yes, in the same run. Master data is transferred in DATEV format so the postings meet accounts that already exist at the tax firm.
Yes — the plug-in is compatible with all editions of Oracle NetSuite and needs no additional module.
An assistant guides the configuration, and we set the mappings together once. After that the monthly effort is a matter of minutes.
We set up the mapping for a section of your accounts and export one month as a DATEV batch — ready for your tax firm to review.