Sintropix Expense Claims API: Submit and Approve Renditions

An Expense Claim (rendición) is one expense that a person paid with their own money and asks the Entity to pay back. You submit it in Sintropix itself, with no outside tool such as Rindegastos. It waits until the Organization’s Approver approves or rejects it:

Approved: Sintropix creates the person’s payable Invoice in a Source that holds Expense Renditions, and books it in the same request. From then on it’s an Expense Rendition like any other, and you pay it from a Payment Batch.
Rejected: the claim keeps the reason, and the decision is final. To try again, submit a new claim.

An Xpendit expense Feed also creates claims: each expense Xpendit approved lands as a claim that is already approved, with no wait for the Approver. While a claim waits, it is no Invoice. It isn’t listed among the Expense Renditions or in Compras, isn’t a payable to plan in a Payment Batch, and doesn’t count on the home dashboard.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/{entityId}/expense-renditions?expenseClaimStatus=submitted, where each id in braces is the same UUID as in the API route or response. Rendiciones, under Datos. Por aprobar (expenseClaimStatus=submitted) lists the claims that wait, with the Approve and Reject actions, and Rechazadas (expenseClaimStatus=rejected) lists the rejected ones. Both show each claim's Número. Drop the parameter for the Expense Renditions. Nueva rendición submits a claim. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

Concepts

Person. The Partner who paid the expense and is paid back, never the merchant.
Receipt Kind. What the person holds as proof: a boleta or a factura issued to the Entity. It decides what the approval debits. See What approving books.
Expense Category. What the expense was spent on, such as “Alimentación” or “Movilización”. Each Entity names its own categories, and each category can carry the expense account its claims propose. See Expense Categories.
Proposed expense account. The expense account the claim suggests: the account of the claim’s category, or one the submitter names. It must be an account of type cost_of_goods_sold, operating_expense, or other_expense. The Approver can pick another one on approval.
Number. Each claim takes the next number of its Entity when you submit it: 1, 2, 3, and so on. Numbers never repeat within an Entity. The Expense Rendition of an approved claim carries it as its Document Number, R-<number>, so a claim reads the same before and after approval.
Approver. The one User of the Organization who approves and rejects the claims of all its Entities. It must be a member with the client Role: someone of the client’s own team, never Sintropix staff or a viewer. The Approver role ends when the User’s Membership ends.
Status. Sintropix derives it, and never stores it:
- submitted: the claim waits for the Approver.
- approved: the claim has its Expense Rendition, in invoiceId.
- rejected: the claim has a rejectionReason.

Who approved or rejected a claim, and when, is in the Audit Trail. Once a claim is approved, the Actividad of its Expense Rendition shows who submitted it and who approved it.

Before you submit claims

Approving needs two settings. Set them in Configuración → Rendiciones, at /{entityId}/settings/expense-claims, or through the API:

The Approver of the Organization. Use PUT /organizations/:organizationId/expense-claim-approver.
The booking setting of each Entity. Use PUT /expense-claim-setting. It names three things:
- The Source the Expense Renditions land in. It must be a Source that holds Expense Renditions.
- The Rendición por pagar account, which the approval credits with the person as Partner. It must be a liability account with the sub-type expense_rendition_payable. If the Entity already books renditions into a payable account, you can switch its sub-type to expense_rendition_payable even though it has entries.
- The supplier payable account, which a factura claim debits. It must have the sub-type payable, and it must be the account the Entity’s SII invoices credit, so that you can match the two lines later.

You can submit claims before you set either one. Only approving and rejecting need them. To let submitters pick a category instead of an account, also create the Entity’s Expense Categories and assign each one its expense account. In the app, each pick saves at once, with no Guardar button. The booking setting saves once the Source and both accounts are set. While the setting names a Source, you can’t unmark the Source as one that holds Expense Renditions, or delete it. Sintropix refuses both with 409 and SOURCE_PINNED_ERROR. Each account also keeps its sub-type while the setting names it: a change is refused with 409 and LEDGER_ACCOUNT_FACT_PINNED_ERROR. To change any of them, set another one first.

