Sintropix Ledger Entries API: Book, Reverse, and Schedule Transactions

Ledger Entries are the core double-entry transactions in Sintropix. Each entry has a header (date, memo, notes) and at least two balanced lines. This page covers creating entries (one at a time or in bulk), listing, reversing, and unbooking them, plus Scheduled Entries and line-level updates. All amounts are integers in the minor unit of the currency (for example, cents). Dates are YYYY-MM-DD strings; timestamps are ISO 8601 datetimes.

Entities with Books. An Entity may hold zero or more Books. When it has at least one, every Ledger Entry it posts must name a bookId on the header (or leave it null to mark the Entry common), and the Open Item Lines read must carry bookId as a query parameter. See Books for the model and the exact rule.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/{entityId}/entries/{entryId}, where each id in braces is the same UUID as in the API route or response. The list is at /{entityId}/entries. An entry's open item is at /{entityId}/receivables?open={entryId} or /{entityId}/payables?open={entryId}. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

GET /api/entities/:entityId/ledger/entries

List Ledger Entries with pagination, filtering, and sorting. Defaults to live entries (active and reversed statuses). Pass ids instead to read the full detail of up to 100 specific entries in one request.

Path param: entityId (UUID)
Query params:

Param	Type	Required	Default	Description
`ids`	UUID[]	No	—	1 to 100 entry ids. Repeat the parameter for each id (`?ids=A&ids=B`). Cannot be combined with any other query parameter. See Reading several entries by id.
`cursor`	UUID	No	—	Last entry id of the previous page
`limit`	integer	No	50	Page size, max 100
`from`	ISO date	No	—	Earliest entry date
`to`	ISO date	No	—	Latest entry date (must be >= from)
`search`	string	No	—	Up to 100 characters. Case-insensitive contains-match on the memo, the notes, and the name of any account the entry posts to. A search that reads as an amount also matches the entry’s `total`; see Search by amount.
`sort`	enum	No	`date`	`date`, `memo`, or `amount`
`direction`	enum	No	`desc`	`asc` or `desc`
`statuses`	string	No	`active,reversed`	Comma-separated list of `active`, `deleted`, `reversed`, `scheduled`, `cancelled`

Success response: a page of entries
Status: 200

Field	Type	Description
`entries`	array	Ledger Entries on this page, each with the fields below
`nextCursor`	UUID or null	Pass as `cursor` to fetch the next page; `null` on the last page

Each item in entries carries the Ledger Entry fields plus three line-derived totals:

Field	Type	Description
`id`	UUID	Entry id
`entityId`	UUID	Owning Entity
`entryDate`	ISO date	Transaction date
`memo`	string or null	Short description
`notes`	string or null	Longer notes
`status`	enum	`active`, `deleted`, `reversed`, `scheduled`, or `cancelled`
`reversalOfEntryId`	UUID or null	The entry this one reverses; `null` for ordinary entries
`bookId`	UUID or null	The Book the entry counts in; `null` for a common entry
`intercompanyEntryId`	UUID or null	The Intercompany Entry this entry is one side of; `null` for ordinary entries. See Entries of an Intercompany Entry
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp
`total`	integer	Sum of the entry’s debit lines
`lineCount`	integer	Number of lines
`accountNames`	string[]	Distinct names of the accounts the entry touches, debit-side accounts first
`attachmentCount`	integer	Number of attachments on the entry
`otherEntityOfIntercompanyEntry`	object or null	`{ id, name }` of the other Entity of the entry’s Intercompany Entry; `null` for ordinary entries

The first eleven fields are the Ledger Entry object; other endpoints on this page return it on its own.

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries?limit=20&sort=date&direction=desc" \
  -H "x-api-key: $SINTROPIX_API_KEY"

Reading several entries by id

When you pass ids, the response is an array of Ledger Entry detail objects instead of a { entries, nextCursor } page. Each element has the same shape as the response of GET /api/entities/:entityId/ledger/entries/:entryId, including lines, relatedInvoices, relatedMovements, and allocations. Use this when you already hold a set of entry ids and need their full detail without one request per entry.

Results follow the order of ids. A repeated id is returned once, at its first position.
Ids the Entity does not hold are left out of the array rather than refused. Compare the returned id values against the ids you sent.
Combining ids with cursor, limit, statuses, or any other query parameter returns 400.
Sintropix reads every element from one consistent snapshot.

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries?ids=$ENTRY_ID_1&ids=$ENTRY_ID_2" \
  -H "x-api-key: $SINTROPIX_API_KEY"

GET /api/entities/:entityId/ledger/entries/:entryId

Get the full detail of a single Ledger Entry, including lines, related invoices, related bank movements, and allocations.

Path params: entityId (UUID), entryId (UUID)
Success response: the Ledger Entry fields (see the list endpoint above) plus:
Status: 200

