Wealth & investments
Advisory, trading and reporting platforms wired into custody and post-trade
We build platforms for advisers and portfolio managers, with model portfolios, drift monitoring and proposals generated from held positions. Orders route through a layer that records execution evidence per fill. Custody feeds, reconciliation and performance reporting run on one position store instead of four exports.
Where it fits
The problem
Advisers rebuild the same proposal in a spreadsheet because the platform cannot model a household. Orders reach the desk by email, and best execution evidence is whoever remembers the call. Reconciliation breaks against the custodian sit in a shared inbox, and quarterly statements get assembled by hand the week they are due.
What we build
We build a position store fed by custodian and fund data, an advisory workspace with model portfolios and suitability checks, and an order layer that stamps timing, venue and price on each execution. Reporting draws returns and fees from the same positions the adviser saw.
How we engage
Senior engineers work with your investment, operations and compliance staff inside your cloud and your repositories. Reconciliation rules and reporting definitions get written down with the people who currently hold them in their heads. Operations runs the platform after handover, with runbooks and data lineage documented.
What we build
Six pieces of work that show up across wealth and investment platforms.
Advisory and proposal workspace
Households, mandates and goals sit in one model, so a proposal starts from held positions and shows the trades needed to reach the target allocation. Advisers stop rebuilding the same spreadsheet per client, and a signed proposal stays retrievable with the assumptions it used.
Order management and routing
Orders are captured with mandate and cash checks applied before release, then routed with venue, timestamp and price recorded per fill. Best execution reporting under MiFID II comes out of that record. Desks stop reconstructing intent from email threads when a client questions a price.
Suitability and pre-trade checks
Client risk profile, product knowledge and mandate limits are evaluated before an order leaves, with the result stored against the trade. MiFID II suitability assessments reference the profile version in force at the time. Advisers get a blocked-order reason they can read rather than a silent rejection.
Rebalancing and drift
Portfolios are compared against their model on a schedule and on cash events, with tolerance bands per asset class and tax or fee awareness in the trade proposal. Bulk rebalances generate orders in one pass, which retires the quarterly ritual of editing tickets one client at a time.
Custody and post-trade
Custodian and clearing files are normalized into positions and cash, with breaks classified, aged and assigned rather than parked in an inbox. T+1 settlement leaves less room for a manual fix, so affirmation and allocation run on trade date with exceptions surfaced the same afternoon.
Performance and client reporting
Returns are computed from the position store with time-weighted and money-weighted figures, fees and benchmarks attached, and a report pack generated per household. Statements stop being assembled by hand in the week they are due, and the numbers on a client PDF trace to the positions behind them.
One position store behind advice, trading and reporting
When the adviser, the desk, the operations team and the client statement read the same positions, the quarter-end scramble mostly goes away.
How we work
Discover
Systems, constraints, and the regulation you operate under get mapped before implementation starts, so the design accounts for what already runs and for what examiners will ask about.
Architect
A design that fits your stack. Integration-first, self-hostable, and built to change as rules, regulation, and volume do.
Build
Senior engineers ship in tight increments, each tested and reviewed as it goes, so the system is reviewable at every step instead of only at the end.
Harden
Security, compliance, and load-testing run inside the build, so controls, audit trails, and peak-volume behavior are proven before launch.
Run
The handover includes clean, documented systems, with the option to keep the same engineers operating them once they are live.
Why Oxagile
One store for positions
Advice, trading, reconciliation and reporting read the same positions and cash, with lineage back to the custodian file. Platforms that keep four copies spend their operations budget explaining which copy is right, usually at quarter end when the client is already waiting.
Post-trade under T+1
Affirmation, allocation and break handling are designed for trade-date work, with exceptions routed to a named owner and an age on the clock. Overnight batch reconciliation that reports a break the next morning leaves too little time to fix it before settlement.
Compliance evidence as data
Suitability results, execution records and fee calculations are stored as structured records with the version of the policy applied. Answering a MiFID II question then becomes a query rather than a project, and the same records feed client reporting without a second pipeline.
Questions
Can you integrate with our custodian and clearing broker?
Usually yes, through the files and APIs they publish. The work sits in normalizing positions, transactions and cash into one model, then building reconciliation that classifies breaks by cause instead of dumping a difference report. Where a custodian offers only overnight files, we design the trade-date workflow around that limit and say so up front.
How do you handle MiFID II suitability and best execution evidence?
Suitability runs as a check before order release, against the client profile version in force, and the outcome is stored with the trade. Execution records keep venue, timestamp, price and the reason a route was chosen. Your compliance team defines the policy and the reports it needs. We build the capture and the queries behind them.
What does T+1 settlement change for our operations team?
Most of the work moves to trade date. Allocation and affirmation cannot wait for a nightly cycle, static data errors surface with less time to correct, and FX funding gets tighter on cross-border flows. We build exception handling that shows breaks during the trading day with an owner attached, and instrument the queue so managers see aging.
Do you build performance reporting or connect an existing vendor?
Both patterns work. If your vendor already computes returns you trust, we feed it clean positions and take the output into the client report pack. If the vendor is the bottleneck, we compute time-weighted and money-weighted returns from the position store and keep the calculation documented for review by your investment team.
Trading and portfolio systems
built for real rails.
Tell us what you need to run: execution, reporting, local and international rails. We'll architect it for the regulators too.