--- title: "Invoicing Plus Integration" description: "Invoicing.plus is a French electronic invoicing platform. Agents issue invoices, estimates, and recurring invoices with their lines and PDFs, manage customers, contacts, and products, and keep company data in sync." url: https://flowrunner.ai/integrations/invoicing-plus date_modified: 2026-09-04T14:53:04-07:00 --- # Invoicing Plus [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Invoicing.plus is a French electronic invoicing platform. Agents issue invoices, estimates, and recurring invoices with their lines and PDFs, manage customers, contacts, and products, and keep company data in sync. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 42 actions · API key · available [Invoicing Plus website](https://invoicing.plus/) · [Platform Documentation](https://api.invoicing.plus/docs) · Capability data verified 2026-08-24 1. A completed order lands from the storefront 2. Agent reads the buyer's email address, the priced lines, and each product's item code 3. List Customers confirms whether that email already belongs to a customer account 4. Create Invoice writes the draft against the resolved customer with its lines and headings 5. The draft is read back and its totals compared against what the storefront charged 6. Anything whose email or item code did not resolve is queued with the mismatch named 7. A person confirms the match before Validate Invoice assigns the number and locks the document ## What This Integration Enables Invoicing.plus is a French electronic invoicing platform, and its API is built around one boundary that most invoicing APIs blur. Create Invoice does not produce a legal document. It produces a draft with no number. Validate Invoice is the separate call that assigns the number and locks the invoice as a legal record, and under French electronic invoicing rules a validated invoice cannot simply be edited back. Everything a FlowRunner agent does well on this connector follows from taking that boundary seriously: assemble in the draft, verify in the draft, and treat validation as a commitment rather than a save. Agents create and read customers, contacts, and products, link a named person to a company account, build invoices and estimates from priced lines and heading rows, create recurring invoices, download PDFs, and record payments. They also maintain the reference data that makes a French accounting export line up, since the ledger account codes on a customer, a product, and a VAT rate are the difference between an export the accountant can post and one they cannot. The [connectors](https://flowrunner.ai/concepts/connectors) do the assembly; the moment of no return is where a person belongs, and this vendor was unusually clear about where that moment is. ### Without FlowRunner **The draft stage skipped**: Invoices go out as finished documents, so every error becomes a correction rather than an edit **Customer records multiply**: The same buyer arrives under three spellings and the ledger accounts stop lining up **Ledger codes filled in later**: Chart of accounts codes are added by hand at export time, or not at all ### With FlowRunner **The draft stage used on purpose**: Everything is assembled, recalculated, and read back while it is still editable **One matching key, deliberately chosen**: The email address and the item code are treated as the identifiers they actually are **Codes carried on the record**: Customers, products, and VAT rates hold their account codes, so the export posts without rework ## Use Case Scenarios ### Storefront orders into French invoicing, with the match proven first Orders arrive from [WooCommerce](https://flowrunner.ai/integrations/woocommerce). For a shop with a clean product catalog, Create Invoice Effortless does the whole import in one call, matching or creating the customer on its email address and each product on its item code. That convenience is exactly why the agent checks first. Before it uses the effortless route, it calls List Customers and List Items and confirms that the email resolves to one account and every item code resolves to one product. Where it does, the one call runs. Where it does not, the agent falls back to the explicit route, creates nothing new, and queues the order for a person. The draft is then read back with Get Invoice and its total compared to the order total before Validate Invoice is ever called. ### Estimate accepted, invoice raised, payment recorded A sales conversation ends with an accepted quote. The agent has already built the estimate with Create Estimate, using heading rows to break a long scope into sections a client can read, and stored the file with Download Estimate PDF. On acceptance it creates the invoice draft with the same lines, validates it, sends it with Send Invoice, and posts the reference into [Slack](https://flowrunner.ai/integrations/slack) for the account owner. When the money arrives through [GoCardless](https://flowrunner.ai/integrations/gocardless), Create Payment records it against the invoice with its date, amount, and method, so the receivable closes in the same system that raised it. ### Keeping the accounting export postable An agent audits the reference data on a schedule. It reads List Customers, List Items, and List Tax Types and reports every record missing its ledger account code, since a customer without one, a product without one, or a VAT rate without one is a line the accountant has to code by hand. It writes the findings to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and, where the correct code is unambiguous from an existing record of the same type, proposes it. Nothing is written until a person accepts the proposal, because a wrong account code produces an export that posts cleanly to the wrong place. ## Human-in-Loop Highlight The gate on this connector is not the send. It is Create Invoice Effortless followed by Validate Invoice, and the reason is that the effortless route never fails on a bad key. It matches or creates the customer on the email address and each product on the item code, so a typo in an email does not produce an error. It produces a new customer. Two products sharing an item code do not produce a warning. They become one product. Then Validate Invoice assigns a number and locks the result as a legal document that cannot be edited back. So the agent runs the effortless route only when it has already proved the keys resolve, and when they do not it stops with the specific ambiguity named: "This order's email matches no existing customer, and the item code SKU-4471 matches two different products. Create a new customer and pick a product, or is this an existing account under a different address?" A person answers in a minute. The alternative is a numbered French invoice, addressed to a customer who does not exist, that can only be unwound with a credit note. 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 42 actions ### Connection and Companies 5 - **Check Service** Checks that the service is reachable, without reading or writing any data. - **Who Am I** Reads which user the connection's token belongs to, which is the quickest proof that it works. - **Revoke Token** Revokes the token this connection is using. A permanent token cannot be recovered afterwards, so every flow on that connection stops until a new one is issued. - **List Companies** Lists the companies this login can act for, and the identifier each one needs in the company header. The only route that works without it. - **Get Company** Reads the details of the company the connection is acting for. ### Customers and Contacts 10 - **List Customers** Lists the customers of a company. The lookup that proves an email address resolves before a write relies on it. - **Get Customer** Reads one customer by its ID. - **Create Customer** Creates a customer with its billing address, tax numbers, and ledger account. - **Update Customer** Updates a customer in a company. - **List Contacts** Lists the contacts of a company. A contact is a person, separate from the customer account. - **Get Contact** Reads one contact by its ID. - **Create Contact** Creates a contact in a company. - **Update Contact** Updates a contact. The vendor documents a wider field set here than on create, so a field that cannot be set at creation may still be set afterwards. - **Link Contact To Customer** Attaches a contact to a customer account, so that person appears on that account's documents. - **Unlink Contact From Customer** Detaches a contact from a customer account, leaving both records in place. ### Invoices 7 - **List Invoices** Lists the invoices of a company, optionally between two dates. - **Get Invoice** Reads one invoice with its lines and totals. The read back step before validation. - **Create Invoice** Creates a draft invoice against an existing customer, with its priced lines and heading rows. A draft has no number and is the editable stage. - **Create Invoice Effortless** Creates an invoice in one call, matching or creating the customer by email address and each product by its item code. Fast when the keys are known to resolve, which is why the gate on this page sits here. - **Validate Invoice** Validates a draft, which assigns its number and locks it as a legal document. The one way door. - **Send Invoice** Emails an invoice to its customer, optionally from a different address and with your own subject. - **Download Invoice PDF** Downloads an invoice as a PDF into FlowRunner file storage. ### Estimates 4 - **Get Estimate** Reads one estimate with its lines and totals. - **Create Estimate** Creates an estimate against an existing customer, with its priced lines and heading rows. - **Create Estimate Effortless** Creates an estimate in one call, matching or creating the customer by email address and each product by its item code. The same matching keys apply as on the invoice route. - **Download Estimate PDF** Downloads an estimate as a PDF into FlowRunner file storage. ### Recurring Invoices 3 - **List Recurring Invoices** Lists the recurring invoices of a company. - **Get Recurring Invoice** Reads one recurring invoice by its ID. - **Create Recurring Invoice** Creates a recurring invoice against a customer, with its lines. ### Products and Units 6 - **List Items** Lists the products of a company, which is where item codes come from and where duplicates are caught. - **Get Item** Reads one product by its ID. - **Create Item** Creates a product with its price, ledger account, default VAT rate, and unit. - **Update Item** Updates a product in a company. - **List Units** Lists the units of measure a company sells in. - **Create Unit** Creates a unit of measure, with its singular and plural forms. ### VAT and Payments 7 - **List Tax Types** Lists the VAT rates configured in a company. - **Create Tax Type** Creates a VAT rate with its percentage and ledger account. - **Update Tax Type** Updates a VAT rate in a company. - **List Payments** Lists the payments recorded in a company. - **Get Payment** Reads one payment by its ID. - **Create Payment** Records a payment against an invoice, with its date, amount, and payment method. - **List Payment Methods** Lists the payment methods configured in a company. ## Frequently Asked Questions ### What can FlowRunner do with Invoicing Plus? FlowRunner agents can run Check Service, Who Am I, and Revoke Token in Invoicing Plus, plus 39 more actions. ### Does connecting Invoicing Plus to FlowRunner require OAuth? No. Invoicing Plus connects to FlowRunner with an API key, no OAuth flow required. ### Can Invoicing Plus trigger a FlowRunner workflow automatically? Invoicing Plus doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Invoicing Plus?** This integration exposes Invoicing Plus 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/invoicing-plus. Site index: https://flowrunner.ai/llms.txt