Product / ReconFlow

Close the books from one wallet operating record.

ReconFlow gives finance teams ledger matching, fee attribution, exception queues, and audit packages across providers.

Finance proof: Provider webhooks, wallet state, transaction intent, and fee data become close-ready evidence.
Product console

Finance should not rebuild provider history every month.

ReconFlow is designed around exception resolution, ledger exports, and evidence packages rather than raw provider CSV stitching.

Operating boundary

Close inputsProvider eventsBalancesFeesLedger
ReconFlow workspaceMatchExceptionsOwnershipExports
Review teamsFinanceOperationsComplianceAudit
OutputsClose packageOpen itemsSource links
Outputs

Every exception has a next action.

Match

Balances and transactions line up across systems.

Investigate

Open items are grouped by reason and owner.

Export

Audit and accounting outputs are packaged from the same record.

Explain

Source links, provider IDs, and review notes stay attached to each close item.

Exception lifecycle

Close work needs states finance can trust.

Collected

Provider, chain, ledger, and business-reference records are present.

Matched

Balances, fees, confirmations, and internal ledger state agree.

Open exception

An owner reviews the reason-coded variance before close.

Closed with evidence

Resolved state and supporting source records are packaged for review.

Evidence

Proof the buyer can inspect.

Every route keeps Alloy's public story grounded in operating records, custody boundaries, and right-sized modules.

Ledger-ready recordsTransaction state and fees remain tied to business references.
Exception ownershipOpen items have reason codes and review state.
Monthly close proofExports are designed for finance and audit users.
Provider-neutral closeFinance can keep one close workflow as the provider mix changes.
Next step

Bring your current provider stack.

We will map the first workflow Alloy should stabilize, the custody boundary, and the modules that create evidence.