Choose how the general ledger lands there

PUT /ledgers/{ledgerId}/settings

Choose how the general ledger lands there — what activates the ledger: granularity (daily-summary — one journal per effective date, each account's debits and credits summed; per-posting — one per posting), accounts (map onto the other ledger's accounts, or create Manifold's there) and syncFrom, where day-by-day journals begin.

Every ledger's books begin at the opening stocktake, which going live completes: before the organization has one, saving is 409 OpeningStocktakeRequired. syncFrom is any day from the opening's to today (409 SyncFromOutOfRange names both): its day, or none, backfills every day since the opening however long ago it was; a later day sends every posting before it first as one carried-forward journal dated the day before, so the books start from the same opening balance whatever the date. syncFrom is fixed once a journal has been planned (409 LedgerSyncStarted). Books kept in another currency than the organization's home currency are never activated (409 LedgerCurrencyMismatch). Nothing is planned until settings are saved; any other change applies to journals not yet planned. A person, or the ledger's own app (403 NotThisLedgersApp for another). Appends accounting.ledger-settings-saved. Idempotent by content: the settings as they stand append nothing.

Access

Requires financials:write.

How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.

Retries

Idempotent by content: the settings as they stand append nothing.

Why every write carries a key: Idempotency and retries.

Facts appended

accounting.ledger-settings-saved

What a fact is: Facts and the journal.

AI agent tool

No agent tool. How the ledger lands in the other books — journal granularity, account matching, the first date sent — is the merchant's and their bookkeeper's call in the ledger app's page.

Connecting an agent: AI agents.

Example

curl

curl -X PUT 'https://accounting.getmanifold.io/ledgers/lgr_01a0f6b2-1c00-7f71-8a82-465768798a9b/settings' \
  -H "Authorization: Bearer $MANIFOLD_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{
  "granularity": "daily-summary",
  "accounts": "map",
  "syncFrom": "2026-10-01"
}'

JavaScript (fetch)

const response = await fetch("https://accounting.getmanifold.io/ledgers/lgr_01a0f6b2-1c00-7f71-8a82-465768798a9b/settings", {
  method: "PUT",
  headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}`, "Content-Type": "application/json" },
  body: JSON.stringify({
    "granularity": "daily-summary",
    "accounts": "map",
    "syncFrom": "2026-10-01"
  }),
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();

Request body · application/json

{
  "granularity": "daily-summary",
  "accounts": "map",
  "syncFrom": "2026-10-01"
}

Response · 200 · application/json

{
  "id": "lgr_01a0f6b2-1c00-7f71-8a82-465768798a9b",
  "appId": "app_85cedb60-f616-4fe5-b9ea-dcd3689b4bc6",
  "externalId": "01a15897-023d-7b5f-9c7d-2e4f6a8b0c1d",
  "name": "Saltbush Homewares Pty Ltd",
  "baseCurrency": "AUD",
  "status": "connected",
  "connectedAt": "2026-10-01T02:14:05.000Z",
  "createdAt": "2026-10-01T02:14:05.000Z",
  "updatedAt": "2026-10-01T02:18:12.000Z",
  "mappings": [],
  "settings": {
    "granularity": "daily-summary",
    "accounts": "map",
    "syncFrom": "2026-10-01"
  }
}

The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: accounting-manager.openapi.json. Base URL https://accounting.getmanifold.io.

Errors

Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.

`401`

Refusal	What it means	What to do
`Unauthorized` reason	The token is missing, expired or not one Manifold issued.	Get a fresh token and send the call again.
`TokenAlreadyUsed` tokenId	A single-use app token was already spent.	Mint a new token for this call.

`402`

Refusal	What it means	What to do
`SubscriptionRequired` status	The organization's subscription has lapsed, so writes are refused.	An owner settles billing. Reads still work meanwhile.

`403`

Refusal	What it means	What to do
`NotThisLedgersApp` ledgerId	This ledger belongs to another app.	Call it with the app that connected the ledger.
`TenantRequired` userId	The token names no organization.	Choose the organization, then get a new token.
`ScopeRequired` required	The token's roles do not grant the scope this call needs.	Ask an owner or admin for a role that grants it.

`404`

Refusal	What it means	What to do
`LedgerNotFound` ledgerId	No such record in this organization.	Check the id in the path or the body.

`409`

Refusal	What it means	What to do
`LedgerDisconnected` ledgerId	The ledger is disconnected.	Reconnect it first.
`OpeningStocktakeRequired` reason	The ledger cannot start until the opening stocktake is complete.	Complete the opening stocktake first: going live does it.
`LedgerSyncStarted` ledgerId, syncFrom	The ledger has started sending, so its start date is fixed.	Nothing to change: it keeps its `syncFrom`.
`SyncFromOutOfRange` syncFrom, earliest, latest	The start date is outside what may be sent. `earliest` and `latest` give the range.	Choose a date in that range.
`LedgerCurrencyMismatch` ledgerId, baseCurrency, homeCurrency	The accounting software's base currency is not the organization's home currency.	Connect books kept in the home currency.
`MirroredFromSource` source	This area is fed by your source system until the organization goes live.	Make the change in the source system, or go live first.

`503`

Refusal	What it means	What to do
`RequestLogUnavailable` tokenId, reason	The service could not record the request, so it did nothing.	Send the same request again shortly.

How refusals work everywhere: Errors.