ReconStandard
← ReconStandard

Explore the work.

Illustrative concepts. Fictional data. A platform in development.

Optional sound is off. Enable a quiet ambient chord and gentle interaction tones.

FROM SOURCE FRAGMENTS TO A REVIEWABLE RECORD

Messy inputs.
A usable picture.

Follow four fictional rows as formats are standardized, duplicates are handled and records reconciled. Every output keeps its source; uncertainty goes to review.

Illustrative transformation · Fictional snapshot: 15 Sep 2026 · Fixed mappings

Source records become a connected evidence set An original geometric illustration using fictional records. R1 expects USD 12,500 for DIV-204 and AT-041, due 10 September 2026. R3 receives USD 12,500, posted 15 September 2026, reference RMT-731. Separate plates retain duplicate R2 outside totals and hold R4 for review because its date, 09/10/26, is unclear. Human review remains pending. SOURCES, IN FORMATION DIV-204 / AT-041 Same amount. Different dates. The timing difference stays visible. R3 / RECEIVED USD 12,500 RMT-731 Posted 15 Sep 2026 R1 / EXPECTED USD 12,500 DIV-204 · AT-041 Due 10 Sep 2026 Source links attached · Human review pending KEPT SEPARATE R2 / DUPLICATE Excluded from totals Lineage retained R4 / QUARANTINED 09/10/26 · Date unclear No date guessed Four messy rows become a reviewable record. Two rows accepted, duplicate R2 retained but excluded, uncertain R4 held for review. 01 / SOURCE FRAGMENTSR1 · " usd "12,500.00R3 · cash12 500.00+ R2 duplicate+ R4 unclear 02 / TWO ACCEPTED ROWSR1 expected · USD 12,500R3 received · USD 12,500 03 / CONNECT THE EVIDENCE12,500 ↔ 12,500Amount agrees · Late receipt visible 04 / REVIEWABLE OUTPUTDIV-204 · AT-041 · Sources attachedHuman review remains pending R2 excluded from totals · R4 stays held
01 / Four source rows arrive in different formats.
Inspect the example: source rows, checks and review package

Four rows. Several ways to say the same thing.

SOURCE SNAPSHOT / 15 SEP
R1 / entitlement.csv" AT-041 "," div-204 ","usd"
"12,500.00","2026-09-10",expectedSpacing · case · number formatting
R2 / repeated importAT-041 | DIV-204 | USD
12500.00 | 2026-09-10 | expectedSame expected event as R1
R3 / cash statementat-041 / div-204 / USD
12 500.00 / 2026-09-15 / RMT-731Receipt recorded in a later snapshot
R4 / legacy extractAT-099 : UNMAPPED : usd
1,250.00 : 09/10/26 : unknownAmbiguous date · unknown event

Standardize fields. Preserve the original.

2 ACCEPTED / 2 HELD OUT
Accepted rows and their original sources
SourceAccount / eventCurrency / amountDate / meaning
R1AT-041
DIV-204		USD
12,500.00		10 Sep 2026
Expected
R3AT-041
DIV-204		USD
12,500.00		15 Sep 2026
Receipt RMT-731

R2 · Duplicate flaggedKept in the source history; excluded from totals.

R4 · Held for reviewDate and event require clarification. No guess applied.

Compare like with like.

EVENT DIV-204 / ACCOUNT AT-041
R1 / EXPECTEDUSD 12,500.00Due 10 Sep 2026
R3 / RECEIVEDUSD 12,500.00Posted 15 Sep 2026 · RMT-731

Amount agrees. Receipt arrived after the due date. The relationship is ready for a reviewer; it is not automatically approved.

R4 remains held for review. R2 remains excluded from totals.

A record someone can work with.

REVIEW PACKAGE / FICTIONAL

DIV-204 / AT-041

Expected → receipt → evidence

USD 12,500.00 · R1 linked to R3
Due 10 Sep · Posted 15 Sep · RMT-731

Ready for human review
  1. Standardized fields linked to the original records
  2. Duplicate excluded; original retained
  3. Timing difference visible in the record
  4. R4 remains in the clarification queue

