Run Re-Sign-Off Checks
POST/api/ledger/close/periods/:period/re-sign-off/checks
Queue every check a re-sign-off is held to, the expensive deferred ones included, as a background job. The provider trial balance is captured first, outside the transaction, since a capture can rotate the connection's credentials; the checks then run against it as a re-sign-off would, and are rolled back: the month keeps the checklist it was signed on. Preview Re-Sign-Off Checks then returns the deferred results for 30 minutes. Returns the background job id. Period keys are YYYY-MM.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Bearer token. Requires the accounting settings management permission.
Errors: 422 when the month has no restatement waiting for sign-off or is on or before the hard close date.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.