Exact Online + Ziggu

Exact Online and Ziggu connect through Ziggu's public REST API, built by your own integrator or your internal developers. Invoices raised in Exact reach the right client in Ziggu, and project and contact data can move the same way so a project does not have to be set up twice. Exact stays your back office. Ziggu is the client portal where your client sees only what concerns them.

Key takeaways

• There is no Ziggu app inside Exact Online. This connection is built on Ziggu's public REST API, normally by the partner who already looks after your Exact environment.
• Invoices can arrive as a document under an Invoices category, or as a line in Financials with a due date, a status and a running total.
• Project and contact data can move the same way, so a project does not have to be set up twice.
• The schedule is whatever your integrator builds. Ziggu does not impose one on this route.
• Ziggu's API is rate limited to 60 requests per minute across all endpoints, which is what shapes a first load of an existing ledger.

Why connect when Exact already sends the invoice

Exact can already email a PDF, so the sending is not what you are buying. The gap opens about eight invoices later.

On a project that runs for a year or more, a client pays in instalments. By the end, what they paid lives in a mailbox, in an accountant's folder and in somebody's memory. The question that arrives is never about one invoice; it is what is still open and what comes next. That question is unanswerable by email and trivial in a portal, and it is the one that eats the most time from the people who can least spare it.

What Exact holds is your ledger, your suppliers and your margins. None of that is client material, and it is the reason a portal exists at all rather than a shared login.

Project, unit, and why the difference matters here

Ziggu organises work as projects, and a project can hold one unit or hundreds. A unit is the smallest thing a single client has: one apartment in a development, one house, one fit-out, one order. Between project and unit sit optional levels, phases and lots and buildings, which large projects use and small ones never see.

If you run one job per client, your project and your unit are the same record and those levels stay invisible. If you deliver ninety apartments in one development, you use all of them, and every invoice has to find its way to exactly one of them. That is the mapping question your integrator will ask first.

What data moves between Exact Online and Ziggu

The first column is the name your team knows from the app. The second is the endpoint your developer actually calls. Everything here is available on the public API; what your integrator builds is the part that decides what runs.

‍

Where an invoice lands, and why the choice matters

You decide between two destinations before anything is built, and the difference is bigger than it looks.

As a document. The invoice arrives in the client's documents under an Invoices category. Simple, and it sits with the rest of the paperwork for that project.

As a line in Financials. The invoice becomes an instalment carrying a title, a description, a date, a payment deadline, a status and its own attachments. More importantly, the client gets a dashboard instead of a pile: the total, what is paid, what is open and what is still to come.

If you invoice in instalments, the second is the one that removes the phone calls. Decide this first, because it changes what your integrator builds.

How do you connect Exact Online to Ziggu?

This one is built rather than deployed, so the sequence is a project, not a setup wizard.

1. Request an integration token from Ziggu. Tokens are issued per organisation.
2. Decide where invoices should land: as documents under a category, or as instalments in Financials.
3. Agree the mapping. Which Exact record becomes a Ziggu project, which becomes a unit, and how an invoice finds the right client.
4. Your integrator or your own developers build it against api.ziggu.app/public. Endpoint reference: Ziggu API documentation.
5. Test on one client end to end, and look at what they see in their portal before you turn it on for the ledger.

If you would rather not build anything, a ready-made connector platform can do the same job. That is the route behind Microsoft SharePoint and Teamleader Focus. And if you want Ziggu to build and run the connection, that is how Salesforce and Eenvoudig Factureren work.

Where teams use it

Portfolios where the invoice count is the problem

A hundred-unit project with nine instalments is nine hundred invoices. Sending those by hand is not admin, it is a job.

Keeping the ERP out of the client's view

Exact holds every client, every supplier and every margin you have. Ziggu shows each client their own project and nothing else, which is what makes access safe to give.

Running it across a portfolio

Once projects and units exist in Ziggu, everything else attaches to them: documents, decisions, reports. See how property developers use Ziggu.

What Exact Online and Ziggu do not do

• There is no Ziggu app in Exact Online and no connector inside it. Somebody builds this, and that somebody is usually the partner who already runs your Exact environment.
• Ziggu does not set the schedule. How often it runs, and whether it reacts to an event or polls, is what your integrator builds.
• Payments are not collected in Ziggu. The client sees the status of an instalment; the money moves the way it moves today.
• Data flows from Exact into Ziggu. Nothing is written back unless your integrator builds that too.
• Ziggu's public API has no webhooks, so a connection built on it polls rather than listens. Task management and milestones have no endpoint at all.

Questions about the Exact Online integration

Is there a Ziggu app for Exact Online?

No. The connection is built on Ziggu's public REST API, usually by the partner who already looks after your Exact environment.

Where do invoices appear for the client?

Wherever you decide before it is built: as a document under an Invoices category, or as an instalment in Financials with a due date, a status and a running total.

How often does it sync?

Whatever your integrator builds. Ziggu does not impose a schedule on this route.

Can we sync projects and contacts too?

Yes. Projects, units, contacts and companies all have endpoints, so a project can be created in Ziggu from Exact rather than set up by hand.

Can clients pay through Ziggu?

No. Ziggu shows what is due and what is paid. Collection stays where it is today.

We would rather not build anything.

Then use a ready-made connector platform, the route behind Microsoft SharePoint, or pick an invoicing tool Ziggu connects itself, such as Eenvoudig Factureren.

Last verified: 28 August 2026.