Report a rendition to Erwin

A person can also report a rendition to Erwin, for example in a Slack channel bound through an Agent Channel: “pagué un almuerzo con cliente con mi tarjeta, ¿me lo devuelven?”. Erwin submits it as an Expense Claim, and the Approver approves or rejects it like any other claim. Erwin never approves, rejects, or books the claim himself.

Erwin checks the setup. When the Entity has no booking setting or the Organization has no Approver, Erwin submits nothing. He tells you that Rendiciones isn’t set up yet, and that someone who keeps the books sets it in Configuración → Rendiciones.
He gets the facts. Erwin asks for a proof if you sent none: a photo, a receipt, or a screenshot. He reads the date, the merchant, and the amount from it, and asks only for what it doesn’t show. The amount is what the Entity pays back, in its functional currency. When the proof is in another currency, he asks what was charged to you in the functional currency, as your card statement shows it. The claim is a factura when the proof is a factura electrónica issued to the Entity’s RUT, and a boleta otherwise, including when there’s no document.
He submits the claim. The person who paid is the claim’s Partner, never the merchant. Erwin creates the Partner when there’s none. The memo holds the merchant, what the expense was, and the other facts the Approver needs, such as the payment method, the document number, and the original currency and amount. A claim holds no file, so when you report it from Slack, the memo ends with a link to the Slack message that holds the proof.
He proposes what it was spent on. Erwin names an Expense Category when one clearly fits the expense and has an expense account. Otherwise he proposes an expense account, following your Organization’s practices in his wiki. He never creates a category, and the Approver can book to another account.

Erwin answers that the rendition is submitted and waits for the Approver, with its amount, its memo, and a link to Rendiciones → Por aprobar. He doesn’t say which account he proposed: that’s for the Approver.

What approving books

Approving creates one payable Invoice and books it in the same request:

Invoice field	Value
`partnerId`	The claim’s person
`sourceId`	The Source of the Entity’s setting
`documentKind`	`invoice`
`documentNumber`	`R-<number>`, from the claim’s `number`, for example `R-12`
`currency`, `total`	The Entity’s functional currency, and the claim’s `amount`
`issueDate`	The claim’s `expenseDate`
`memo`	The claim’s `memo`

The booking entry is dated on the expense date. Its Control Line credits the Rendición por pagar account with the person as Partner. The debit depends on the Receipt Kind:

Receipt Kind	Debit	Why
`boleta`	The expense account: the proposed one, or the one the Approver picks	The expense exists only in the claim.
`factura`	The supplier payable account of the setting	The factura was issued to the Entity, so its expense and IVA reach the books with the SII invoice. Debiting an expense account would book it twice.

For a factura, the claim keeps the expense account as the suggestion for booking the SII invoice. The debit to the supplier payable stays open until you settle it against the Control Line of the SII invoice with POST /ledger/allocations/match. The SII invoice then reads as paid. If you unbook the Expense Rendition and delete it, the claim loses its invoiceId and is submitted again.

Access

Route	Who can call it
Read claims, the setting, or the Approver	Any member of the Organization
Read Expense Categories	Any member of the Organization
Submit a claim, create, change, or delete an Expense Category, set the Approver, or set the setting	A member with the `staff` or `client` Role. The Approver they set must be a `client` member.
Approve or reject a claim	The Approver alone, from a session or their own API key

A viewer who writes receives 403 with PERMISSION_DENIED_ERROR. Anyone but the Approver who approves or rejects receives 403 with EXPENSE_CLAIM_NOT_APPROVER_ERROR, even a staff member. See Access and roles.

The Expense Claim object

