Sintropix Follow-ups API: Propose, Ask, Wait, Approve

A Follow-up is the mark of pending work on one Bank Movement or one Invoice, stored on that record. It proposes how to book or match the record, asks a person a question, or marks the record as waiting on something. An agent such as Erwin or a person can write it. A person then approves it or discards it, in the app or through the API. Until someone approves it, a Follow-up changes nothing in the books. Use Follow-ups when an agent or integration prepares reconciliation work but a person should confirm it. The agent writes the Follow-up. The person reviews the proposed steps and approves them with one write.

Each host has one route under its own path:

Bank Movement: /api/entities/:entityId/bank-accounts/:bankAccountId/movements/:movementId/follow-up
Invoice: /api/entities/:entityId/invoices/:invoiceId/follow-up

Both routes accept the same bodies and return the same errors. This page writes …/follow-up for either one.

Which records can hold a Follow-up

Host	Accepts a Follow-up when
Bank Movement	The Movement is `unbooked`, or booked by an entry that still has a line on the Suspense Account.
Invoice	The Invoice is unbooked, or booked with open amount left on its Control Line.

An Invoice or Bank Movement excluded from the books is no pending work, so it holds no Follow-up. Excluding a record clears its Follow-up. A PUT or an approval on an excluded record answers 409 with INVOICE_EXCLUDED_ERROR or BANK_MOVEMENT_EXCLUDED_ERROR. A record holds at most one Follow-up. Writing a new one replaces the current one. Every Bank Movement and Invoice row carries a followUp field. It holds the Follow-up as written, or null when the record has none. To find records by Follow-up, filter GET /movements or GET /invoices/pages with followUpKind. It takes proposal, question, waiting, or none (records with no Follow-up).

Kinds

The kind field tells the three Follow-ups apart. Each kind has its own fields and says who moves next.

`kind`	Fields	Meaning	Who moves next	Can be approved
`proposal`	`reason`, `plan`	One Plan fits and the evidence is clear.	A person approves or discards it.	Yes, runs `plan`.
`question`	`question`, `options`	The agent needs a fact only a person has. Each option carries a `label` and a `plan`.	A person picks an option, or answers the question.	Yes, when `options` is not empty. The approver picks one option.
`waiting`	`reason`, `checkBack`	The record waits on something outside Sintropix, for example a bill that has not arrived or the other leg of a transfer. `checkBack` says in free text when to look again, for example `a fin de mes`.	Nobody until the outside fact arrives.	No. Discard it once resolved.

A question with an empty options array is an open question. No approval can run it. In the app, a person answers it to Erwin from the record’s panel, and Erwin writes a new Follow-up from the answer. A record that waits stays unbooked. For example, when only one leg of an internal transfer has arrived, leave that leg unbooked and mark it waiting. Do not book it to the bridge account.

In the app

The panel of a Bank Movement or an Invoice shows its Follow-up in a Follow-up section (Seguimiento in Spanish), with the proposed steps of each Plan named in full:

Approve runs the Plan of a proposal. For a question, Choose runs the Plan of the option you pick. The app blocks either one, and says why, while the Plan names a record the Entity doesn’t hold, such as a missing account or the missing Recognition Account of a deferred line.
A line that a booking defers shows its terms in one sentence under it: the months, the Recognition Account, and the amount of each month. For example, Diferido de oct 2026 a dic 2026 (3 meses) · se reconoce en 4.01.01.02 Ventas B2B · $350.000 / mes.
Discard removes the Follow-up of any kind.
Answer Erwin (Responder a Erwin) lets you write to Erwin about that record, for every kind. Use it to answer a question, correct a proposal, or tell Erwin what a record waits on. Your answer is posted to Erwin in the record’s ERP Thread, and the panel opens its Thread tab (Hilo), where you follow what Erwin does. Erwin acts with your rights, and writes, replaces, or settles the Follow-up through these routes.