Field	Type	Description
`reversedByEntryId`	UUID or null	The live reversal that points at this entry, if any
`lines`	array	The entry’s lines, each with the fields below
`relatedInvoices`	array	Invoices this entry books, each with the invoice fields below
`relatedMovements`	array	Bank movements this entry books, each with the movement fields below
`allocations`	array	Allocations that settle one of this entry’s lines, each with the allocation fields below
`deferralRelease`	object or null	Set when this entry is a Release of a Deferral: `{ deferralId, invoiceId, invoiceDocumentNumber }`. `null` for other entries, and once the Invoice booking that holds the deferred line is unbooked or reversed
`otherEntityOfIntercompanyEntry`	object or null	`{ id, name }` of the other Entity of the entry’s Intercompany Entry; `null` for ordinary entries
`deferrals`	array	The Deferrals whose deferred line this entry books; empty for other entries. Unbooking or reversing this entry also undoes their Releases

Each item in lines is a Ledger Entry Line (the first eleven fields, which other endpoints return on their own) plus the names the detail view shows:

Field	Type	Description
`id`	UUID	Line id
`entryId`	UUID	Parent entry
`accountId`	UUID	Ledger Account the line posts to
`entityId`	UUID	Owning Entity
`functionalAmount`	integer	Nonnegative magnitude in the functional currency
`side`	enum	`debit` or `credit`
`partnerId`	UUID or null	Counterparty partner
`transactionCurrency`	string or null	Foreign currency code, if the line is denominated in another currency
`transactionAmount`	integer or null	Amount in the foreign currency
`transactionFxRate`	decimal string or null	Rate used for conversion
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp
`accountCode`	string	Code of the account
`accountName`	string	Name of the account
`accountType`	enum	`asset`, `liability`, `equity`, `income`, `cost_of_goods_sold`, `operating_expense`, `other_income`, or `other_expense`
`partnerName`	string or null	Name of the partner
`partnerWebsite`	string or null	Website of the partner, as a bare domain (`acme.cl`); `null` when it has none. The partner’s logo is read from it
`lineDimensionValues`	array	Tags on the line: `{ dimensionId, dimensionValueId, dimensionName, dimensionValueCode, dimensionValueName }`
`intercompanyPairId`	UUID or null	The Intercompany Pair the line belongs to; `null` for an unpaired line

Each item in relatedInvoices:

Field	Type	Description
`id`	UUID	Invoice id
`entityId`	UUID	Owning Entity
`partnerId`	UUID	Customer or vendor
`partnerName`	string or null	Name of the partner
`direction`	enum	`receivable` or `payable`
`documentKind`	enum	`invoice`, `credit_note`, or `tax_only`
`documentNumber`	string	Number printed on the document
`currency`	string	Denomination currency
`total`	integer	Gross total in `currency`
`issueDate`	ISO date	Issue date
`dueDate`	ISO date or null	Due date
`memo`	string or null	Free text
`metadata`	array	Additional information as `{ label, value }` pairs
`sourceId`	UUID or null	Source the document came from
`bookingEntryId`	UUID or null	The Ledger Entry that books it; `null` when unbooked
`controlLineId`	UUID or null	The receivable/payable line that books it; `null` when unbooked, and always `null` on a `tax_only` document
`controlAccountId`	UUID or null	Account of the control line; `null` exactly when `controlLineId` is `null`
`followUp`	object or null	The Follow-up on the Invoice; `null` when there is none
`excludedAt`	ISO datetime or null	When the Invoice was excluded from the books; `null` when it isn’t excluded
`exclusionReason`	string or null	Why it was excluded; `null` exactly when `excludedAt` is null
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp

Each item in relatedMovements:

Field	Type	Description
`id`	UUID	Movement id
`entityId`	UUID	Owning Entity
`bankAccountId`	UUID	Bank Account the movement belongs to
`bankAccountCurrency`	string	Currency of that Bank Account
`bankAccountLedgerAccountId`	UUID	Ledger Account mapped to that Bank Account
`movementDate`	ISO date	Date on the statement
`amount`	integer	Nonnegative magnitude
`side`	enum	`debit` or `credit`
`description`	string	Description reported by the bank
`externalRef`	string or null	Bank’s own reference
`partnerId`	UUID or null	Counterparty partner
`partnerName`	string or null	Name of the partner
`ledgerEntryId`	UUID or null	Entry that books the movement
`ledgerLineId`	UUID or null	Bank line of that entry
`ledgerAccountId`	UUID or null	Account of that bank line
`metadata`	array	Additional information as `{ label, value }` pairs
`followUp`	object or null	The Follow-up on the Movement; `null` when there is none
`excludedAt`	ISO datetime or null	When the Movement was excluded from the books; `null` when it isn’t excluded
`exclusionReason`	string or null	Why it was excluded; `null` exactly when `excludedAt` is null
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp

Each item in allocations:

Field	Type	Description
`id`	UUID	Allocation id
`entityId`	UUID	Owning Entity
`debitLineId`	UUID	Settled debit line
`creditLineId`	UUID	Settled credit line
`accountId`	UUID	Open-Item Account
`amount`	integer	Settled amount
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp
`counterpart`	object	The other side of the allocation: `{ lineId, entryId, entryDate, entryMemo, accountId, accountCode, accountName, partnerId, partnerName }`

