ControllerAccountingMonth-End Close

Automated monthly close — the Controller checklist with Claude

Month-end close always means the same list of manual checks in Spendesk. With the MCP, Claude runs the checklist in a single command and immediately surfaces any blocking anomalies.

The Spendesk MCP Team·6 July 2026·5 min read

Automated monthly close — the Controller checklist with Claude

The problem

Monthly accounting close in Spendesk always means the same checklist: unexported invoices, outstanding expense reports, cards with residual balances, missing GL codes… Each check is done manually, in a different tab.

The result: 2 to 3 hours of repetitive work every month-end just to make sure nothing is missing.

The close checklist in a single command

Claude Code — MCP Spendesk

Vous

Run the close checklist for June 2026. I want to see what's OK and what's blocking.

⚙get_payables⚙list_cards⚙get_settlements

Close Checklist — June 2026

✅Approved and paid invoices

→284 invoices — €2,847,300 — all exported to Netsuite

⚠️Approved invoices not exported (3 — blocking)

Supplier	Amount	Reason blocked
Deloitte	€18,500	Missing GL code: 6278
PwC	€12,000	Unknown cost center: MKTG-NL
Carta	€3,400	EU intra-community VAT not filled in

❌Unreimbursed expense reports — 7 employees

→Total: €4,280 — automatic reminder sent this morning

⚠️Expired virtual cards with residual balance (2)

→Alice Martin — card #4521 — blocked balance: €420

→Thomas Lefèvre — card #3814 — blocked balance: €420

Completion score: 94%

→3 blocking actions to resolve to reach 100%

Where would you like to start: fix GL codes, recover card balances, or see expense report details?

Step-by-step guided corrections

Fix missing GL codes

Claude doesn't just list the problem — it helps you resolve it.

Claude Code — MCP Spendesk

Vous

Show me how to fix the missing GL code on the Deloitte invoice

⚙get_chart_of_accounts

For the Deloitte invoice (€18,500), here's what I see:

→GL code entered: 6278 — not recognized in your Spendesk chart of accounts

→Available GL codes in the "Fees / Advisory" category:

Code	Label
6220	Accounting fees
6221	Legal fees
6222	Advisory fees
6229	Other fees

Code 6278 does not match any entry. This is likely a data entry error.

→Suggestion: 6222 — Advisory fees (Deloitte = strategic advisory engagement based on the invoice description)

Would you like me to update the GL code on this invoice?

Detect duplicates before export

A classic that's expensive if it slips through.

Claude Code — MCP Spendesk

Vous

Check for duplicate invoices in this month's data before I export to accounting

⚙get_payables

I analyzed 284 June 2026 invoices. I identified 2 potential duplicates:

Duplicate #1 — Confidence: 94%

→INV-2026-0823 — Salesforce — €12,000 — created Jun 3

→INV-2026-0841 — Salesforce — €12,000 — created Jun 5

→Same amount, same supplier, same month — slightly different descriptions

Duplicate #2 — Confidence: 78%

→INV-2026-0756 — AWS — €6,340 — created Jun 1

→INV-2026-0801 — Amazon Web Services — €6,340 — created Jun 4

→Same amount, different supplier names but likely the same entity

⚠️If both duplicates are confirmed, this represents €18,340 in potential double payment.

Would you like me to open both invoices to compare attachments and confirm?

Key takeaways

The checklist runs in a single command — no more manually navigating between tabs
Every anomaly comes with an explanation and a suggested fix
Duplicate detection before export prevents costly double payments
Ideal at D-2 before the accounting close date to leave time for corrections
Pairs perfectly with FEC export: clean close → error-free export

List all invoices and expenses ready to export to the accounting system using bookingStatusToExport.

87/100Month-end close checklist

Run a full month-end close checklist: pending invoices, unmatched settlements, overdue payables, and unexported entries.

65/100Duplicate invoice detection

Detect potential duplicate invoices by identifying payables with the same supplier, amount, and close invoice dates.

73/100GL account mapping validation

Validate that all payables are correctly mapped to general ledger accounts before ERP export.

← Back to blog