Design partners We're building agentic inventory management and are looking for design partners to shape it with us. Agentic inventory design partners Contact us
OrchaDATEV

Orcha × DATEV. Pre-coded, straight into DATEV.

Orcha captures, checks and codes your supplier invoices and sends each document with its booking proposal to DATEV Unternehmen Online and hands over the journal entries as a booking batch for DATEV Rechnungswesen. Once your tax advisor or your own team has posted them, Orcha reads the entries back and checks them. Built on top of DATEV, not instead of it.

  • Two-way: Unternehmen Online and Rechnungswesen
  • SKR 03, SKR 04 or your own chart of accounts
  • Works with your accounting firm
DATEV products
DATEV Unternehmen Online and DATEV Rechnungswesen
Interface
DATEV data services, including Rechnungsdatenservice 1.0
Direction
Two-way: documents to Unternehmen Online, journal entries to Rechnungswesen, postings back from Rechnungswesen
Chart of accounts
SKR 03, SKR 04 or your own
Posting
In DATEV, by your tax advisor or your team
Availability
Available today

Orcha prepares. DATEV keeps the books.

The work before the booking runs in Orcha. DATEV stays the system of record, and your accounting firm keeps the final review, the VAT return and the year-end close.

Orcha takes over
  • Intake of supplier invoices and credit notes from inboxes, uploads and e-invoices
  • Capture of header data and line items
  • Coding: supplier, account, tax key, cost centre
  • Approval routing by amount, cost centre and supplier
  • Documents and booking proposals to DATEV Unternehmen Online
  • Journal entries as a DATEV booking batch for DATEV Rechnungswesen
  • Receivables: outgoing invoices and customer credit notes, with their journal entries
  • Checking the posted entries against the proposal
Stays in DATEV
  • The posting in DATEV Rechnungswesen
  • Final review and sign-off of the books by your accounting firm
  • VAT returns and the year-end close
  • Your firm's chart of accounts and master data

Orcha's DATEV interface: two routes into DATEV.

Orcha works with both sides of DATEV. Documents go to DATEV Unternehmen Online, journal entries to DATEV Rechnungswesen. The booking happens in DATEV, by your tax advisor or your accounting team.

DATEV Unternehmen Online
  • Document as PDF or e-invoice, with a booking proposal
  • Handover through Rechnungsdatenservice 1.0
  • The document sits in your company's stock, ready for your firm
  • Prerequisite: Rechnungsdatenservice 1.0 is enabled for your company
DATEV Rechnungswesen
  • Journal entries as a DATEV booking batch (Buchungsstapel), a file in DATEV format
  • Read in and booked by your tax advisor or your accounting team
  • Chart of accounts, suppliers and booking history taken over at setup
  • Posted entries read back and compared with the proposal

How data flows between Orcha and DATEV.

Orcha learns your chart of accounts and booking history at setup, sends every approved invoice to DATEV Unternehmen Online, hands over the journal entries for DATEV Rechnungswesen and reads the posted entries back.

01 · InEvery channel

Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.

02 · OrchaCapture, code, approve

Agents read each invoice, propose supplier, account, tax key and cost centre, and route it for approval.

03 · DATEVBooked, then checked

Document and booking proposal land in DATEV Unternehmen Online. Once posted in DATEV Rechnungswesen, Orcha compares the entry with its proposal and flags differences early, not at month-end.

ObjectDirectionInterface
Document (PDF) with booking proposalOrcha to DATEV Unternehmen OnlineRechnungsdatenservice 1.0
E-invoice (XRechnung, ZUGFeRD)Orcha to DATEV Unternehmen OnlineRechnungsdatenservice 1.0
Journal entries for invoices, credit notes and receivables (booking batch)Orcha to DATEV RechnungswesenDATEV booking batch (Buchungsstapel)
Chart of accounts, suppliers, cost centresDATEV to OrchaImported during setup
Booking historyDATEV to OrchaExported during setup, then read continuously from DATEV Rechnungswesen
Posted entriesDATEV Rechnungswesen to OrchaDATEV data service

What Orcha covers with DATEV.

Built for how DATEV works. With or without a firm.

Most German companies book through an accounting firm, some book themselves, many run more than one entity.