curl https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries/$ENTRY_ID \
  -H "x-api-key: $SINTROPIX_API_KEY"

POST /api/entities/:entityId/ledger/entries

Create a new Ledger Entry. The entry must have at least two lines and total debits must equal total credits. The client supplies the idempotency id.

Path param: entityId (UUID)
Body:

Field	Type	Required	Description
`id`	UUID	Yes	Client-supplied idempotency id
`entryDate`	ISO date	Yes	Transaction date
`memo`	string or null	Yes	Short description
`notes`	string or null	No	Longer notes; trimmed, blank becomes null
`bookId`	UUID or null	Conditional	Book the Entry counts in; `null` marks the Entry common. Must be sent (as an id or as `null`) when the Entity has at least one Book; must be omitted otherwise.
`newLedgerEntryLines`	array	Yes	At least 2 lines, max 10,000, balanced

Each line in newLedgerEntryLines:

Field	Type	Required	Description
`id`	UUID	Yes	Client-supplied line id. Must not already exist.
`accountId`	UUID	Yes	Ledger Account id
`functionalAmount`	integer	Yes	Nonnegative magnitude
`side`	enum	Yes	`debit` or `credit`
`partnerId`	UUID or null	No	Counterparty partner
`transactionCurrency`	string	No	Foreign currency code
`transactionAmount`	integer	No	Foreign amount
`transactionFxRate`	decimal string	No	Rate as plain decimal string
`dimensionValueIds`	UUID[]	No	Default `[]`; tags for this line. Each must be a Value of the Entity’s Organization; see Dimensions

The transaction trio (currency, amount, rate) must be provided together or omitted together. The rate is a plain decimal string, never a float.

You choose the id of every line, the same way you choose the entry id. Because you know each line id before the write, a later request can name a line before it exists. For example, a Follow-up Plan can book an Invoice and then match a Movement to its Control Line. A line id that already exists answers 409 LEDGER_ENTRY_LINE_ALREADY_EXISTS_ERROR with params: { lineIds }, and Sintropix writes nothing.

Success response: the Ledger Entry fields plus ledgerEntryLines, an array of Ledger Entry Line objects (see the entry detail endpoint) each extended with dimensionValueIds (UUID[])
Status: 201

{
  "id": "33333333-3333-4333-8333-333333333333",
  "entityId": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
  "entryDate": "2026-01-15",
  "memo": "Venta al contado",
  "notes": null,
  "status": "active",
  "reversalOfEntryId": null,
  "bookId": null,
  "intercompanyEntryId": null,
  "createdAt": "2026-01-15T14:02:11.000Z",
  "updatedAt": "2026-01-15T14:02:11.000Z",
  "ledgerEntryLines": [
    {
      "id": "77777777-7777-4777-8777-777777777777",
      "entryId": "33333333-3333-4333-8333-333333333333",
      "accountId": "11111111-1111-4111-8111-111111111111",
      "entityId": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
      "functionalAmount": 100,
      "side": "debit",
      "partnerId": null,
      "transactionCurrency": null,
      "transactionAmount": null,
      "transactionFxRate": null,
      "createdAt": "2026-01-15T14:02:11.000Z",
      "updatedAt": "2026-01-15T14:02:11.000Z",
      "dimensionValueIds": []
    },
    {
      "id": "88888888-8888-4888-8888-888888888888",
      "entryId": "33333333-3333-4333-8333-333333333333",
      "accountId": "22222222-2222-4222-8222-222222222222",
      "entityId": "aaaaaaaa-aaaa-4aaa-8aaa-aaaaaaaaaaaa",
      "functionalAmount": 100,
      "side": "credit",
      "partnerId": null,
      "transactionCurrency": null,
      "transactionAmount": null,
      "transactionFxRate": null,
      "createdAt": "2026-01-15T14:02:11.000Z",
      "updatedAt": "2026-01-15T14:02:11.000Z",
      "dimensionValueIds": []
    }
  ]
}

curl -X POST https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "id": "33333333-3333-4333-8333-333333333333",
    "entryDate": "2026-01-15",
    "memo": "Venta al contado",
    "notes": null,
    "newLedgerEntryLines": [
      { "id": "77777777-7777-4777-8777-777777777777", "accountId": "11111111-1111-4111-8111-111111111111", "functionalAmount": 100, "side": "debit" },
      { "id": "88888888-8888-4888-8888-888888888888", "accountId": "22222222-2222-4222-8222-222222222222", "functionalAmount": 100, "side": "credit" }
    ]
  }'

POST /api/entities/:entityId/ledger/entries/bulk

Create up to 100 Ledger Entries in a single request and transaction. Each element is a full entry with the same fields as POST /api/entities/:entityId/ledger/entries, and follows the same rules.

Path param: entityId (UUID)
Body:

