← e-invoices.itCONTENT HISTORY

Update to e-invoices.it

Snapshot Nov 10, 2026 · 00:09 UTC · version 1.4.0

Collection source: downloaded plugin package.

WHAT CHANGED

Payment or plan references changed

Full description — Now says: it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for...

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save e-invoices.it and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 5, 2026 · 00:58 UTC

it.

After

Nov 10, 2026 · 00:09 UTC

it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant.

Skill instructions

Before

Nov 5, 2026 · 00:58 UTC

it. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected ("scartata"). termini): what it means. - **Several invoices** (more files, or a zip with more than one in...

After

Nov 10, 2026 · 00:09 UTC

it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an at...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: read-italian-e-invoice
-description: Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected ("scartata").
+description: Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected ("scartata").
 ---
 
 # Read Italian e-invoice files
@@ -16,7 +16,10 @@
   with the rejected invoice if attached: each error explained, with the current
   values of the fields it concerns;
 - **another SdI receipt** (delivery receipt, mancata consegna, esito, decorrenza
-  termini): what it means.
+  termini): what it means;
+- **several invoices** (more files, a zip or a download massivo from Fatture e
+  Corrispettivi): aggregates for the business and its accountant, not the single
+  invoices.
 
 ## When to use it
 
@@ -71,6 +74,30 @@
 6. `NotaFattura`: if present, mention it. The attached invoice may not be the one
    that was rejected.
 
+## How to answer about several invoices
+
+1. Answer only from the tool result (`structuredContent`): aggregates, not the single
+   invoices. `company` is the business the invoices are about (the party of most of
+   them); if `tied_with` is set, another party has as many, so say which one was
+   taken and ask if it is the right one.
+2. Unless the user asks something specific, give a short overview:
+   - the company and the period;
+   - issued (`sales`) and received (`purchases`) invoices: number, taxable amount,
+     VAT, total; the largest customers and suppliers;
+   - the VAT position (`vat_position`) and, if useful, the trend by period
+     (`by_period`) and the expected cash flow from the due dates (`cash_flow`);
+   - what an accountant (commercialista) looks at, when present: imposta di bollo per
+     quarter with its F24 code (`bollo`, and `to_check`: invoices without bollo that
+     may need it), ritenute d'acconto operated and suffered per month and supplier
+     (`ritenute`), and the anomalies to check (`controlli`, each with the invoices
+     concerned).
+3. `remarks` point out what stands out (a customer or supplier with a large share,
+   a weak period, a possible cash shortfall): mention them.
+4. Everything is an aid to be checked, not a tax return or a verification of the
+   invoices: say so when the user may act on it.
+5. For one Excel file, readable PDFs or the full dashboard of the same invoices,
+   point to https://e-invoices.it.
+
 ## In every answer
 
 - Answer in the user's language. Keep the Italian terms and field names the user
@@ -79,10 +106,10 @@
 
 ## When the tool cannot read the files
 
-- **Several invoices** (more files, or a zip with more than one invoice): the tool
-  reads one at a time and answers with a note. Tell the user that e-invoices.it
-  turns many invoices into one Excel file, PDFs or a dashboard at
-  https://e-invoices.it, and offer to read one invoice here.
+- **Too many invoices**, or **the analyses of several invoices are used up** for
+  now: the chat has a limit of invoices per call and of analyses per user. Relay the
+  note: e-invoices.it handles many invoices at once (one Excel file, PDFs, a
+  dashboard) at https://e-invoices.it; or offer to look at fewer invoices here.
 - **Several notifiche di scarto**: the tool explains one at a time; ask which one.
 - **Another SdI receipt**: relay what the tool says. These are not rejections.
 - **Not an e-invoice** or an unreadable file: say so, and suggest the XML or
Full technical diff · 2 changed fields

changed /description

BEFORE
"Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\")."
AFTER
"Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\")."

changed /skill_md_contents