A person does not set a Follow-up directly in the app. To mark a record waiting, ask Erwin in the record’s ERP Thread. Listings show the Follow-up as a chip with its kind: Proposal, Question, or Waiting (Propuesta, Pregunta, En espera):

The bank Movement listings, of one Bank Account and of every account, and the Invoice listings show it in their own Follow-up column. Hover or focus the chip to read the reason or the question. You can hide the column from the Display menu.
In these listings, approve a proposal or discard a Follow-up of any kind from the row itself, without opening the panel. To answer a question, open the panel and choose an option.
The Filters menu of each listing filters by Follow-up kind, or by the records with none.

Plans

A Plan is an ordered list of acts that an approval runs. Each act matches one existing API route. It carries the path ids of that route and the same body that route takes.

`act`	Path ids	Body key	Same body as
`bookMovement`	`bankAccountId`, `movementId`	`booking`	`POST /movements/:movementId/book`
`match`	`bankAccountId`, `movementId`	`match`	`POST /movements/:movementId/match`
`bookInvoice`	`invoiceId`	`booking`	`POST /invoices/:invoiceId/book`, without `expectedBookingVersion`
`matchLines`	none	`lineIds` at the top level of the act	`POST /ledger/allocations/match`
`assign`	`bankAccountId`, `movementId`	`assignment`	`POST /movements/:movementId/assign`

A Plan needs at least one act. Keep these rules in mind when you build one:

You choose every id. Each entry id and each line id in the Plan is a UUID you generate. See Ledger Entry Line ids.
A later act can name a line an earlier act creates. Use the line id you gave it. For example, one Plan can book an Invoice and then match a Movement to the Invoice’s Control Line.
An act can target a record other than the host. A Plan on one leg of an internal transfer can book both legs and match the bridge lines.
A bookInvoice act carries no booking version. Writing the Follow-up changes the Invoice, so a version read before the write never matches at approval. Sintropix drops expectedBookingVersion from the act’s booking and does not store it. The Follow-up id guards the Plan instead: an approval names the Follow-up it read, and a replaced one refuses to run.
An assign clears the rest parked on the Suspense Account. Use it on a Bank Movement booked with a Suspense line. With a lineId, it settles that open line. With lineId: null, it books the amount to the accounts of its lines. It adds lines to the Ledger Entry that booked the Movement, so it names no entry of its own.
Sintropix validates the acts only on approval. A PUT checks the shape of the Plan, not whether each booking balances or each line is still open. Check the bodies before you write them.

PUT `…/follow-up`

Set or replace the Follow-up of a record. Setting one changes no books. Body: one of three shapes, chosen by kind.

Field	Type	Required	Description
`id`	uuid	Yes	Client-generated id of this Follow-up. Use a new id on every change.
`kind`	string	Yes	`proposal`, `question`, or `waiting`.
`reason`	string	`proposal`, `waiting`	Why the agent proposes this Plan, or what the record waits on. Non-blank.
`checkBack`	string	`waiting`	Free text that says when to look at the record again. Non-blank.
`plan`	array of acts	`proposal`	The Plan to run on approval.
`question`	string	`question`	The question for a person. Non-blank.
`options`	array of `{ label, plan }`	`question`	The possible answers, each with a non-blank `label` and its own `plan`. Send `[]` for an open question.

Retrying a PUT with the same id and the same body changes nothing. Sending the current id with a different body answers 409 FOLLOW_UP_ALREADY_EXISTS_ERROR. An approval names a Follow-up by its id, so a new body always needs a new id. Response (200): the host’s own update answer.

Bank Movement: { movement, bankAccount }
Invoice: the same answer as PATCH /invoices/:invoiceId

This example proposes matching a Movement to the Control Line of an open Invoice:

curl -X PUT "https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID/movements/$MOVEMENT_ID/follow-up" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "0f1e2d3c-4b5a-4968-8778-695a4b3c2d1e",
    "kind": "proposal",
    "reason": "Mismo monto que la Factura 60 de Arriendos Sur; el RUT está en la glosa.",
    "plan": [
      {
        "act": "match",
        "bankAccountId": "'"$BANK_ACCOUNT_ID"'",
        "movementId": "'"$MOVEMENT_ID"'",
        "match": {
          "id": "9a0b1c2d-3e4f-4a5b-8c6d-7e8f9a0b1c2d",
          "entryDate": "2026-09-20",
          "memo": "Pago Factura 60 Arriendos Sur",
          "lineId": "5b6c7d8e-9f0a-4b1c-8d2e-3f4a5b6c7d8e",
          "newCounterpartLines": [
            {
              "id": "6c7d8e9f-0a1b-4c2d-8e3f-4a5b6c7d8e9f",
              "accountId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
              "functionalAmount": 450000,
              "side": "debit",
              "partnerId": "a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d"
            }
          ]
        }
      }
    ]
  }'

A record waiting on a document that has not arrived yet:

{
  "id": "2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
  "kind": "waiting",
  "reason": "Falta la factura de Arriendos Sur por este pago.",
  "checkBack": "a fin de mes"
}

A Plan that assigns the rest of an overpaid Movement to the Control Line of another Invoice:

{
  "id": "3c4d5e6f-7a8b-4c9d-8e0f-2a3b4c5d6e7f",
  "kind": "proposal",
  "reason": "El resto de $300.000 coincide con la Factura 61 de Arriendos Sur.",
  "plan": [
    {
      "act": "assign",
      "bankAccountId": "4d5e6f7a-8b9c-4d0e-9f1a-3b4c5d6e7f8a",
      "movementId": "5e6f7a8b-9c0d-4e1f-8a2b-4c5d6e7f8a9b",
      "assignment": {
        "lineId": "7e8f9a0b-1c2d-4e3f-8a4b-5c6d7e8f9a0b",
        "newCounterpartLines": [
          {
            "id": "8f9a0b1c-2d3e-4f4a-8b5c-6d7e8f9a0b1c",
            "accountId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
            "functionalAmount": 300000,
            "side": "credit",
            "partnerId": "b2c3d4e5-f6a7-4b8c-9d0e-1f2a3b4c5d6e"
          }
        ]
      }
    }
  ]
}

A question with two options, where each plan matches the Movement to a different Invoice:

{
  "id": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
  "kind": "question",
  "question": "¿Este pago de $450.000 es la Factura 60 o la 61 de Arriendos Sur?",
  "options": [
    { "label": "Factura 60 · $450.000 · vence 20-09", "plan": [{ "act": "match", "...": "..." }] },
    { "label": "Factura 61 · $450.000 · vence 20-10", "plan": [{ "act": "match", "...": "..." }] }
  ]
}

GET `…/follow-up`

Read the Follow-up of a record with every record in its Plan named, so you can show it to a person without extra reads. Response (200): { followUp }, where followUp is null when the record has none. Otherwise it has the fields written with PUT, except that each act in plan (and in each option’s plan) is replaced by its named detail:

`act`	Detail fields
`bookMovement`	`movement`, `entry` (`id`, `entryDate`, `memo`), `newLines`
`match`	`movement`, `target`, `entry`, `newLines`
`bookInvoice`	`invoice`, `controlLineId`, `entry`, `newLines`
`matchLines`	`targets`
`assign`	`movement`, `target`, `newLines`

movement names the Movement with its date, amount, side, description, and Bank Account.
invoice names the Invoice with its document kind, number, direction, issue date, total, currency, and Partner.
controlLineId is the id of the line in newLines that the booking makes the Invoice’s Control Line, or null for a tax_only document, which books no Control Line. Another line in newLines can post to the same account. In the app, the Plan marks the Control Line as línea del documento.
Each item in newLines is a line the act creates: its id, side, functionalAmount, transactionCurrency, and transactionAmount, with its account ({ id, code, name }) and partner ({ id, name }) named, and its deferral.
deferral is null unless the line carries deferral in a bookInvoice act. Then it holds the terms the booking will defer the line by: startMonth (YYYY-MM), monthCount (integer), and recognitionAccount ({ id, code, name }), the account each Release will land in.
Each target is a line to settle. Its kind is existing (a line on the books, with its current openAmount and any Invoice it controls), new (a line an earlier act creates, with its actIndex), or notFound. The target of an assign is null when its lineId is null.