Field	Type	Required	Description
`entries`	array	Yes	1 to 100 entries, each with the body of the single create. Each `id` must be unique within the request. No other field is accepted.

Success response: an array of the created entries, in request order. Each element has the same shape as the single create response.
Status: 201

The request is all or nothing:

An empty entries, more than 100 entries, or two entries with the same id return 400, and Sintropix writes nothing.
When any entry fails validation or a domain rule, Sintropix writes no entry. The response carries the error the single create would return (for example 404 LEDGER_ACCOUNT_NOT_FOUND_ERROR or 409 LEDGER_ENTRY_DATE_LOCKED_ERROR) plus elementIndex, the zero-based position of the refused entry in entries.

Retrying is safe. When you send a batch again, each entry whose id is already a live entry of the Entity (active or reversed) answers the stored entry, and the response is 201 again. An id whose entry is no longer live, for example an unbooked one, returns 409 with LEDGER_ENTRY_ALREADY_EXISTS_ERROR and its elementIndex, and Sintropix writes nothing.

curl -X POST https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries/bulk \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "entries": [
      {
        "id": "33333333-3333-4333-8333-333333333333",
        "entryDate": "2026-01-15",
        "memo": "Venta al contado",
        "newLedgerEntryLines": [
          { "id": "77777777-7777-4777-8777-777777777777", "accountId": "11111111-1111-4111-8111-111111111111", "functionalAmount": 100, "side": "debit" },
          { "id": "88888888-8888-4888-8888-888888888888", "accountId": "22222222-2222-4222-8222-222222222222", "functionalAmount": 100, "side": "credit" }
        ]
      },
      {
        "id": "99999999-9999-4999-8999-999999999999",
        "entryDate": "2026-01-16",
        "memo": "Pago de arriendo",
        "newLedgerEntryLines": [
          { "id": "a1a1a1a1-a1a1-4a1a-8a1a-a1a1a1a1a1a1", "accountId": "55555555-5555-4555-8555-555555555555", "functionalAmount": 500, "side": "debit" },
          { "id": "a2a2a2a2-a2a2-4a2a-8a2a-a2a2a2a2a2a2", "accountId": "11111111-1111-4111-8111-111111111111", "functionalAmount": 500, "side": "credit" }
        ]
      }
    ]
  }'

A refused batch, where the second entry is dated on or before the ledger lock date:

{
  "code": "LEDGER_ENTRY_DATE_LOCKED_ERROR",
  "params": { "entryDate": "2026-01-16", "ledgerLockDate": "2026-01-31" },
  "elementIndex": 1
}

PATCH /api/entities/:entityId/ledger/entries/:entryId

Update an entry’s header fields (date, memo, notes). At least one field must be provided.

Path params: entityId (UUID), entryId (UUID)
Body:

Field	Type	Required	Description
`entryDate`	ISO date	No	New transaction date
`memo`	string or null	No	New memo
`notes`	string or null	No	New notes; trimmed, blank becomes null

Success response: the updated Ledger Entry object (see the list endpoint)
Status: 200

curl -X PATCH https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries/$ENTRY_ID \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{"memo": "Updated description"}'

POST /api/entities/:entityId/ledger/entries/:entryId/reverse

Reverse a live Ledger Entry by posting a mirror entry. The reversal date must be on or after the original entry date and after the ledger lock date. The reversal takes the Book of the original; do not send bookId.

Path params: entityId (UUID), entryId (UUID)
Body:

Field	Type	Required	Description
`id`	UUID	Yes	Client-supplied idempotency id for the reversal entry
`entryDate`	ISO date	Yes	Reversal date

If the entry books a deferred Invoice line, its booked Releases are reversed on the same date and its Scheduled ones are cancelled. A booked Release on or before the ledger lock date refuses the whole reversal with LEDGER_ENTRY_FROZEN_ERROR. An Entry that still holds a line on the Suspense Account is refused with LEDGER_REVERSAL_ENTRY_HAS_SUSPENSE_LINE_ERROR. Unbook the Bank Movement instead, or assign the rest first.

Success response: every row the reversal changed
Status: 201

Field	Type	Description
`reversalEntry`	object	The mirror entry just posted: Ledger Entry fields plus `ledgerEntryLines` (same shape as the create response)
`reversedEntry`	object	The original entry as it now stands, with `status` set to `reversed`
`severedInvoices`	array	Invoices whose booking link was cut (invoice fields as in the entry detail, without `partnerName`)
`severedMovements`	array	Bank movements whose booking link was cut (movement fields as in the entry detail, without `bankAccountCurrency`, `bankAccountLedgerAccountId`, and `partnerName`)
`settledChainEntries`	array	Ledger Entry objects whose status changed because a reversal chain was settled, in the order they changed; empty when nothing else changed

curl -X POST https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries/$ENTRY_ID/reverse \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "id": "44444444-4444-4444-8444-444444444444",
    "entryDate": "2026-01-20"
  }'

