FenRecon

What FenRecon reconciles

Buy-side firms routinely hold the “same” positions, cash, transactions, or valuations in more than one place: the investment book of record, the accounting book of record, the fund administrator, the custodian, an internal warehouse, or a vendor-enriched file. Those copies drift. FenRecon is the engine that makes drift visible and workable.

It is aimed at middle- and back-office users as well as data teams. The published product position is that non-technical users can set up reconciliation checks and see results quickly, using the same no-code style as the rest of the Fencore suite: connectors to bring the two (or more) sides in, rules to define a match, thresholds in nominal or percentage terms, and an exception list for everything that failed.

• IBOR versus ABOR and related books of record
• Internal records versus fund administrator files
• Internal records versus custodian positions and cash
• Operational store versus data warehouse or downstream reporting extracts
• Other pairwise or multi-source comparisons the firm defines

Reconciliation is not mastering

DataHub’s mastering process builds a golden record: several sources describe the same instrument or entity, matching decides they are the same thing, and source priority decides which field values win. That is a constructive process. FenRecon is a comparative process. Both sides remain systems of record for their own purpose; the output is the break list, not a merged row that replaces either side.

Conflating the two is how recon projects accidentally become “shadow mastering” and how mastering projects accidentally become un-owned break lists. Fencore keeps them as separate products and separate workflows so ownership stays clear: data management owns the golden store; operations owns the breaks between books.

How teams run it

1. Onboard each side through universal connectors (files, APIs, databases, and related channels).
2. Define matching keys and comparison rules in the no-code interface, including multi-step logic where needed.
3. Set nominal or percentage thresholds so economically trivial differences do not flood the queue.
4. Run on a schedule or after upstream pipelines complete.
5. Work exceptions with traceability back to the contributing values.
6. Optionally raise alerts and route them through the same assignment and approval patterns used elsewhere in DataHub.

Published capabilities include a proprietary reconciliation engine, assisted matching where it helps the operator, configurable thresholds, and intelligent exception management. The operational goal is less time spent hunting for the row that does not tie, and more time spent deciding what to do about a real break.

FenRecon uses the same underlying cloud architecture as DataHub, so volume and additional sources are a scaling problem rather than a new product implementation. Interoperability is the same story as FenDQ: it can sit beside current pipelines without requiring those pipelines to be rewritten first.

Inside DataHub or standalone

FenRecon ships with Fencore DataHub. It is also offered with a standalone licence because many firms have a recon gap before they are ready for a full operational data store. Governance features — granular access control, four-eye approval, lineage, and audit trail — apply in both packaging models.

When FenRecon runs inside DataHub, breaks sit next to quality alerts, mastering, and FenWarehouse updates as part of one operating loop. The DataHub overview at /products/datahub/full describes that loop. FenDQ at /products/fendq/full is the quality layer; use both when you need “is this file good?” and “does this book still tie?” as separate questions.

Cori

Cori is Fencore’s in-product assistant in DataHub. In a DataHub workspace that includes FenRecon, users can ask Cori about documentation, configuration, metadata, data, and alerts — including recon-driven exceptions — and can build pipelines from natural language. Cori assists; it does not close breaks on its own or skip approval. See /products/datahub/full.

Where it sits in the suite