Delete All Financial Data
Hard-deletes every financial RECORD the company holds, returning the number of rows removed: invoices, payments, the journal and ledger, and per-entity account balances. Financial configuration is kept — transaction categories, line item types, the accounts minted from them, and approval configuration all survive, so the company’s financial setup does not need to be re-authored.
This is the first rung of the breaking-config reset ladder. A company
with live books cannot have its entities bulk-wiped without orphaning
every financial row’s entity references, so the per-type entity wipe
(POST .../entities/{entityType}/deleteAll) rejects with 409 while
financials hold a live claim. The full reset order for re-importing a
breaking configuration is:
POST .../financials/deleteAll(this endpoint)POST .../entities/{entityType}/deleteAllper affected entity type- re-import the configuration
Delete-guarded. The wipe also consults the company’s delete guard —
the same mechanic that gates the internal admin wipes. A company whose
guard is active or onboarding-active (the default posture for a live
company) is rejected with 409 (DeleteGuardConflict) and nothing is
deleted; the wipe requires a non-active delete guard, set from the
Control Plane.
Required permission: company.financial-data:deleteAll — a privileged
operational permission granted to SUPER_ADMIN keys only. A key lacking it
receives 403.
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Response
All financial records were deleted (configuration kept)
Total number of rows removed across the financial-record tables (journal, ledger, invoices, payments, balances).
