Reconciliation

Overview

The reconciliation engine matches imported external records against your internal ledger data. It supports three types of records:

Import Sources

Records can be imported through several methods:

Transaction Reconciliation

Import

Import transactions from your bank, broker, exchange, or blockchain wallet. Each transaction includes a date, description, amount, currency, and optional reference numbers.

Duplicate detection runs automatically during import — transactions with matching external IDs, transaction hashes, or identical date/amount/description combinations are skipped.

Auto-Matching

After import, run the auto-match engine to find corresponding ledger events. The engine scores potential matches using multiple signals:

Transactions scoring above the auto-match threshold (default: 90/100) are automatically matched. Lower-scoring matches are flagged for manual review.

Manual Matching

For unmatched transactions, you can:

• Match to an existing event — link the transaction to a ledger event
• Create a new event — generate a ledger event directly from the transaction, which flows through the posting engine
• Exclude — mark the transaction as not relevant (e.g. internal transfers)

The system learns from your manual matches — counterparty patterns are saved and applied to future auto-matching.

Status Lifecycle

Each transaction progresses through these statuses:

• Unmatched — no corresponding ledger event found
• Matched — linked to a ledger event (auto or manual)
• Confirmed — match verified and locked
• Excluded — marked as not relevant

You can unmatch a previously matched transaction to send it back to the unmatched queue.

Position Reconciliation

Import holdings snapshots from brokers, custodians, or blockchain wallets to verify that your ledger balances match external records.

The engine matches imported positions to ledger accounts by currency and name, then computes the variance between the imported quantity and the ledger balance as of the snapshot date.

Balance Reconciliation

Import end-of-period balance confirmations to verify that your ledger account totals match external statements.

The engine matches imported balances to ledger accounts by account code, name, or role mapping, then computes the variance between the reported balance and the computed ledger balance.

Reconciliation Workflow

1. Import — upload CSV or sync from a connected source
2. Auto-match — run the matching engine to find correspondences
3. Review — examine matched and unmatched items in the dashboard
4. Resolve exceptions — handle unmatched items (match, create event, or exclude)
5. Confirm — lock reconciled items

Use Confirm All to bulk-confirm all matched items in a batch.

API Reference

Reading Data

GET /api/reconciliation?entityId=...&type=transactions&status=UNMATCHED

Transaction Actions

Position Actions

import_positions, auto_match_positions, confirm_position, unmatch_position, exclude_position

Balance Actions

import_balances, auto_match_balances, confirm_balance, unmatch_balance, exclude_balance

All write operations use POST /api/reconciliation with an action field.