DELETE /api/entities/:entityId/ledger/entries/:entryId

Unbook (soft-delete) a Ledger Entry. The entry status becomes deleted. This severs any linked invoices, bank movements, and allocations. If the entry is a reversal, the chain behind it is settled back to its prior state. If it books a deferred Invoice line, its booked Releases are unbooked and its Scheduled ones are cancelled; a booked Release on or before the ledger lock date refuses the whole unbook with LEDGER_ENTRY_UNBOOK_FROZEN_ERROR.

Path params: entityId (UUID), entryId (UUID)
Success response: every row the unbook changed
Status: 200

Field	Type	Description
`unbookedEntry`	object	The Ledger Entry object with `status` set to `deleted`
`severedInvoices`	array	Invoices whose booking link was cut (same shape as in the reverse response)
`severedMovements`	array	Bank movements whose booking link was cut (same shape as in the reverse response)
`settledChainEntries`	array	Ledger Entry objects whose status changed because a reversal chain was settled; empty when nothing else changed

curl -X DELETE https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/entries/$ENTRY_ID \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Entries of an Intercompany Entry

An Intercompany Entry books one Ledger Entry in each of two Entities. Its Entries carry its id in intercompanyEntryId, and change only with the act. The routes on this page refuse to edit, unbook, reverse, reclassify, or change the Partner of such an Entry:

PATCH /api/entities/:entityId/ledger/entries/:entryId
DELETE /api/entities/:entityId/ledger/entries/:entryId
POST /api/entities/:entityId/ledger/entries/:entryId/reverse
PATCH /api/entities/:entityId/ledger/lines/:lineId/account
PATCH /api/entities/:entityId/ledger/lines/:lineId/partner

Each returns 409 with LEDGER_ENTRY_IN_INTERCOMPANY_ENTRY_ERROR. params.ledgerEntryId names the Entry and params.intercompanyEntryId names its act:

{
  "code": "LEDGER_ENTRY_IN_INTERCOMPANY_ENTRY_ERROR",
  "params": {
    "ledgerEntryId": "1a2b3c4d-0001-4a00-8a00-000000000001",
    "intercompanyEntryId": "6f1d2c3b-4a59-4e68-8d7c-1b2a3c4d5e6f"
  }
}

To correct the Entry, unbook the whole act with DELETE /api/organizations/:organizationId/intercompany-entries/:intercompanyEntryId and create it again. See Correct an Intercompany Entry. Tagging its lines with Dimension values still works.

Scheduled Entries

POST /api/entities/:entityId/ledger/scheduled-entries

Schedule a Ledger Entry for future booking. The entry date must be in the future. Scheduled entries cannot carry transaction currency lines.

Path param: entityId (UUID)
Body: the same fields as POST /api/entities/:entityId/ledger/entries above
Success response: the Ledger Entry fields plus ledgerEntryLines (same shape as the create response), with status set to scheduled
Status: 201

curl -X POST https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/scheduled-entries \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "id": "55555555-5555-4555-8555-555555555555",
    "entryDate": "2026-03-01",
    "memo": "Future rent",
    "notes": null,
    "newLedgerEntryLines": [
      { "id": "c1c1c1c1-c1c1-4c1c-8c1c-c1c1c1c1c1c1", "accountId": "11111111-1111-4111-8111-111111111111", "functionalAmount": 500, "side": "debit" },
      { "id": "c2c2c2c2-c2c2-4c2c-8c2c-c2c2c2c2c2c2", "accountId": "22222222-2222-4222-8222-222222222222", "functionalAmount": 500, "side": "credit" }
    ]
  }'

POST /api/entities/:entityId/ledger/scheduled-entries/:entryId/book

Book a Scheduled Entry immediately. The entry date must be on or before today.

Path params: entityId (UUID), entryId (UUID)
Success response: the Ledger Entry fields plus ledgerEntryLines (same shape as the create response), with status set to active
Status: 200

curl -X POST https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/scheduled-entries/$ENTRY_ID/book \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

PATCH /api/entities/:entityId/ledger/scheduled-entries/:entryId

Reschedule a planned entry. Replaces the date, memo, notes, and the entire line set. Fields other than the four below are rejected.

Path params: entityId (UUID), entryId (UUID)
Body:

Field	Type	Required	Description
`entryDate`	ISO date	Yes	New scheduled date
`memo`	string or null	Yes	New memo
`notes`	string or null	Yes	New notes
`newLedgerEntryLines`	array	Yes	Full new line set, balanced; same line fields as the create endpoint

Success response: the Ledger Entry fields plus ledgerEntryLines (same shape as the create response)
Status: 200

curl -X PATCH https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/scheduled-entries/$ENTRY_ID \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "entryDate": "2026-04-01",
    "memo": "Updated future rent",
    "notes": null,
    "newLedgerEntryLines": [
      { "id": "d1d1d1d1-d1d1-4d1d-8d1d-d1d1d1d1d1d1", "accountId": "11111111-1111-4111-8111-111111111111", "functionalAmount": 600, "side": "debit" },
      { "id": "d2d2d2d2-d2d2-4d2d-8d2d-d2d2d2d2d2d2", "accountId": "22222222-2222-4222-8222-222222222222", "functionalAmount": 600, "side": "credit" }
    ]
  }'

