--- title: "Billit Integration" description: "Billit is a Belgian invoicing platform and Peppol access point that reaches national e-invoicing networks across Europe and beyond. Agents issue and send invoices, receive incoming e-invoices, and route documents to the right country channel without leaving the workflow." url: https://flowrunner.ai/integrations/billit date_modified: 2026-09-04T14:53:04-07:00 --- # Billit [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Billit is a Belgian invoicing platform and Peppol access point that reaches national e-invoicing networks across Europe and beyond. Agents issue and send invoices, receive incoming e-invoices, and route documents to the right country channel without leaving the workflow. 1 trigger · 66 actions · API key · available [Billit website](https://www.billit.be/) · [Platform Documentation](https://docs.billit.be/) · Capability data verified 2026-08-24 1. A completed order is ready to bill in the operations system 2. Search Companies looks the buyer up in the public registers by name or VAT number 3. Create Or Update Order files the invoice in Billit with your own reference on it 4. Check Peppol Participant reports whether the receiver is registered and which document types it accepts 5. The agent confirms the transport the buyer actually supports rather than assuming Peppol 6. The prepared document and its intended route post to the finance channel 7. The finance owner confirms the route before Send Orders puts it on the wire ## What This Integration Enables Billit is not only a Belgian invoicing platform. It is a Peppol access point, which means the connector's real job is getting a document onto somebody else's national e-invoicing network: the Italian SDI, the Polish KSeF, the Hungarian OSA, the Romanian ANAF, the Mexican SAT, the Malaysian MyInvois and the French Chorus. If your business sells across European borders, that routing problem is the thing that actually costs you time, and it is the thing this connector is built around. Two design decisions shape how agents work with it. Everything is an order: invoices, credit notes, offers, delivery notes and order forms are one register separated by a type and a direction, so a sales invoice and a supplier invoice differ by two fields rather than by two endpoints. And create and update are the same call, so Create Or Update Order writes a new document when the identifier is absent and edits an existing one when it is present. Both make an agent's life simpler and both reward putting your own identifier in the external provider field, because that field is filterable and Billit's own numbers then never need storing anywhere. ### Without FlowRunner **Delivery route decided by guesswork**: Whether a customer takes Peppol, email or a national network is stored in nobody's system **Failures found by the customer**: A perfect invoice sent to an unregistered participant fails, and the first sign is a chase call **Incoming e-invoices as a manual queue**: The Peppol inbox is drained by whoever remembers to open it, and items stay until they are ### With FlowRunner **Route confirmed against the register**: The participant check runs before the send, and it needs no credential to answer **Failures caught before delivery**: A receiver who cannot take the document type gets flagged while the document is still filed and unsent **The inbox drains itself**: Each item is downloaded, matched and confirmed, so the queue reflects work outstanding rather than attention outstanding ## Use Case Scenarios ### The Peppol inbox that drains itself Get Peppol Inbox returns the first ten items and they stay there until each one is confirmed or refused, which means an inbox read by a flow that never confirms shows the same ten forever. The agent reads the queue, calls Download File on each message to get the document itself, matches it against an open purchase order, and books it. Items that match cleanly get Confirm Peppol Inbox Item and leave the queue. Items that do not, a supplier nobody recognizes or a total that disagrees with the order, stay in the queue and arrive in [Slack](https://flowrunner.ai/integrations/slack) with both figures shown. Refuse Peppol Inbox Item is only ever called by a person, because refusing an inbound e-invoice is a statement to the sender. ### Incremental sync into the systems that need the numbers List Orders ordered by last modified, paired with List Deleted Orders, is a complete incremental sync: everything that changed and everything that went away. The agent runs it on a schedule and pushes the deltas into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the reporting the Billit interface does not do, and into a CRM like [Teamleader](https://flowrunner.ai/integrations/teamleader) so the account owner sees settlement without asking finance. Because the agent set its own reference on create, it matches records without ever having stored a Billit order number. ### The accountant feed as a handover that cannot drop anything Create Feed opens a queue, and everything exported afterwards accumulates in it until each item is confirmed, so nothing is lost by a downstream system being offline. The agent lists the feed, downloads each item, delivers it to the accounting practice, and only then calls Confirm Feed Item. Billit asks that the feed is polled at most once a minute, so the flow paces itself rather than looping. The handover to the accountant stops being an email with attachments and becomes a queue where an unconfirmed item is visible work. ## Human-in-Loop Highlight This connector has two send verbs that look interchangeable and are not. Send Orders puts a document you have already filed onto the wire, over Peppol, email, a physical letter or a national network. Send Peppol Document puts a document on the network without filing it as an order, which means it reaches the customer, satisfies the receiving tax authority, and your own Billit bookkeeping never sees it. Neither can be recalled. So the agent prepares and asks: "Invoice 2026-0412 to Fabbrica Rossi, 8,940.00 EUR, filed as order 55187. Participant check says the receiver is registered on Peppol and accepts BIS 3.0 invoices. Route: Send Orders over Peppol, which files and sends. Confirm, or send over email instead?" What makes this gate specific is that the failure is not a rejected document. It is a delivered one that your books have no record of, discovered at close by an accountant looking for an invoice that a customer has already paid. 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 66 actions ### Account 3 - **Get Account Information** Returns the connected party's own details, the cheapest confirmation that the key and the party identifier agree. - **Get Single Sign On Token** Issues a token for handing a user into the Billit interface without a second login. - **Consume Number Sequence** Takes the next number from a sequence. It advances the sequence rather than reading it, so a number taken and not used leaves a gap auditors ask about. ### Parties 5 - **List Parties** Lists customers and suppliers with OData filtering. - **Get Party** Retrieves a single party. - **Create Or Update Party** Creates a party when the identifier is absent and updates it when present. The route for anything touching addresses or bank accounts. - **Patch Party** Changes a few fields on a party without sending the whole record. It cannot touch sub objects such as addresses. - **Search Companies** Looks a company up in the public registers by name or VAT number, so the party you create is the right legal entity. ### Products 3 - **List Products** Lists the catalog. - **Get Product** Retrieves a single catalog product. - **Create Or Update Product** Creates or updates a catalog product, with separate net and gross price fields. ### Orders 10 - **List Orders** Lists documents filtered by type and direction. With neither set it reads every document the company has, purchases and sales together. - **Get Order** Retrieves a single document. - **Create Or Update Order** Files an invoice, credit note, offer, delivery note or order form. It takes either an existing party identifier or a whole party object, and passing both is how duplicate parties accumulate. - **Patch Order** Changes a few fields on a filed document. - **Delete Order** Removes a document. - **List Deleted Orders** Lists what has been removed, which is the other half of an incremental sync. - **Send Orders** Puts filed documents on the wire over Peppol, email, post or a national network. It cannot be recalled, and it carries this page's human gate. - **Add Order Payment** Records a settlement against a document. - **Set Order Booking Entries** Sets the bookkeeping entries a document generates. - **Sign Order** Applies a signature to a document. ### Files 1 - **Download File** Turns a file identifier into stored bytes. Order PDFs, attachments and Peppol inbox messages all arrive as identifiers rather than content. ### Documents 3 - **List Documents** Lists stored documents on the account. - **Get Document** Retrieves a single stored document. - **Upload Document** Stores a document against the account. ### Inbox 3 - **List Documents To Process** Lists documents waiting to be turned into orders. - **Upload Document To Process** Adds a document to that queue, typically a supplier PDF from a mailbox. - **Delete Document To Process** Removes a document from the processing queue. ### Peppol 7 - **Check Peppol Participant** Reports whether a receiver is registered on Peppol and which document types it accepts. It needs no API key, so it is cheap to run before every send. - **Register Peppol Participant** Registers a company as a Peppol participant. - **Delete Peppol Participant** Removes a Peppol registration. - **Get Peppol Inbox** Returns the first ten inbound items, which stay in the queue until confirmed or refused. - **Confirm Peppol Inbox Item** Accepts an inbound item and clears it from the queue. - **Refuse Peppol Inbox Item** Declines an inbound item, which is a statement back to the sender rather than a local cleanup. - **Send Peppol Document** Puts a document on the Peppol network without filing it as an order, so Billit's own bookkeeping never records it. ### Cash book 7 - **Get Cash Book** Returns the current cash book. - **Initialize Cash Book** Opens a cash book for a period. - **Close Cash Book** Closes the cash book permanently. It cannot be reopened, and its entries move to the history. - **List Cash Book Entries** Lists entries in the open cash book. - **List Closed Cash Books** Lists cash books that have been closed. - **List Closed Cash Book Entries** Reads the entries of a closed cash book from the history. - **Add Cash Book Entry** Records an entry in the open cash book. ### Daily receipts 4 - **Add Daily Receipt** Records a day's takings. - **Get Daily Receipt** Retrieves a single daily receipt. - **List Daily Receipt Books** Lists the daily receipt books on the account. - **Get Daily Receipt Book** Retrieves a single daily receipt book. ### Banking 3 - **List Financial Transactions** Lists bank transactions held in Billit. - **Import Financial Transactions** Loads bank transactions, which is what a reconciliation flow feeds. - **Import Coda File** Loads a Belgian CODA bank statement file. ### Bookkeeping 3 - **Create General Ledger Account** Adds an account to the chart. - **Import General Ledger Accounts** Loads a chart of accounts in bulk. - **Import Journals** Loads journal entries in bulk. ### Accountant feeds 6 - **List Feeds** Lists the accountant feeds configured on the account. - **Create Feed** Opens a feed, after which everything exported queues in it until confirmed. - **List Feed Items** Lists what is waiting in a feed. Billit asks that this is called at most once a minute. - **Download Feed Item** Fetches the content of a queued item. - **Confirm Feed Item** Marks a feed item as handled and removes it from the queue. - **Delete Feed** Removes a feed. ### Reports 2 - **List Reports** Lists the reports available on the account. - **Get Report** Runs a report and returns its result. ### Reference 2 - **List Type Codes** Lists Billit's own type codes, used to interpret a raw response. - **Get Type Code Translation** Returns the readable translation of a type code. ### Webhooks 4 - **List Webhooks** Shows what is currently registered. - **Create Webhook** Registers a webhook by hand, outside the trigger's own lifecycle. - **Delete Webhook** Removes a registered webhook. - **Refresh Webhook Secret** Rotates the signing secret on a registered webhook. ## Triggers 1 triggers ### Event Triggers 1 - **On Billit Event** Fires when a document is created, updated or deleted, and when an e-invoice delivery reports back its status across any of the transport types. The trigger registers the webhook, keeps the signing secret Billit generates for it, and checks the signature header before the flow runs, so a delivery that cannot be verified does not start work. The callback must be HTTPS; Billit refuses to deliver to plain HTTP. ## Frequently Asked Questions ### What can FlowRunner do with Billit? FlowRunner agents can run Get Account Information, Get Single Sign On Token, and Consume Number Sequence in Billit, plus 63 more actions. ### Does connecting Billit to FlowRunner require OAuth? No. Billit connects to FlowRunner with an API key, no OAuth flow required. ### Can Billit trigger a FlowRunner workflow automatically? Yes. Billit supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Billit?** This integration exposes Billit 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/billit. Site index: https://flowrunner.ai/llms.txt