--- title: "Fatture in Cloud Integration" description: "Fatture in Cloud is the leading Italian invoicing platform from TeamSystem, built around electronic invoicing. Agents file documents with the Sistema di Interscambio, pick up supplier e-invoices as they arrive, and manage clients, products, and receipts in between." url: https://flowrunner.ai/integrations/fatture-in-cloud date_modified: 2026-09-04T14:53:04-07:00 --- # Fatture in Cloud [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) Fatture in Cloud is the leading Italian invoicing platform from TeamSystem, built around electronic invoicing. Agents file documents with the Sistema di Interscambio, pick up supplier e-invoices as they arrive, and manage clients, products, and receipts in between. 1 trigger · 54 actions · OAuth · available [Fatture in Cloud website](https://www.fattureincloud.it/) · [Platform Documentation](https://developers.fattureincloud.it/) · Capability data verified 2026-08-24 1. An order closes upstream and reaches the agent on the company it belongs to 2. Get Pre-Create Info reports the numbering series, payment methods, and VAT types this company actually has 3. Create Issued Document writes the invoice with its lines and its payment schedule 4. Verify E-Invoice checks the document against the schema without sending anything 5. The agent confirms the client carries a recipient code or a certified email address 6. The finance owner receives the document, its totals, and the validation result 7. The finance owner approves, and only then does Send E-Invoice file it with the exchange system ## What This Integration Enables Fatture in Cloud is the leading Italian invoicing platform, and reading it as an invoicing tool undersells what the connector is for. The document's real destination is the Sistema di Interscambio, the exchange system that Italian electronic invoices are filed through, and supplier invoices arrive back the same way. The PDF is a courtesy copy. That reframes the job: the work worth automating is not producing a document, it is producing one that will be accepted, and then knowing what happened to it. FlowRunner agents build issued documents across the platform's eleven kinds from one register, price them before they exist with Get Issued Document Totals, validate them against the schema, file them, and read back a rejection reason when the exchange system refuses one. On the incoming side they work the pending received documents queue, file supplier invoices, and route them for approval. Clients, suppliers, products, price lists, receipts, taxes, and the cashbook are all reachable in between. One structural detail shapes every flow: nothing here is global, so the company sits in the path of almost every call and is set once as configuration rather than repeated. The act this connector cannot take back is the filing itself, which is exactly where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design puts a person. ### Without FlowRunner **Filing checked after the fact**: A rejection from the exchange system is the first sign that a field was missing **Totals computed by hand**: Withholding, cassa, rivalsa, stamp duty, and split payment are assembled in a spreadsheet **Supplier invoices found by looking**: Incoming electronic invoices are noticed when someone opens the pending list ### With FlowRunner **Filing checked before sending**: Every document is validated against the schema first, while correcting it is still free **Totals priced by the platform**: The document is priced before it exists, using the company's own tax profile **Supplier invoices start a flow**: An arriving e-invoice begins approval routing instead of waiting to be discovered ## Use Case Scenarios ### An order becomes a filed invoice, checked twice An order closes in [Shopify](https://flowrunner.ai/integrations/shopify) or a payment settles in [Stripe](https://flowrunner.ai/integrations/stripe). The agent resolves the client with List Entities and confirms the record carries what an electronic invoice needs: a recipient code or a certified email address for a business, or a tax code for a private person. Get Pre-Create Info reports the numbering series, payment methods, payment accounts, VAT types, and templates this company actually has, so the document references things that exist rather than things that seemed reasonable. Get Issued Document Totals prices it before it exists, which matters because Italian totals involve VAT types, withholding, cassa, rivalsa, split payment, and stamp duty. Create Issued Document writes it with a payment schedule, because a document created without one has no due date and never shows as overdue. Verify E-Invoice then checks it against the schema. Everything up to here is reversible. ### Supplier invoices that route themselves Incoming electronic invoices land in the pending received documents queue. The trigger reports the arrival, the agent reads the document, matches the supplier against the entity register, and compares the lines against the purchase order. Where the match is clean and the amount sits inside the tolerance for that supplier, Create Received Document files it and the approval note goes to the cost center owner in [Slack](https://flowrunner.ai/integrations/slack) as a record rather than a question. Where the supplier is new, or the amount exceeds what that supplier has ever billed, the same message becomes an approval request with the document attached. Upload Attachment holds the supporting file, which is only really attached once its token is sent on the create, and an unused token expires. ### Reading a rejection instead of waiting for one The exchange system refuses documents, and a refusal that nobody reads is an invoice that will never be paid. The agent watches for the e-invoice status change, calls Get E-Invoice Rejection Reason, and turns the code into something a person can act on. Recoverable cases are drafted as a corrected document for review. The agent also runs a standing sweep: List Issued Documents for anything filed but not confirmed within the expected window, with the results appended to a tracking sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) so the backlog is visible before month-end rather than during it. Download E-Invoice XML archives the accepted version for the company's own records. ## Human-in-Loop Highlight Send E-Invoice is the only genuinely final act in this connector, and it is worth being precise about why. A deleted document is not gone: Delete Issued Document moves it to the bin, List Bin finds it, and Recover Document From Bin puts it back, with Empty Document From Bin as the one deletion that means it. A filed e-invoice has no equivalent. It cannot be recalled and it cannot be edited, and the correction is a credit note that the customer, the accountant, and the revenue agency all see. What makes this a real gate rather than a formality is that a free check already exists: Verify E-Invoice runs the document against the schema and sends nothing, which catches the missing recipient code or tax field that produces most rejections. So the agent runs the check and stops. It posts: "Invoice 2026/0311 for Bianchi S.r.l., 6,340.00 EUR, split payment applied because the client is flagged as public administration. Verification passed. This is the first document to this client, and split payment changes what they remit rather than what they pay. File with the exchange system, or review the tax profile first?" The finance owner answers. The agent did the pricing, the validation, and the drafting. It did not file. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 54 actions ### Account 4 - **Get User Info** Returns the connected user. One of only two operations that do not need a company. - **List Companies** Lists the companies the connection can reach, which is how a flow finds the identifier every other call needs. - **Get Company Info** Reads a company's settings and profile. - **Get Plan Usage** Reports usage against the account's plan. Worth checking before a large batch run. ### Entities 5 - **List Entities** Lists clients and suppliers, with the vendor's own filter expression syntax for narrowing by name, date, or VAT number. - **Get Entity** Retrieves one entity, including the recipient code or certified email address an electronic invoice needs. - **Create Entity** Creates a client or supplier record. - **Update Entity** Updates an entity's details, including the destination fields that decide whether an e-invoice can reach them. - **Delete Entity** Removes an entity record. ### Products 6 - **List Products** Lists the product catalog used on document lines. - **Get Product** Retrieves one product with its pricing and tax type. - **Create Product** Adds a product to the catalog. - **Update Product** Updates a product. - **Delete Product** Removes a product. - **List Price Lists** Lists the price lists a document line can be priced from. ### Issued Documents 9 - **List Issued Documents** Lists documents of any of the eleven issued kinds, which share one register separated by type. The detailed fieldset carries line items and is much larger, so flows ask for it deliberately. - **Get Issued Document** Retrieves one document with its lines and payment schedule. - **Create Issued Document** Creates an invoice, quote, proforma, receipt, delivery note, credit note, order, work report, supplier order, or self invoice. A document created without a payment schedule has no due date and never shows as overdue. - **Update Issued Document** Updates a document. Sending the items list or the payment schedule replaces that list rather than merging into it. - **Delete Issued Document** Moves a document to the bin, where it can still be recovered. - **Get Pre-Create Info** Reports the numbering series, payment methods, payment accounts, VAT types, templates, and defaults this company actually has. One call that removes most of the guesswork before a document is built. - **Get Issued Document Totals** Prices a document without creating it, applying the company's VAT types, withholding, cassa, rivalsa, split payment, and stamp duty. - **Send Document By Email** Emails a document to its recipient. Separate from filing it electronically. - **Get Email Data** Reads the email configuration a document would be sent with. ### E-Invoicing 4 - **Send E-Invoice** Files the document with the Italian exchange system. This step is final: it cannot be recalled or edited, and a mistake is corrected by issuing a credit note. - **Verify E-Invoice** Checks a document against the schema without sending anything. The free pre-check where a missing recipient code or tax field shows up. - **Get E-Invoice Rejection Reason** Reads why the exchange system refused a document, so a rejection becomes an actionable case rather than a stalled invoice. - **Download E-Invoice XML** Fetches the filed XML for your own records. ### Received Documents 6 - **List Received Documents** Lists supplier documents across the four received kinds. - **Get Received Document** Retrieves one supplier document with its lines. - **Create Received Document** Files a supplier invoice, passive credit note, passive delivery note, or self invoice. - **Update Received Document** Updates a filed supplier document, with the same list replacement behavior as issued documents. - **Delete Received Document** Moves a supplier document to the bin. - **List Pending Received Documents** Lists electronic invoices that have arrived and not yet been filed. The accounts payable work list. ### Receipts 3 - **List Receipts** Lists receipts recorded on the account. - **Create Receipt** Records a receipt. - **Get Receipts Monthly Totals** Returns receipt totals for a month, which is the figure a period close reconciles against. ### Taxes 2 - **List Taxes** Lists tax records held on the account. - **Create Tax** Records a tax entry. ### Cashbook 2 - **List Cashbook Entries** Lists cash movements. - **Create Cashbook Entry** Records a cash movement. ### Archive 2 - **List Archive Documents** Lists documents held in the archive. - **Create Archive Document** Files a document into the archive. ### Attachments 1 - **Upload Attachment** Uploads a file and returns a token. The file is only attached when that token is sent on a document create or update, and an unused token expires. ### Reference 4 - **Get Reference List** Reads any of the platform's reference lists in one operation, covering the code sets a document has to reference. - **Get Tax Profile** Reads the company's tax profile, which decides how a document is treated before any line is priced. - **Create Payment Setting** Creates a payment method or payment account for the company to reference. - **List Emails** Lists the emails sent from the account, which is the evidence trail behind a delivery question. ### Bin 3 - **List Bin** Lists deleted documents that can still be recovered. - **Recover Document From Bin** Restores a deleted document. - **Empty Document From Bin** Permanently removes a document from the bin. The one deletion in this connector that means it. ### Webhooks 3 - **List Webhook Subscriptions** Lists webhook subscriptions on the company. - **Create Webhook Subscription** Registers a subscription against an endpoint of your choosing, separate from the trigger below. - **Delete Webhook Subscription** Removes a subscription. ## Triggers 1 triggers ### Event Triggers 1 - **On Fatture in Cloud Event** Fires on the platform's documented events, from any document being created down to a product's stock changing, and including the two that matter most for Italian electronic invoicing: an e-invoice status change and an e-invoice arriving. FlowRunner registers the subscription when the trigger is switched on and removes it when it is switched off, and its endpoint answers the platform's verification challenge, without which a subscription stays silent. The delivery carries identifiers rather than the record, so the flow's first step is reading the document with Get Issued Document or Get Received Document. ## Frequently Asked Questions ### What can FlowRunner do with Fatture in Cloud? FlowRunner agents can run Get User Info, List Companies, and Get Company Info in Fatture in Cloud, plus 51 more actions. ### Does connecting Fatture in Cloud to FlowRunner require OAuth? Yes. Fatture in Cloud connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Fatture in Cloud trigger a FlowRunner workflow automatically? Yes. Fatture in Cloud supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Fatture in Cloud?** This integration exposes Fatture in Cloud 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/fatture-in-cloud. Site index: https://flowrunner.ai/llms.txt