DELETE /api/entities/:entityId/ledger/scheduled-entries/:entryId

Cancel a Scheduled Entry. The entry status becomes cancelled.

Path params: entityId (UUID), entryId (UUID)
Success response: the Ledger Entry object with status set to cancelled
Status: 200

curl -X DELETE https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/scheduled-entries/$ENTRY_ID \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Ledger Lines

GET /api/entities/:entityId/ledger/lines

List Ledger Entry Lines. Defaults to live entries only. Optionally filter by partner.

Path param: entityId (UUID)
Query params:

Param	Type	Required	Default	Description
`partnerId`	UUID	No	—	Narrow to one partner’s lines
`statuses`	string	No	`active,reversed`	Comma-separated list of `active`, `deleted`, `reversed`, `scheduled`, `cancelled`

Success response: an array of Ledger Entry Line objects (see the entry detail endpoint), each extended with:
Status: 200

Field	Type	Description
`openAmount`	integer or null	Amount not yet settled by allocations; `null` on accounts that do not track open items
`entryDate`	ISO date	Date of the parent entry

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/lines?partnerId=$PARTNER_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY"

GET /api/entities/:entityId/ledger/open-item-lines

List Open Item lines for an Open-Item Account with pagination. Shows unsettled lines by default.

Path param: entityId (UUID)
Query params:

Param	Type	Required	Default	Description
`accountId`	UUID	Yes	—	Open-Item Account id
`cursor`	UUID	No	—	Last line id of the previous page
`limit`	integer	No	50	Page size, max 100
`statusFilter`	enum	No	`unsettled`	`unsettled`, `all`, or `settled`
`partnerId`	UUID	No	—	Filter by partner
`sort`	enum	No	`entryDate`	`entryDate`, `entryMemo`, `partnerName`, `debit`, `credit`, `openAmount`, or `settlementStatus`
`sortDirection`	enum	No	`asc`	`asc` or `desc`
`bookId`	UUID	Conditional	—	Required when the Entity has at least one Book; must be omitted otherwise

An account that does not track open items returns 400 with ACCOUNT_TRACKS_NO_OPEN_ITEMS_ERROR.

Success response: a page of open-item lines
Status: 200

Field	Type	Description
`lines`	array	Lines on this page, each with the fields below
`nextCursor`	UUID or null	Pass as `cursor` to fetch the next page; `null` on the last page
`openTotal`	integer	Open amount of the whole account, regardless of filter or page
`partnerOptions`	array	Partners named by the account’s lines, as `{ id, name }`

Each item in lines is a Ledger Entry Line object (see the entry detail endpoint) extended with:

Field	Type	Description
`openAmount`	integer or null	Amount not yet settled by allocations
`entryDate`	ISO date	Date of the parent entry
`entryMemo`	string or null	Memo of the parent entry
`partnerName`	string or null	Name of the partner
`partnerWebsite`	string or null	Website of the partner, as a bare domain (`acme.cl`); `null` when it has none. The partner’s logo is read from it
`settlementStatus`	enum	`open` (nothing settled), `partial`, or `settled` (nothing left open)
`invoiceId`	UUID or null	The Invoice whose Control Line this line is; `null` for any other line, even on the same account
`invoiceDocumentNumber`	string or null	Document number of that Invoice. In the app, Partidas abiertas prefixes the line with `Doc.` and this number

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/open-item-lines?accountId=$ACCOUNT_ID&limit=20" \
  -H "x-api-key: $SINTROPIX_API_KEY"

PATCH /api/entities/:entityId/ledger/lines/:lineId/partner

Change the partner on a Ledger Entry Line. null clears the partner.

Path params: entityId (UUID), lineId (UUID)
Body:

Field	Type	Required	Description
`partnerId`	UUID or null	Yes	New partner or null

Success response: the updated Ledger Entry Line object (see the entry detail endpoint)
Status: 200

curl -X PATCH https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/lines/$LINE_ID/partner \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{"partnerId": "66666666-6666-4666-8666-666666666666"}'

PATCH /api/entities/:entityId/ledger/lines/:lineId/account

Reclassify a Ledger Entry Line to a different Ledger Account. The line must have no Allocation and no document link, and its entry must be open.

Path params: entityId (UUID), lineId (UUID)
Body:

Field	Type	Required	Description
`accountId`	UUID	Yes	New Ledger Account id

Success response: the updated Ledger Entry Line object plus lineDimensionValues, an array of { dimensionId, dimensionValueId, dimensionName, dimensionValueCode, dimensionValueName }
Status: 200

curl -X PATCH https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/lines/$LINE_ID/account \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{"accountId": "22222222-2222-4222-8222-222222222222"}'

