Take action on your Spendesk data with AI - MCP Write Tools

Spendesk MCP can now do more than answer questions about your financial data.

With MCP Write Tools, authorised users can ask their AI assistant to take specific actions in Spendesk, such as updating accounting information, creating a supplier, managing analytical fields or preparing a payable for export.

Write Tools are available only for supported actions and only when the user, organisation and MCP connection have the required permissions.

Important: Some Write Tools change data or trigger business operations. Always review the proposed action, its impact and its reversibility before confirming it.

What are MCP Write Tools?

MCP tools connect your AI assistant to Spendesk.

Tool type	What it does	Example
Read Tool	Finds, retrieves or analyses data	“Show all overdue payables”
Write Tool	Creates, updates, archives or triggers an action	“Update the cost centre on this payable”

A Write Tool does not give your AI assistant unrestricted access to Spendesk. Every action remains subject to your Spendesk role and permissions, the scopes granted to the MCP connection, the organisation and entity context, Spendesk business rules, and the availability of the specific tool for your organisation.

Before you use a Write Tool

Before confirming an action, ask your AI assistant to show:

The object that will be changed.
The action that will be performed.
The fields and values that will be affected.
Whether the action can be undone in the Spendesk interface.
Where the action can be undone, if applicable.
What may happen to existing or exported data.

Example: “Before executing this action, tell me whether it can be undone in the Spendesk UI, where I can undo it, and which data could be affected.”

Write Tool reversibility

Status	Meaning
✅ Undo available in Spendesk	The action can be reversed directly through a documented UI action.
⚠️ No one-click undo	The result may be corrected with another action, but Spendesk does not provide a direct Undo button.
🛑 No UI undo	The action cannot currently be reversed from the Spendesk interface. Support intervention or a separate remediation may be required.
⏳ To confirm	The behaviour must be confirmed before this tool is documented as generally available.

Available Write Tools

Suppliers

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_suppliers`	Create one or more supplier records, including supplier and payment information.	⚠️ No one-click undo	Archive the supplier afterwards from Settings → Accounts Payable, if eligible.	Archiving is a corrective action, not a true rollback of the creation.
`update_supplier`	Update selected fields on an existing supplier.	⚠️ No automatic undo	Edit the supplier again with the previous values.	The previous values may not be available to the user.
`archive_supplier`	Archive or restore a supplier while preserving historical records.	✅ Yes	Go to Settings → Accounts Payable → Archived, select the supplier and click Un-archive.	Archiving hides the supplier from future use but preserves historical data.

Chart of Accounts

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_accounts`	Create entries in the company chart of accounts.	⏳ To confirm	Confirm the UI path for archiving or removing an account.	Check whether the account is already used before taking corrective action.
`update_accounts`	Update existing chart-of-accounts entries.	⚠️ No automatic undo	Update the account again with the previous values.	There is no general version rollback described for this action.
`delete_accounts`	Archive or remove chart-of-accounts entries, depending on the supported business rules.	✅ Yes via MCP UI path to confirm	Call `update_accounts` with `isArchived=false` on the same account. Confirm whether the Spendesk UI also exposes restoration.	The account must be fetched with archived records included. Do not publish a UI path until confirmed.

