Fatture in Cloud automation · runs daily
Find and explain rejected Fatture in Cloud e-invoices
An invoice sent to SDI can come back days later as Scartata, and if nobody opens the document, the 5-day window to reissue it runs out quietly.
Cotlet does it in your own Fatture in Cloud account with list_invoices, get_einvoice_status and get_einvoice_rejection_reason, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Can Fatture in Cloud do this on its own?
Fatture in Cloud shows the rejection status and notification in the app, and its API returns ei_status plus getEInvoiceRejectionReason (reason, code, date) and a webhook for e-invoice status updates (checked 14 Oct 2026). It has no built-in daily summary of rejections, and no MCP server that an agent can read it through.
How you do it in Fatture in Cloud today
- Open the invoices you sent and look at the status of each e-document; a rejection by SDI shows as Scartata a few days after sending.
- Open the notification of the rejected invoice to read the error code and its short description.
- Edit the document to fix the error. Fatture in Cloud's guide says a rejected invoice counts as not issued, so no credit note is needed.
- Send it again within 5 days of the rejection notice, preferably with the same number and date as the original.
- Nothing alerts you if you do not look, so rejections are easy to miss between invoicing days.
How to find and explain rejected Fatture in Cloud e-invoices
Every morning, check the e-invoices I sent in the last 14 days in Fatture in Cloud. For each one rejected or discarded by SDI, tell me the error code and reason and what to correct. Do not resend anything.- 01
Collect recent e-invoices
list_invoices pulls the invoices of the last 14 days, or the window in your prompt, that were sent as e-invoices, so old history is not re-read each morning.
- 02
Read the status of each
get_einvoice_status returns the ei_status of every invoice. The agent groups them: accepted, still in transit (attempt, pending, processing), and problems (discarded, not delivered, error, rejected).
- 03
Fetch the reason for discarded ones
For invoices with status discarded, get_einvoice_rejection_reason returns the SDI code, the reason text and the date, and the agent counts 5 days from that date.
- 04
Say what to change
The agent matches the reason to the invoice field, such as a wrong tax code on the client, and states which field to correct. It does not edit or resend: both change a legally binding document.
- 05
Keep the quiet ones quiet
Accepted invoices are counted but not listed, so the report is short on a good day.
What you get back
E-invoices checked (last 14 days): 12
Accepted: 9
In transit: 1 (#17, processing)
Discarded by SDI: 2
- #14 Rossi Consulting SRL, code 0036: customer tax code is incorrect, reissue by 2026-11-05
- #15 Studio Verdi SRL, code 00417: seller or customer identifier missing, reissue by 2026-11-06Other ways to ask
- Do the same check right after I send a batch of invoices, and again two days later.
- Only list invoices not delivered, with the client's name, so I can email them a copy.
- List every discarded invoice from this quarter and group them by error code.
What Fatture in Cloud allows, and what to know first
- Fatture in Cloud documents these ei_status values: attempt, missing, not_sent, sent, pending, processing, error, discarded, not_delivered, accepted, rejected, no_response, manual_accepted and manual_rejected.
- The rejection reason call returns the reason text, the SDI code and the date of the rejection, and is meant for invoices discarded by SDI.
- Fatture in Cloud's guide says a rejected invoice is considered not issued, so no variation note to the SDI is needed, and it should be sent again within 5 days of the rejection notice.
- The guide prefers reissuing with the same number and date; a new number and date is possible, but then the 12-day deadline from the operation date still applies.
- The status needs the detailed fields, so a plain list does not show ei_status.
Every tool here only reads, so it can run daily from n8n, Make, Zapier or cron without waiting for your OK.
Sources: Developers: E-Invoice management · Fatture in Cloud: Fattura elettronica scartata dal SdI · Fatture in Cloud: Problemi fattura elettronica
Call get_einvoice_rejection_reason from a script
curl https://cotlet.dev/api/v1/fatture-in-cloud/invoices/88120/einvoice-rejection-reason \
-H "Authorization: Bearer $COTLET_API_KEY"{
"invoice_id": 88120,
"reason": "Customer tax code is incorrect.",
"code": "0036",
"date": "2026-10-05"
}MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is fatture_in_cloud_read → get_einvoice_rejection_reason. Example data.
Schedule it in n8n, Make, Zapier or cronFatture in Cloud tools this automation uses
| Tool | Parameters |
|---|---|
| list_invoices | company_id, date_from, date_to, client_id, payment_status, due_before, page, per_page |
| get_einvoice_status | company_id, invoice_id |
| get_einvoice_rejection_reason | company_id, invoice_id |
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.
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.