Tipalti scales AP automation across the ERP systems Europe runs on.
Tipalti automates the full accounts payable cycle, from supplier onboarding and invoice capture to global payments and reconciliation. The part that decides whether any of it lands is the last one: getting the booking into the customer's own ERP system.
Tipalti books into local ERP systems it never had to build
“With Maesn, we accelerated our European expansion by making complex ERP integrations seamless across Benelux and DACH. As an AP platform, reliable access to key local ERP systems is critical and Maesn gives us exactly that.”
Who Tipalti is, and what runs on Maesn
- Website
- tipalti.com
- About Tipalti
- Founded in 2010, more than 1.000 employees and nine offices across seven countries. Tipalti publishes 90 billion USD in payments processed annually and 750 million USD in total funding to date.Source: tipalti.com/company/
- Use case
- The full accounts payable cycle, from supplier onboarding and invoice capture to global payments and reconciliation. The workflow itself, independent of any one customer, is on the accounts payable automation page.
- Previous solution
- Manual CSV export of booking data, and a few in-house integrations built for selected systems, each carrying its own maintenance.
- ERP systems
- Exact Online, DATEV Rechnungswesen and Dynamics 365 Business Central
- Endpoints
- Get SuppliersPost BillGet AccountsGet Tax RatesPost Document
The ERP system landscape changes with every border
An AP platform delivers its full value only when invoices, payments and bookings land in the customer's own ERP system. In Europe that ERP system is a different product in almost every country.
Customers in the Netherlands run Exact Online, customers in the DACH region rely on DATEV, and mid-market and enterprise buyers expect deep connectivity to ERP systems like Dynamics 365 Business Central. Without those integrations the customer is back to manual rework, which is a sales conversation before it is a support one. Tipalti's published starting point was exactly that: a manual CSV export of booking data between its platform and the customer's ERP system.
Enterprise customers add a second layer to it. An ERP system at that size is rarely the standard product: it carries custom fields, extra objects and conventions that exist only in that one installation, and an integration that only knows the standard shape stops at the first of them. Customization handling is the part of Maesn that reaches those fields, so a customer-specific ERP setup does not turn into a customer-specific integration.
Tipalti concluded that building and maintaining an in-house European integration layer would not yield a viable business case. The study names three reasons:
- The engineering cost of building it
- The deep local product knowledge systems like DATEV demand
- The ongoing maintenance across dozens of platforms
Maesn is the integration layer under every market Tipalti enters
Three reads to find out what a bill has to be booked against, two writes to put it there. The same five against every connected system, through one API.
What makes those five the same five everywhere is the layer underneath. Each system names and shapes a supplier, an account and a tax rate differently, and the common data model resolves that before the data reaches Tipalti's code. Getting a connection at all differs just as widely, which is what unified authentication covers, including customers who run several companies in one system.
Strong adoption in each market the expansion opens up
The rollout the study publishes starts in the Netherlands with Exact Online and continues into DACH, first with DATEV and then with the enterprise ERPs of the German-speaking region.
- Synchronise suppliers, bills, chart of accounts and tax rates across European accounting and ERP systems through a single API.
- Post bookings and documents directly into systems like DATEV Rechnungswesen in line with local accounting standards and GoBD requirements.
- Launch new country markets and new integrations in a fraction of the time required for in-house builds.
- Avoid the cost and complexity of recruiting, training and retaining engineers for each European accounting system.
- Offer customers in DACH, Benelux and beyond a fully integrated, compliant AP workflow from day one.
Read as a list of five that is a product claim. Read against the previous solution it is narrower and more useful: the manual export is gone, and the next country is a configuration step rather than a new integration project. Where a payment has to be matched back afterwards, that is the neighbouring workflow on payment reconciliation. Posting into a local ledger without an export step is what the work looks like from the desk of the financial teams on the other side of it.
Common questions
Which systems does Tipalti connect to through Maesn?
What does the integration actually call?
Why does the rollout start in the Netherlands?
Did Tipalti consider building the integrations itself?
Does Maesn handle the accounting compliance?
Can another AP platform use the same setup?
Turns tracked project time into draft invoices inside the accounting system the customer already runs.Read the case study
Pulls overdue invoices out of the customer's ledger so collection can start without a manual upload.Read the case study
Syncs client data and invoices between the CRM and the DACH accounting systems its customers run.Read the case study
Hands a complete set of books to the tax advisor's system, receipt images and person accounts included.Read the case study