Prepare an invoice by text
Internal chat prepares proposals; it does not save invoices. Use the conversation to draft a description or clarify the information you need to review. Creation, issuance and delivery happen outside this chat.
A useful example
This is a fictional request example, not an executed operation:
Help me draft an invoice description: ten consulting hours at EUR 80 per hour and EUR 200 for travel. Identify missing information. Do not invent the client or the tax treatment.
Those lines total EUR 1,000 before taxes or other adjustments. Check the amounts in the editor. Chat does not search your client directory or create a missing contact.
Complete the invoice in the application
- Open Invoices in the appropriate workspace.
- Select the actual client and complete the required fields; a proposed name is not proof of identity.
- Enter and review lines, currency, taxes, dates and terms.
- Save or issue using the appropriate interface action. Check the resulting document in the list.
A chat response does not reserve a number, save a draft or send an invoice. It does not automatically transfer fields into the editor either. Delivery options are handled separately.
Work with a connected agent
For programmatic operations, use the MCP reference or the REST API. First check the workspace, authorization and schema of the available operation.
Separate client identification, document creation and delivery. Do not assume one request can create, issue and send, or that all tools accept the same fields. Verify each operation's result before continuing.
Before considering the task complete
Check the saved document, not just the conversation text. Make sure an ambiguous response has not led to a duplicate operation. If the request involved an expense or quote, use the corresponding module: the chat proposal does not persist those either.