Analytical Fields

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_analytical_field`	Create a company-defined analytical dimension.	⚠️ No one-click undo	Delete or archive the field from the configuration UI, if eligible.	Existing classifications may be affected.
`update_analytical_field`	Update an analytical field configuration.	⚠️ No automatic undo	Edit the field again with the previous values.	There is no automatic rollback of previous values.
`delete_analytical_field`	Delete or archive an analytical field.	🛑 No MCP undo	No restore tool is available in MCP.	The field is soft-deleted, but its values are not deleted. They become stranded and cannot be managed individually.
`create_analytical_field_value`	Add a value to an analytical field.	⚠️ No one-click undo	Delete the value from the configuration UI, if eligible.	The value may already be used on payments.
`update_analytical_field_value`	Update an analytical field value.	⚠️ No automatic undo	Edit the value again with the previous value.	Renaming may affect future selections and reporting.
`delete_analytical_field_value`	Delete an analytical field value.	🛑 No MCP undo	No restore tool is available in MCP.	Review the value and its usage before confirming deletion.

Expense Categories

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_expense_category_field`	Create the company expense-category field.	⚠️ No one-click undo	Delete the field from the configuration UI, if eligible.	This may affect all categories in the field.
`update_expense_category_field`	Update the expense-category field configuration.	⚠️ No automatic undo	Edit the configuration again with the previous values.	Review whether the field is mandatory before changing it.
`delete_expense_category_field`	Delete the expense-category field and its categories.	🛑 No MCP undo	No restore tool is available in MCP.	This action deletes all categories belonging to the field.
`create_expense_category`	Create an employee-facing expense category.	⚠️ No one-click undo	Delete the category from Settings → Organisation → Analytical fields, if eligible.	The category may already be used on payments.
`update_expense_category`	Update an expense category and its classification links.	⚠️ No automatic undo	Edit the category again with the previous values.	Renaming can affect exported payable labels.
`delete_expense_category`	Delete or archive an expense category.	🛑 No MCP undo	No restore tool is available in MCP.	Review the category and its usage before confirming deletion.

Cost Centres

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_cost_center`	Create a cost centre.	⚠️ No one-click undo	Archive or delete the cost centre, if eligible.	Check whether it is already used before taking corrective action.
`update_cost_center`	Update a cost centre.	⚠️ No automatic undo	Edit the cost centre again with the previous values.	No general version rollback is documented.
`delete_cost_center`	Archive or delete a cost centre.	🛑 No MCP undo	No restore tool is available in MCP. Restoration in the Spendesk UI must be confirmed.	High-sensitivity action. Do not describe this as reversible until the UI path is verified.

Payables and Settlements

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`update_payable`	Update accounting information on an existing payable.	⚠️ No automatic undo	Update the payable again with the previous values.	Updating line items may replace several accounting fields at once.
`mark_payable_as_ready`	Move a payable from `toPrepare` to `toExport`.	✅ Yes	Go to Payments → Export → Review, select the payable and send it back to Prepare.	The payable must still be eligible for this state transition.
`mark_payable_as_exported_manually`	Record that a payable was exported outside Spendesk.	🛑 No UI undo currently	No self-service undo is currently documented. Contact Support if a correction is required.	Do not use this action unless the payable was actually exported outside Spendesk.
`mark_settlement_as_exported_manually`	Record that a settlement was handled outside Spendesk.	🛑 Effectively irreversible	No MCP tool can move a settlement back out of the exported state.	Confirm that the settlement was handled outside Spendesk before using this tool.

Purchase Orders

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_purchase_order`	Create a purchase order and spending commitment.	⚠️ No true undo	Cancel the purchase order if it is still eligible.	Cancellation is a separate lifecycle action, not a rollback.
`cancel_purchase_order`	Cancel an open purchase order.	🛑 No UI undo	No direct Undo action is available.	This action is irreversible.
`close_purchase_order`	Close a completed purchase order.	🛑 No UI undo	No direct Undo action is available.	This action is irreversible. Closing also rewrites the PO amount to match the billed amount, so the original approved amount cannot be recovered.

Accounting Exports

Tool	Description	Undo in Spendesk?	Where or how?	Warning
`create_accounting_export`	Trigger a purchase or bank journal export for a defined period.	🛑 No rollback	No user-facing rollback is available.	Each call can mark entries as exported and is not idempotent. Verify the period, journal type and selected records before confirming.

How to use Write Tools effectively

Identify the object clearly

Include the name or ID of the object you want to update.

Good example: “Update payable pay_12345.”

Describe the action explicitly

Be specific about the operation you want to perform.

“Archive supplier supplier_123.”

