Illustrative demonstration · Synthetic dataOrganisations, transactions, documents, figures and outcomes shown here are fictional or modelled for demonstration purposes. No client, bank or confidential data is used. Results are illustrative, not actual client outcomes or professional advice.
AQAssetQuant ← Back to AssetQuant
Technology & data enablement · Interactive demo

One chain. Fifty funds. Zero re-keying.

A quarter-end reporting pipeline for a 50-fund real-estate manager. Instead of 50 hand-built branches, the chain fans out by data domain, validates every figure against rules, and stops at a human gate before anything is published. Press Execute to run it.

Idle · last run Q2 2026 completed in 11m 40s
WaitingRunningCompleteExceptions routedHuman gate

Run log

What the chain is doing, as it does it

Waiting for execution…

What each stage does

Same four stages in every lane; that is what makes 50 funds maintainable

QueryRuns the domain's master query against the source system for all funds in scope: one parameterised query, not one per fund.
ExtractPulls the result set and maps it to the reporting schema: fund, period, line item, value, source reference.
ValidateApplies the rule set: completeness, period roll-forward, cross-domain ties, tolerance bands. Failures become exceptions, never silent overwrites.
LoadWrites validated values into the reporting workbook cells they belong to, with the source reference attached to every figure.

Run history

QuarterFundsValidationsExceptionsRuntimeManual edits
Q2 202650142211m 40s0
Q1 202650142412m 05s0
Q4 205048136713m 20s1
Q3 2025 before automation48n/an/a~9 working days~2,100
Fan out by domain, not by fund

Four lanes carry 50 funds because the fund is a parameter, not a branch. Adding fund 51 is a register row, not a new pipeline.

Validate before load, always

Every figure passes the rule set before it touches the workbook. Exceptions are routed to people with context attached, not overwritten and not ignored.

A human gate before publication

The chain prepares; a named reviewer approves. Automation removes the re-keying, not the accountability.