Field	Type	Description
`id`	uuid	Expense Claim id. You choose it on create.
`number`	integer	The claim’s number in its Entity, from 1. See Concepts.
`entityId`	uuid	Owning Entity.
`partnerId`	uuid	The person who paid the expense.
`partnerName`	string	The person’s name.
`expenseDate`	date (`YYYY-MM-DD`)	When the expense was paid.
`amount`	integer	The amount to pay back, in minor units of the Entity’s functional currency. Always positive.
`memo`	string	What the expense was.
`receiptKind`	`boleta` \| `factura`	The proof the person holds.
`expenseAccountId`	uuid	The proposed expense account. After approval, the account the Approver booked or suggested.
`expenseAccountCode`, `expenseAccountName`	string	The code and name of that account.
`expenseCategoryId`	uuid or null	The claim’s Expense Category. `null` when the claim named an account instead. The claim keeps its category when the Approver books to another account.
`expenseCategoryName`	string or null	The category’s name.
`status`	`submitted` \| `approved` \| `rejected`	Derived. See Concepts.
`invoiceId`	uuid or null	The Expense Rendition the approval created. `null` until the claim is approved.
`rejectedAt`	ISO datetime or null	When the claim was rejected.
`rejectionReason`	string or null	Why the claim was rejected.
`createdAt`, `updatedAt`	ISO datetime	Row timestamps.

POST `/expense-claims`

Submit an Expense Claim. It starts as submitted, with the next number of its Entity. Body

Field	Type	Required	Description
`id`	uuid	Yes	Id of the new claim. You choose it, so a retried request can’t submit the claim twice. A second request with the same `id` receives `409` with `EXPENSE_CLAIM_ALREADY_EXISTS_ERROR`.
`partnerId`	uuid	Yes	The person who paid. A Partner of the Organization. It can’t be the Partner that represents the Entity, or a Merged Partner.
`expenseDate`	date (`YYYY-MM-DD`)	Yes	When the expense was paid.
`amount`	integer	Yes	Positive, in minor units of the Entity’s functional currency.
`memo`	string	Yes	Non-blank after trimming.
`receiptKind`	`boleta` \| `factura`	Yes	The proof the person holds.
`expenseCategoryId`	uuid	One of the two	An Expense Category of the Entity. The claim proposes the category’s expense account. A category with no account yet receives `409` with `EXPENSE_CATEGORY_EXPENSE_ACCOUNT_NOT_SET_ERROR`.
`expenseAccountId`	uuid	One of the two	The proposed expense account: an account of the Entity of type `cost_of_goods_sold`, `operating_expense`, or `other_expense`.

Send exactly one of expenseCategoryId and expenseAccountId. A body with both, or with neither, receives 400. In the app, Nueva rendición asks for a Categoría, and the picker shows each category’s account or Sin cuenta asignada. A category without an account is refused, and the dialog keeps your draft so you can assign the account in Configuración → Rendiciones and submit again. Response (201): the Expense Claim object.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-claims" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "3f6c2a1e-7b4d-4c8e-9a1f-2d3e4f5a6b7c",
    "partnerId": "8a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d",
    "expenseDate": "2026-10-20",
    "amount": 18500,
    "memo": "Almuerzo con cliente",
    "receiptKind": "boleta",
    "expenseCategoryId": "4c5d6e7f-8a9b-4c0d-9e1f-2a3b4c5d6e7f"
  }'

GET `/expense-claims`

List the Entity’s Expense Claims, newest expense first. Claims with the same expenseDate come in a stable order. Query parameters

Parameter	Type	Required	Description
`status`	`submitted` \| `approved` \| `rejected`	No	Keep only the claims with this status. Omit for every claim.
`limit`	integer	No	Page size, 1 to 100. Default `50`.
`cursor`	string	No	The `nextCursor` of the previous page. An invalid cursor receives `400`.

Response

Field	Type	Description
`expenseClaims`	array	Expense Claim objects.
`nextCursor`	string or null	Pass it as `cursor` for the next page. `null` on the last page.

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-claims?status=submitted" \
  -H "x-api-key: $SINTROPIX_API_KEY"

GET `/expense-claims/:expenseClaimId`

Read one Expense Claim. Response: the Expense Claim object. An unknown id receives 404 with EXPENSE_CLAIM_NOT_FOUND_ERROR.

