B2B services
Approved service orders become structured invoice cases.
Web2DATEV product line
The invoicing backend for German websites
From the order on a website to a controlled DATEV handover – with one data model, technical validation and an explicit exception path.
Web2DATEV is not another universal shop connector. We start with one revenue process in a website, portal or web app and turn it into an accepted, traceable invoicing route. Direct DATEV services are separate extensions with their own prerequisites.
Target processes
Built for business that begins on the web
IT, SaaS and agencies
Portal, project or subscription events enter one invoice model.
Trades and field service
Job and acceptance data are prepared for invoicing without retyping.
Booking and training
Bookings, references and line items stay traceable through handover.
Four defined products
Start with Core, add only what is approved
Available as a scoped pilot project
Tezza Web2DATEV Core
From the website order to a prepared DATEV handover – without manual double entry in the normal path.
Client resultAn accepted pilot data route for one clearly defined source system and invoice type. Test cases run traceably from the web event to the agreed export; invalid cases arrive in the review area with a readable reason.
Open product
After interface and production approval
DATEV RDS1 Connect
Transfer Web2DATEV documents and structured invoice data to DATEV Unternehmen online through a controlled route.
Client resultFor one approved client, an accepted transfer case runs from Web2DATEV to DATEV Unternehmen online. You can see whether a job was accepted, processed or rejected with a protocol; failed cases remain actionable.
Open product
Extension after API and production review
TRAFFIQX E-Invoice Exchange
Send e-invoices from web processes, receive incoming invoices and trace delivery status.
Client resultAn accepted send and/or receive case for XRechnung or ZUGFeRD. Users see document ID, validation, delivery status, actual channel and original document instead of merely assuming successful transmission.
Open product
With a production-approved connection
DATEV Integration Care
Keep the data route visible, actionable and supportable, even when a source system or interface rejects a case.
Client resultA named support and escalation route, visible job states, prioritised failures and technical evidence for diagnosis and retry. Authorisation data is excluded from operational logs.
Open product
Shared architecture
One event-driven route, not continuous polling
- 1Business event
An approved order, booking or invoice starts the route.
- 2Canonical model
Customer, invoice, items, payments and references are normalised.
- 3Validation
Required fields, arithmetic, format and duplicates are checked.
- 4Controlled output
The case goes to an agreed export/API route or to the exception centre.
Product maturity
What can be promised at which stage
Core can be scoped as a pilot without a live DATEV cloud API. RDS1 and TRAFFIQX are only confirmed after the concrete product, rights, onboarding and production approval have been verified. Care begins with an accepted production route.
No new RDS2 dependency
Rechnungsdatenservice 2.0 can no longer be ordered and ends on 31 December 2026. The product line therefore uses RDS1 for the intended direct document/data handover and does not build a new RDS2 route.
Project price after scope
The price depends on the source system, invoice types, mappings, exception rules and approved target route. The guided intake first produces a technical blueprint; no unvalidated market-price promise is published.
Safe first step
Choose a product and describe one anonymised process
The intake keeps the existing DATEV request, admin and AI-assistant route intact. It asks for system types and process problems, not passwords, tokens or real accounting documents.