> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Adjust entry for an exception > Use this endpoint to resolve an exception by creating an adjustment entry. This is used when a monetary correction is needed to reconcile the transaction. ## OpenAPI ````yaml /en/openapi/v3-current/matcher.yaml post /v1/exceptions/{exceptionId}/adjust-entry openapi: 3.1.0 info: title: Matcher APIs description: >- Complete API reference for the Matcher reconciliation engine, providing automated transaction matching between Midaz Ledger and external systems. version: v2.1.1 license: name: Elastic License 2.0 url: https://www.elastic.co/licensing/elastic-license servers: - url: https://matcher.sandbox.lerian.net security: [] paths: /v1/exceptions/{exceptionId}/adjust-entry: post: tags: - Exception summary: Adjust entry for an exception description: >- Use this endpoint to resolve an exception by creating an adjustment entry. This is used when a monetary correction is needed to reconcile the transaction. operationId: adjustEntryException parameters: - description: A unique identifier for tracing the request across services. in: header name: X-Request-Id schema: type: string - $ref: '#/components/parameters/XIdempotencyKey' - description: Exception ID in: path name: exceptionId required: true schema: type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/AdjustEntryRequest' description: Adjust entry payload required: true responses: '200': description: >- Indicates that the request was successful and the response contains the expected data. The response includes the `X-Idempotency-Replayed` header. If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request. See [Retries and idempotency](/en/reference/retries-idempotency) for more details. content: application/json: schema: $ref: '#/components/schemas/ExceptionResponse' headers: X-Idempotency-Replayed: $ref: '#/components/headers/XIdempotencyReplayed' '400': description: The request contains invalid parameters or payload. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: The request lacks valid authentication credentials. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: You do not have permission to access this resource. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: The requested resource was not found. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: The request was well-formed but contains semantic errors. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: An unexpected error occurred on the server. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - BearerAuth: [] components: parameters: XIdempotencyKey: name: X-Idempotency-Key in: header required: false description: >- Optional idempotency key for safe retries. Also accepts `Idempotency-Key` as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with `X-Idempotency-Replayed: true`. See [Retries and idempotency](/en/reference/retries-idempotency) for details. schema: type: string schemas: AdjustEntryRequest: description: Adjust entry request payload properties: amount: description: Adjustment amount example: 150.5 type: number currency: description: Currency code (ISO 4217) example: BRL type: string effectiveAt: description: When the adjustment takes effect format: date-time type: string notes: description: Additional notes explaining the adjustment example: Correcting processing fee discrepancy maxLength: 1000 type: string reasonCode: description: Reason code for the adjustment example: FEE_ADJUSTMENT maxLength: 255 type: string required: - amount - currency - effectiveAt - notes - reasonCode type: object ExceptionResponse: description: Exception details properties: assignedTo: description: User the exception is assigned to example: user@example.com type: string createdAt: description: Creation timestamp in RFC3339 format example: '2025-01-15T10:30:00.000Z' type: string dueAt: description: Due date for resolution in RFC3339 format example: '2025-01-20T10:30:00.000Z' type: string externalIssueId: description: External issue ID in the external system example: RECON-1234 type: string externalSystem: description: External system where exception was dispatched example: JIRA type: string id: description: Unique identifier for the exception example: 019c96a0-10d2-7134-ba5f-664142ee7052 type: string reason: description: Reason the exception was raised example: Amount mismatch detected type: string resolutionNotes: description: Resolution notes when resolved example: Resolved via force match type: string resolutionReason: description: Reason for the resolution example: BUSINESS_DECISION type: string resolutionType: description: Type of resolution applied enum: - FORCE_MATCH - ADJUST_ENTRY example: FORCE_MATCH type: string severity: description: Severity level enum: - LOW - MEDIUM - HIGH - CRITICAL example: HIGH type: string status: description: Current status enum: - OPEN - ASSIGNED - PENDING_RESOLUTION - RESOLVED example: OPEN type: string transactionId: description: Transaction ID this exception is for example: 019c96a0-10ce-75fc-a273-dc799079a99c type: string updatedAt: description: Last update timestamp in RFC3339 format example: '2025-01-15T10:30:00.000Z' type: string type: object ErrorResponse: description: Standard error response returned by all API endpoints type: object required: - code - title - message properties: code: type: string description: HTTP status code as a string. example: '404' title: type: string description: Error type identifier. example: not_found message: type: string description: Human-readable error message with details. example: context not found error: type: string description: Deprecated. Error message for backward compatibility. deprecated: true details: description: Additional error context as key-value pairs additionalProperties: {} type: object headers: XIdempotencyReplayed: description: >- Indicates whether this response was served from the idempotency cache. When `true`, the response is a replay of the original request with the same idempotency key. See [Retries and idempotency](/en/reference/retries-idempotency) for details. schema: type: boolean example: false securitySchemes: BearerAuth: type: http scheme: bearer bearerFormat: JWT description: 'Bearer token authentication (format: "Bearer {token}")' ````