POST `/expense-claims/:expenseClaimId/approve`

Approve a submitted claim. Sintropix creates its Expense Rendition and books it, as What approving books describes. Only the Approver can call it. Body

Field	Type	Required	Description
`expenseAccountId`	uuid	No	Book to this expense account instead of the proposed one. Same rules as on create. For a `factura`, it becomes the suggested account for the SII invoice. The claim keeps its Expense Category.

Response (200)

Field	Type	Description
`expenseClaim`	object	The Expense Claim object, now `approved`.
`invoice`	object	The created Invoice, in the shape of the `POST /invoices` response, with its `bookingEntry`.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-claims/$EXPENSE_CLAIM_ID/approve" \
  -H "x-api-key: $SINTROPIX_APPROVER_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{}'

POST `/expense-claims/:expenseClaimId/reject`

Reject a submitted claim. The rejection is final. Only the Approver can call it. Body

Field	Type	Required	Description
`reason`	string	Yes	Why the claim is rejected. 1 to 500 characters after trimming.

Response (200): the Expense Claim object, now rejected.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-claims/$EXPENSE_CLAIM_ID/reject" \
  -H "x-api-key: $SINTROPIX_APPROVER_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{ "reason": "El gasto no corresponde a la empresa." }'

Expense Categories

An Expense Category names what an expense was spent on, such as “Alimentación”, “Movilización”, or “Hospedaje”. Each Entity keeps its own list. A category can carry an expense account: a claim that names the category proposes that account, so the submitter picks what the expense was, not where it books.

A category’s name is unique within its Entity. Sintropix trims surrounding spaces, so " Taxi " and "Taxi" are one name.
A category starts with no account. Assign one before a claim names it.
You can rename a category and assign it another account, but you can’t clear an account once it’s assigned.
The account must be an expense account of the Entity: of type cost_of_goods_sold, operating_expense, or other_expense.
You can delete a category while no Expense Claim names it. Once a claim names it, whatever the claim’s status, the category stays: rename it instead.

In the app, open Configuración → Rendiciones. The Categorías card lists the Entity’s categories. Add one with Agregar categoría, rename it in place, and pick its Cuenta de gasto. To remove a category, click the trash icon on its row and confirm. A name can’t be blank: clearing it is refused with El nombre es obligatorio. Para quitar la categoría, elimínala.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/{entityId}/settings/expense-claims, where each id in braces is the same UUID as in the API route or response. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

The Expense Category object

Field	Type	Description
`id`	uuid	Expense Category id. You choose it on create.
`entityId`	uuid	Owning Entity.
`name`	string	The category’s name.
`expenseAccountId`	uuid or null	The expense account a claim of the category proposes. `null` until you assign one.
`expenseAccountCode`, `expenseAccountName`	string or null	The code and name of that account. `null` until you assign one.
`sourceFeedId`, `providerCategoryId`	uuid or null, string or null	The expense Feed that brought the category and the category’s id in the expense tool. A Feed also sets them on a category of yours with the same name. `null` for every other category you create.
`createdAt`, `updatedAt`	ISO datetime	Row timestamps.

GET `/expense-categories`

GET /api/entities/:entityId/expense-categories List the Entity’s Expense Categories, in name order. Response: an array of Expense Category objects.

curl "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-categories" \
  -H "x-api-key: $SINTROPIX_API_KEY"

POST `/expense-categories`

POST /api/entities/:entityId/expense-categories Create an Expense Category. Body

Field	Type	Required	Description
`id`	uuid	Yes	Id of the new category. You choose it, so a retried request can’t create it twice. A second request with the same `id` receives `409` with `EXPENSE_CATEGORY_ALREADY_EXISTS_ERROR`.
`name`	string	Yes	Non-blank after trimming. A name another category of the Entity uses receives `409` with `EXPENSE_CATEGORY_NAME_TAKEN_ERROR`.
`expenseAccountId`	uuid or null	No	The expense account its claims propose. Omit it to assign one later.

