DATEV WooCommerce POS — Gabay sa Integration ng Oliver POS

Oliver POS doesn't have a partnership with DATEV. It supports DATEV the same way any WooCommerce store does — through the DATEV for WooCommerce, which already syncs WooCommerce orders, customers, and refunds into DATEV in real time (or on the schedule you've configured). Once you understand that, the rest of this guide is mechanical: every sale Oliver rings on the counter writes a normal WooCommerce order, the DATEV connector posts it, and your in-store revenue lands on the same DATEV ledger as your online revenue. DATEV does the accounting. WooCommerce is the system of record. Oliver is the till on top.

What DATEV is, exactly

DATEV is the German accounting platform used by the vast majority of Steuerberater (tax advisors). German SMBs typically don't use DATEV directly — the Steuerberater does, and the business hands over data that DATEV can ingest. The WooCommerce + DATEV connector exports orders as DATEV-format CSV files with SKR03/SKR04 account assignments and Umsatzsteuer codes.

For our purposes the important thing about DATEV isn't any specific feature — it's that the WooCommerce connector is mature, well-supported, and treats every WooCommerce order as a first-class transaction in DATEV. Oliver POS doesn't add a second DATEV connector or modify the data path. It writes register sales into WooCommerce, and the existing DATEV connector picks them up.

How Oliver POS feeds in-store sales into DATEV

The DATEV WooCommerce POS flow inside Oliver is short and predictable:

1. The cashier rings the sale on the Oliver register, scans or selects items, and taps Charge.
2. Oliver prompts to attach a Debitor — by email lookup, phone-number lookup, or a fresh Debitor card.
3. The cashier takes payment through whatever WooCommerce payment gateway the store uses.
4. Oliver writes a standard WooCommerce order with the Debitor ID, line items, totals, Umsatzsteuer splits, and payment method.
5. The DATEV for WooCommerce sees the new order through WooCommerce hooks within seconds.
6. The connector posts a Beleg (booking record) to DATEV with the right Umsatzsteuer codes, Debitor, and revenue/payment-account mappings.
7. DATEV's standard processing runs on the new document — journal entries, payment matching, Umsatzsteuer accruals, and any downstream automation you've set up.

End to end, the in-store sale arrives in DATEV before the customer has left the store (in per-order mode) or as part of the next end-of-day summary (in daily-summary mode). Either way, no manual entry is required.

The DATEV WooCommerce connector — what Oliver rides on

Oliver doesn't add a second DATEV connector or duplicate the sync. The plugin Oliver rides on is the standard DATEV for WooCommerce, available at wordpress.org/plugins/datev-for-woocommerce/. It's built specifically to handle the WooCommerce → DATEV data path, including Umsatzsteuer mapping, Debitor matching, refund handling, and the standard reporting flow.

Setup is identical to setup for any WooCommerce store: install the connector, connect to your DATEV account, map the chart of accounts and Umsatzsteuer codes, and let the initial sync run. Once that's done, every WooCommerce order — including every Oliver POS register sale — flows into DATEV on the same path.

Why pushing in-store sales into DATEV matters

Most retailers running DATEV on a WooCommerce store have an online-skewed ledger, because online is where the data has historically flowed automatically. The result is a DATEV ledger that knows everything about online orders and almost nothing about counter sales. The downstream consequences are real:

• GoBD compliance breaks. German tax-compliant bookkeeping requires a complete data trail. A POS that produces a manual end-of-day spreadsheet that the Steuerberater rekeys is exactly what GoBD is meant to prevent.
• The Umsatzsteuer-Voranmeldung is wrong. Monthly or quarterly Umsatzsteuer-Voranmeldungen pull from the DATEV ledger.
• Kassennachschau (the German cash-register inspection) finds gaps. A POS that doesn't produce a DATEV-ready trail is exactly what a Kassennachschau is looking for.

Push Oliver POS sales through the WooCommerce sync and all of those problems resolve at once. DATEV sees one revenue stream, one Umsatzsteuer-liability total, and one customer ledger across online and in-store activity. The bookkeeper's reconciliation against the bank stops being a forensic exercise. The advisor or accountant works from one source. The dashboard finally tells you what your business is really doing — online and in store combined.

What this is NOT

Oliver POS is not a DATEV partner. There is no co-marketing agreement, no revenue share, and no special DATEV pricing for Oliver merchants. Oliver does not insert itself between WooCommerce and DATEV; the data path is exactly the same one any WooCommerce store uses. Oliver doesn't charge a markup, doesn't add a per-transaction fee on top, and doesn't take a cut of the DATEV subscription. Your DATEV account, ledger, and contract are entirely between you and DATEV.

It's also worth saying that Oliver POS doesn't change the data ownership story. The WooCommerce orders table on your own WordPress install remains the source of truth. Oliver writes into it; DATEV reads from it through the connector. If you ever leave DATEV, the data stays where it has always been — in WooCommerce.

Setup in 4 steps

1. Install the DATEV for WooCommerce on your WordPress site and connect it to your DATEV account, mapping the WooCommerce sales, Umsatzsteuer, and payment-method accounts to your DATEV chart of accounts.
2. Verify the initial sync completes and confirm a recent online order appears as the expected Beleg (booking record) in DATEV.
3. Install Oliver POS, sign in to the register on your counter tablet, and confirm the Debitor-capture prompt is enabled at checkout.
4. Run a small live test sale at the counter, attach a Debitor, and confirm the Beleg (booking record) appears in DATEV with the right totals and Umsatzsteuer splits.

FAQ

Does the DATEV export respect SKR03 vs SKR04 account schemas?

Yes. The DATEV WooCommerce connector lets you map WooCommerce revenue, tax, and payment accounts to the SKR03 or SKR04 accounts your Steuerberater uses. Oliver POS sales follow the same mapping.

Is Oliver POS GoBD- and Kassennachschau-compliant for the German market?

Oliver POS is itself the GoBD-compliant register at the point of sale. The DATEV export covers the downstream accounting trail. Together — Oliver POS at the counter, WooCommerce as the order store, DATEV as the export to the Steuerberater — the full GoBD documentation is in place.

Does Oliver POS have a partnership with DATEV?

No. Oliver doesn't partner with DATEV or any other accounting platform. We support DATEV because its WooCommerce connector already pulls orders, refunds, Umsatzsteuer, and Debitors from your store — and Oliver writes every in-store sale into WooCommerce as a standard order, so the same connector picks it up automatically. Your DATEV subscription, your ledger, and your contract stay between you and DATEV.

Does Oliver charge extra to use DATEV?

No. You pay DATEV directly on DATEV's published pricing. Oliver's pricing is a flat monthly POS software fee that has nothing to do with the accounting platform you choose.

Will my in-store and online sales reconcile against one set of books in DATEV?

Yes. Oliver POS writes register sales into the same WooCommerce store that powers your online checkout, so by the time orders reach the DATEV connector they're already a unified order stream. DATEV sees one revenue feed, one Umsatzsteuer-liability total, and one Debitor ledger — no manual reconciliation between an online and an in-store set of books.

Try Oliver POS free for 30 days at /demo/ — bring your existing WooCommerce store and your existing DATEV subscription and have your in-store revenue on the same DATEV ledger as your online orders within an hour. Built for Germany retailers but available wherever WooCommerce runs.