Empty the chart of accounts

Delete every account nothing has been posted to, after literal CLEAR confirmation. Accounts the ledger has touched are kept and named in the response. Use this before a migration: the other system's chart should come across as it stands, because a template applied first collides with it — the same code means different accounts in two charts.

Outcome

Before you start

Verify the intended environment, authenticated identity and specifically approved organization context.
The published application permission is accounts:write. Discover the exact granted canonical Books workspace and bind it separately from action input.
Approve the actual mutation, accounting inputs and any provider/recipient effects before CLI --confirm or MCP confirm:true. Fixture identifiers and simulated provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.accounts.clear --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json

Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.

Request

POST /api/accounts/clear

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

Field	Required	Meaning	Schema and constraints
`confirmation`	Required	Literal confirmation required by this schema, such as ERASE or REPAIR; obtain approval for the actual effects first.	{"type":"string","const":"CLEAR"}

Inspect nested fields and the complete input schema.

Effects

Deletes every account with no postings. Accounts the ledger has touched are kept, and any bank account pointing at a deleted account is unlinked rather than orphaned.

Interpret the response

Read $.keptAccounts[].id for the returned account identifier. Empty collections and nullable fields do not discover a target.

Call app_topolo_books.accounts.list and confirm only the kept accounts remain.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.accounts.clear --data @payload.json --json
topolo actions plan app_topolo_books.accounts.clear --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.accounts.clear --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_books.accounts.clear",
    "input": {
      "confirmation": "CLEAR"
    },
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "confirm": true,
    "detail": true
  }
}

Refused response · auth_error

Input · payload.json:

{
  "confirmation": "CLEAR"
}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Successful response · HTTP 200

Input · payload.json:

{
  "confirmation": "CLEAR"
}

Captured response · HTTP 200

{
  "deleted": 1,
  "kept": 0,
  "keptAccounts": []
}

HTTP 200. Call app_topolo_books.accounts.list and confirm only the kept accounts remain.

Verify the result

Call app_topolo_books.accounts.list and confirm only the kept accounts remain.

Errors and recovery

auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Deleted accounts are gone. Take app_topolo_books.organizations.data.export first, or re-seed with coa.templates.apply.

Import from Xero: Pull the chart of accounts, tax rates, contacts, sales invoices, supplier bills, payments, bank history, manual journals and attachments from the connected Xero organisation. Books posts imported documents before rebuilding ledger history from each bank transaction account, retaining coding already delivered by a live feed. Transactions before the conversion date remain represented by the opening position. Manual journals preserve adjustments such as accruals, depreciation and reclassifications without requesting Xero Advanced general-ledger data. Attachments stay linked to the journal they support and are keyed by their Xero attachment id. The default dryRun preview reports counts without writing; dryRun false imports. Re-running skips or refreshes records by source identity instead of duplicating them.
Import chart of accounts: Import accounts from a Xero or QuickBooks Online chart-of-accounts CSV export (or a generic code,name,type file). Previews by default (dryRun true): every row is reported as create, skip_existing or error with a reason. Pass dryRun false to create the new accounts; existing accounts are never changed, and codes are generated for rows without one.
List accounts: List the chart of accounts. Filter by type or archived state, search across code, name and description, and sort by code, name, type, subtype or status.