Response (201): the Expense Category object.

curl -X POST "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-categories" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Add the meals category for expense claims" \
  -H "Content-Type: application/json" \
  -d '{
    "id": "4c5d6e7f-8a9b-4c0d-9e1f-2a3b4c5d6e7f",
    "name": "Alimentación",
    "expenseAccountId": "1b2c3d4e-5f6a-4b7c-8d9e-0f1a2b3c4d5e"
  }'

PATCH `/expense-categories/:expenseCategoryId`

PATCH /api/entities/:entityId/expense-categories/:expenseCategoryId Rename a category, assign its expense account, or both. Send at least one field. A field you omit keeps its value. Claims already submitted keep the account they proposed. Body

Field	Type	Required	Description
`name`	string	No	The new name. Same rules as on create.
`expenseAccountId`	uuid	No	The expense account to assign. It can’t be `null`: an assigned account is never cleared.

Response (200): the Expense Category object. An unknown id receives 404 with EXPENSE_CATEGORY_NOT_FOUND_ERROR.

curl -X PATCH "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-categories/$EXPENSE_CATEGORY_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Book meals to the representation expenses account" \
  -H "Content-Type: application/json" \
  -d '{ "expenseAccountId": "7e8f9a0b-1c2d-4e3f-8a4b-5c6d7e8f9a0b" }'

DELETE `/expense-categories/:expenseCategoryId`

DELETE /api/entities/:entityId/expense-categories/:expenseCategoryId Delete a category that no Expense Claim names, such as one created by mistake. The call has no body.

A category that any Expense Claim names, whatever the claim’s status, is refused with 409 and EXPENSE_CATEGORY_IN_USE_ERROR. The category and its claims stay as they are. Rename the category instead.
An unknown id receives 404 with EXPENSE_CATEGORY_NOT_FOUND_ERROR.

A category that an expense Feed brought comes back the next time the Feed reads an expense of that category. It returns with no expense account, so the expense is rejected with expense_category_unassigned until you assign one again. In the app, the delete confirmation of such a category says so.

Response (200): the deleted Expense Category object.

curl -X DELETE "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-categories/$EXPENSE_CATEGORY_ID" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Remove the duplicate taxi category"

GET `/expense-claim-setting`

Read the Entity’s booking setting. Response

Field	Type	Description
`setting`	object or null	The setting, or `null` when the Entity has none yet.
`setting.entityId`	uuid	The Entity.
`setting.sourceId`	uuid	The Source the Expense Renditions land in.
`setting.renditionPayableAccountId`	uuid	The Rendición por pagar account.
`setting.supplierPayableAccountId`	uuid	The supplier payable account a `factura` claim debits.
`setting.createdAt`, `setting.updatedAt`	ISO datetime	Row timestamps.

PUT `/expense-claim-setting`

Create or replace the Entity’s booking setting. A change applies to the claims you approve after it. Expense Renditions already created keep their Source and booking. Body

Field	Type	Required	Description
`sourceId`	uuid	Yes	A Source of the Entity that holds Expense Renditions. Otherwise `400` with `EXPENSE_CLAIM_SETTING_SOURCE_INELIGIBLE_ERROR`.
`renditionPayableAccountId`	uuid	Yes	An account of the Entity with the sub-type `expense_rendition_payable`.
`supplierPayableAccountId`	uuid	Yes	An account of the Entity with the sub-type `payable`.

An account without the right sub-type receives 400 with EXPENSE_CLAIM_SETTING_ACCOUNT_INELIGIBLE_ERROR. Its params.role says which one: rendition_payable or supplier_payable. Response: the same shape as GET /expense-claim-setting.

curl -X PUT "https://api.sintropix.com/api/entities/$ENTITY_ID/expense-claim-setting" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{
    "sourceId": "6d7e8f9a-0b1c-4d2e-8f3a-4b5c6d7e8f9a",
    "renditionPayableAccountId": "2c3d4e5f-6a7b-4c8d-9e0f-1a2b3c4d5e6f",
    "supplierPayableAccountId": "9f8e7d6c-5b4a-4392-8170-6f5e4d3c2b1a"
  }'

