---
title: "Update payments in bulk"
method: PATCH
path: "/payments/{companyId}"
tags: ["Payments"]
---

# Update payments in bulk

`PATCH /payments/{companyId}`

Updates the synchronization status, error message, registration status or additional info of several payments, identified by `customId`. Entries whose `customId` does not match any payment are silently skipped — the call returns `200` for the whole batch.

## Path parameters

- `companyId` string, required

## Request body

- BulkPatchPaymentsRequestSchema
  - `data` AuxBulkPatchPaymentsRequestSchema[], required — Payments to update, identified by `customId`.
    - `sync` boolean, nullable — Marks the payment as synchronized with the accounting system.
    - `additionalInfo` object, nullable — Free-form key/value metadata to attach to the payment.
    - `error` string, nullable — Error message to record against the payment. Sending an empty string clears a previously set error.
    - `registered` boolean, nullable — Marks the payment as registered in the accounting system.
    - `customId` string, required — Embat custom/auto-generated unique payment ID. You can use it as your own custom ERP payment ID.

## Response `200`

Successful Response

- BulkModifyPaymentsResponseSchema
  - `data` ModifyPaymentsResponseSchema[], required — Result of the bulk operation, one entry per payment.
    - `id` string, required — Embat payment ID

## Other responses

- `401` — Unauthorized. The bearer token is missing, invalid or expired.
- `404` — Not found. The requested resource or `companyId` does not exist.
- `422` — Validation Error
- `500` — Unexpected error. Contact support if it persists.

---

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