Ask for a preview first

“Show me what would change on this payable, but do not update it yet.”

Ask about reversibility

“Before executing this action, tell me whether it can be undone in the Spendesk UI, where I can undo it, and what data could be affected.”

Ask for confirmation after the action

“Confirm that the payable was updated and show me its resulting accounting fields.”

Important limitations

A corrective action is not always a rollback

Archiving an object, editing it again or recreating a deleted value does not necessarily restore the exact previous state. In particular, some delete tools have no MCP restore tool, even when the underlying record remains in the database.

If you do not see a direct Undo action in the table above, review the impact carefully before confirming.

Some actions are irreversible

Examples include marking a payable or settlement as manually exported, cancelling or closing a purchase order, deleting an analytical field or value, deleting an expense category or field, and creating an accounting export.

Warning: Review these actions carefully before confirming them. If an action was made by mistake, contact Spendesk Support with the object ID, the action performed and the approximate time of execution.

Data may be affected differently depending on its state

Exported historical records preserve the value used at the time of export.
Records still in Prepare may lose a deleted or changed value.
Future transactions may no longer offer an archived or deleted value.

Permissions and access

Write Tools are available only when your organisation has access to the MCP Write Tools release, your AI connection has the required scopes, your Spendesk role allows the requested operation, the object is eligible for the requested action, and the tool is available for your organisation and environment.

MCP does not bypass Spendesk permissions. Your AI assistant cannot grant itself additional access or use a tool that is not available to your connection.

Security and control

Actions are scoped to your authorised organisation and entities.
Spendesk permissions continue to apply.
The MCP connection cannot expand its own permissions.
Sensitive actions should be reviewed before confirmation.
OAuth credentials should be stored securely and never pasted into an AI conversation.
Access can be revoked from your Spendesk MCP connection settings.

Example prompts

Update a payable

“Show me the accounting fields for payable pay_12345. I want to update its cost centre to Marketing, but do not make any changes yet. Also tell me whether I can undo this change in the Spendesk UI.”

Create a supplier

“Create a supplier named Acme Ltd using the following details. First show me the data that will be created, tell me how I could correct the action if needed, and ask for my confirmation.”

Manage an analytical field

“Add Germany as a value to the Business Unit analytical field. Before doing this, tell me whether the new value can be deleted or restored later.”

Update an expense category

“Rename the expense category Software to Software and AI Tools. Show me which records and configuration may be affected, and tell me whether this can be undone in Spendesk.”

Create a purchase order

“Create a purchase order for Acme Ltd for €12,000, starting on 1 October 2026 and ending on 31 December 2026. Do not create it until I confirm. Also tell me whether the purchase order can later be cancelled or reopened.”

Prepare an accounting export

“Prepare the purchase accounting export for September 2026. Before running it, show me the period, journal type, records included and whether this action can be undone.”

Frequently Asked Questions

Can MCP change my Spendesk data?

Yes. Authorised Write Tools can create, update, archive or trigger specific operations in Spendesk.

Can every user use Write Tools?

No. Access depends on the organisation, the user’s Spendesk permissions and the scopes granted to the MCP connection.

Can MCP modify any Spendesk object?

No. Write Tools are available only for the objects and actions listed in this article.

Can I undo an action?

It depends on the action. This article shows whether a direct Undo action is available in Spendesk and where to find it.

What is the difference between Undo and a corrective action?

An Undo restores the previous state through a dedicated Spendesk action. A corrective action performs another operation to compensate for or modify the result. It may not restore the exact previous state.

What should I do if an action cannot be undone?

Do not perform the action unless you are certain it is correct. If it was already performed by mistake, contact Spendesk Support with the tool name, object ID, action performed, values submitted and approximate time of execution.

Why did my Write Tool action fail?

The most common reasons are missing permissions, missing scope, an invalid object ID, an unsupported object status, an object changed since it was retrieved, missing or invalid information, or the tool being unavailable for your organisation.