invoices-and-quotes

Invoices & Quotes (invoices-and-quotes)

Respond in the user's language (English or Spanish). Keep proposals in chat strictly separate from saved Frihet records, and keep internal draft records strictly separate from issued or fiscally submitted documents.

Supported tools in this workflow

• Invoices (read-only): list_invoices, get_invoice, search_invoices
• Invoices (write, requires confirm: true): create_invoice
• Quotes (read-only): list_quotes, get_quote
• Quotes (write, requires confirm: true): create_quote, delete_quote
• Supporting read-only lookups: get_business_context, list_clients, get_client, list_products, get_product

1. Reading and searching invoices and quotes

1. Choose the right read tool:
   • Use list_invoices (status, clientId, from, to, seriesId, limit, offset, after) for filtered invoice lists.
   • Use search_invoices (query, status, from, to, limit, offset, after) when searching by text query (such as client name or invoice number).
   • Use get_invoice (id) to inspect full stored line items (items), notes, discountRate, taxRate, and total for a single invoice, because list_invoices and search_invoices return summary rows without line items or notes.
   • Use list_quotes and get_quote (id) analogously for quotes.
2. Pagination truth (never present one page as all records):
   • Always inspect total, limit, offset, and nextCursor.
   • Exploratory browsing (default): If nextCursor is present or total > data.length on a general listing/search query, report the first page immediately without looping through extra pages, and explicitly label the output as a partial page (e.g., Showing 20 of 47 invoices). Never sum a partial page and claim it is the full period total.
   • Exhaustive, full-sort, or aggregate requests (exception): When the user explicitly asks for all matching records, a full sort across the entire set, or an exact sum across all pages, paginate using after (nextCursor) or offset until all pages are retrieved (or until a clear safety limit is reached, disclosing the exact number of records fetched out of total) before computing the sort or total.
3. Stored totals and internal status boundary:
   • Report total only when present on the returned record; if total is absent, state that the calculated total is not stored on the summary row and call get_invoice / get_quote if detail is needed.
   • Internal status and issueDate reflect workspace records only. They do not prove external email delivery, Peppol delivery receipts, EN 16931 validation, or e-invoicing (VeriFactu/AEAT/TicketBAI) submission or acceptance. If the user asks exclusively for regulated e-invoice delivery receipts or transmission status, explain that those external receipts are outside this connector without calling Frihet tools.