---
title: "Enrich Accounting Entry V2"
method: POST
path: "/v2/accounting-entries:enrich"
tags: ["AccountingEntryEnrichmentV2"]
---

# Enrich Accounting Entry V2

`POST /v2/accounting-entries:enrich`

Enriches an existing Pleo card accounting entry by attaching one or more receipts and applying optional cost categorisation tags. Pleo identifies the matching entry using the transaction details provided as query parameters. Use this endpoint for all new implementations.

## Query parameters

- `email` string — Email address of the Pleo user who made the purchase. Used as an optional matching parameter.
- `performed_at` string — ISO 8601 timestamp of when the purchase was authorised (i.e. when the transaction happened). Either `performed_at` or `settled_at` must be provided.
- `settled_at` string — ISO 8601 timestamp of when the purchase was settled (i.e. when the funds were transferred). Either `performed_at` or `settled_at` must be provided.
- `amount` integer, required — Transaction amount in minor units (e.g. 1500 represents €15.00).
- `currency` string, required — ISO 4217 currency code of the transaction (e.g. EUR, GBP, DKK).
- `card_last_four_digits` string, required — Last four digits of the Pleo card used for the transaction. Used as a matching parameter to identify the correct accounting entry.
- `merchant_name` string, required — Name of the merchant as it appears on the transaction.

## Request body

- AccountingEntryEnrichmentV2BodyRequest
  - `receipts` string[], required — List of Base64 encoded ByteArray as string
  - `tags` string[] — List of Tags in UUID format

## Response `200`

No matching accounting entry found. The receipt has been stored in the Receipt Inbox for manual resolution.

- DataResponseAccountingEntryEnrichmentResponse
  - `data` AccountingEntryEnrichmentResponse — The result of an enrichment request.
    - `accountingEntryId` string, uuid — The unique identifier of the accounting entry that was matched and enriched. Only present when receiptStatus is UPLOADED.
    - `receiptStatus` string — This can be one of ReceiptStatus values
    - `tags` string[] — List of tag UUIDs that were applied to the accounting entry.

## Other responses

- `201` — Matching accounting entry found. The receipt has been attached and tags applied.
- `202` — Request accepted. Pleo will retry matching the receipt to an accounting entry asynchronously.
- `404` — Request could not be processed. The card, employee, or one or more tag IDs were not found.

---

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