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.
Bearer token authentication (format: "Bearer {token}")
A unique identifier for tracing the request across services.
A unique key to ensure safe retries of the request.
Exception ID
Adjust entry payload
Adjust entry request payload
Adjustment amount
150.5
Currency code (ISO 4217)
"USD"
When the adjustment takes effect
Additional notes explaining the adjustment
1000"Correcting processing fee discrepancy"
Reason code for the adjustment
255"FEE_ADJUSTMENT"
Indicates that the request was successful and the response contains the expected data.
Exception details
User the exception is assigned to
Creation timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"
Due date for resolution in RFC3339 format
"2025-01-20T10:30:00.000Z"
External issue ID in the external system
"RECON-1234"
External system where exception was dispatched
"JIRA"
Unique identifier for the exception
"550e8400-e29b-41d4-a716-446655440000"
Reason the exception was raised
"Amount mismatch detected"
Resolution notes when resolved
"Resolved via force match"
Reason for the resolution
"BUSINESS_DECISION"
Type of resolution applied
FORCE_MATCH, ADJUST_ENTRY "FORCE_MATCH"
Severity level
LOW, MEDIUM, HIGH, CRITICAL "HIGH"
Current status
OPEN, ASSIGNED, RESOLVED "OPEN"
Transaction ID this exception is for
"550e8400-e29b-41d4-a716-446655440001"
Last update timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"