BEFORE
"---\nname: read-italian-e-invoice\ndescription: Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\").\n---\n\n# Read Italian e-invoice files\n\nThe `read_e_invoice_files` tool of e-invoices.it reads the files of Italian\nelectronic invoicing (FatturaPA, the XML exchanged through the Sistema di\nInterscambio, SdI). What it returns depends on the files:\n\n- **one invoice**: its data, and the invoice is shown as a readable document next to\n  the answer;\n- **a notifica di scarto** (the SdI rejected an invoice the user sent: an XML file\n  with `_NS_` in its name and one or more five-digit error codes, e.g. `00404`),\n  with the rejected invoice if attached: each error explained, with the current\n  values of the fields it concerns;\n- **another SdI receipt** (delivery receipt, mancata consegna, esito, decorrenza\n  termini): what it means.\n\n## When to use it\n\n- The user attached a `.xml`, `.xml.p7m` or `.zip` file that is, or may be, an\n  Italian e-invoice or an SdI receipt. Pass **all** attached files in one call: a\n  notifica di scarto together with its invoice gives the best answer.\n- Call `read_e_invoice_files` with the attached files. Do not ask the user to paste\n  the XML as text, and do not try to read the file yourself first.\n- The user says an invoice was rejected but attached only the invoice: read it, and\n  ask for the `_NS_` file they received (by PEC, from their invoicing software or\n  from the Fatture e Corrispettivi portal) to explain the rejection.\n- Do not call it without an attached file, or to create, check in advance, change\n  or send an invoice: it only reads.\n\n## How to answer about an invoice\n\n1. Answer only from the tool result (`structuredContent`). Never invent or estimate a\n   value; if a field is missing, say that the invoice does not contain it.\n2. Unless the user asks something specific, give a short summary:\n   - document type, number and date\n   - supplier and customer, with their VAT numbers\n   - total amount and currency; the net amount to pay if there is withholding tax\n   - due dates, payment method and IBAN\n   - names of the attachments, if any\n3. The invoice is shown in full next to your answer: do not repeat every line item\n   unless the user asks for them.\n4. Codes: the result has a description next to each code (document type `TD..`, VAT\n   nature `N..`, VAT due `I`/`D`/`S`, payment method `MP..`). Use the descriptions and\n   explain them briefly when they matter, e.g. `S` is split payment.\n5. Amounts with two decimals and their currency; dates in the user's usual format.\n\n## How to answer about a rejection (notifica di scarto)\n\n1. Answer only from the tool result (`structuredContent`). For each error in\n   `Errori`:\n   - the code and, in one sentence, what is wrong (`Spiegazione`; else the SdI's\n     `Descrizione`);\n   - where: the field (`Campi`) and, if the invoice was attached, the value it has\n     now (`ValoriNellaFattura`);\n   - the correction: start from `Correzione` and the SdI's `Suggerimento`, and make\n     it concrete with the values, e.g. \"line 3: 8 × 18.40 = 147.20, not 147.00\".\n2. The SdI's `Descrizione` often names the exact field, line or value: use it.\n3. Keep the correction a **proposal**. Say what to change and in which field; the\n   user changes it in their invoicing software. Do not write a corrected XML file\n   unless the user asks for it, and if you do, say that their software has to\n   produce and sign the file it sends.\n4. When you cannot tell the right value (a VAT number, the recipient code, the\n   correct VAT nature), say what to check and with whom (the customer, their\n   accountant), and do not guess.\n5. End with what to do now (`DopoLoScarto`): the rejected invoice counts as not\n   issued and is sent again, corrected.\n6. `NotaFattura`: if present, mention it. The attached invoice may not be the one\n   that was rejected.\n\n## In every answer\n\n- Answer in the user's language. Keep the Italian terms and field names the user\n  sees on the invoice or in their software (imponibile, ritenuta d'acconto, imposta\n  di bollo, PrezzoTotale) and translate them once.\n\n## When the tool cannot read the files\n\n- **Several invoices** (more files, or a zip with more than one invoice): the tool\n  reads one at a time and answers with a note. Tell the user that e-invoices.it\n  turns many invoices into one Excel file, PDFs or a dashboard at\n  https://e-invoices.it, and offer to read one invoice here.\n- **Several notifiche di scarto**: the tool explains one at a time; ask which one.\n- **Another SdI receipt**: relay what the tool says. These are not rejections.\n- **Not an e-invoice** or an unreadable file: say so, and suggest the XML or\n  `.xml.p7m` from the Agenzia delle Entrate portal (Fatture e Corrispettivi) or from\n  the supplier. A PDF is only a copy of the invoice and cannot be read by the tool.\n- **The service is busy**: say so and suggest trying again in a minute.\n\n## Limits\n\n- This is no tax or legal advice, and e-invoices.it does not check invoices before\n  they are sent: a corrected invoice may still be rejected for another reason. For\n  decisions and doubts about VAT, refer the user to their accountant\n  (commercialista).\n- The legally valid invoice is the XML file; a PDF attached to it is only a copy.\n- e-invoices.it processes the files only in memory: it does not store them and\n  does not log anything about them. Say only this about e-invoices.it, and make no\n  statement about how ChatGPT or OpenAI handle the user's data.\n"
AFTER
"---\nname: read-italian-e-invoice\ndescription: Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\").\n---\n\n# Read Italian e-invoice files\n\nThe `read_e_invoice_files` tool of e-invoices.it reads the files of Italian\nelectronic invoicing (FatturaPA, the XML exchanged through the Sistema di\nInterscambio, SdI). What it returns depends on the files:\n\n- **one invoice**: its data, and the invoice is shown as a readable document next to\n  the answer;\n- **a notifica di scarto** (the SdI rejected an invoice the user sent: an XML file\n  with `_NS_` in its name and one or more five-digit error codes, e.g. `00404`),\n  with the rejected invoice if attached: each error explained, with the current\n  values of the fields it concerns;\n- **another SdI receipt** (delivery receipt, mancata consegna, esito, decorrenza\n  termini): what it means;\n- **several invoices** (more files, a zip or a download massivo from Fatture e\n  Corrispettivi): aggregates for the business and its accountant, not the single\n  invoices.\n\n## When to use it\n\n- The user attached a `.xml`, `.xml.p7m` or `.zip` file that is, or may be, an\n  Italian e-invoice or an SdI receipt. Pass **all** attached files in one call: a\n  notifica di scarto together with its invoice gives the best answer.\n- Call `read_e_invoice_files` with the attached files. Do not ask the user to paste\n  the XML as text, and do not try to read the file yourself first.\n- The user says an invoice was rejected but attached only the invoice: read it, and\n  ask for the `_NS_` file they received (by PEC, from their invoicing software or\n  from the Fatture e Corrispettivi portal) to explain the rejection.\n- Do not call it without an attached file, or to create, check in advance, change\n  or send an invoice: it only reads.\n\n## How to answer about an invoice\n\n1. Answer only from the tool result (`structuredContent`). Never invent or estimate a\n   value; if a field is missing, say that the invoice does not contain it.\n2. Unless the user asks something specific, give a short summary:\n   - document type, number and date\n   - supplier and customer, with their VAT numbers\n   - total amount and currency; the net amount to pay if there is withholding tax\n   - due dates, payment method and IBAN\n   - names of the attachments, if any\n3. The invoice is shown in full next to your answer: do not repeat every line item\n   unless the user asks for them.\n4. Codes: the result has a description next to each code (document type `TD..`, VAT\n   nature `N..`, VAT due `I`/`D`/`S`, payment method `MP..`). Use the descriptions and\n   explain them briefly when they matter, e.g. `S` is split payment.\n5. Amounts with two decimals and their currency; dates in the user's usual format.\n\n## How to answer about a rejection (notifica di scarto)\n\n1. Answer only from the tool result (`structuredContent`). For each error in\n   `Errori`:\n   - the code and, in one sentence, what is wrong (`Spiegazione`; else the SdI's\n     `Descrizione`);\n   - where: the field (`Campi`) and, if the invoice was attached, the value it has\n     now (`ValoriNellaFattura`);\n   - the correction: start from `Correzione` and the SdI's `Suggerimento`, and make\n     it concrete with the values, e.g. \"line 3: 8 × 18.40 = 147.20, not 147.00\".\n2. The SdI's `Descrizione` often names the exact field, line or value: use it.\n3. Keep the correction a **proposal**. Say what to change and in which field; the\n   user changes it in their invoicing software. Do not write a corrected XML file\n   unless the user asks for it, and if you do, say that their software has to\n   produce and sign the file it sends.\n4. When you cannot tell the right value (a VAT number, the recipient code, the\n   correct VAT nature), say what to check and with whom (the customer, their\n   accountant), and do not guess.\n5. End with what to do now (`DopoLoScarto`): the rejected invoice counts as not\n   issued and is sent again, corrected.\n6. `NotaFattura`: if present, mention it. The attached invoice may not be the one\n   that was rejected.\n\n## How to answer about several invoices\n\n1. Answer only from the tool result (`structuredContent`): aggregates, not the single\n   invoices. `company` is the business the invoices are about (the party of most of\n   them); if `tied_with` is set, another party has as many, so say which one was\n   taken and ask if it is the right one.\n2. Unless the user asks something specific, give a short overview:\n   - the company and the period;\n   - issued (`sales`) and received (`purchases`) invoices: number, taxable amount,\n     VAT, total; the largest customers and suppliers;\n   - the VAT position (`vat_position`) and, if useful, the trend by period\n     (`by_period`) and the expected cash flow from the due dates (`cash_flow`);\n   - what an accountant (commercialista) looks at, when present: imposta di bollo per\n     quarter with its F24 code (`bollo`, and `to_check`: invoices without bollo that\n     may need it), ritenute d'acconto operated and suffered per month and supplier\n     (`ritenute`), and the anomalies to check (`controlli`, each with the invoices\n     concerned).\n3. `remarks` point out what stands out (a customer or supplier with a large share,\n   a weak period, a possible cash shortfall): mention them.\n4. Everything is an aid to be checked, not a tax return or a verification of the\n   invoices: say so when the user may act on it.\n5. For one Excel file, readable PDFs or the full dashboard of the same invoices,\n   point to https://e-invoices.it.\n\n## In every answer\n\n- Answer in the user's language. Keep the Italian terms and field names the user\n  sees on the invoice or in their software (imponibile, ritenuta d'acconto, imposta\n  di bollo, PrezzoTotale) and translate them once.\n\n## When the tool cannot read the files\n\n- **Too many invoices**, or **the analyses of several invoices are used up** for\n  now: the chat has a limit of invoices per call and of analyses per user. Relay the\n  note: e-invoices.it handles many invoices at once (one Excel file, PDFs, a\n  dashboard) at https://e-invoices.it; or offer to look at fewer invoices here.\n- **Several notifiche di scarto**: the tool explains one at a time; ask which one.\n- **Another SdI receipt**: relay what the tool says. These are not rejections.\n- **Not an e-invoice** or an unreadable file: say so, and suggest the XML or\n  `.xml.p7m` from the Agenzia delle Entrate portal (Fatture e Corrispettivi) or from\n  the supplier. A PDF is only a copy of the invoice and cannot be read by the tool.\n- **The service is busy**: say so and suggest trying again in a minute.\n\n## Limits\n\n- This is no tax or legal advice, and e-invoices.it does not check invoices before\n  they are sent: a corrected invoice may still be rejected for another reason. For\n  decisions and doubts about VAT, refer the user to their accountant\n  (commercialista).\n- The legally valid invoice is the XML file; a PDF attached to it is only a copy.\n- e-invoices.it processes the files only in memory: it does not store them and\n  does not log anything about them. Say only this about e-invoices.it, and make no\n  statement about how ChatGPT or OpenAI handle the user's data.\n"
Full snapshot data
{
  "description": "Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\").",
  "included_files": [],
  "name": "read-italian-e-invoice",
  "skill_md_contents": "---\nname: read-italian-e-invoice\ndescription: Read the files of Italian electronic invoicing that the user attached (FatturaPA invoices as .xml, signed .xml.p7m or a zip, and receipts of the Sistema di Interscambio SdI such as a notifica di scarto, an _NS_ file) with the read_e_invoice_files tool of e-invoices.it. Explain an invoice - parties, amounts, VAT, due dates, payment details, withholding tax - or why the SdI rejected an invoice the user sent and how to correct it, or sum up several invoices (a download massivo) - revenue, costs, VAT, top customers and suppliers, imposta di bollo, ritenute and anomalies to check for the accountant. Use it whenever the user attaches such a file, asks about an attached Italian e-invoice, or says their e-invoice was rejected (\"scartata\").\n---\n\n# Read Italian e-invoice files\n\nThe `read_e_invoice_files` tool of e-invoices.it reads the files of Italian\nelectronic invoicing (FatturaPA, the XML exchanged through the Sistema di\nInterscambio, SdI). What it returns depends on the files:\n\n- **one invoice**: its data, and the invoice is shown as a readable document next to\n  the answer;\n- **a notifica di scarto** (the SdI rejected an invoice the user sent: an XML file\n  with `_NS_` in its name and one or more five-digit error codes, e.g. `00404`),\n  with the rejected invoice if attached: each error explained, with the current\n  values of the fields it concerns;\n- **another SdI receipt** (delivery receipt, mancata consegna, esito, decorrenza\n  termini): what it means;\n- **several invoices** (more files, a zip or a download massivo from Fatture e\n  Corrispettivi): aggregates for the business and its accountant, not the single\n  invoices.\n\n## When to use it\n\n- The user attached a `.xml`, `.xml.p7m` or `.zip` file that is, or may be, an\n  Italian e-invoice or an SdI receipt. Pass **all** attached files in one call: a\n  notifica di scarto together with its invoice gives the best answer.\n- Call `read_e_invoice_files` with the attached files. Do not ask the user to paste\n  the XML as text, and do not try to read the file yourself first.\n- The user says an invoice was rejected but attached only the invoice: read it, and\n  ask for the `_NS_` file they received (by PEC, from their invoicing software or\n  from the Fatture e Corrispettivi portal) to explain the rejection.\n- Do not call it without an attached file, or to create, check in advance, change\n  or send an invoice: it only reads.\n\n## How to answer about an invoice\n\n1. Answer only from the tool result (`structuredContent`). Never invent or estimate a\n   value; if a field is missing, say that the invoice does not contain it.\n2. Unless the user asks something specific, give a short summary:\n   - document type, number and date\n   - supplier and customer, with their VAT numbers\n   - total amount and currency; the net amount to pay if there is withholding tax\n   - due dates, payment method and IBAN\n   - names of the attachments, if any\n3. The invoice is shown in full next to your answer: do not repeat every line item\n   unless the user asks for them.\n4. Codes: the result has a description next to each code (document type `TD..`, VAT\n   nature `N..`, VAT due `I`/`D`/`S`, payment method `MP..`). Use the descriptions and\n   explain them briefly when they matter, e.g. `S` is split payment.\n5. Amounts with two decimals and their currency; dates in the user's usual format.\n\n## How to answer about a rejection (notifica di scarto)\n\n1. Answer only from the tool result (`structuredContent`). For each error in\n   `Errori`:\n   - the code and, in one sentence, what is wrong (`Spiegazione`; else the SdI's\n     `Descrizione`);\n   - where: the field (`Campi`) and, if the invoice was attached, the value it has\n     now (`ValoriNellaFattura`);\n   - the correction: start from `Correzione` and the SdI's `Suggerimento`, and make\n     it concrete with the values, e.g. \"line 3: 8 × 18.40 = 147.20, not 147.00\".\n2. The SdI's `Descrizione` often names the exact field, line or value: use it.\n3. Keep the correction a **proposal**. Say what to change and in which field; the\n   user changes it in their invoicing software. Do not write a corrected XML file\n   unless the user asks for it, and if you do, say that their software has to\n   produce and sign the file it sends.\n4. When you cannot tell the right value (a VAT number, the recipient code, the\n   correct VAT nature), say what to check and with whom (the customer, their\n   accountant), and do not guess.\n5. End with what to do now (`DopoLoScarto`): the rejected invoice counts as not\n   issued and is sent again, corrected.\n6. `NotaFattura`: if present, mention it. The attached invoice may not be the one\n   that was rejected.\n\n## How to answer about several invoices\n\n1. Answer only from the tool result (`structuredContent`): aggregates, not the single\n   invoices. `company` is the business the invoices are about (the party of most of\n   them); if `tied_with` is set, another party has as many, so say which one was\n   taken and ask if it is the right one.\n2. Unless the user asks something specific, give a short overview:\n   - the company and the period;\n   - issued (`sales`) and received (`purchases`) invoices: number, taxable amount,\n     VAT, total; the largest customers and suppliers;\n   - the VAT position (`vat_position`) and, if useful, the trend by period\n     (`by_period`) and the expected cash flow from the due dates (`cash_flow`);\n   - what an accountant (commercialista) looks at, when present: imposta di bollo per\n     quarter with its F24 code (`bollo`, and `to_check`: invoices without bollo that\n     may need it), ritenute d'acconto operated and suffered per month and supplier\n     (`ritenute`), and the anomalies to check (`controlli`, each with the invoices\n     concerned).\n3. `remarks` point out what stands out (a customer or supplier with a large share,\n   a weak period, a possible cash shortfall): mention them.\n4. Everything is an aid to be checked, not a tax return or a verification of the\n   invoices: say so when the user may act on it.\n5. For one Excel file, readable PDFs or the full dashboard of the same invoices,\n   point to https://e-invoices.it.\n\n## In every answer\n\n- Answer in the user's language. Keep the Italian terms and field names the user\n  sees on the invoice or in their software (imponibile, ritenuta d'acconto, imposta\n  di bollo, PrezzoTotale) and translate them once.\n\n## When the tool cannot read the files\n\n- **Too many invoices**, or **the analyses of several invoices are used up** for\n  now: the chat has a limit of invoices per call and of analyses per user. Relay the\n  note: e-invoices.it handles many invoices at once (one Excel file, PDFs, a\n  dashboard) at https://e-invoices.it; or offer to look at fewer invoices here.\n- **Several notifiche di scarto**: the tool explains one at a time; ask which one.\n- **Another SdI receipt**: relay what the tool says. These are not rejections.\n- **Not an e-invoice** or an unreadable file: say so, and suggest the XML or\n  `.xml.p7m` from the Agenzia delle Entrate portal (Fatture e Corrispettivi) or from\n  the supplier. A PDF is only a copy of the invoice and cannot be read by the tool.\n- **The service is busy**: say so and suggest trying again in a minute.\n\n## Limits\n\n- This is no tax or legal advice, and e-invoices.it does not check invoices before\n  they are sent: a corrected invoice may still be rejected for another reason. For\n  decisions and doubts about VAT, refer the user to their accountant\n  (commercialista).\n- The legally valid invoice is the XML file; a PDF attached to it is only a copy.\n- e-invoices.it processes the files only in memory: it does not store them and\n  does not log anything about them. Say only this about e-invoices.it, and make no\n  statement about how ChatGPT or OpenAI handle the user's data.\n"
}

SHA-256 of public snapshot: c82dd5b24201c9ea7f0e1a7efd3220698ba5716fa935b7541ce0ef14811e18cd