Illustrative preparation for use in the next process. Each institution's required data format, rules and approvals still need to be checked.

Four source rows → two accepted records + one flagged duplicate + one row held for review. No uploaded or customer data is used.

01 / FROM FRAGMENTS TO PERSPECTIVE

Follow the information.
Keep the questions visible.

A short story about connection, exceptions and the people behind a decision.

Skip the story
Illustrative concept — sample data, not a live product session
EXAMPLE / HARBOR FUNDFICTIONAL RECORDS

Bank

Cash receipt · A01USD 24,800Statement entry
Income · B02USD 1,250Amount received

Custody

Cash receipt · A01USD 24,800Custody entry
Income · B02USD 1,250Custody record

Ledger

Cash receipt · A01USD 24,800Internal entry
Income · B02USD 1,300Expected amount

A01 Illustrative relationshipSame reference and amount shown across sources.

B02 Unresolved exceptionUSD 50 difference · Further investigation required

OPEN

A01 relationship identifiedIllustrative comparison

Review not recorded

B02 remains openUnresolved difference retained in the outcome

01 / SEPARATE SOURCES

One event.
Different perspectives.

A bank statement, a custody record and an internal ledger describe the same activity in different contexts. Start by seeing them side by side.

02 / VISIBLE RELATIONSHIPS

Connection creates context.

The fictional A01 entries share a reference and amount. Highlighting that relationship makes the example easier to follow; it is not a result from a reconciliation engine.

03 / EXCEPTIONS

Clarity includes
what doesn’t fit.

The B02 records differ by USD 50. The exception stays open, with the difference visible. A connection alone does not explain or resolve it.

04 / HUMAN REVIEW

Keep people
in the decision.

Try recording an example review of the A01 relationship. This does not approve a real transaction or resolve the separate B02 exception.

No example review recorded.

05 / TRACEABLE OUTCOME

A clearer trail.
An honest outcome.

The illustrative trail keeps the relationship, review state and unresolved item together. If you skipped human review, it remains unrecorded.

The open exception stays visible.

Local demonstration only. Selections reset when this page reloads.

02 / THE CONNECTED OPERATIONS EXPLORER

See the relationships.
Explore the possibilities.

Seven areas. One intended direction.
Select an area to explore its role in a wider operational picture.

Illustrative concept · Fictional connections · Intended scope, not completed modules

Choose an area using the buttons. Highlighted lines show illustrative connections.

Seven connected areas

Data
Source information and context.
Reconciliation
Compare records and make differences visible.
Controls
Evidence, oversight and accountability.
Investment Operations
Cash, positions and income in context.
Payments
Payment records and operational follow-up.
Workflow
People, responsibilities and review.
Reporting
Relationships, decisions and open items.

THE RECONSTANDARD RESEARCH ROOM

One break.
The context around it.

See the proposed value of AI assistance: connect current evidence with past human decisions, identify what is still unknown and prepare a useful next action.

Illustrative playback · Fictional records, emails and chats · Scripted answers, not a live AI session

DIV-204 / OVERDUE DIVIDENDUSD 12,500.00

Atlas Income Fund · AT-041 · Due 10 Sep 2026

ILLUSTRATED CASE STATEOpen · No receipt in initial snapshot

Starts: 14 Sep 2026, 09:00 · Permitted-source scope is illustrative

THE CONTEXT, CONNECTED

Six sources. One investigation.

Six fictional sources · Select a source to trace its connections

RECONSTANDARD / RESEARCH CONTEXTDIV-204

Receipt missing

2 sources in this step
OPEN QUESTION
ILLUSTRATIVE RELATIONSHIP FIELD

Six fictional sources · Abstract visual context

E1 · The entitlement establishes the expected event, not payment.

History suggests the next question. It does not prove today’s cause or approve closure. Surrounding points are abstract visual context, not additional records or live AI activity.

ReconStandard

Illustrative operations assistant

DEMO
YOU / SAMPLE QUESTION

Why is dividend DIV-204 still open, what have we already checked, and has another team handled something similar?

