Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
ReconFlow
Transaction and ledger reconciliation workbench
Reconciliation workbench that ingests statements and ledgers, auto-matches transactions, and routes breaks to investigators with AI-suggested causes.
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v2
Problem
Finance operations teams reconcile high volumes across files and spreadsheets; breaks age without ownership and root causes repeat.
Outcome
Most items match automatically, breaks are owned and aged transparently, and recurring causes are visible.
Who uses it
- Finance Analyst
- Operations Analyst
- COO
Key capabilities
File and ledger ingestion
IncludedIngest statements, ledgers and payment files in standard formats.
Domain:
ingestionRule-based matching
IncludedConfigurable one-to-one, one-to-many and tolerance matching.
Domain:
matchingBreak investigation queue
IncludedAssign, investigate and resolve breaks with SLAs.
Domain:
breaksAI root-cause suggestions
AI-assistedIncludedSuggest likely causes from similar historical breaks.
Resolution approval
ConfigurableFour-eyes approval before adjustments post.
Typical workflow
Daily reconciliation run
Trigger: New statement and ledger files arrive
Automated
Stage 1: Ingest files
System
Automated
Stage 2: Auto-match transactions
System
AI-assisted
Stage 3: Classify unmatched breaks
System
Task
Stage 4: Investigate break
Investigator
Human checkpoint
Stage 5: Approve resolution
Supervisor
Automated
Stage 6: Post adjustment
System
Task Automated AI-assisted Human checkpoint Decision
About this foundation
ReconFlow ingests bank statements, ledgers and payment files, applies configurable matching rules, and routes unmatched items to an investigation queue. Investigators see AI-suggested root causes and similar historical breaks, and resolutions post back with approval.
Operations leads see ageing, volumes and break categories in real time.
Related applications
- Stablecoin Settlement
Stablecoin payments, settlement and reconciliation
- • Addresses the same problem: Reconciliation Burden, Manual Workflow
- • Shared capabilities: Reconciliation, Approval Workflow
- GridCrew
Field-service operations for utilities
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Workflow Automation, Reporting
- Regula Evidence
Regulatory evidence collection and control attestation
- • Addresses the same problem: Manual Workflow
- • Shared capabilities: Workflow Automation, Reporting, Approval Workflow
- Mashroo
Government portfolio and program delivery management
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Reporting
- CarePath
Referral and care-coordination workflow
- • Addresses the same problem: Manual Workflow, Poor Visibility
- • Shared capabilities: Workflow Automation
- SOC Pilot
Security operations alert triage and investigation
- • Addresses the same problem: Manual Workflow
- • Shared capabilities: Anomaly Detection, Workflow Automation
Daily reconciliation run
Trigger: New statement and ledger files arrive
Automated
Stage 1: Ingest files
System
Automated
Stage 2: Auto-match transactions
System
AI-assisted
Stage 3: Classify unmatched breaks
System
Task
Stage 4: Investigate break
Investigator
Human checkpoint
Stage 5: Approve resolution
Supervisor
Automated
Stage 6: Post adjustment
System
Actors
Operations analyst, Investigator, Supervisor
Outputs
- Matched set
- Resolved breaks
- Ageing report
Evidence generated
- Resolution approvals
Exceptions
- File arrives late or malformed
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
File and ledger ingestion
IncludedIngest statements, ledgers and payment files in standard formats.
Domain:
ingestionRule-based matching
IncludedConfigurable one-to-one, one-to-many and tolerance matching.
Domain:
matchingBreak investigation queue
IncludedAssign, investigate and resolve breaks with SLAs.
Domain:
breaksAI root-cause suggestions
AI-assistedIncludedSuggest likely causes from similar historical breaks.
Resolution approval
ConfigurableFour-eyes approval before adjustments post.
ISO 20022 message ingestion
ExtensionNative camt.053 / pain message parsing.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 7
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- 7 bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- sources
- ingestion
- matching
- breaks
- resolutions
- reports
- identity
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
ERP
| Integration | Status | Direction | Method |
|---|---|---|---|
| Core banking / ERP ledgers | Standard API Pattern | bidirectional | Files / REST |
Payments
| Integration | Status | Direction | Method |
|---|---|---|---|
| SWIFT / ISO 20022 statements | Customer-Specific | bidirectional | MT940 / camt.053 |
Identity
| Integration | Status | Direction | Method |
|---|---|---|---|
| Microsoft Entra ID | Reference Adapter | bidirectional | OIDC |
Deployment
- Deployment models
- Customer Cloud, Customer VPC/VNet
- Cloud profiles
- AWS Profile, Azure Profile
- Containerized
- Yes
- Regions
- GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Yes
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
Deployment-Ready Foundation
Application has passed the defined fazeZERO scaffold, build and testing baseline.
Customer-specific integration, security, configuration, hardening and acceptance remain part of implementation.
Issued 23 Sept 2026
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 2
- Last published
- 23 Sept 2026