GET `/organizations/:organizationId/expense-claim-approver`

Read the Organization’s Approver, and the members offered as one. Response

Field	Type	Description
`approver`	object or null	The Approver, or `null` when the Organization has none.
`candidates`	array	The members with the `client` Role, the only members who can be the Approver.

approver and each element of candidates carry userId (uuid), name (string), and email (string).

curl "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/expense-claim-approver" \
  -H "x-api-key: $SINTROPIX_API_KEY"

PUT `/organizations/:organizationId/expense-claim-approver`

Set or change the Organization’s Approver. The new Approver decides every claim that still waits, in every Entity of the Organization. Body

Field	Type	Required	Description
`userId`	uuid	Yes	A member of the Organization with the `client` Role. A `staff` or `viewer` member, or a User outside the Organization, receives `400` with `EXPENSE_CLAIM_APPROVER_INELIGIBLE_ERROR`.

Response: the same shape as GET /organizations/:organizationId/expense-claim-approver.

curl -X PUT "https://api.sintropix.com/api/organizations/$ORGANIZATION_ID/expense-claim-approver" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "Content-Type: application/json" \
  -d '{ "userId": "0192a3b4-c5d6-7e8f-9a0b-1c2d3e4f5a6b" }'

Status codes

Status	Meaning
`200`	Success on `GET`, `PUT`, `PATCH`, `DELETE`, approve, and reject.
`201`	Expense Claim submitted, or Expense Category created.
`400`	Validation error (including a claim with both or neither of `expenseCategoryId` and `expenseAccountId`), an invalid cursor, an ineligible account, Source, or Approver, or missing `x-audit-actor` on a key-authenticated mutation.
`403`	Your Role can’t write (`PERMISSION_DENIED_ERROR`), or you aren’t the Approver (`EXPENSE_CLAIM_NOT_APPROVER_ERROR`).
`404`	Entity, Organization, Expense Claim, Expense Category, or Partner not found.
`409`	The claim’s or category’s `id` already exists, a category name is taken, the category to delete is in use, the claim’s category has no account, the claim was already decided, the Organization has no Approver, the Entity has no setting, or the Partner was merged.
`422`	The Partner represents the Entity (`PARTNER_REPRESENTS_ENTITY_ERROR`).

Domain error codes

Code	Status	When
`EXPENSE_CLAIM_NOT_FOUND_ERROR`	`404`	No Expense Claim of the Entity has this id. `params.expenseClaimId`.
`EXPENSE_CLAIM_ALREADY_EXISTS_ERROR`	`409`	A claim with this `id` already exists. When you retry a request, treat it as submitted. `params.expenseClaimId`.
`EXPENSE_CLAIM_EXPENSE_ACCOUNT_INELIGIBLE_ERROR`	`400`	The expense account of a claim or a category isn’t an expense account of the Entity. `params.ledgerAccountId`.
`EXPENSE_CATEGORY_NOT_FOUND_ERROR`	`404`	No Expense Category of the Entity has this id. `params.expenseCategoryId`.
`EXPENSE_CATEGORY_ALREADY_EXISTS_ERROR`	`409`	A category with this `id` already exists. When you retry a request, treat it as created. `params.expenseCategoryId`.
`EXPENSE_CATEGORY_NAME_TAKEN_ERROR`	`409`	Another category of the Entity has this name. `params.name`.
`EXPENSE_CATEGORY_IN_USE_ERROR`	`409`	An Expense Claim names the category, so it can’t be deleted. Rename it instead. `params.expenseCategoryId`.
`EXPENSE_CATEGORY_EXPENSE_ACCOUNT_NOT_SET_ERROR`	`409`	The claim’s category has no expense account yet. Assign one, or name another category. `params.expenseCategoryId`.
`EXPENSE_CLAIM_ALREADY_DECIDED_ERROR`	`409`	The claim isn’t `submitted` anymore. `params.status` is `approved` or `rejected`.
`EXPENSE_CLAIM_APPROVER_NOT_SET_ERROR`	`409`	The Organization has no Approver. Set one first. `params.organizationId`.
`EXPENSE_CLAIM_NOT_APPROVER_ERROR`	`403`	You aren’t the Approver. `params.approverUserId` names who is.
`EXPENSE_CLAIM_APPROVER_INELIGIBLE_ERROR`	`400`	The User isn’t a `client` member of the Organization. `params.userId`.
`EXPENSE_CLAIM_SETTING_NOT_SET_ERROR`	`409`	The Entity has no booking setting, so the claim can’t be approved. `params.entityId`.
`EXPENSE_CLAIM_SETTING_ACCOUNT_INELIGIBLE_ERROR`	`400`	An account of the setting lacks its sub-type. `params.ledgerAccountId` and `params.role`.
`EXPENSE_CLAIM_SETTING_SOURCE_INELIGIBLE_ERROR`	`400`	The Source isn’t a Source of the Entity that holds Expense Renditions. `params.sourceId`.
`PARTNER_NOT_FOUND_ERROR`	`404`	The `partnerId` names no Partner. `params.partnerId`.
`PARTNER_MERGED_ERROR`	`409`	The Partner was merged into another one. Use `params.mergedIntoPartnerId`.
`PARTNER_REPRESENTS_ENTITY_ERROR`	`422`	The Partner represents the Entity itself. `params.partnerId` and `params.entityId`.