PUT /api/entities/:entityId/ledger/lines/:lineId/dimension-values

Replace the Dimension Value tags on a Ledger Entry Line. An empty array untags the line.

Path params: entityId (UUID), lineId (UUID)
Body:

Field	Type	Required	Description
`dimensionValueIds`	UUID[]	Yes	Full replacement tag set. Each must be a Value of the Entity’s Organization

Success response: the updated Ledger Entry Line object plus lineDimensionValues, an array of { dimensionId, dimensionValueId, dimensionName, dimensionValueCode, dimensionValueName }
Status: 200

curl -X PUT https://api.sintropix.com/api/entities/$ENTITY_ID/ledger/lines/$LINE_ID/dimension-values \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{"dimensionValueIds": ["dddddddd-dddd-4ddd-8ddd-dddddddddddd"]}'

Domain error codes

Code	Meaning
`LEDGER_ACCOUNT_NOT_FOUND_ERROR`	Referenced account does not exist
`LEDGER_ENTRY_ALREADY_EXISTS_ERROR`	Entry id already used
`LEDGER_ENTRY_NOT_FOUND_ERROR`	Entry not found
`LEDGER_ENTRY_LINE_NOT_FOUND_ERROR`	Line not found
`LEDGER_ENTRY_LINE_ALREADY_EXISTS_ERROR`	One or more line ids already used
`LEDGER_ENTRY_DATE_LOCKED_ERROR`	Entry date is on or before the ledger lock date
`LEDGER_ENTRY_FROZEN_ERROR`	Entry is frozen (locked date)
`LEDGER_ENTRY_LOCKED_ERROR`	Ledger is locked
`LEDGER_ENTRY_UNBOOK_FROZEN_ERROR`	Cannot unbook a frozen entry
`LEDGER_ENTRY_NOT_ACTIVE_ERROR`	Entry is not active
`LEDGER_ENTRY_IN_INTERCOMPANY_ENTRY_ERROR`	The entry belongs to an Intercompany Entry and changes only with it. Unbook the act and create it again; see Correct an Intercompany Entry
`LEDGER_ENTRY_OVER_CORRECTED_ERROR`	Entry already has a reversal
`LEDGER_REVERSAL_NETTING_BLOCKED_ERROR`	Reversal would net an existing allocation
`LEDGER_REVERSAL_DATE_BEFORE_ORIGINAL_ERROR`	Reversal date is before the original
`LEDGER_ENTRY_LINE_IN_REVERSAL_PAIR_ERROR`	Line is part of a reversal pair
`LEDGER_ENTRY_LINE_PARTNER_PINNED_ERROR`	Partner cannot be changed (pinned by constraint)
`LEDGER_ENTRY_LINE_PARTNER_NOT_FOUND_ERROR`	Partner not found
`LEDGER_ENTRY_LINE_PARTNERS_NOT_FOUND_ERROR`	Multiple partners not found
`LEDGER_ENTRY_LINE_PARTNER_MERGED_ERROR`	A line names a Merged Partner. `params.partnerIds` lists them (`409`)
`TRANSACTION_CURRENCY_IS_ENTITY_CURRENCY_ERROR`	A line’s `transactionCurrency` is the Entity’s functional currency (`400`)
`DIMENSION_VALUE_ON_NON_RESULT_ACCOUNT_ERROR`	Dimension values tag only lines on income or expense accounts. `params.accountIds` lists the others (`400`)
`ACCOUNT_TRACKS_NO_OPEN_ITEMS_ERROR`	The account named in an Open Item Lines read does not track open items (`400`)
`LEDGER_ENTRY_LINE_ACCOUNT_PINNED_ERROR`	Account cannot be changed (pinned by constraint)
`LEDGER_ACCOUNT_SUSPENSE_RESERVED_ERROR`	A line posts to the Suspense Account, which only bank Match, Assign, and Unassign can use
`LEDGER_ENTRY_LINE_PARTNER_ON_SUSPENSE_ACCOUNT_ERROR`	A line on the Suspense Account cannot carry a Partner
`LEDGER_ENTRY_LINE_RECLASSIFY_SUSPENSE_ACCOUNT_ERROR`	Reclassify cannot move a line to or from the Suspense Account
`TAX_ONLY_LINE_ON_CONTROL_ACCOUNT_ERROR`	Reclassify cannot move a line of a `tax_only` document’s booking to an account whose sub-type is `payable`, `expense_rendition_payable`, or `receivable`. `params: { ledgerAccountId, ledgerAccountSubtype }` (`409`)
`LEDGER_REVERSAL_ENTRY_HAS_SUSPENSE_LINE_ERROR`	Entry holds a Suspense line and cannot be reversed
`LEDGER_ENTRY_NOT_SCHEDULED_ERROR`	Entry is not a Scheduled Entry
`LEDGER_ENTRY_SCHEDULED_DATE_NOT_FUTURE_ERROR`	Scheduled date must be in the future
`LEDGER_ENTRY_SCHEDULED_NOT_DUE_ERROR`	Scheduled entry is not yet due
`LEDGER_ENTRY_SCHEDULED_TRANSACTION_CURRENCY_ERROR`	Scheduled entries cannot carry foreign currency
`DEFERRAL_RELEASE_LOCKED_ERROR`	The entry is a Release of a Deferral; its date cannot change, and it cannot be rescheduled
`DIMENSION_VALUE_SET_VALUES_NOT_FOUND_ERROR`	One or more dimension value ids not found in the Entity’s Organization
`DIMENSION_VALUE_SET_DUPLICATE_DIMENSION_ERROR`	Multiple values from the same dimension
`RECONCILIATION_ALLOCATION_NOT_FOUND_ERROR`	Allocation not found
`RECONCILIATION_ALLOCATION_NETS_REVERSAL_ERROR`	Allocation nets a reversal

