Post-merger finance: two platforms, one truth

After the merger of Goboony and Yescapa, CFO Uwe van Rensburg ran a full ERP selection and walked away. What he built instead to consolidate two platforms across 10 countries.

The Actuals teamActuals · 3 min read

On Monday the board sees a number. On Wednesday it is a different one. By Friday both have moved again, and the finance team spends the week explaining the gap instead of closing it.

Uwe van Rensburg knows that week well. He became CFO of Goboony in August 2023 and walked straight into a cross-border merger with French competitor Yescapa. A fast-growing Dutch marketplace for camper rentals became a European group operating in 10 countries. It now ran on two platforms, two ERPs and a patchwork of PSPs, currencies and VAT regimes. In this episode of High Volume Accounting Live, he tells Peter Engel what financial control looks like in that setup.

The drift had to stop

Uwe describes the starting point in one sentence.

"On a Monday see a number, on a Wednesday we get a new one, and by the Friday they both look a little bit different than on the Thursday. That’s what we’re moving away from now."

The drift is not a reporting problem. The data underneath is still moving when the report is pulled.

A full RFP that ended in no

After the merger, the group did what most CFOs would do. It ran an RFP for the big ERP names, compared modules and estimated the cost. Then it did not sign.

"The complexity of a really big ERP onto our platform, which already has all the logic, just didn’t make sense."

The platform already decides what happens to a booking. A big ERP would have meant rebuilding that logic in a second place and changing the ERP every time the business changed.

Marketplace money is not all yours

The deeper reason is the nature of the money itself.

"A hundred euro might come in, but it’s not all our one hundred euro. It’s not an e-commerce platform."

Part of that money has to be safeguarded separately, and the company has to be able to show who it belongs to.

Some of each payment belongs to the camper owner. Part is held for the traveller until the trip, and part is insurance. Each part has its own owner and treatment, so the books have to split it the moment the money arrives.

A booking keeps changing

On top of that, a booking is not one transaction.

"In the basic model it’s not so complicated. But a booking, a single booking has many different flows. There are modifications like cancellations, extensions. There are post-trip events that still happen and have impact, like disputes and claims."

A cancellation reverses revenue and triggers a refund. An extension adds revenue, possibly with different VAT. A claim reaches insurance. If each event lands in the ledger as a separate entry, the link to the booking is lost.

Two ERPs, one layer above

So the group kept both ERPs, one for France and one for the Netherlands. Above them, it built a consolidation layer through API integrations, with intercompany and elimination logic that finance owns. Each system keeps doing what fits its market, and the seam between them sits where finance can see it and change it.

Uwe describes where they stand now: "Now we have basically inter-day positions on statements, on both consolidated level for all three entities."

The order mattered. Reconciliation came first, then platform consolidation, then speed. "Starting from a shaky foundation and just jumping, that would have been too much of a risk. Now I can move the finance function into new places because it’s reliable."

AI will not fix it

Uwe also explained what happens if you skip the foundation and go straight to AI. Point the strongest model at their 40 different Excel sheets, he said, and the first month may look close to correct. Then the deviations start.

"And the month after that, you will try to force an answer and fix the deviation with some numbers that, if you add them together, they also make a 10."

The totals add up. Whether they reflect what happened is a different question.

What to take from it

Uwe closed with a line about culture that also fits finance.

"Freedom needs an outline for it to really be the best it can be."

For a marketplace, the outline is the data architecture. Finance knows at receipt whose money it is and follows every booking through its changes. And it keeps the consolidation logic in its own hands.

Merging or adding a market? Check first whether your numbers still drift between Monday and Friday. The Actuals scan takes 15 minutes and shows where your payouts and your books first stop matching.

In practiceNew country, new PSP, new currency. Same close?

Written by

The Actuals teamActuals