Our story

Built by someone who closed the books with the other tools.

Meulenbase began at month-end in an international group: a consolidation tool that only two people could open, three reports nobody could extend, and a pack rebuilt by hand in Excel. So we built the opposite: one place where the finance team owns every number, every report and every close, without waiting on anyone.

“Define a number once. Use it everywhere. Let it explain itself.”

The idea the whole platform is built on

How it came about

Four chapters, one recurring problem.

  1. The frustration

    Month-end in a group should not feel like this.

    Years of closing the books in an international group with the established consolidation tools meant the same frustrations every month. Data entered only through an integration the IT department owned, or through an Excel add-in two licensed people could use. Three reports had been set up by a consultant once, and nobody in the company knew how to add a fourth, or how to load a dataset the template had not foreseen.

    The monthly pack was a hand-built workbook linked to the tool, refreshed by hand, hoping the links held. There were no dashboards and no charts. A consolidated figure could not be explained without rebuilding it line by line in Excel.

  2. The realisation

    The arithmetic was never the problem.

    The established tools consolidate correctly. What costs the finance team its month is everything around the arithmetic: how data gets in, who may open a figure, who can build the next report, and whether a number can explain itself. Those are design choices, and they can be made differently.

  3. The build

    So the platform was built around those choices.

    Every row carries its entity and its counterparty, so any set of entities behaves as a group and eliminations follow from the data. Every number is a named measure with filters, inspected on its rows while it is defined, and every report, chart and dashboard is a layout over those measures. Every list is the same Excel-like table.

    Scope is a parameter: any entities, any reporting currency, eliminations on or off, with one request each. Unknown is never zero. Every output exports from the browser into Excel, PowerPoint or a slide.

  4. Today

    From raw file to closed month, in one browser.

    Uploads, movement schedules, journals and the consolidation run all land in one balances dataset. The translation engine turns every row into cells per reporting currency, and reports, charts and dashboards read those cells with one request. The close board, the lock and the audit trail sit on top. The whole path is designed for the person who owns the numbers, from a laptop or a phone, in Singapore or Frankfurt.

What we stand for

Principles, not buzzwords.

See what it does

One request per question

Opening a report, changing a parameter and clicking into a cell are the interactions the platform is judged by. Each is one request, served from a cache that data changes invalidate.

The finance team builds it

Datasets, hierarchies, measures, reports, charts and dashboards are made by the person who owns the numbers, in the browser, with no developer and no consultant.

Every figure can explain itself

Rows, journal, rate and definition version behind every number. Incomplete cells say so. Immutable versions and an audit trail, so an auditor sees who changed what and when.

What it does

From the first file to the closed month.

The five problems, the ten things done differently, and every capability from upload to audit trail. Already have an account? Sign in to open your reports.

Sign inSee what it does