Generate the month's accounting export

# Accounting export: preview, check, commit

## ⚠️ Write tool in Beta

`create_accounting_export`, `get_accounting_export` and `get_journal_templates` need the "Manage accounting exports" permission, off by default: an Admin or Account Owner enables it on the connection, then the user reconnects and ticks it. Without it, these tools do not appear at all.

**A committed export cannot be undone**: the payables and settlements it includes move to "exported". A preview changes nothing. This skill always previews first and only commits on the user's explicit request.

Only available when the company's accounting software is Spendesk Accounting, Sage or Cegid. For any other connected software (Xero, Netsuite, Datev…), these tools return an error: do not retry.

## Step 1 — State the period

State the exact dates before any call ("from 2026-09-01 to 2026-09-30"). The window cannot exceed **31 days**.

## Step 2 — Check what will be left out (the main trap)

Payables still in `toPrepare` are **excluded from the purchase journal with no warning**: the result carries no count and no skipped list. Count them before exporting:

```json
{
  "tool": "get_payables",
  "params": { "filters": { "operator": "and", "subfilters": [
    { "field": "payableDate", "operator": "between", "value": { "from": "2026-09-01T00:00:00.000Z", "to": "2026-09-30T23:59:59.999Z" } },
    { "field": "bookkeepingStatus", "operator": "=", "value": ["toPrepare"] }
  ] } }
}
```

Tell the user how many payables will stay out of the export, and for what amount. `mark_payable_as_ready` moves one to `toExport` ("Manage payables" permission; no tool moves it back).

Verified live: for September 2026, both of the month's payables (EUR 15,779.40 and EUR 10,055.50) were in `toPrepare`. The purchase journal preview for that period, downloaded and opened, held only the header row: no entries, and no message to say so.

## Step 3 — Pick the template (optional)

```json
{ "tool": "get_journal_templates", "params": {} }
```

Returns `id`, `name`, `type` (`purchase` or `bank`), `isDefault`.

- `isDefault: true` means "Spendesk built-in template", **not** "the company's default template": several rows can be `true`. On the demo account, 11 templates were listed, 6 built-in (Spendesk Accounting, Sage, Cegid) and 5 created by the company.
- Without `templates`, the export uses the standard templates, in English.
- Only pass a Sage or Cegid template when the user asks for that layout.
- An empty list means no accounting integration is connected.

## Step 4 — Preview

```json
{
  "tool": "create_accounting_export",
  "params": { "from": "2026-09-01", "to": "2026-09-30", "journals": ["purchase"], "markEntriesAsExported": false }
}
```

- `journals` defaults to `["purchase", "bank"]`: pass only the journal that was asked for.
- `markEntriesAsExported: false` (default) = preview. Observed response: a `key`, `journalTypes: ["purchase"]`, `markedAsExported: false`.
- The purchase journal follows the payables' document date; the bank journal follows each movement's own date. Bank fees are only included by whole calendar month: a period that does not end on the last day of the month leaves that month's fees out.
- Already-exported payables are excluded unless `includeAlreadyExportedPayables: true`. Already-exported settlements are never re-included.

## Step 5 — Get the file

```json
{ "tool": "get_accounting_export", "params": { "key": "<key from step 4>" } }
```

Four possible outcomes:

| Response | What to do |
|----------|------------|
| `downloadUrl` | Done. A signed link to a single zip, valid for about 1 hour: tell the user. If it expires, call again with the same key |
| "still being generated" | Retry with the **same** key, 3 times at most, then hand the key back to the user |
| "failed" | Final. Do not retry: create a new export |
| "not found" | Final. Wrong key, or export created in another company: check both |

## Step 6 — Commit (only on explicit request)

Before committing, remind the user of: the period, the journals, the number of payables left out, and the fact that it cannot be undone. Wait for an explicit go-ahead, then repeat the step 4 call with `"markEntriesAsExported": true`.

After the call, say clearly what happened: a preview (nothing changed) or a commit (entries marked as exported). If the outcome is unclear, re-read the payables' state rather than running the export again.

## What was tested

Tested live on the demo account: the template list, the `toPrepare` payables check, creating a preview, getting the download link and opening the zip (one CSV file per journal). **The commit (`markEntriesAsExported: true`) was not run**, because it cannot be undone; its behaviour is described from the tool's documentation.

## Example user prompts

- "Give me a preview of September's purchase journal, without marking anything as exported"
- "How many September invoices will not go into the export, and why?"
- "The preview looks right: commit the September export"