Accessing exception details
On the Exceptions page, select the linked Reason in the exception row to open its detail page. You can also focus a queue row and press Enter. Both paths carry the queue’s context scope when one is active.
Figure 1. Exception detail showing the transaction information, candidate matches, comments, and action history.
Page layout
The page header always uses the title Exception details. It does not use the exception’s reason or ID as its title. It includes a back button and, depending on your permissions, can show View audit trail, Assign, Open dispute, Dispatch, Adjust entry, Resolve, and Force match. These controls are permission-gated, not selected by a configured workflow. For an exception in RESOLVED or PENDING_RESOLUTION, the UI hides Open dispute, Dispatch, Adjust entry, Resolve, and Force match. The UI can still show Assign to an operator with assignment permission, even in those states. The Match to this action belongs to the candidate panel rather than the header and requires manual-match permission. The View audit trail action appears only to an administrator or to a user with audit-log read permission. It opens a slide-over with the exception’s immutable governance audit events. Below the header, a status rail shows the exception ID, its severity and status badges, and the Updated timestamp. The body is a three-column sheet. The Transaction, Information, Candidate matches or Resolution, and Comments panels fill the two left columns. The History panel runs the full height of the right column.
Queue navigation
The queue controls work only within the currently loaded page of the filtered Exceptions queue. The Previous exception / Next exception buttons and a position indicator let you move among those siblings. They appear when the exception is present in that session-scoped snapshot and the page has more than one item. They do not traverse to another cursor page. The page disables the boundary button. The Advance to next after resolving checkbox appears only for a non-terminal exception that has a next sibling. After a successful Resolve, Force match, Adjust entry, or Match to this action, it opens that recorded next sibling when selected. At the last item, the exception has no next sibling and the page hides the checkbox. If the browser cannot persist the session snapshot, the page omits sibling navigation.Panels
Transaction
The exception-detail API enriches the record from its linked transaction and source. The page can then show Amount, Currency, Transaction date, and Source without first resolving a reconciliation context. It is not an arbitrary full transaction-payload viewer. If the linked transaction or its source has been deleted, enrichment is unavailable. The panel still shows the transaction ID and explains why instead of showing a zero amount. The context selector in the panel header controls the scope for candidate matches, not whether transaction enrichment is available.Information
The Information panel displays read-only details about the exception:Candidate matches
For an exception that is not RESOLVED or PENDING_RESOLUTION, the Candidate matches panel requests counterpart candidates for the exception transaction in one reconciliation context. It requests up to 50 ranked proposals by default. The candidate endpoint accepts a limit from 1 through 200. Each proposal has a required 0–100 score, displayed with Strong, Plausible, or Weak confidence bands. The panel also shows the candidate’s amount, currency, identifier, rule type, and date. It shows the candidate’s amount and date deltas. It shows the score rationale for amount, currency, date, reference similarity, and any configured composite match fields. Candidates are 1:1 opposite-side counterparts ranked over raw amounts, without fee normalization or FX-variance bands. The panel requires a context. If none is available, it asks you to select one. An empty result is distinct from an error, and a request failure shows Retry. If you have manual-match permission, Match to this opens Match to this candidate? for confirmation. Confirming links the two transactions into a confirmed match group, removes them from the unmatched queue, and refreshes the exception.Resolution
For RESOLVED and PENDING_RESOLUTION exceptions, a Resolution panel replaces the candidate panel. It can show the Resolution type, Resolution reason, Resolution notes, Resolved by, and Resolved at values recorded for the exception.Comments
The Comments panel shows each comment’s author, relative timestamp, and content. The oldest comment appears first. Enter text and click Send, or press Ctrl+Enter / Cmd+Enter. A comment must contain text and the service accepts up to 5,000 characters. Only your own comments show a delete control. Deleting one requires confirmation and permanently removes it. You cannot add comments to an exception in RESOLVED or PENDING_RESOLUTION, but existing comments remain visible.History
The History panel shows an action timeline. Each entry contains the action description, the actor (or “system” for automated actions), and a relative timestamp. New entries are published asynchronously, so an action can take roughly two to three seconds to appear.Actions
The header contains the lifecycle actions. Their visibility follows the permissions and status rules above. Manual matching is available from Candidate matches. Assign Opens the Assign exception dialog. The Assignee field starts with the current assignee when there is one. Enter a nonempty assignee of up to 255 characters and click Assign. Open dispute Opens the Open dispute dialog. Select a Category (Bank Fee Error, Unrecognized Charge, Duplicate Transaction, Amount Mismatch, or Other) and provide a Description. The dialog requires both fields and limits the description to 2,000 characters. Then click Open dispute. Evidence submission and dispute closure happen on the dispute’s own detail page. See Managing Disputes. Dispatch Opens the Dispatch to External System dialog to send the exception to an external system for handling:
If the selected target system does not have a connector configured, dispatch fails. Make sure the integration exists in Exception Routing before you dispatch.
Adjust entry
Opens the Adjust entry dialog to record a monetary correction that resolves the exception. The dialog requires every field. These fields are not conditional on a workflow configuration:
Click Record adjustment to submit the adjustment and resolve the exception.
Resolve
Opens the Resolve exception dialog to mark the exception resolved directly. The dialog requires Resolution and limits it to 255 characters. Add an optional Reason of up to 1,000 characters for the record, then click Resolve.
Force match
Opens the Force match dialog to override normal matching and resolve the exception:
Click Confirm force match to resolve the exception.