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.
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 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.
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.
Supplier invoices arrive by email or upload, as PDF or as XRechnung and ZUGFeRD e-invoices.
Agents read each invoice, propose supplier, account, tax key and cost centre, and route it for approval.
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.
| Object | Direction | Interface |
|---|---|---|
| Document (PDF) with booking proposal | Orcha to DATEV Unternehmen Online | Rechnungsdatenservice 1.0 |
| E-invoice (XRechnung, ZUGFeRD) | Orcha to DATEV Unternehmen Online | Rechnungsdatenservice 1.0 |
| Journal entries for invoices, credit notes and receivables (booking batch) | Orcha to DATEV Rechnungswesen | DATEV booking batch (Buchungsstapel) |
| Chart of accounts, suppliers, cost centres | DATEV to Orcha | Imported during setup |
| Booking history | DATEV to Orcha | Exported during setup, then read continuously from DATEV Rechnungswesen |
| Posted entries | DATEV Rechnungswesen to Orcha | DATEV data service |
Most German companies book through an accounting firm, some book themselves, many run more than one entity.
Your accounting firm keeps working in DATEV as before, but receives coded documents instead of a pile of PDFs.
Your accounting team posts in DATEV Rechnungswesen itself. Orcha takes over the capture and coding.
Each company has its own DATEV client with its consultant and client number, kept strictly separate.
Who books, and in which DATEV client.
In DATEV, by you or your accounting firm.
Through DATEV's data service.
So Orcha codes the way your firm does.
Check the first handovers together with your firm.
Documents go through DATEV's official interface, not a CSV import.
Each company's data is isolated, with its own DATEV client.
Hosted in the EU, processing under a GDPR data processing agreement.
Documents archived unalterably, every coding and approval recorded.
Anything else? Talk to the team that builds the integration.
Book a demoOrcha 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.
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.
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.
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.
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.
Yes. Orcha receives and validates XRechnung and ZUGFeRD and sends them to DATEV Unternehmen Online coded, the same way as PDF invoices.
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.
Yes. Each company has its own DATEV client, with its own consultant and client number, and its data is kept strictly separate in Orcha.
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.
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.
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.