Nordhealth turns invoices written at the practice into bookings in DATEV.
Nordhealth builds practice management software for veterinary and therapy clinics, from Provet Cloud in 44 countries to Vetera in the German-speaking market. In veterinary care the invoice is settled on the spot by the animal owner, which puts billing at the centre of the software rather than at the end of it.
Who Nordhealth is, and where Maesn sits in it
- Website
- nordhealth.com
- About Nordhealth
- A Nordic practice management software provider, building since 2001 and listed on Euronext Growth Oslo, where it raised €120M. Over 400 people work from 18 offices in ten countries, and more than 13.000 clinics and hospitals run on its products.
- The product here
- Provet Cloud, veterinary practice management available in 44 countries with over 70.000 customers. Vetera, its German-speaking sibling, was serving more than 2.000 practices, clinics and partners in Germany, Austria and Switzerland when Nordhealth acquired it in 2022.
- Use case
- Getting the content of a finished invoice into the accounting system without anyone at the practice handling it. The workflow itself, independent of any one product, is on the invoice creation page.
- Previous solution
- CSV export and import, with manual work in between that produced errors and delays in the accounting process.
- Accounting systems
- DATEV Rechnungswesen and DATEV Unternehmen Online, the two products this flow needs, with the other accounting systems its customers keep on the same connection
The invoice is complete before the accounting system sees it
Veterinary care is paid for on the spot. The animal owner settles at the counter, so the invoice is not a claim that gets chased later, it is the moment the practice earns its money.
That makes billing a core part of practice software rather than a module at the edge, and it means the invoice is assembled where the work happens. By the time it is issued, the debtor, the articles, the services, the tax rates, the service periods, the cost centres and the charge factors are all set, and they are set by the person who knows them.
The default way out of a practice system is a file, and Nordhealth's own products show it. Vetera lists four accounting destinations on its integrations page, and every one of them is a transfer rather than a connection: DATEV data emailed to the tax advisor to be read in, Lexware moved across by click, Banana as a data transfer, Eurofibu through an export interface. Provet Cloud lists more than 150 partners across eight categories, and of the six entries under finance and reporting, one is an accounting system.
A CSV in between is where the detail goes. Someone has to map columns, someone has to fix what the mapping got wrong, and the accounting month waits for both. The practice, meanwhile, has already done the work twice: once at the counter and once for the export.
What arrives in DATEV is a booking rather than a file
The invoice does not travel as an invoice, and it could not: on the systems these practices keep, the invoice is often not an object at all. What every accounting system does keep is the booking.
A finished invoice with its lines: the debtor, every article and service, a tax rate per line, the period the work belongs to.
Ten of the 30+ connected systems accept an invoice. Exactly one accepts its lines.
A booking on DATEV Rechnungswesen or a booking proposal on DATEV Unternehmen Online, the rate read from the system itself, the document attached, the person account written where the booking lands.
Neither DATEV product accepts an invoice or its lines. Both expose their tax rates and both take a document.
The debtor is the clearest case of why this needs translating. On sevdesk or Lexware Office the animal owner is a customer record. On DATEV Rechnungswesen there is no customer object at all, and the same person is a contact, because that is what a person account is called there. The common data model resolves that before Provet Cloud has to know about it, which is the difference between one integration and one per accounting system.
The tax rates work the same way round. A veterinary invoice can carry several of them, and which rate is valid is decided by the receiving system rather than by the practice software, so the booking is written with the rate that system defines. Everything downstream of that, from the advance return to the annual accounts, is the tax automation side of the same data.
Nothing has to be typed a second time
The bookings now leave Provet Cloud on their own. Nobody at the practice starts an export, corrects a mapping or waits for the accounting month to catch up.
What a veterinary practice wants from its software is time with animals, and every minute spent on a bookkeeping export is a minute it did not get. Removing that step does not just save the export itself, it removes the corrections after it and the delay behind those, which is where a manual handover actually costs.
For Nordhealth the same change shows up somewhere else: in what its own teams have to handle. An export that nobody runs is an export nobody supports, and an accounting system that is already reachable is one that does not need a project of its own when the next market asks for it. The mechanics of that, from onboarding a practice to the questions that never reach a support queue, are on the page for customer success teams.
Common questions
Which DATEV product does the data reach?
Why a booking rather than the invoice itself?
Do articles and cost centres become records in the accounting system?
Does the document travel with the booking?
Does this only work for German practices?
Could another practice-management vendor use the same setup?
Reads the ledger through Maesn and keeps the bank side on its own connection, then writes the reconciled bookings back.Read the case study
Automates the full accounts payable cycle and posts every payment back into the customer's ERP.Read the case study
Turns tracked project time into draft invoices inside the accounting system the customer already runs.Read the case study