Intelligent reconciliation for multi-rail treasury.

Bank wires, on-chain settlements, and stablecoin float, reconciled in one close cycle. The AI agent explains every match, flags every break, and learns your tolerances.

Built by operators from

CoinbaseWealthsimpleShopify
HighBatch reconciliation
May 14 · 03:00 AM

Batch settlement — ACH payout file

Ledger $1,001,247.50·Bank $999,012.80·Δ −$2,234.70
Sub-reconciliations15 / 1883%
15 matched2 discrepancies1 unmatched

3 sub-reconciliations need attention. J. Morrison −$25 likely NACHA return fee. R. Dhillon $82,500 missing from bank batch — possible compliance hold. T. Nakamura $15.30 overage on FX rounding.

Amount
38/40
Date
24/25
Reference
22/35

01By the numbers

Reconciliation that’s fast, accurate, and built for audit.

Treasury teams aren’t short on tools. They’re short on the right ones for the books they actually run.

  • Hours

    Not days

    Fast close

    Multi-rail books shouldn't take days to close. The agent auto-confirms the obvious matches and triages the rest in one feed — sign-off in a single session, not five.

  • Tunable

    Per-rail thresholds

    Low error rate

    Tunable thresholds per rail. The agent learns your tolerances over time, so the cases that need a human stay human. Confidence scoring on every proposed match — amount, date, and reference.

  • SOC 2*

    Controls aligned

    Compliance & audit-grade

    Every action — confirm, escalate, resolve, snooze, override — logged immutably with actor, timestamp, and reasoning. Auditors stop asking for screenshots. Compliance stops asking for spreadsheets. *Type II certification on the roadmap.

02Dashboard preview

See discrepancies the moment they happen.

The Command Center ranks every break by confidence and severity. Open any match to see how the agent scored it — amount, date, reference — and which sub-recs are still open.

opentally.ai / command-centerMigie Labs Inc.

Command Center

AI-triaged feed of items requiring your attention.

Agent: Review 2 high-confidence NAV exceptions first — they affect end-of-day reporting.

  • HighBatch rec
    moments ago

    Batch settlement — ACH payout file ($1M)

    15 / 18 sub-recs resolved · 83%
  • CriticalVelocity
    moments ago

    Settlement velocity mismatch — $1.8M wire

    Bank $1,800,000 · Chain $1,795,000 · Δ $5,000
  • HighReview
    moments ago

    Proposed match — Wire $500,000 → USDC mint $499,250

    Amount 38/40 · Date 24/25 · Reference 22/35

03Multi-asset · Multi-institution

One reconciliation layer for every rail and every institution.

OpenTally connects to the banks, custodians, exchanges, and ERPs your treasury team already uses — and reconciles them against each other in a single close cycle.

5 sources

Banking & payments

  • Plaid
  • ACH
  • Wire
  • RTP
  • SWIFT
4 sources

Custody & exchanges

  • Fireblocks
  • Coinbase
  • Kraken
  • BitGo
5 sources

Stablecoins & on-chain

  • Circle USDC
  • Tether USDT
  • Ethereum
  • Bitcoin
  • Solana
5 sources

ERP, accounting, ops

  • Xero
  • NetSuite
  • QuickBooks
  • Slack
  • Webhooks

Mix of live, pilot, and roadmap connectors — see the FAQ for the current tier per integration. Custom connectors on request.

04How it works

Built around the workflow treasury teams actually run.

01

Multi-rail feed

One triaged feed across every rail.

Wires, ACH, on-chain transfers, USDC mints, exchange settlements — every recon item surfaces in a single AI-triaged feed, ranked by confidence and severity. The agent narrates its scoring so you know exactly why a 78% confidence match is in your review queue.

02

Sub-reconciliations

Walk every leg. Resolve at the right grain.

When a $1M batch settles into 18 client transactions, OpenTally doesn't pretend it's one line. Match 15 cleanly, isolate the 3 that need attention, resolve at sub-rec level. Parent reconciliations stay blocked until every leg closes.

03

Audit trail

An audit trail every regulator and CFO already understands.

Every action logged immutably. Actor (human or Agent), timestamp, target, reasoning. Hand auditors a link instead of a stack of spreadsheets. SOC2-aligned posture from day one.

05Slack

Lives in your Slack — where treasury already works.

The agent doesn’t just notify Slack — it triages there. Operators resolve, snooze, and escalate from inside the message; every action is identity-verified and written to the same audit trail.

  • Posts where you already work

    Every break lands in your team's Slack channel — severity, dollar bucket, the agent's one-line read of why. No new tab. No new login.

  • Resolve from the message

    One-click Resolve, Snooze, Investigate, and Create-ticket (Linear, Jira, GitHub) right inside the post. The dashboard's RBAC enforces the action — Slack is the surface, not the policy.

  • Audit-grade by default

    Every Slack-driven action is HMAC-signed, attributed to the operator's OpenTally identity, and written to the same audit log auditors review. Unauthorized clicks are recorded and refused inline.

Compliance posture

  • Signed callbacks
  • Identity-verified actions
  • Audit-logged
  • Tenant-scoped redaction
  • Encrypted bot tokens
  • Per-tenant disable

When enabled, Slack is a sub-processor; disable per tenant anytime. Bot tokens are encrypted at rest, and sensitive identifiers are masked by default.

#treasury-recon· slack
03:14 AM
OpenTally
OpenTallyAPP3:14 AM

🔴 CRITICAL: Settlement Lag — wire 1*********45 USD

Wire to account AC********90 delayed beyond threshold. Bank shows pending; chain shows confirmed. Issuer queue backlog suspected.

Elapsed: 48h · Threshold: 24h

ZO
Zuwa3:17 AM

Confirmed with issuer — backlog cleared at 03:11. Resolving.

OpenTally · ✅ Alert resolved by Zuwa · audit row a7b8c4d3

06How OpenTally is different

Built for the in-between books current tools don’t cover.

CapabilityOpenTallyLegacy TMSPayments-firstCrypto-only
Fiat rails (bank read, ACH / wire via bank data)
On-chain settlement
Stablecoin float
Sub-reconciliations
AI agent + auto-resolve
Audit-grade trail
Reconcile from Slack with one-click actions
Time to first closedaysmonthsweeksweeks

Comparison reflects our read of the category in 2026 based on public docs and operator conversations. Vendor functionality changes.