Status codes

Status	Meaning
200	Success (GET, PATCH, DELETE, book)
201	Created (POST entries, POST entries/bulk, POST reverse, POST scheduled-entries)
400	Validation error
401	Unauthenticated
403	Forbidden
404	Resource not found
409	Domain rule violation

Get Started

Ledger

Banking

Documents

Reports & Audit

Sources & Integrations

Platform

Sintropix Ledger Entries API: Book, Reverse, and Schedule Transactions

GET /api/entities/:entityId/ledger/entries

Reading several entries by id

GET /api/entities/:entityId/ledger/entries/:entryId

POST /api/entities/:entityId/ledger/entries

POST /api/entities/:entityId/ledger/entries/bulk

PATCH /api/entities/:entityId/ledger/entries/:entryId

POST /api/entities/:entityId/ledger/entries/:entryId/reverse

DELETE /api/entities/:entityId/ledger/entries/:entryId

Entries of an Intercompany Entry

Scheduled Entries

POST /api/entities/:entityId/ledger/scheduled-entries

POST /api/entities/:entityId/ledger/scheduled-entries/:entryId/book

PATCH /api/entities/:entityId/ledger/scheduled-entries/:entryId

DELETE /api/entities/:entityId/ledger/scheduled-entries/:entryId

Ledger Lines

GET /api/entities/:entityId/ledger/lines

GET /api/entities/:entityId/ledger/open-item-lines

PATCH /api/entities/:entityId/ledger/lines/:lineId/partner

PATCH /api/entities/:entityId/ledger/lines/:lineId/account

PUT /api/entities/:entityId/ledger/lines/:lineId/dimension-values

Domain error codes

Status codes

​GET /api/entities/:entityId/ledger/entries

​Reading several entries by id

​GET /api/entities/:entityId/ledger/entries/:entryId

​POST /api/entities/:entityId/ledger/entries

​POST /api/entities/:entityId/ledger/entries/bulk

​PATCH /api/entities/:entityId/ledger/entries/:entryId

​POST /api/entities/:entityId/ledger/entries/:entryId/reverse

​DELETE /api/entities/:entityId/ledger/entries/:entryId

​Entries of an Intercompany Entry

​Scheduled Entries

​POST /api/entities/:entityId/ledger/scheduled-entries

​POST /api/entities/:entityId/ledger/scheduled-entries/:entryId/book

​PATCH /api/entities/:entityId/ledger/scheduled-entries/:entryId

​DELETE /api/entities/:entityId/ledger/scheduled-entries/:entryId

​Ledger Lines

​GET /api/entities/:entityId/ledger/lines

​GET /api/entities/:entityId/ledger/open-item-lines

​PATCH /api/entities/:entityId/ledger/lines/:lineId/partner

​PATCH /api/entities/:entityId/ledger/lines/:lineId/account

​PUT /api/entities/:entityId/ledger/lines/:lineId/dimension-values

​Domain error codes

​Status codes

GET /api/entities/:entityId/ledger/entries

Reading several entries by id

GET /api/entities/:entityId/ledger/entries/:entryId

POST /api/entities/:entityId/ledger/entries

POST /api/entities/:entityId/ledger/entries/bulk

PATCH /api/entities/:entityId/ledger/entries/:entryId

POST /api/entities/:entityId/ledger/entries/:entryId/reverse

DELETE /api/entities/:entityId/ledger/entries/:entryId

Entries of an Intercompany Entry

Scheduled Entries

POST /api/entities/:entityId/ledger/scheduled-entries

POST /api/entities/:entityId/ledger/scheduled-entries/:entryId/book

PATCH /api/entities/:entityId/ledger/scheduled-entries/:entryId

DELETE /api/entities/:entityId/ledger/scheduled-entries/:entryId

Ledger Lines

GET /api/entities/:entityId/ledger/lines

GET /api/entities/:entityId/ledger/open-item-lines

PATCH /api/entities/:entityId/ledger/lines/:lineId/partner

PATCH /api/entities/:entityId/ledger/lines/:lineId/account

PUT /api/entities/:entityId/ledger/lines/:lineId/dimension-values

Domain error codes

Status codes