---
title: "Match entries"
method: POST
path: "/consumers/{consumer_id}/accounting/matching"
tags: ["Accounting", "Journal entries"]
---

# Match entries

`POST /consumers/{consumer_id}/accounting/matching`

Match existing entries in the accounting system

## Path parameters

- `consumer_id` string, uuid, required

## Query parameters

- `folder_id` string, nullable

## Request body

- MatchingIn
  - `entries` string[], required — List of entries to match. Must contain at least 2 entries. Entries are typically journal entry id, invoice id or financial entry id.
  - `partner_id` string, required — Id of the thirdparty (customer, supplier or employee) in the accounting system . All entries are must be linked to one same partner.

## Response `200`

Successful Response

- MatchingOut
  - `matching_number` string, required — Unique 'number' of the matching operation in the accounting system.
  - `balance` number, required — Balance of the matching operation. This is the sum of all entries in the matching operation. It should be zero if the matching is complete.

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `422` — Validation Error

---

[API](https://skmtc.net/chift/apis/chift-api.md) · [All operations](https://skmtc.net/chift/apis/chift-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chift/chift-api/versions/b5f1214a482a/schema)