Skip to main content

Re-Sign Period

POST 

/api/ledger/close/periods/:period/re-sign-off

Accept the change to a restated month and sign it again. The month stays closed throughout. The background job stores the report pack as a new signed revision of kind re_sign_off, and later closed months that carried the change take a carried_refresh revision. Earlier revisions stay readable. Returns the background job id. Period keys are YYYY-MM.

Required scope: accounting:write

Grant this scope to your token under Settings → Developer → Personal Access Tokens.

The gates are the same as for Close Period, checked now and again in the job. Preview Re-Sign-Off Checks returns them as they run now, and the job captures the provider trial balance fresh before it checks them, so the acknowledgements and overrides sent here match what is checked.

Body:

  • reason — string, required, up to 500 characters. Why the change is accepted.
  • notes — string or null, optional, up to 2000 characters.
  • acknowledged_keys — array of strings, optional. Must cover every warning-level failure and incomplete manual item.
  • overrides — object of {check key: reason}, optional, for blocking checks that permit being closed over. See Close Period.

Authentication: Bearer token. Requires the accounting settings management permission.

Errors: 422 when the month has no restatement waiting for sign-off, is on or before the hard close date, a blocking check fails, or an acknowledgement is missing. 403 when an override needs a permission the caller lacks.

Independent review applies as it does to a close: while review is required, someone other than the people who changed the month since its last sign-off must re-sign it (422 under review otherwise).

self_review_reason (string, optional, max 2000): required when the tenant has only one accounting user and that user changed the month. It goes on the month's record.

Request​

Responses​

OK

Response Headers
    Content-Type