RECONSTANDARD / SCRIPTED ILLUSTRATION

Start with the missing receipt.

The entitlement expects USD 12,500.00 for AT-041, due 10 Sep. The cash snapshot through 14 Sep, 09:00 has no corresponding receipt. The initial break remains open.

An entitlement establishes what is expected. It does not prove that cash arrived.

Next: connect the current records and messages. No email has been sent.

  1. 14 SEP / RESEARCHAI illustration

    Assemble E1–E4 and H1–H2. Identify the missing acceptance confirmation.

  2. 14 SEP / DRAFTAI → person

    Prepare a cited follow-up. A person checks the wording before any real use.

  3. 14 SEP / REPLYCustodian scenario

    Acceptance and payment date arrive. Keep the break awaiting cash.

  4. 15 SEP / VERIFYCash evidence → reviewer

    Compare the receipt, then record an explicit example closure. Retain the trail.

See the wider dashboard, sample reports and automation boundaries ↗

The full fictional case, without playback

At the initial review, USD 12,500 is expected but has not arrived. A custodian message reports pending document review; operations reports submission without acceptance confirmation. H-118 shows a similar prior human sequence on a different account: confirm acceptance, wait for cash, then review closure.

The illustrative follow-up asks for acceptance, remaining requirements and a remittance reference. A later sample reply schedules payment for 15 Sep. Only the subsequent USD 12,500 receipt makes this case ready for a human closure decision. No message is delivered or real record changed.

AI AGENTS / PLANNED CAPABILITY

Work with direction.
Authority with limits.

Our vision is for teams to assign reconciliation work, agents to carry out permitted tasks, and people to supervise exceptions and significant decisions.

Planned across data, cash, positions, income and payments reconciliation. These are coordinated responsibilities, not seven separately deployed models.

01Data organiser

Interpret available inputs, suggest field labels and flag missing or inconsistent data.

From
Records and documents within the permitted source scope.
Prepare
Usable fields with source references and visible gaps.
What it cannot do
Ambiguous values remain flagged; a proposal does not become approved data.
02Match analyst

Run approved matching workflows and propose relationships for independent checks.

From
Prepared transactions and an applicable approved rule.
Prepare
A possible match with financial validation results.
What it cannot do
Amount alone is insufficient: transaction identity, currency, account and rule conditions must agree.
03Investigator

Follow references, dates, fees, reversals and supporting documents to test possible explanations.

From
A difference and the evidence available for that case.
Prepare
A cited explanation or a precise request for missing evidence.
What it cannot do
A possible explanation is not a confirmed cause until the required evidence supports it.
04Rules guide

Retrieve applicable approved instructions, client rules and relevant past decisions.

From
Authorized procedures and accessible case history.
Prepare
The applicable guidance, its source and the differences from past cases.
What it cannot do
History suggests a question; it cannot establish today's cause or override the current rule.
05Case coordinator

Prepare review tasks, track outstanding evidence and deadlines, and escalate within configured permissions.

From
An open case, its outstanding items and permitted next actions.
Prepare
A clear handoff to the responsible role, with an activity history.
What it cannot do
Work outside the agent's authority stops for human review or a referral to the responsible team.
06Review reporter

Assemble source references, validation results and decision history into a reviewable record.

From
The evidence, checks and recorded decisions for the case.
Prepare
A connected evidence pack and report for review.
What it cannot do
Keep unresolved items visible and distinguish proposals from approved decisions.
07Process analyst

Identify recurring issues and suggest rule or workflow improvements for testing and approval.

From
Permitted historical patterns and reviewed outcomes.
Prepare
An improvement proposal with examples to evaluate.
What it cannot do
No silent changes to rules, instructions or authority.

INTENDED OPERATING MODEL / PLANNED

What agents may do
stays a team decision.

Customers are intended to control what agents may do. Manual investigation, operator controls and required human approvals remain part of every mode.

