Bleez
AccountingConnect AI agents to Bleez, a French cloud accounting and invoicing platform. Agents issue and track invoices, post journal entries, and upload documents into the dossier for processing.
What This Integration Enables
The unit of work in Bleez is the dossier, the company file, and this connector addresses it in a way that shapes every flow built on top: the encrypted dossier key is a parameter on the action, not part of the connection. One connection reaches every company file the credential can see. For a French accounting practice running dozens of client files that is exactly the right ergonomics, and it is also the single most important thing to be careful about, because nothing in the connection itself constrains which client's books a call lands in.
On the invoicing side agents read products with their codes, designations, unit prices and VAT codes, and clients with their addresses, payment terms, currency and linked accounting account. They create clients, and they create invoices singly or as a batch, quotes and delivery notes, each returning the assigned document number. Invoices carry an etat field that decides whether the document is booked or held as a draft project, which is the vendor's own separation between a document that exists and a document that counts. On the accounting side agents read fiscal years and resolve the exercice containing a given date, and pull the balance for a period. They search movements by journal, date range, reconciliation state, account and document reference, read account balances in bulk or one at a time, and work through debit and credit movements into loan and fixed-asset balances. They post balanced journal entries singly or as a batch, with an optional base64 file attached to the entry. Reference data comes from Get VAT Codes, Get Analytic Axes, Get Analytic Axis Values and the account-wide Get Chart Standards. Upload Document files a scanned purchase invoice, receipt or bank statement into a company file for processing, tagged with its Bleez document nature and optional analytic tags. To be precise about what that does: it files a document into the dossier, it does not attach one to an existing journal entry. The only entry-level attachment is the optional file supplied when the entry is created.
Two operational facts drive flow design. Dates are format-sensitive in opposite directions: list and search filters expect DD/MM/YYYY, while journal-entry movement dates use ISO YYYY-MM-DD. And error reporting is thin. An invalid dossier key returns HTTP 500 with an empty body rather than a structured error, and server-side validation failures on writes can also come back as a generic 500, so a flow cannot always tell from the response whether it addressed the wrong company or hit a technical problem. There is no trigger and no webhook contract here, so a flow that needs to notice new documents polls List Invoices or Search Movements on a schedule.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Orders that become invoices in the right dossier
Paid orders accumulate in Stripe or a storefront. On a schedule the agent reads Get Clients to resolve the customer's accounting account and Get Products to resolve line codes, unit prices and their VAT codes, builds the invoice object with the French field names Bleez expects, and calls Create Invoice against the client's dossier key. The returned numero is written back onto the order record so the two systems can be reconciled later without a name match. Because the invoice's etat decides whether the document is booked or held as a draft project, the flow can be configured to produce drafts that a human books.
Period-end reporting without opening the file
At each period close the agent calls Get Fiscal Year By Date to resolve the exercice, Get Balance for the per-account balances and Get Account Balances for the general-ledger snapshot, then Search Movements filtered by journal and reconciliation state to isolate anything still unlettered. It writes the result to Google Sheets as a trial balance with the unreconciled items called out on their own tab. The partner reviewing the file starts from the exceptions rather than from the export.
Scanned purchase documents filed as they arrive
Supplier invoices, receipts and bank statements arrive by email or land in a shared folder. The agent reads each one, chooses the Bleez document nature it belongs to (keeping the vendor's exact spelling, since the field is an enumerated list rather than free text), encodes the file, and calls Upload Document against the correct dossier with the analytic tags that apply. Documents reach the company file for processing on the day they arrive instead of in a monthly envelope, and the flow reports anything whose nature it could not confidently determine rather than guessing.
Human-in-Loop Highlight
Create Journal Entries is the gate, and the reason is a combination of what Bleez does and what it does not say. The dossier key is a parameter on the call rather than a property of the connection, so a batch built for one client and posted with another client's key lands in the wrong company's books. There is no delete or reversal action anywhere in this surface for an invoice or an entry. The way back is a correcting entry made by an accountant. The API also will not help you catch it: an invalid dossier key returns HTTP 500 with an empty body, and a server-side validation failure returns a generic technical error, so the response cannot reliably distinguish wrong company from broken request. So the agent does all the verification it can and then hands the decision over. It resolves the exercice with Get Fiscal Year By Date, confirms every referenced account against Get Account Balances and every VAT code against Get VAT Codes, and totals the batch. Then it asks the accountant: "Ready to post 214 movements in journal [code] to dossier [name], period [dates], total debit [amount] and total credit [amount], balanced. Three accounts in this batch do not yet exist in the file and would be created. Post, or return the batch?" On approval the agent calls Create Journal Entries and records the assigned numbers. The same discipline shows up on the invoicing side through the vendor's own draft state: the agent can create documents with etat set to project and leave the booking to a person. Parsing, resolving and balancing run unattended. Writing to a client's books does not.
Agent Capabilities
23 actionsInvoicing
8- Get Products Retrieves the full list of products (produits) defined in a Bleez company file. Each product includes its code, designation, unit price, and associated VAT code. Use the product code when building invoice, quote, or delivery note lines.
- Get Clients Retrieves the list of clients in a Bleez company file. Each client includes contact details, billing and delivery addresses, payment terms, currency, and the linked accounting account. Use a client account number when creating invoices, quotes, or delivery notes.
- List Invoices Retrieves invoices issued from the Bleez Facturation module of a company file, optionally filtered by date, account number, engagement number, subject, or custom fields. Returns full invoice objects including client, lines, amounts, state, and a document link. Date filters use DD/MM/YYYY.
- Create Invoice Creates a single invoice (facture) in the Bleez Facturation module of a company file and returns the assigned invoice number. The etat field controls whether the invoice is booked or kept as a draft project, which is the natural place to hold a document for human review.
- Create Invoices Creates several invoices in a single call from an array of invoice objects, returning the assigned numbers. Use this for batch invoicing instead of calling Create Invoice repeatedly.
- Create Quote Creates a quote (devis) in the Bleez Facturation module of a company file and returns the assigned number. A quote uses the same structure as an invoice but represents a proposal rather than a booked document.
- Create Delivery Note Creates a delivery note (bon de livraison) in the Bleez Facturation module of a company file and returns the assigned number, using the same structure as an invoice.
- Create Client Adds a client to a Bleez company file. Provide the client name, language, currency, optional billing and delivery addresses, payment terms, and the linked accounting account. Use this before issuing documents to that client.
Fiscal Years and Balances
7- Get Fiscal Years Retrieves the fiscal years (exercices) of a company file, each with its start date, end date, and status. Use a fiscal year number with Get Debit Credit Movements, or a date with the balance and dated lookups.
- Get Fiscal Year By Date Retrieves the fiscal year of a company file that contains the given date, with its start date, end date, and status. Call this before posting to confirm the accounting date falls in an open exercice.
- Get Balance Retrieves the accounting balance for the fiscal year of a company file that contains the given date. Returns one entry per account with its balance. Use this to reconcile account totals for a period.
- Get Account Balances Retrieves the list of account balances for a company file, pairing each account with its current balance. Use this for a general-ledger style snapshot across all accounts.
- Get Account Balance Retrieves the balance of a single account in a company file. Set the response level to Detailed to include the itemized detail, or Summary for just the account number and balance.
- Get Debit Credit Movements Retrieves debit and credit movements for a specific fiscal year of a company file, identified by its fiscal year number. The identifiers returned here can be supplied to Get Debit Credit Balances.
- Get Debit Credit Balances Computes debit and credit balances for loans and fixed assets for a fiscal year of a company file. Provide the movement parameters obtained from Get Debit Credit Movements as an array of parameter objects.
Movements and Entries
3- Search Movements Searches accounting movements in a company file, filtered by journal code, date range, reconciliation state (lettrage), account number, and document reference. All filters are optional and are combined together.
- Create Journal Entry Creates a balanced journal entry (ecriture) in a company file. Provide the journal and an array of movements, each posting a debit or credit to an account on a shared accounting date. Missing journals and accounts can be created automatically when their optional name fields are supplied. An optional base64 file can be attached.
- Create Journal Entries Creates several journal entries in a single call from an array of entry objects. Use this for batch posting instead of calling Create Journal Entry repeatedly. This is the action routed for human sign-off.
Reference Data
4- Get VAT Codes Retrieves the VAT codes configured for a company file. Each code includes its label, VAT type, rate, and the linked VAT account. Use a VAT code when building invoice or journal-entry lines.
- Get Analytic Axes Retrieves the analytic axes of a company file, each with its code and label. Use an axis code with Get Analytic Axis Values, or when tagging invoice and journal-entry lines with analytical dimensions.
- Get Analytic Axis Values Retrieves the available values of a single analytic axis in a company file, identified by its axis code. Each value includes its code and label.
- Get Chart Standards Retrieves the reference chart-of-accounts standards (etalons) available across the Bleez account. This endpoint is account wide and is not scoped to a single company file.
Documents
1- Upload Document Uploads a document to a company file for processing, for example a purchase invoice, receipt, or bank statement. Provide the document name, its nature (one of the Bleez document types, kept with the vendor's exact spelling), and the file content as a base64 string. Optional analytic tags can be attached.
Frequently Asked Questions
What can FlowRunner do with Bleez?
FlowRunner agents can run Get Products, Get Clients, and List Invoices in Bleez, plus 20 more actions.
Does connecting Bleez to FlowRunner require OAuth?
Bleez uses a custom authentication method to connect to FlowRunner.
Can Bleez trigger a FlowRunner workflow automatically?
Bleez doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Bleez
$100 in credits. No card required. Connect in minutes.