[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)

# Find and explain rejected Fatture in Cloud e-invoices

> Check every day which Fatture in Cloud e-invoices SDI rejected, get the error code and reason, and fix them inside the 5-day window. Runs daily.

Source: https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server/fix-rejected-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.

[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 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

1. 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.
2. Open the notification of the rejected invoice to read the error code and its short description.
3. 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.
4. Send it again within 5 days of the rejection notice, preferably with the same number and date as the original.
5. 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

Prompt

```
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.
```

1. 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.
2. 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).
3. 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.
4. 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.
5. 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

Example data

```
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-06
```

### Other 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](https://developers.fattureincloud.it/docs/guides/e-invoice-management/) · [Fatture in Cloud: Fattura elettronica scartata dal SdI](https://www.fattureincloud.it/guida-fatturazione-elettronica/fattura-elettronica-scartata/) · [Fatture in Cloud: Problemi fattura elettronica](https://www.fattureincloud.it/guida-fatturazione-elettronica/problemi-fattura-elettronica/)

## Call get\_einvoice\_rejection\_reason from a script

curl

```
curl https://cotlet.dev/api/v1/fatture-in-cloud/invoices/88120/einvoice-rejection-reason \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"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 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 find and explain rejected Fatture in Cloud e-invoices__
| 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 |

[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

- [Create and send Fatture in Cloud invoices from a list](https://cotlet.dev/integrations/fatture-in-cloud-api-mcp-server/create-and-send-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.