01 Review only
Compare agent work with reviewed outcomes without changing production records.
02 Suggest next steps
Prepare proposed matches, explanations and actions for review.
03 Act after approval
Complete specifically authorized actions only when the required evidence, validation and permissions are satisfied.
04 Follow an approved process
Coordinate an approved process from intake to completion, escalating anything outside its authority.

HOW THE PLANNED MODEL DIVIDES RESPONSIBILITY

Agents investigate and propose. The reconciliation engine validates financial relationships. Permissions and approvals govern execution.

  • Source-backed explanations and traceable decisions.
  • Client-specific access and approved instructions.
  • Independent validation of proposed matches.
  • Human approval for significant changes.
  • Clear escalation when evidence is incomplete.
  • Visible activity history and operator controls.
Explore the agent workflow Follow the dividend investigation

Planned capabilities describe the product vision. The website's examples are local scripted illustrations using fictional data; they do not connect to live AI, financial records, email or an approval service.

FROM INDIVIDUAL BREAKS TO OPERATIONAL OVERSIGHT

See the work.
Understand what moves it.

For bank operations, custody, investment and fund-accounting teams. Explore how case context could connect daily controls, follow-up and reporting.

THE PROBLEM TO SOLVEWhen records, explanations and ownership sit in separate systems, teams have to reconstruct the story before they can act.

THE RECONSTANDARD DIRECTIONAn open item, its supporting evidence and its next responsible action, together. From the daily queue to a report someone can explain.

Illustrative dashboard · Six fictional work items · Fixed snapshot: 14 Sep 2026, 09:05 · Not a live product or owner/admin area

ReconStandard

Operations desk

DAILY OVERSIGHT / SAMPLE
Snapshot stays fixed during other demonstrations.

One queue. Different reasons to stay open.

Showing all 6 sample work items.

Select an item to see its problem, proposed preparation and responsible next action.

All six are open work items; two await review. Queue age means days since entering this sample queue, not days past due. Expected amounts, differences and matched amounts are different measures and are not added together.

SAMPLE DAILY OPERATIONS REPORT

What is holding up the work?

14 SEP 2026 / 09:05
Same six items. No hidden population.

Open work by next decision
4 need action2 await review
Queue age · work-item count

Entered today2

1–2 days3

3+ days1

Age is measured from entry to this sample queue. These are counts of work items, not transaction volume, exposure or performance results.

ILLUSTRATIVE MANAGEMENT COMMENTARY

Four need action.
Two need a decision.

Two income items still lack a confirmed receipt. One reconciliation difference needs an explanation. One ambiguous input remains held for review.

A01 has aligned records ready for review. CTRL-09 has a compiled evidence set awaiting reviewer attestation. Neither is approved in this snapshot.

Next operational focus

Income operations confirms payment status; reconciliation investigates B02; the data steward resolves DATA-17; reviewers consider A01 and CTRL-09.

Prewritten sample commentary. An operational oversight illustration, not a regulatory filing, certification or generated live report.

SAMPLE COVERAGE

2 Income

2 Reconciliation

1 Data quality

1 Financial controls

PROPOSED AUTOMATION / DEVELOPMENT DIRECTION

Automate preparation.
Make decisions explicit.

Explore the boundary at each stage.
No automation rate is claimed.

FRICTION IN A DISCONNECTED WORKFLOW
The same event arrives in different formats. Ambiguity gets carried into the next spreadsheet.
CONFIGURED RULES
Repeatable preparation

Validate required fields, standardize known formats and flag duplicates against institution-approved rules. Preserve the original records and hold unclear fields for review.

AI ASSISTANCE
Context and proposals

Suggest a possible field interpretation with its source and uncertainty. A suggestion does not silently become trusted data.

HUMAN CONTROL
Judgment and authority

A data steward confirms ambiguous dates and mappings. Approved configuration and acceptance criteria govern what can move downstream.

The intended automation stops where evidence or authority is missing.

Approved connectors, data access, configured rules, validation and server-enforced permissions would be prerequisites. This website does not execute these processes. Real email sending, approvals and closure are separate controlled actions.

Follow one case through its evidence ↗Explore the raw-data transformation ↗

03 / THE PEOPLE IN THE PICTURE