A named record is null when the Plan names a record the Entity does not hold. That includes the recognitionAccount of a deferral. Approving that Plan fails. A bookInvoice act whose Plan defers a line reads, for example:

{
  "act": "bookInvoice",
  "invoice": { "id": "6f1c2b1e-0d1a-4c7b-9a3e-2b8f5d0e1a11", "documentKind": "invoice", "documentNumber": "369", "direction": "receivable", "issueDate": "2026-10-01", "total": 1249500, "currency": "CLP", "partner": { "id": "0b6c0f2e-5a4d-4e8f-b1c3-7d9e2a4f6c88", "name": "Cliente Ejemplo SpA" } },
  "controlLineId": "7a8b9c0d-1e2f-4a3b-8c4d-5e6f7a8b9c0d",
  "entry": { "id": "9c4d5e6f-7a8b-4c9d-8e0f-1a2b3c4d5e6f", "entryDate": "2026-10-01", "memo": "Factura 369" },
  "newLines": [
    {
      "id": "8c9d0e1f-2a3b-4c4d-8e5f-6a7b8c9d0e1f",
      "side": "credit",
      "functionalAmount": 1050000,
      "transactionCurrency": null,
      "transactionAmount": null,
      "account": { "id": "c3d4e5f6-a7b8-4c9d-8e0f-1a2b3c4d5e6f", "code": "2.10.01.02", "name": "Ingresos por Adelantado" },
      "partner": { "id": "0b6c0f2e-5a4d-4e8f-b1c3-7d9e2a4f6c88", "name": "Cliente Ejemplo SpA" },
      "deferral": {
        "startMonth": "2026-10",
        "monthCount": 3,
        "recognitionAccount": { "id": "d4e5f6a7-b8c9-4d0e-8f1a-2b3c4d5e6f7a", "code": "4.01.01.02", "name": "Ventas B2B" }
      }
    }
  ]
}

The example shows only the deferred line. The other lines of the booking, including the Control Line, carry "deferral": null.

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/invoices/$INVOICE_ID/follow-up" \
  -H "x-api-key: $SINTROPIX_API_KEY"

POST `…/follow-up/approve`

Run the Plan of the current Follow-up, then clear it. Sintropix runs every act in order in one transaction, through the same checks as the act’s own route. If any act fails, nothing is written and the Follow-up stays. Body

Field	Type	Required	Description
`followUpId`	uuid	Yes	The `id` of the Follow-up you reviewed.
`optionIndex`	integer	Conditional	Zero-based index of the option to run. Required for a `question`; must be omitted for a `proposal`.

The body accepts no other fields. Response (200): the host’s own update answer plus acts. acts holds one result per act, in Plan order. Each result carries its act and the same answer as the act’s own route.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID/movements/$MOVEMENT_ID/follow-up/approve" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{ "followUpId": "1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d", "optionIndex": 0 }'

DELETE `…/follow-up`

Discard the Follow-up of a record. Discarding changes no books. Response (200): the host’s own update answer. For a Bank Movement, { movement, bankAccount }. For an Invoice, the same answer as PATCH /invoices/:invoiceId.

curl -X DELETE "https://api.sintropix.com/api/entities/$ENTITY_ID/invoices/$INVOICE_ID/follow-up" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

When Sintropix clears a Follow-up

A Follow-up advises on the record as it stood when it was written. Sintropix clears it when the record’s reconciliation changes:

