--- title: "EenvoudigFactureren Integration" description: "EenvoudigFactureren is Belgian small business invoicing software. Agents manage clients, contacts, and stock items, create and send documents by email or post, record payments and reminder costs, and pull document files and events." url: https://flowrunner.ai/integrations/eenvoudigfactureren date_modified: 2026-09-04T14:53:04-07:00 --- # EenvoudigFactureren [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) EenvoudigFactureren is Belgian small business invoicing software. Agents manage clients, contacts, and stock items, create and send documents by email or post, record payments and reminder costs, and pull document files and events. 41 actions · API key · available [EenvoudigFactureren website](https://eenvoudigfactureren.be/) · [Platform Documentation](https://www.eenvoudigfactureren.be/info/help/api/) · Capability data verified 2026-08-24 1. A job is signed off and is ready to bill 2. Create Document writes the invoice against the client with its net or gross flag set deliberately 3. Add Document Item adds each line, carrying the stock item identifier so the catalog drives the description and the VAT band 4. List Document Items reads the lines back and the agent compares the count and the total against the source 5. Each line's VAT rate is confirmed to be one of the document's own three rates or zero 6. Send Document By Email delivers the PDF or the electronic invoice format the client accepts 7. A person approves before Send Document By Post commits a paid physical mailing ## What This Integration Enables EenvoudigFactureren models seven kinds of document as one shape on seven paths: invoices, cash receipts, quotes, orders, delivery notes, payment requests and free form documents all carry the same fields, the same lines, the same remarks and the same event history. That means a FlowRunner agent learns one document pattern and applies it everywhere, and it means a workflow written for quotes moves to delivery notes without rework. A credit note is not an eighth kind either. It is an invoice with a negative total, derived rather than declared. What is worth knowing before you automate is how easy this API makes it to destroy a record politely. A write with the vendor's replace semantics treats what you send as the whole record and deletes everything you left out, so an empty payments array removes every payment on an invoice. FlowRunner's connector only ever writes with the merge semantics, which means there is no operation on this page that can silently empty a record. The hazard that remains is subtler: on an update, a line carrying an identifier is changed and a line without one is created, so reading a document and sending its lines straight back duplicates all of them. Nothing errors, the totals add up, and the invoice is exactly twice what it should be. That is the failure this page's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate is built around. ### Without FlowRunner **Lines quietly doubled**: A read and write back that loses the line identifiers adds a second copy of every line, and the invoice is exactly twice right **VAT rates typed as percentages**: A stock item's VAT is a band number rather than a percentage, and entering the percentage asks for a band that does not exist **Errors hidden inside a success**: A failed create can answer with a success code and an error in the body, so a flow reports work it never did ### With FlowRunner **Lines written with their identifiers**: The agent tracks which lines exist and which are new, so an update changes rather than duplicates **Bands resolved from the account**: The three configured rates are read once and mapped, so a line carries a rate the document will accept **Failures raised as failures**: The response body is checked for an error before anything downstream treats the write as done ## Use Case Scenarios ### Import days that do not get the account throttled Client and article data arrives from a CRM like [Teamleader](https://flowrunner.ai/integrations/teamleader) or a spreadsheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). Rather than looping one record at a time, which is exactly how a key gets blocked, the agent batches with Bulk Save Clients and Bulk Save Stock Items. Each row carrying an identifier is an update and each row without one is a create, so the same call handles both sides of a sync. Rows whose VAT band cannot be resolved from the account's own three rates, typically because the source held a percentage rather than a band, are held back and shown to a person with the mapping the agent would apply. ### Payments matched to the invoice that earned them A settlement lands in [Mollie](https://flowrunner.ai/integrations/mollie) or on the bank feed. The agent finds the invoice through the document listing filtered on the outstanding amount and the client, then calls Add Payment against it. Where a reminder has already gone out, Add Reminder Cost records the administrative charge separately so the ledger shows why the balance moved. Payments only apply to invoices, receipts and payment requests, so the flow resolves the document kind before it tries. A digest of what settled and what is still open posts to [Slack](https://flowrunner.ai/integrations/slack) each morning. ### Delivery proof read from the document's own event trail List Document Events is the audit trail this platform keeps: printed, sent, viewed and paid, with the recipients on each. A collections agent reads it before writing anything, because an invoice that was never viewed and an invoice viewed three times deserve different first messages. Where the trail shows nothing since sending, the agent proposes a resend rather than an escalation. Where it shows repeated views and no payment, it proposes the escalation and attaches the evidence. List Activities gives the same picture across the whole account for the weekly review. ## Human-in-Loop Highlight Send Document By Post goes through BPost. It costs money, it produces a physical object, and it cannot be recalled by anyone. That would be reason enough for a gate, but the specific reason it belongs on this connector is what can be wrong with the document by the time it reaches that call. Because an update treats a line without an identifier as a new line, a flow that read the invoice and wrote its lines back has already doubled them, and nothing in the response distinguishes that from a correct write. The document is well formed, the VAT is right, the totals are internally consistent, and the amount is twice what was agreed. So the agent stops with the evidence in front of it: "Invoice 2026-0114 for Bouwbedrijf Claes, 6 lines, total 14,760.00 EUR including VAT. The source job lists 3 lines totalling 7,380.00. Line descriptions appear twice. Send by post, or hold for review?" On email a mistake is a follow up. On paper it is a printed, posted, paid for mistake sitting in somebody's letterbox, and the only correction is a second document. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 41 actions ### Clients 10 - **List Clients** Lists clients with filtering, search and sorting. Listings cap at a hundred records per request. - **Get Client** Retrieves a single client with its contacts and custom values. - **Create Client** Creates a client record. - **Update Client** Updates a client, changing only the fields sent. - **Delete Client** Removes a client record. - **Bulk Save Clients** Creates and updates up to a hundred clients in one call. A row with an identifier updates, a row without one creates. The documented import path. - **List Client Contacts** Lists the people attached to a client. - **Create Client Contact** Adds a person to a client, which is how a document reaches a named recipient. - **Update Client Contact** Updates a client contact. - **Delete Client Contact** Removes a client contact. ### Stock items 6 - **List Stock Items** Lists the article catalog with prices, VAT bands and ledger accounts. - **Get Stock Item** Retrieves a single article. - **Create Stock Item** Creates an article. Its VAT is a band number referring to the account's own rates, not a percentage. - **Update Stock Item** Updates an article. - **Delete Stock Item** Removes an article. - **Bulk Save Stock Items** Creates and updates up to a hundred articles in one call, the documented path for a catalog import. ### Documents 8 - **List Documents** Lists documents of any of the seven kinds, filtered on top level fields, searched and sorted. - **Get Document** Retrieves a single document with its lines and remarks. - **Create Document** Creates a document of a chosen kind. The net or gross flag decides which price field every line uses. - **Update Document** Updates a document, changing only what is sent. A line carrying an identifier is changed and a line without one is added. - **Delete Document** Removes a document. - **Download Document** Produces the document as PDF, CSV, XML or JSON, or as one of the electronic invoicing formats, which are available on invoices only. - **Send Document By Email** Emails the document. A recipient can be a keyword such as the main contact or all contacts rather than a literal address. - **Send Document By Post** Commits a paid physical mailing through BPost. It cannot be recalled, and it carries this page's human gate. ### Document lines 4 - **List Document Items** Lists a document's lines, which is the read that proves an update did not duplicate them. - **Add Document Item** Adds a line. Setting a stock item identifier pulls the description, price, VAT and ledger account from the catalog and adjusts the stock count. - **Update Document Item** Changes an existing line. - **Delete Document Item** Removes a line from a document. ### Payments and remarks 6 - **List Payments** Lists the settlements recorded against a document. - **Add Payment** Records a settlement. Only invoices, receipts and payment requests carry payments. - **Delete Payment** Removes a recorded settlement. - **Add Reminder Cost** Records an administrative charge raised by a reminder, so the ledger shows why a balance moved. - **Add Document Remark** Adds a remark to a document, which is where an agent records the reasoning behind a decision. - **List Document Events** Reads the document's audit trail: printed, sent, viewed and paid, with the recipients on each. ### Files 3 - **List Invoice Files** Lists the files stored against an invoice. - **Download Invoice File** Fetches a stored invoice file. - **Upload Attachment** Uploads a file for use in a send. The upload is short lived and the file name is not retained, so it is passed again on the send call. ### Subscriptions and reference 4 - **List Subscriptions** Lists the recurring billing definitions on the account. - **Get Subscription** Retrieves a single recurring definition. - **List Layouts** Lists the document layouts available. - **List Activities** Reads the account wide activity feed, which is the polling path since no webhook registration is published. ## Frequently Asked Questions ### What can FlowRunner do with EenvoudigFactureren? FlowRunner agents can run List Clients, Get Client, and Create Client in EenvoudigFactureren, plus 38 more actions. ### Does connecting EenvoudigFactureren to FlowRunner require OAuth? No. EenvoudigFactureren connects to FlowRunner with an API key, no OAuth flow required. ### Can EenvoudigFactureren trigger a FlowRunner workflow automatically? EenvoudigFactureren doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at EenvoudigFactureren?** This integration exposes EenvoudigFactureren to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/eenvoudigfactureren. Site index: https://flowrunner.ai/llms.txt