Eenvoudig Factureren + Ziggu

Eenvoudig Factureren and Ziggu are connected by Ziggu. We build the connection and we run it, so there is nothing to install and nothing for your team to maintain. Every invoice you create in Eenvoudig Factureren reaches the right client in the right project, and the client is notified. Eenvoudig Factureren stays where you invoice. Ziggu is the client portal where your client sees what they owe and what they have paid.

Key takeaways

• Ziggu builds and runs this connection. No uploads, no exports, no plugin.
• An invoice 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. You choose.
• The client is notified by email or in the app the moment a new invoice is available.
• This is an invoicing connection. Contacts and projects are not created by it.
• A hundred units with nine instalments each is nine hundred invoices that nobody has to file by hand.

Why connect when the invoice already goes out by email

Eenvoudig Factureren already emails a PDF, so the sending is not the problem. The problem starts about eight invoices later.

On a project that runs for a year or more, a client pays in instalments. By the end, the record of what they paid lives in a mailbox, in an accountant's folder and in someone's memory, and the question that arrives is never about one invoice. It is: what is still open, and what is coming next.

That question is unanswerable by email and trivial in a portal. It is also the question that generates the most calls to the people who can least afford them.

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 each client only ever sees their own.

What data moves between Eenvoudig Factureren and Ziggu

The first column is the name your team knows from the app. The second is the endpoint a developer would call if you ever wanted to extend this on Ziggu's public API.

‍

Where an invoice lands, and why the choice matters

You pick one of two destinations, and the difference is larger 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 option is the one that removes the phone calls. The first is enough if the invoice is really just a document to keep.

How do you connect Eenvoudig Factureren to Ziggu?

1. Ask Ziggu for the Eenvoudig Factureren connection. Because we build and run it, this starts as a conversation rather than an install.
2. Decide where invoices should land: as documents under a category, or as instalments in Financials.
3. Agree how an invoice finds its client, so that the right person sees the right document and nobody sees anybody else's.
4. Invoice one client end to end and look at what they see before you switch it on for everything.

If you would rather build or extend it yourself, the same endpoints are available on Ziggu's public REST API. Endpoint reference: Ziggu API documentation.

Where teams use it

Portfolios where the invoice count is the problem

A hundred-unit project with nine instalments is nine hundred invoices. Filing those by hand is not an admin task, it is a job. This is the case the connection was built for.

Cutting the payment questions before they arrive

A client who can open their own payment schedule does not call to ask what is left. The overview does the answering.

Keeping the finance system out of the client's view

Your invoicing tool holds every client you have. Ziggu shows each client their own project and nothing else. See how property developers use Ziggu.

What Eenvoudig Factureren and Ziggu do not do

• This connection carries invoices. It does not create projects or contacts in Ziggu; those come from your CRM or are set up in Ziggu itself. If you want deals to become projects, see HubSpot and Ziggu or Salesforce and Ziggu.
• Payments are not collected in Ziggu. The client sees the status of an instalment; the money moves the way it moves today.
• Nothing is written back into Eenvoudig Factureren by this connection.
• Ziggu's public API has no webhooks, so anything you build yourself polls on a schedule rather than listening for events.
• The API is rate limited to 60 requests per minute across all endpoints, which is what shapes a first load of an existing portfolio.

Questions about the Eenvoudig Factureren integration

Do we have to upload anything?

No. Creating the invoice in Eenvoudig Factureren is the whole action.

Where does the invoice appear for the client?

Wherever you choose: as a document under an Invoices category, or as an instalment in Financials with a due date, a status and a running total.

Does the client get notified?

Yes, by email or in the app, as soon as the invoice is available in their portal.

Can the client pay through Ziggu?

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

Does this create the project too?

No. This connection carries invoices. Projects and clients come from your CRM connection or from Ziggu itself.

Does the client need an Eenvoudig Factureren account?

No. Clients only ever see Ziggu.

Last verified: 28 August 2026.