logo

Exceptions

Review transactions that still need to be matched or explained.
Open Reconciliation β€Ί Exceptions in the app.
(Formerly Unmatched transactions.)

What you see

A work queue of transactions that still need to be matched (description in-app: β€œReview transactions that still need to be matched.”). Use the date range (often Inherited from the company financial range β€” Overwrite / Clear all), Refresh, and Export.
Screenshot coming soon β€” Replace with: Reconciliation β€Ί Exceptions (work queue + Explain/Approve)
Screenshot coming soon β€” Replace with: Reconciliation β€Ί Exceptions (work queue + Explain/Approve)
Typical columns include matching sources, source, ledger, transaction ID, explain category, status, timestamp, amount, matching difference, balance pattern, labels/supplier, and explanation fields. Row actions include View and Explain.

Explain and approve

Select compatible rows, then:
  • Explain β€” assign an explanation category (and related action) for unmatched or rejected items
  • Approve β€” confirm explained items that need approval, when your role allows it
Selection must be compatible (same explanation mode/category rules). Open a row to view transaction detail, matching-package status mix, and explain from the detail sheet.

Workflow tips

  1. Check Reconciliation OverviewReconciliation Overview for which packages need attention
  1. Confirm matching packages and rules are configured under Setup
  1. Explain remaining exceptions here (or rely on Explanation RulesExplanation Rules for automation)
  1. Re-run matching if configuration changed

Related