Built around the questions
operations teams ask.

Fund accounting and investment operations shape the intended focus, with a broader perspective across treasury, banking and payments.

FUND ACCOUNTING / INTENDED USE

What needs attention
before the next close?

A view of cash, positions and income that keeps differences and review context alongside the records.

  • Compare records across operational perspectives.
  • Keep unresolved exceptions in view.
  • Understand what has—and hasn’t—been reviewed.

YOU ASK

What is preventing this overdue dividend from closing?

ILLUSTRATIVE ANSWER / DIV-204 / INITIAL SNAPSHOT

USD 12,500.00 expectedNo receipt through 14 Sep, 09:00

E1 entitlement + E2 cash + E3 custodian + E4 chat

Confirm document acceptance; keep the income item open.

Inspect the question and its evidence ↗
Original operational perspective

AN ILLUSTRATIVE CLOSE PERSPECTIVE

CashSource context
PositionsRelationships
IncomeOpen questions

Context before conclusion.

INVESTMENT OPERATIONS / INTENDED USE

How does one movement
affect the wider picture?

Bring cash, holdings and income into a shared operational context for investment and asset-management teams.

  • Follow relationships between activity and records.
  • Carry source context into exception review.
  • Maintain visibility across operational handoffs.

YOU ASK

Has another team resolved a comparable case?

ILLUSTRATIVE ANSWER / H-118 / HISTORICAL COMPARISON

MI-022 · USD 8,400.00Another fund and team · 12–14 Aug

H1 case + H2 human decision and receipt

Prior sequence: confirm acceptance → observe cash → review. Similarity is a lead, not today’s cause.

Inspect the question and its evidence ↗
Original operational perspective

AN ILLUSTRATIVE OPERATIONS PERSPECTIVE

ActivitySource records
HoldingsPosition context
IncomeReview questions

Connections across the lifecycle.

TREASURY / INTENDED USE

Which cash movements
still need an explanation?

Connect bank and internal records with the questions that matter to daily treasury operations.

  • Compare cash movements across sources.
  • Keep timing and amount differences explicit.
  • Carry open questions into the next review.

YOU ASK

Is this expected dividend available cash yet?

ILLUSTRATIVE ANSWER / DIV-204 / INITIAL CASH VIEW

Expected: USD 12,500.00Observed receipt: none in the initial snapshot

Due 10 Sep · cash checked 14 Sep, 09:00

Separate an expected inflow from a verified receipt. A scheduled payment stays pending.

Inspect the question and its evidence ↗
Original operational perspective

AN ILLUSTRATIVE CASH PERSPECTIVE

BankStatement context
LedgerInternal view
TimingOpen differences

Visibility into the movement.

BANKING & PAYMENTS / INTENDED USE

Where does the record end
and follow-up begin?

A direction for connecting payment records, operational controls and responsibilities without losing the original context.

  • See related records across process boundaries.
  • Make exceptions and ownership visible.
  • Preserve an understandable review trail.

YOU ASK

What should we ask the custodian, and who acts next?

ILLUSTRATIVE ANSWER / DIV-204 / NEXT ACTION

Ask for acceptance + payment referenceDraft prepared for the account owner to check

E3 reported review pending; E4 reports submission

Confirm remaining requirements and payment date. A reply alone cannot authorize closure.

Inspect the question and its evidence ↗
Original operational perspective

AN ILLUSTRATIVE PAYMENT PERSPECTIVE

RecordPayment context
ControlReview point
Follow-upOpen responsibility

Accountability across the handoff.

Illustrative use cases describe the intended direction. They are not currently available product workflows.

THE REPORTING PERSPECTIVE

Clear statements.
Numbers you can follow.

Performance, operations, reconciliation and financial position. One fictional fund, presented consistently.

Illustrative report layouts · Fictional data · Not verified product exports

EXAMPLE FUND A FICTIONAL

Performance summary

Net assets and simple period return