With a firmYour tax advisor books

Your accounting firm keeps working in DATEV as before, but receives coded documents instead of a pile of PDFs.

In houseYour own team books

Your accounting team posts in DATEV Rechnungswesen itself. Orcha takes over the capture and coding.

Several entitiesOne account, separate clients

Each company has its own DATEV client with its consultant and client number, kept strictly separate.

Set up with your firm. Checked before go-live.

  1. 01
    Agree on the setup with your accounting firm

    Who books, and in which DATEV client.

  2. 02
    Enable Rechnungsdatenservice 1.0

    In DATEV, by you or your accounting firm.

  3. 03
    Connect Orcha to DATEV Unternehmen Online

    Through DATEV's data service.

  4. 04
    Chart of accounts, suppliers and booking history

    So Orcha codes the way your firm does.

  5. 05
    First documents, then go-live

    Check the first handovers together with your firm.

Connected securely.

DATEV's own data service

Documents go through DATEV's official interface, not a CSV import.

Separate clients

Each company's data is isolated, with its own DATEV client.

EU data residency

Hosted in the EU, processing under a GDPR data processing agreement.

GoBD and audit trail

Documents archived unalterably, every coding and approval recorded.

Orcha and DATEV: questions.

Anything else? Talk to the team that builds the integration.

Book a demo
Does Orcha post directly in DATEV?

Orcha prepares the journal entries and hands them over as a DATEV booking batch (Buchungsstapel) for DATEV Rechnungswesen. It also sends the document with a booking proposal to DATEV Unternehmen Online. The entries are imported and finally posted in DATEV, by your tax advisor or your accounting team.

What is Orcha's DATEV interface?

Orcha (getorcha.com) works with two sides of DATEV. The document and booking proposal go to DATEV Unternehmen Online through Rechnungsdatenservice 1.0, and the journal entries go to DATEV Rechnungswesen as a DATEV booking batch (Buchungsstapel). The booking stays with your tax advisor or your accounting team.

What is the difference between Rechnungsdatenservice and a booking batch?

Rechnungsdatenservice 1.0 is DATEV's interface for documents: it brings the invoice with its booking proposal into DATEV Unternehmen Online. A booking batch (Buchungsstapel) is a file in DATEV format with finished journal entries that is read into DATEV Rechnungswesen. Orcha uses both, depending on the target.

Which DATEV products does Orcha use?

Both. DATEV Unternehmen Online for the handover of documents and booking proposals, through DATEV's Rechnungsdatenservice 1.0, and DATEV Rechnungswesen for journal entries as a booking batch and to read the posted entries back and compare them with the proposal.

What does my tax advisor need to do?

Enable Rechnungsdatenservice 1.0 for your company in DATEV, if it isn't already. After that, your accounting firm books the way it always has.

Can e-invoices go to DATEV?

Yes. Orcha receives and validates XRechnung and ZUGFeRD and sends them to DATEV Unternehmen Online coded, the same way as PDF invoices.

Does Orcha replace my tax advisor?

No. DATEV stays your system of record and your accounting firm keeps the final review of the books. Orcha takes over the capture and coding before it and prepares the journal entries.

Does it work with several companies?

Yes. Each company has its own DATEV client, with its own consultant and client number, and its data is kept strictly separate in Orcha.

What is a DATEV booking batch (Buchungsstapel)?

A DATEV booking batch is a file in DATEV format that bundles several journal entries and is read into DATEV Rechnungswesen. Orcha (getorcha.com) creates it from approved and coded documents, and your accounting firm or team reads it into DATEV and books it.

Which data goes to DATEV, and which stays in Orcha?

The document, the booking proposal and the journal entries of approved invoices go to DATEV. Intake, checks, the approval history and the full audit trail stay in Orcha. From DATEV, Orcha takes your chart of accounts, suppliers, cost centres and booking history at setup, and reads the booking history from DATEV Rechnungswesen continuously afterwards.

Does Orcha also hand over outgoing invoices and credit notes to DATEV?

Yes. Orcha (getorcha.com) hands over the journal entries for supplier invoices, outgoing invoices and credit notes as a DATEV booking batch for DATEV Rechnungswesen.