All articles
Getting started

Connecting your accounting to your rental system — Holded, e-Boekhouden and the NL/ES dual administration

Retyping every booking into your accounting costs time and creates errors. Here's how a link between your rental system and Holded, e-Boekhouden or Moneybird actually works.

Laurens BosJune 22, 20266 min read

A booking comes in, the customer pays, an invoice goes out — and then that same evening you retype the whole thing into your accounting package. Create the customer, enter the invoice, match the payment. A few minutes per booking; with dozens of bookings a month, a few hours, and every time a chance of a typo, a wrong amount, a duplicate customer. A link between your rental system and your accounting turns that into one flow: what happens in your rental system shows up in your accounting on its own. This piece explains how that works — for Holded, e-Boekhouden, Moneybird and similar packages — and what it takes when you, like many rental operators on the Costa Brava, run accounting in two countries.

What a connection actually does

An accounting connection synchronises the things that exist in both systems, so you only have to enter them once:

  • Customers. A new renter in your rental system becomes (or matches with) a contact in your accounting — with address, VAT number, email. No duplicate entry, no "that customer is already in there three times".
  • Invoices. An invoice your rental system creates — for the rent, the deposit, extras — appears as a sales invoice in your accounting, with the correct VAT code and ledger account.
  • Payments. When a payment comes in (via your payment provider, or a bank connection), the invoice in your accounting is marked "paid" and the payment is matched to it. No manual reconciliation.
  • Optionally: credit notes and corrections. A cancelled booking, a partially refunded deposit — if your system handles that cleanly, the credit note can flow through automatically too.

The idea is the same single-source principle as everywhere else: a piece of data belongs in one place. Your rental system is the source for "what was rented and invoiced"; your accounting reads that and handles the bookkeeping side. You don't retype anything. (That same single-source principle is what underlies preventing double bookings — the same reason Excel as an availability calendar breaks sooner or later.)

How it works technically

In practice there are two ways:

Via the accounting package's API. Holded, e-Boekhouden, Moneybird, Exact, Snelstart — almost every modern package has an API to create and read invoices, contacts and payments. Your rental system calls that API when something happens: booking confirmed → create customer + invoice in accounting; payment received → mark invoice paid. This is the clean way — real-time, no in-between step.

Via a middleman or export/import. If your package doesn't have a usable API, or you want to keep it simple, you can periodically export (invoices as a file) and import them — or put a connector service in between. Less elegant, not real-time, but works. Whether your current rental system even has a decent API is one of the criteria in comparing rental software in 2026 — many SaaS packages are surprisingly limited here.

What you need to set up beforehand, either way:

  1. A mapping of VAT codes and ledger accounts. What VAT applies to the rent, to the deposit (which usually isn't revenue, so it's treated separately), to extras? Which ledger account? You agree this once and the system applies it automatically from then on.
  2. What does your rental system do with the deposit? A deposit isn't revenue — it's an amount temporarily held in trust. How that should appear in the books (suspense account, not revenue) is something you agree on so the connection posts it correctly.
  3. How do customers get matched? On email, on VAT number, on name? You don't want the same customer to end up as two contacts.
  4. What wins in a conflict? If an invoice has been edited manually in the accounting, does the connection overwrite it? Usually not — the accounting is then the lead for that record. Those kinds of rules you nail down up front.

The NL/ES dual administration

Many rental operators on the Costa Brava (and similar: a Dutch entrepreneur with a Spanish activity) keep two sets of books: a Dutch one and a Spanish one, each with its own VAT rules, its own package, its own accountant. Holded is popular in Spain; e-Boekhouden, Moneybird or Exact in the Netherlands. That makes the connection a bit more involved — but not impossible:

  • Which booking belongs where? A rental of a property in Spain to a Spanish guest is a Spanish invoice (Spanish VAT, Holded). A rental via your Dutch entity might be a Dutch invoice. Your rental system needs to know which entity/country belongs to which property and which customer, and send the invoice to the right accounting.
  • Two connections, not one. In practice you connect your rental system to both packages, each with its own mapping (VAT codes, ledger, customer matching). The system routes each invoice to the right one.
  • One overview for you. The nice part: even though the accounting is split, your operational overview — what's rented, what's paid, what's outstanding — stays in one place inside your rental system. The split only exists on the accounting side, not in your daily work.
  • Coordinate with your accountants. The VAT mapping and entity routing are things you set up together with your Dutch and your Spanish accountant — once, properly, then automatic. (That bilingual, two-country setup is exactly what Webstability is built around; see why your rental system should run in two languages.)

What it costs to build a connection

An accounting connection is usually not a standalone project but a part of your custom rental booking system — with a Rental Panel (EUR895/mo) or a Custom Admin Panel (EUR1,295/mo) the connection is simply included, as is the work to keep building on it (adding another package, changing the mapping, a new VAT category). No separate project invoice, no "that wasn't in scope" — just part of the monthly fee. If you want a pure connection bolted onto an existing system I don't build, you fall outside the panel model; that's not what I do, those are loose Zapier-style integrations or a different kind of developer.

When this fits

You run dozens of bookings a month or more, you keep books in NL or ES (or both), and the manual retyping is starting to eat real hours — or causing real mistakes. You want one system instead of five disconnected tools, with one person on the other end.

When it doesn't

You have five bookings a month and a simple spreadsheet for your accountant — a full connection is overkill. Or you're happy with your current rental SaaS and just need a one-off Zapier-style export; that's a different conversation, and probably a different developer.

To finish

Retyping every booking into your accounting is time you don't have to spend — and a source of errors you don't need. A connection between your rental system and your accounting package lets customers, invoices and payments flow through on their own, with the VAT and ledger mapping agreed once. Work in two countries, and you simply connect two sides — while your daily overview stays in one place.

Want to know whether your accounting package connects well and what it would cost in your situation? Send me which package you use (NL and/or ES) and how many invoices you run per month — honest answer within a day, no pitch deck. Or have a look at the rental booking system page for the full picture.

LB

Laurens Bos

By · webstability.eu

Also relevant