[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create and send Fatture in Cloud invoices from a list

> Turn a list of clients and hours into Fatture in Cloud invoices, check the e-invoice XML and send to SDI after your OK. Runs from Claude Code or n8n.

Source: https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server/create-and-send-invoices

At month end a freelancer has hours per client in a spreadsheet or a chat, and has to retype each one as an invoice, then send each as an electronic invoice to the Sistema di Interscambio.

Cotlet does it in your own Fatture in Cloud account with list\_clients, create\_client, create\_invoice, verify\_einvoice and send\_einvoice, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=fatture-in-cloud) [All Fatture in Cloud tools](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Fatture in Cloud do this on its own?

Fatture in Cloud documents the whole flow in its API (checked 14 Oct 2026): createIssuedDocument, verifyEInvoiceXml and sendEInvoice with a dry\_run option. It has no MCP server, and no way to turn a list of hours into invoices without code that registers an OAuth app or holds a manual token. Zapier lists create-issued-document and send-e-invoice actions for the same API.

## How you do it in Fatture in Cloud today

1. For each client, open the client record, or create it with name, VAT number or tax code, address and, for an e-invoice, the e-invoice code or certified email.
2. Create a new invoice, fill the document date, the lines with net price and VAT, and the payment due date.
3. Send the invoice to the SDI as an electronic invoice; Fatture in Cloud says sending to the SDI is automatic.
4. Open the document later to see its status and the notification of delivery; a rejection shows as Scartata.
5. Repeat for every client every month, and retype anything that repeats from last month.

## How to create and send Fatture in Cloud invoices from a list

Prompt

```
Here are this month's three billable clients with hours and rates. Create a Fatture in Cloud invoice for each, add the client first if it is new, check the e-invoice XML and wait for my OK before sending to SDI.
```

1. 01  
### Match each client  
The agent calls list\_clients with the name or VAT number from your list and uses the existing record when exactly one matches. Two matches or none are reported to you instead of guessed.
2. 02  
### Add the missing clients  
For a client that does not exist, create\_client stores the name, VAT number or tax code and address from your list. For an e-invoice the agent also needs the e-invoice code or certified email, and asks for it if it is missing.
3. 03  
### Build each invoice  
create\_invoice gets the client, the lines (description, quantity, net price, VAT) and the due date. The agent sums the lines itself and shows you net, VAT and gross before you confirm.
4. 04  
### Check the XML before SDI  
verify\_einvoice runs the checks without sending. A validation error, such as an invalid date field, is shown to you with the invoice it belongs to, and that invoice is not sent.
5. 05  
### Send only what you approved  
send\_einvoice runs per invoice after your OK, because a sent e-invoice is legally binding and reaches the client and the tax authority. The agent reports each invoice as accepted by the call or failed.

### What you get back

Example data

```
Clients matched: 2, created: 1 (Studio Verdi SRL)
Invoices created: 3
- #14 Rossi Consulting SRL: net 1500.00, VAT 330.00, gross 1830.00
- #15 Studio Verdi SRL: net 800.00, VAT 176.00, gross 976.00
- #16 Bianchi Design: net 450.00, VAT 99.00, gross 549.00
XML check passed: 3, failed: 0
Sent to SDI after your OK: 3
```

### Other ways to ask

- Create the three invoices but do not send anything; list them for me to review in Fatture in Cloud.
- Create this month's invoice for each client I billed last month, with the same lines, and verify the XML.
- Run the XML check on every invoice that is not sent yet and tell me which ones would fail.

## What Fatture in Cloud allows, and what to know first

- Fatture in Cloud's send e-invoice call has a dry\_run option that runs every check without dispatching to the SDI, and it needs e-invoicing to be active on the account.
- For an e-invoice the client needs the e-invoice flag, the e-invoice code (ei\_code) and optionally a certified email.
- An invoice carries a VAT kind: I (immediata), D (differita) or S (split payment), and an accepted payment method code such as MP05.
- Every line needs a VAT type, with a net or gross price and a quantity.
- A sub-user needs the company admin to grant permissions under Impostazioni, Utenti e Permessi, or calls fail with 403.

create\_invoice and send\_einvoice ask for your OK by default. To run it on a schedule without you, switch confirmation off for those tools in your dashboard.

Sources: [Developers: Invoice creation](https://developers.fattureincloud.it/docs/guides/invoice-creation/) · [Developers: E-Invoice management](https://developers.fattureincloud.it/docs/guides/e-invoice-management/) · [Developers: Scopes](https://developers.fattureincloud.it/docs/basics/scopes) · [Fatture in Cloud: product page](https://www.fattureincloud.it/)

## Call create\_invoice from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/fatture-in-cloud/clients/5107/invoices \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"date":"2026-10-31","subject":"October consulting","e_invoice":true,"lines":[{"description":"Consulting, 10 hours","quantity":10,"net_price":150,"vat_percent":22}],"due_date":"2026-11-30"}'
```

Example response

```
{
"id": 88120,
"number": 14,
"date": "2026-10-31",
"client_id": 5107,
"e_invoice": true,
"ei_status": "not_sent",
"amount_net": 1500,
"amount_vat": 330,
"amount_gross": 1830,
"due_date": "2026-11-30"
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is fatture\_in\_cloud\_write → create\_invoice. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server.md#automations)

## Fatture in Cloud tools this automation uses

__Cotlet Fatture in Cloud tools used to create and send Fatture in Cloud invoices from a list__
| Tool | Parameters |
| ---------------- | -------------------------------------------------------------------------------------- |
| list\_clients | company\_id, query, page, per\_page |
| create\_client | company\_id, name, vat\_number, tax\_code, address, e\_invoice\_code, certified\_email |
| create\_invoice | company\_id, client\_id, date, subject, e\_invoice, lines, due\_date |
| verify\_einvoice | company\_id, invoice\_id |
| send\_einvoice | company\_id, invoice\_id, dry\_run |

[All 13 Fatture in Cloud tools with descriptions](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Fatture in Cloud to Cotlet?

Yes. You sign in to Fatture in Cloud yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fatture in Cloud once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Fatture in Cloud automations

- [Find and explain rejected Fatture in Cloud e-invoices](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server/fix-rejected-e-invoices.md)
- [List unpaid Fatture in Cloud invoices and draft reminders](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server/list-unpaid-invoices.md)
- [Fatture in Cloud API and MCP server: every tool](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Fatture in Cloud.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Fatture in Cloud.

[Sign up free](https://cotlet.dev/app/signup?app=fatture-in-cloud)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.