Recommand
AccountingRecommand is a Belgian Peppol access point. Agents put invoices, credit notes, self billing documents, and raw UBL XML onto the Peppol network, read what arrives, and act on message level responses.
What This Integration Enables
Recommand is a Peppol access point, which makes it a different kind of connector from an accounting platform. It does not keep your books. It puts structured documents onto a network that other companies' finance systems read directly, and it receives what they send you. The valuable work is therefore not the invoice, which your billing system already produced. It is everything around addressing it: whether the recipient exists on the network, whether they are registered to receive this particular document type, whether your own company is verified and addressable, and whether what arrived is what you think arrived.
FlowRunner agents send invoices, credit notes, self billing documents, message level responses, and raw UBL XML. They read the inbox, render arriving documents as HTML or PDF, download the full package with its original XML and attachments, and route by label. They also manage the registration layer that most integrations quietly ignore: company records and their verification state, Peppol identifiers, document type registrations, and notification addresses. Two behaviors shape every flow. Sending is irreversible, and a refusal can arrive with a 200 status carrying a success flag set to false, so a status-only reader would hand a rejection to the next step as though it were a record.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Outbound invoices that reach a real participant
An approved invoice leaves the accounting system, whether that is Exact Online or a billing platform of your own. The agent builds the document with amounts carried as decimal strings, because a fraction of a cent lost to a floating point conversion is a legal document with the wrong total on it. Verify Recipient confirms the Peppol address is live and returns the participant's name, and Verify Document Support confirms they accept invoices. Send Invoice transmits. If the buyer is not on the network at all, the same call falls back to email delivery, and the agent records which route was used.
-
Incoming supplier documents routed by label
Documents arrive on the network from suppliers. The agent listens for the arrival event, then calls Get Document to read the parsed structured version rather than trusting the delivery payload. Assign Label To Supplier has already been applied to known suppliers, so their documents arrive pre-labeled, and Assign Label To Document adds anything the content itself implies. The label is what downstream routing acts on: cost center owners get their bills in Slack, the originals land in SharePoint through Download Document Package, and Mark Document As Read clears the inbox only once the handoff succeeded.
-
Onboarding a company onto the network without a manual checklist
Bringing a new entity live on Peppol is a sequence, not a switch. Create Company registers it, Verify Company starts an identity session and returns the URL an authorized representative has to complete, and the company is not addressable until they finish. The agent then adds the addressing layer: Create Company Identifier for each scheme the company should be reachable under, Create Company Document Type for each kind of document it should accept, and Create Notification Email Address so the right mailbox hears about arrivals. Progress is tracked in Google Sheets and the agent reads the company's verified flag rather than assuming the session was finished.
Human-in-Loop Highlight
A Peppol send cannot be recalled. Delete Document removes Recommand's record of the transmission and nothing else, so once the network has carried an invoice it is inside the recipient's accounts payable system and no operation in this connector reaches it. That raises the stakes on the one thing an automated billing flow is most likely to get wrong, which is not the document but the address. A Peppol identifier is a scheme and a number, and a stale or transposed one is not usually invalid. It usually belongs to somebody else. Sending there delivers your customer's prices, terms, and identity to a company with no relationship to either of you, and there is no undo. So the agent verifies before it sends. Verify Recipient returns the name on the participant's business card, and the agent compares that name to the customer of record. When they match, and Verify Document Support confirms the recipient accepts invoices, the send runs unattended, which is the point: most of them match. When the business card names a different company, or the recipient is registered on the network but not for this document type, the agent stops and posts both names side by side with the identifier it was given and where that identifier came from. A billing owner confirms or corrects it. The same gate covers Update Company for a related reason worth stating plainly: changing a company's VAT or enterprise number revokes its verification, which takes it off the network until someone completes a new identity session.
Agent Capabilities
63 actionsConnection and Team
3- Verify Authentication Confirms the API key is accepted. The quickest way to check a connection before a flow starts sending documents.
- Get Playground Reads the playground information for the team behind the key, which answers whether it is pointed at a test team or at production.
- Create Playground Creates a playground team and adds the current user to it, optionally connected to the Peppol Test Network for end-to-end testing.
Companies
6- List Companies Lists the companies registered on the team, optionally narrowed to one enterprise or VAT number.
- Get Company Reads a single company, including whether it has been verified and is active on the network.
- Create Company Registers a company on the team. It still has to be verified before it can send or receive.
- Update Company Updates a company. Changing its VAT or enterprise number revokes verification and it has to be verified again, which is why this sits behind the same gate as sending.
- Delete Company Deletes a company from the team, which also removes its Peppol registration.
- Verify Company Starts an identity verification session and returns the URL where an authorized representative completes it. It verifies nothing by itself.
Peppol Identifiers
5- List Company Identifiers Lists the identifiers a company is addressable by, each a scheme and a number.
- Get Company Identifier Reads a single Peppol identifier of a company.
- Create Company Identifier Adds an identifier to a company, making it addressable under that scheme and number.
- Update Company Identifier Updates an identifier. Both the scheme and the value are required, so it replaces rather than patches.
- Delete Company Identifier Deletes an identifier, after which the company is no longer addressable under it.
Document Type Registrations
5- List Company Document Types Lists the document types a company is registered to receive, which is what other senders check before addressing it.
- Get Company Document Type Reads a single document type registration.
- Create Company Document Type Registers a document type on a company so other participants can send that kind of document to it.
- Update Company Document Type Updates a document type registration. Both identifiers are required, so it replaces rather than patches.
- Delete Company Document Type Deletes a document type registration, after which the company no longer accepts that kind of document.
Notification Addresses
5- List Notification Email Addresses Lists the addresses notified when documents arrive at or leave a company.
- Get Notification Email Address Reads a single notification address, including which attachments it receives.
- Create Notification Email Address Adds an address to notify on arrivals or departures, optionally with the generated PDF and document JSON attached.
- Update Notification Email Address Updates a notification address. The address and both direction flags are required, so it replaces rather than patches.
- Delete Notification Email Address Deletes a notification address, after which it stops receiving document notifications.
Sending
6- Send Invoice Sends an invoice over the network, by email, or both. The document is validated before it goes and cannot be recalled afterwards, which is what this page's human gate is built on.
- Send Credit Note Sends a credit note over the network, by email, or both, optionally referencing the invoices it credits.
- Send Self Billing Invoice Sends a self billing invoice, where the buyer issues the invoice on the supplier's behalf and the seller is the party being stated.
- Send Self Billing Credit Note Sends a self billing credit note, crediting a self billing invoice the buyer issued on the supplier's behalf.
- Send Message Level Response Sends a message level response acknowledging, accepting, or rejecting a document that was received. A rejection travels back into the sender's own system.
- Send XML Document Sends a raw UBL XML document onto the network, with the document type and process identifiers detected from the XML where possible.
Addressing
3- Verify Recipient Checks whether a Peppol address is registered, optionally returning the document types it accepts and the company name on its business card. The check that stops a misaddressed send.
- Verify Document Support Checks whether a recipient is registered to receive a particular document type, given either the full identifier or a short name such as invoice.
- Search Peppol Directory Searches the public Peppol Directory by name or number to find a participant's address.
Documents
8- List Documents Lists the documents the team has sent and received, with filters for company, direction, type, label, read status, and date range.
- Get Document Reads a single transmitted document, including the parsed structured version and its validation result. The read that turns a delivery notification into a fact.
- Get Inbox Lists the unread incoming documents, which is the polling alternative to the document received event.
- Mark Document As Read Marks a document as read, which removes it from the inbox, or as unread to put it back.
- Delete Document Deletes a document record. It does not recall a document that has already been delivered.
- Download Document Package Downloads a document as a zip carrying its JSON, its original XML, and every attachment, into FlowRunner file storage.
- Render Document As HTML Renders a document as an HTML preview, the same one the dashboard shows, and returns the markup.
- Render Document As PDF Renders a document as a PDF preview into FlowRunner file storage, which is what a human review thread usually wants.
Labels
7- Assign Label To Document Puts a label on a document, which fires the label assigned event and is how documents are routed to downstream systems.
- Unassign Label From Document Takes a label off a document, which fires the label unassigned event.
- List Labels Lists the team's labels, which are what documents and suppliers are tagged with for routing.
- Get Label Reads a single label.
- Create Label Creates a label, optionally carrying an external ID from your own system so routing rules can match on it.
- Update Label Updates the text, color, or external ID of a label.
- Delete Label Deletes a label, after which any rule routing on it stops matching.
Customers and Suppliers
10- List Customers Lists the customers stored on the team, which are the supporting records buyer details are filled from.
- Get Customer Reads a single customer, found by either its Recommand ID or the external ID you stored on it.
- Upsert Customer Creates or updates a customer, matching on the Recommand ID when given and otherwise on the external ID. The default write for a sync flow, because it cannot create a duplicate.
- Delete Customer Deletes a customer record. Documents already sent to them are untouched.
- List Suppliers Lists the suppliers stored on the team, whose labels propagate onto matching incoming documents.
- Get Supplier Reads a single supplier, found by either its Recommand ID or the external ID you stored on it.
- Upsert Supplier Creates or updates a supplier, matching on the Recommand ID when given and otherwise on the external ID.
- Delete Supplier Deletes a supplier record, which stops its labels propagating onto incoming documents.
- Assign Label To Supplier Puts a label on a supplier, after which every document arriving from them carries that label. The setup step that makes inbound routing automatic.
- Unassign Label From Supplier Takes a label off a supplier. Documents that already carry it keep it, and only future arrivals stop being tagged.
Webhooks
5- List Webhooks Lists the team's webhooks, including the ones this service's trigger registered.
- Get Webhook Reads a single webhook, including its URL and company scope.
- Create Webhook Creates a webhook that receives every supported event, optionally scoped to one company and signed with a shared secret.
- Update Webhook Updates a webhook's URL, company scope, or signing secret. Leaving the secret out keeps the current one, and passing null disables signing.
- Delete Webhook Deletes a webhook, after which it stops receiving deliveries.
Triggers
1 triggersEvent Triggers
1- On Recommand Event Fires when Recommand reports a Peppol event, such as a document arriving, a label changing, or a company verification finishing. The delivery carries identifiers rather than the document itself, so the pattern that works is to follow it with Get Document and read the parsed version and its validation result before acting.
Frequently Asked Questions
What can FlowRunner do with Recommand?
FlowRunner agents can run Verify Authentication, Get Playground, and Create Playground in Recommand, plus 60 more actions.
Does connecting Recommand to FlowRunner require OAuth?
No. Recommand connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Recommand trigger a FlowRunner workflow automatically?
Yes. Recommand supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Recommand
Free plan, no card required. Connect in minutes.