Accounting export: why you should preview before you commit
An accounting export leaves out every expense that has not been prepared, and says nothing about it. Here is how to check what will be missing, preview the journal without changing anything, and only then commit.
The problem
You run the month's purchase journal, import it into your accounting software, and close. Two weeks later someone asks why a €15,000 invoice from September is not in the books.
It was never in the export. An expense that has not been prepared for bookkeeping is left out of the purchase journal, and the export does not list what it skipped. Nothing fails. The file is simply shorter than you think.
With the Spendesk MCP, an assistant can generate the journals for you. That makes the check before the export more important, not less.
The exchanges below are reconstructed from tests run on a Spendesk demo account on 5 October 2026. The wording is rewritten for readability; the figures and outcomes are the ones the tools returned.
Step 1 — Ask what will be left out
Using 2026-09-01 to 2026-09-30, on the expenses' document date.
Would you like me to show what is missing on each of them?
Every September expense on this account was still to prepare. Without this check, the export would have looked like it worked.
Step 2 — Preview, and look at the file
A preview is the default. It generates the journals and changes nothing in Spendesk.
Preview generated for 2026-09-01 to 2026-09-30, purchase journal only. Nothing was marked as exported.
An empty journal that comes back as a success is exactly the case to catch before closing.
Step 3 — See why an expense is not ready
Invoice RE-2026-08842 — NORDWERK INDUSTRIEBEDARF GMBH — EUR 15779.40, dated 2026-09-06.
Bookkeeping status: to prepare.
| What | Status |
|---|---|
| Expense account on the line | ❌ None |
| VAT account (VAT of EUR 2519.40) | ❌ None |
| Supplier account | ❌ None |
| Receipt | ✅ Attached and valid |
I can set accounting fields with a write tool, but only if "Manage payables" is enabled on your connection, and I would show you each change first. Otherwise this is done in Spendesk.
The list of expenses only carries account IDs (and only when an account is set): to show account codes and names, the assistant reads each expense individually. For a large month, ask for a bounded period.
What to know before you commit
- Role required. The Spendesk MCP can only be used by a Controller or an Account Owner of the company concerned. With any other role, these requests do not work.
- A committed export cannot be undone. The expenses and settlements it includes are marked as exported. The assistant only commits when you explicitly ask.
- Purchase and bank journals are separate. Ask only for the one you need; both are generated by default.
- The window cannot exceed 31 days.
- Journal templates. The export uses the standard templates unless you name another. On the demo account, 11 templates were listed: 6 built-in (Spendesk Accounting, Sage, Cegid) and 5 created by the company.
- Availability. File exports exist for Spendesk Accounting, Sage and Cegid setups (not Sage 100 or Sage Intacct). With another connected accounting software, these tools return an error.
- Beta, off by default. An Admin or Account Owner enables "Manage accounting exports" on the connection, then each user reconnects and ticks it.
One thing this article did not test: committing an export. It is irreversible, so it was not run on the demo account; its behaviour is described from the tool's documentation.
Key takeaways
- Expenses still "to prepare" are left out of the purchase journal with no warning: count them before exporting
- A preview changes nothing, and an empty preview still comes back as a success — open the file
- Account codes and names are read expense by expense; an expense stays out until it is marked ready, which requires valid accounting fields (expense, VAT and supplier account)
- Commit only on explicit request: it marks entries as exported and cannot be undone
- The skill Generate the month's accounting export runs these checks in order
Related skills
Run a month-end close checklist: expenses to prepare, expenses not exported, missing receipts, settlements not exported and overdue invoices.
Check that expenses to export carry their expense, VAT and supplier accounts, and that none sits on an archived account.
Generate the month's purchase or bank journal as a preview, check what is excluded, and commit only on explicit request.