YichenResolveAI-powered financial exception resolution
Close periodAugust 2026
Search cases
Maya ChenDemo operator
Read-only product demo · Generated fictional records, not customer dataDeterministic truth · Advisory AI · Human authority
Controlled close

Audit-ready means explainable, not merely complete.

Review the generated run history, human actions, and evidence-packet readiness before treating the close as reviewed.

Packet readiness3 of 4 controls addressedFive active cases still require review
August 2026 packet

One timeline. Four control layers.

Source lineage, deterministic outcomes, advisory boundaries, and human authority remain separately visible.

14source rows
4match groups
6cases
1decision
Append-only history

A reviewer can reconstruct the close.

9 of 9 events
  1. Evidence requestedCASE

    Requested the next-day bank export before classifying the short receipt.

    Maya Chen · Reconciliation analyst · Aug 20, 2026, 10:12 AM UTCcase-partial-settlement-005 →
  2. Resolution recordedDECISION

    Classified as an approved dispute-administration charge after reviewing the remittance note.

    Maya Chen · Reconciliation analyst · Aug 20, 2026, 9:18 AM UTCcase-fee-variance-004 →
  3. Case review startedCASE

    Opened after the fee schedule check identified an explicit variance.

    Maya Chen · Reconciliation analyst · Aug 20, 2026, 9:04 AM UTCcase-fee-variance-004 →
  4. Evidence requestedCASE

    Requested the ERP journal-source detail before recording a resolution.

    Maya Chen · Reconciliation analyst · Aug 20, 2026, 8:29 AM UTCcase-missing-reference-001 →
  5. Case review startedCASE

    Opened after deterministic run left the ERP entry unresolved.

    Maya Chen · Reconciliation analyst · Aug 20, 2026, 8:22 AM UTCcase-missing-reference-001 →
  6. Exception cases createdRUN

    Four unresolved and two materially ambiguous records became evidence-backed cases.

    Resolve workflow · Aug 20, 2026, 7:42 AM UTCrun-aug-2026 →
  7. Deterministic matching completedRUN

    Seven accepted records joined four match groups; six records entered the exception workflow.

    Resolve rules · Aug 20, 2026, 7:42 AM UTCrun-aug-2026 →
  8. Inputs validatedRUN

    Thirteen rows were accepted and one ERP row was rejected with an explicit validation reason.

    Resolve workflow · Aug 20, 2026, 7:42 AM UTCrun-aug-2026 →
  9. Run contract frozenCONTROL

    Input checksums, mappings, normalization, and matching versions were bound to run-aug-2026.

    Resolve workflow · Aug 20, 2026, 7:42 AM UTCrun-aug-2026 →
Close remains human-controlled.

Resolve preserves the evidence and decision history. It does not certify accounting treatment or create an external financial effect.

See authority boundaries →