ReconStandard
ILLUSTRATIVE LAYOUT
Reporting date / period
01–31 August 2026
Presentation currency
USD thousands, except percentages
Assurance / review
Unaudited · No approval recorded
Net asset movement
DescriptionUSD ’000
Opening net assets · 31 July 2026975
Net subscriptions, redemptions and distributions0
Increase in net assets from operations25
Closing net assets · 31 August 20261,000
Period return
Measure01–31 Aug 2026
Simple return, after the sample expenses2.56%
Supporting net asset observations · USD thousands
Observation dateNet assets
31 Jul 2026975
07 Aug 2026982
14 Aug 2026978
21 Aug 2026990
31 Aug 20261,000

Notes to this illustration

Return = 25 ÷ 975 × 100, rounded to 2.56%. No subscriptions, redemptions or distributions are assumed. The result is after the management fees and operating expenses shown in the statement of operations.

Single-period, simulated figures; not annualized. No benchmark, investment track record or verified methodology is represented.

Example Fund A · Fictional dataReconStandard / PERFORMANCE

EXAMPLE FUND A FICTIONAL

Statement of operations

Profit & loss for the period

ReconStandard
ILLUSTRATIVE LAYOUT
Reporting date / period
01–31 August 2026
Presentation currency
USD thousands, except percentages
Assurance / review
Unaudited · No approval recorded
Income and expenses for the period
DescriptionUSD ’000
Investment income15
Expenses
Management fees7
Operating expenses3
Total expenses10
Net investment income5
Realized and unrealized gains
Net realized gains12
Change in unrealized appreciation8
Total realized and unrealized gains20
Increase in net assets from operations25

Notes to this illustration

Expenses are presented as positive amounts and deducted from investment income. Net investment income of 5 plus realized and unrealized gains of 20 gives the period result of 25.

Opening net assets of 975 plus the result of 25 equals closing net assets of 1,000. This is a simplified illustration, not a complete set of financial statements.

Example Fund A · Fictional dataReconStandard / PNL

EXAMPLE FUND A FICTIONAL

Cash reconciliation

Bank statement and ledger cash comparison

ReconStandard
ILLUSTRATIVE LAYOUT
Reporting date / period
As at 31 August 2026
Presentation currency
USD thousands, except percentages
Assurance / review
Unaudited · No approval recorded
Bank-to-ledger reconciliation
DescriptionUSD ’000
Bank statement balance298
Add: deposits in transit5
Less: outstanding payments(3)
Adjusted bank balance300
Ledger cash balance300
Residual difference0
Outstanding reconciling items
Item / follow-up statusUSD ’000
Deposits in transit Outstanding · Subsequent bank evidence required5
Outstanding payments Outstanding · Subsequent settlement evidence required(3)

Review pending · Two timing items remain for follow-up.

Notes to this illustration

The two timing items are assumptions of this example. No subsequent bank or settlement evidence is attached. A zero residual does not resolve the outstanding items or record approval.

Ledger cash of 300 agrees with the statement of assets and liabilities. Account identifiers and real bank information are not included.

Example Fund A · Fictional dataReconStandard / RECONCILIATION

EXAMPLE FUND A FICTIONAL

Statement of assets and liabilities

Balance sheet / financial position

ReconStandard
ILLUSTRATIVE LAYOUT
Reporting date / period
As at 31 August 2026
Presentation currency
USD thousands, except percentages
Assurance / review
Unaudited · No approval recorded
Financial position
DescriptionUSD ’000
Assets
Cash300
Investments900
Receivables50
Total assets1,250
Liabilities
Settlement payables240
Accrued expenses10
Total liabilities250
Net assets1,000

Notes to this illustration

Assets of 1,250 less liabilities of 250 equal net assets of 1,000. Cash of 300 agrees with the cash reconciliation, and net assets agree with the performance summary.

Illustrative asset composition: cash 24%, investments 72%, receivables 4%. No valuation basis, accounting-policy compliance or per-share net asset value is asserted.

Example Fund A · Fictional dataReconStandard / BALANCE

No real fund or portfolio data. ReconStandard is in development; these examples do not demonstrate product performance. Final deliverables require an approved report specification and validation against actual product output.

Explore the separate operations oversight snapshot ↗