Propose Reconciliation Baselines
POST/api/ledger/close/baselines/propose
Work the baselines out again without saving anything. Baselines record differences between SKU.io and the accounting provider (or between A/R / A/P and their open documents) that were already there before SKU.io's books started, each with a written reason, so the month-end close checks flag only new differences. They are reporting only: nothing is posted, and nothing sent to the provider changes.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body:
kind(required) —trial_balanceorcontrol_account.as_of_date(optional,Y-m-d,trial_balanceonly) — the day to measure at. Defaults to the day before your first open month. Must be before today and no earlier than the day before the books start; otherwise 422 onas_of_date.
For trial_balance this re-captures the provider's trial balance for the as-of date (one metered report call per connection) and compares it with SKU.io's ledger at the same moment. Only balance-sheet accounts are proposed: income and expense accounts are compared year to date, and equity and bank accounts are never compared. An account is proposed when its difference exceeds the trial-balance tolerance, or when it already holds a baseline (then difference may be 0, so a save clears it). A connection whose read fails returns its reason in error and no proposals.
For control_account the proposal is A/R and A/P minus their open documents at the end of the payment-posting start date.
Returns 422 when the start date the kind is measured on is not set.
Authentication: Bearer token. Requires the accounting settings permission.
When payment posting started the day after the as-of date, SKU.io's side includes its opening true-up: Accounts Receivable and Accounts Payable were already reset to the provider's balances, so they carry no difference, and the true-up's offset account shows what it moved. opening_true_up is then {date, account_codes} (the true-up's date and the A/R and A/P account codes it reset); otherwise null.
Request
Responses
- 200
- 401
- 403
- 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.
Unprocessable Entity
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.