Booking or matching the Bank Movement.
Unbooking the Ledger Entry that booked the Bank Movement.
Assigning or unassigning the Bank Movement’s Suspense line.
Booking the Invoice.
Creating or deleting an Allocation on a line of the Bank Movement or the Invoice.
Excluding the Bank Movement or the Invoice from the books.

An approval that names a cleared or replaced Follow-up answers 409 FOLLOW_UP_STALE_ERROR. Read the record again and review its current Follow-up.

Audit trail

Setting, approving, and discarding a Follow-up appear in the audit trail as changes to the host row. In row images, the Follow-up sits under the follow_up key. Images written before Follow-ups replaced Recommendations keep it under recommendation, with a status of confident, needs_clarification, or waiting instead of a kind.

Domain errors

Code	Status	Meaning
`FOLLOW_UP_MOVEMENT_SETTLED_ERROR`	`409`	`PUT` on a booked Bank Movement whose entry has no line on the Suspense Account. `params: { movementId, ledgerEntryId }`.
`FOLLOW_UP_INVOICE_SETTLED_ERROR`	`409`	`PUT` on a booked Invoice whose Control Line has no open amount. `params: { invoiceId, controlLineId }`.
`FOLLOW_UP_ALREADY_EXISTS_ERROR`	`409`	`PUT` reused the `id` of the current Follow-up with a different body. `params: { followUpId }`.
`FOLLOW_UP_STALE_ERROR`	`409`	The approval named a Follow-up the record no longer holds. `params: { followUpId, currentFollowUpId }`, where `currentFollowUpId` is `null` when the record holds none.
`FOLLOW_UP_NOT_APPROVABLE_ERROR`	`409`	The Follow-up is `waiting`, which has no Plan. `params: { followUpId, kind }`.
`FOLLOW_UP_QUESTION_OPEN_ERROR`	`409`	The question has no options. Answer it to Erwin in the record’s panel. `params: { followUpId }`.
`FOLLOW_UP_OPTION_REQUIRED_ERROR`	`400`	Approving a question without `optionIndex`. `params: { followUpId, optionCount }`.
`FOLLOW_UP_OPTION_NOT_FOUND_ERROR`	`400`	`optionIndex` is out of range. `params: { followUpId, optionIndex, optionCount }`.
`FOLLOW_UP_OPTION_UNEXPECTED_ERROR`	`400`	`optionIndex` sent for a `proposal`. `params: { followUpId, optionIndex }`.

An act that fails on approval answers with the error of its own route, for example LEDGER_ENTRY_LINE_ALREADY_EXISTS_ERROR.

Status codes

Status	Meaning
`200`	Success on every route.
`400`	Validation error, an option error above, or missing `x-audit-actor` on a key-authenticated mutation.
`403`	Read-only key attempted a mutation.
`404`	Entity, Bank Account, Bank Movement, or Invoice not found.
`409`	Domain conflict (see above), or a Plan act refused by its own route.

Get Started

Ledger

Banking

Documents

Reports & Audit

Sources & Integrations

Platform

Sintropix Follow-ups API: Propose, Ask, Wait, Approve

Which records can hold a Follow-up

Kinds

In the app

Plans

PUT `…/follow-up`

GET `…/follow-up`

POST `…/follow-up/approve`

DELETE `…/follow-up`

When Sintropix clears a Follow-up

Audit trail

Domain errors

Status codes

​Which records can hold a Follow-up

​Kinds

​In the app

​Plans

​PUT …/follow-up

​GET …/follow-up

​POST …/follow-up/approve

​DELETE …/follow-up

​When Sintropix clears a Follow-up

​Audit trail

​Domain errors

​Status codes

Which records can hold a Follow-up

Kinds

In the app

Plans

PUT `…/follow-up`

GET `…/follow-up`

POST `…/follow-up/approve`

DELETE `…/follow-up`

When Sintropix clears a Follow-up

Audit trail

Domain errors

Status codes