update_xero_invoice
update_xero_invoiceProposes a change to an EXISTING Xero invoice - it does NOT change anything in Xero itself, and never will on its own. This queues a pending change that a human must explicitly approve (your Xero MCP connector - the exact link is this response's own approvalUrl field) before Xero is touched at all; you have no way to approve it yourself. Only works on invoices that are still DRAFT or SUBMITTED in Xero - get_xero_invoice tells you the current status first. Cannot change which contact the invoice is for, or its type - void it and create a new one for that. If you include lineItems at all, it REPLACES every line item on the invoice; to change one, list all of them, or Xero will delete the ones you don't mention. Tell the user exactly what you are proposing to change and that it needs their approval in Invio - never describe it as done. You can also change the invoice currency (currency, checked against the currencies this organisation is actually set up to invoice in) and how its amounts are read (lineAmountTypes: "Exclusive", "Inclusive" or "NoTax"). Omit either to leave it exactly as it is - neither is reset to a default when you leave it out. Changing lineAmountTypes re-interprets EVERY amount already on the invoice and so changes its total: only send it when the user actually asked for that, and say plainly that the total will move. DATES: date and dueDate are strict YYYY-MM-DD, so you always have to convert whatever the user actually said. A date carrying a month name ("8 Sep", "Sept 8th"), a weekday ("last Tuesday"), or an already-unambiguous full date ("2026-09-08") is yours to convert normally. A BARE NUMERIC date with no month name - "9/8", "08/09", "9-8" - is the one that is not: it means 9 August to most of the world and 8 September in the United States, and getting it wrong puts an invoice a month out in a way nobody skimming the approval card will catch. This Invio account is based in a country that writes the DAY first, so read a bare "9/8" as 9 August, not 8 September. Say in plain words how you read it ("I read 9/8 as 9 August") so the user can correct you before they approve. If their own wording points the other way anywhere in the same request, ask them which they meant instead of picking.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | New invoice date, YYYY-MM-DD. Omit to leave unchanged. If the user wrote a bare numeric date with no month name ("9/8", "08/09"), do NOT settle it on your own judgement - it is 9 August to most of the world and 8 September in the US, and nothing downstream of this field can tell which you meant once it is a date. Follow the DATES instruction in this tool's description. | |
| dueDate | No | New due date, YYYY-MM-DD. Omit to leave unchanged. If the user wrote a bare numeric date with no month name ("9/8", "08/09"), do NOT settle it on your own judgement - it is 9 August to most of the world and 8 September in the US, and nothing downstream of this field can tell which you meant once it is a date. Follow the DATES instruction in this tool's description. | |
| currency | No | New currency for the invoice, e.g. "NZD". Checked against the currencies this organisation is actually set up to invoice in. Omit to leave the invoice in whatever currency it is already in - this never resets it to the organisation's base currency. | |
| invoiceId | Yes | Get this from list_xero_invoices or get_xero_invoice first, never guess. | |
| lineItems | No | If you include this at all, it REPLACES every line item on the invoice - Xero deletes any line item you do not list here. To change one line item, list ALL of them (the ones you are not changing too), never just the one that changed. Omit this field entirely to leave every line item as it is. | |
| reference | No | New reference text. Omit to leave unchanged. | |
| organisation | No | The Xero organisation to use, by its display name. Only needed if this connection reaches more than one organisation - omit it when there is only one. | |
| lineAmountTypes | No | Change how this invoice reads its unitAmounts: "Exclusive" (amounts exclude tax), "Inclusive" (amounts already include tax), or "NoTax". Omit to leave it exactly as it is. Changing this re-interprets EVERY amount already on the invoice and so changes its total - only set it when the user actually asks for that (e.g. "those figures were meant to include GST"). |