A Merge of Partners moves the merged Partner’s claims to the kept one.

Get Started

Ledger

Banking

Documents

Reports & Audit

Sources & Integrations

Platform

Sintropix Expense Claims API: Submit and Approve Renditions

Concepts

Before you submit claims

Report a rendition to Erwin

What approving books

Access

The Expense Claim object

POST `/expense-claims`

GET `/expense-claims`

GET `/expense-claims/:expenseClaimId`

POST `/expense-claims/:expenseClaimId/approve`

POST `/expense-claims/:expenseClaimId/reject`

Expense Categories

The Expense Category object

GET `/expense-categories`

POST `/expense-categories`

PATCH `/expense-categories/:expenseCategoryId`

DELETE `/expense-categories/:expenseCategoryId`

GET `/expense-claim-setting`

PUT `/expense-claim-setting`

GET `/organizations/:organizationId/expense-claim-approver`

PUT `/organizations/:organizationId/expense-claim-approver`

Status codes

Domain error codes

​Concepts

​Before you submit claims

​Report a rendition to Erwin

​What approving books

​Access

​The Expense Claim object

​POST /expense-claims

​GET /expense-claims

​GET /expense-claims/:expenseClaimId

​POST /expense-claims/:expenseClaimId/approve

​POST /expense-claims/:expenseClaimId/reject

​Expense Categories

​The Expense Category object

​GET /expense-categories

​POST /expense-categories

​PATCH /expense-categories/:expenseCategoryId

​DELETE /expense-categories/:expenseCategoryId

​GET /expense-claim-setting

​PUT /expense-claim-setting

​GET /organizations/:organizationId/expense-claim-approver

​PUT /organizations/:organizationId/expense-claim-approver

​Status codes

​Domain error codes

Concepts

Before you submit claims

Report a rendition to Erwin

What approving books

Access

The Expense Claim object

POST `/expense-claims`

GET `/expense-claims`

GET `/expense-claims/:expenseClaimId`

POST `/expense-claims/:expenseClaimId/approve`

POST `/expense-claims/:expenseClaimId/reject`

Expense Categories

The Expense Category object

GET `/expense-categories`

POST `/expense-categories`

PATCH `/expense-categories/:expenseCategoryId`

DELETE `/expense-categories/:expenseCategoryId`

GET `/expense-claim-setting`

PUT `/expense-claim-setting`

GET `/organizations/:organizationId/expense-claim-approver`

PUT `/organizations/:organizationId/expense-claim-approver`

Status codes

Domain error codes