Analytics
Portfolio and exposure indicators alongside client trading boards built from a pre-aggregated daily roll, with full-window presentation and PDF export.
Operations Dashboard · Daily Client Activity · Client Dashboard
The platform
Post-trade credit risk, on one platform.
Analytics and automation across the counterparty lifecycle, from the prospect that needs a deposit sign-off to the client that has sat in deficit for eight business days.
Modules
Adopt what you need. Add the rest when you're ready.
Seven modules that stand alone and compose together, sharing data, permissions, and a single login across your organisation.
Financial Analysis
Counterparty financial statements worked through to the ratios that drive the credit view, from raw statements to credit-ready metrics.
Profitability · Cash Flow · Balance Sheet
Risk Analytics
Gross and net exposure by counterparty, a flagged watchlist, the shortfall cycle against whichever control your policy uses, and the sign-off queue for incoming business.
Watchlist · Exposures · Monitoring · Prospective Clients
Relationship and Sales
The prospect pipeline through risk sign-off to whatever acceptance stage your firm operates, plus the same monitoring tables risk sees, so both desks work the one list.
Prospective Clients · Risk · BAC · Deposit Monitoring
Governance, Risk and Compliance
On the operational risk side: risk registers, risk and control self-assessments, incident reporting and risk appetite tracking. On the governance side: policy management, know your customer and anti-money laundering.
Registers · RCSA · Incidents · Appetite · Policy · KYC · AML
Process Automation
The routine work your staff repeat every day, taken off their plate. Fewer copy-and-paste steps between systems, shaped to the business rather than a fixed template.
Ad hoc automation
Collaborative Workflow Tracking
Work that crosses desks stays visible while it is in progress, rather than surfacing once it has stalled. Shared tracking sits inside the module where the work already lives, so ownership, progress, and what each side is waiting on stay apparent to everyone with a reason to see them.
Board · Calendar · Timeline · Insights · Planner hub
The workflow
From prospect to daily oversight.
One counterparty, followed the whole way: onboarding through risk sign-off and committee, then into the daily cycle that decides who gets chased today.
- 01
Prospect
The relationship manager captures domicile, pipeline stage, account type, estimated trade size and monthly volume, and the bond/equity split. An indicative deposit is computed for omnibus accounts; fully funded accounts carry none.
- 02
Risk sign-off
Omnibus prospects route to Risk automatically, while fully funded ones skip the queue. Approvals and rejections are captured with a comment, and every change to an indicative deposit is written to an append-only log recording who changed it, from what, to what, and why.
- 03
Committee
Approved and fully funded prospects close out to the Business Acceptance Committee, where a note is recorded against each counterparty before it is taken on.
- 04
Client
The prospect becomes a client carrying trading accounts, agreed deposit levels, cash balances, market positions and granular trades, each held as a dated revision rather than overwritten, so any past day stays inspectable.
- 05
Daily monitoring
The roll compares the agreed deposit against opening cash on business days in the client's own jurisdiction, tracks the length of the current deficit spell, and surfaces exactly who is due a chase.
The chase cycle
A client in deficit is chased on the eighth business day of the spell, and every eight business days after that. Funding back above the level ends the spell; a later shortfall starts a new one at day one rather than resuming the old count. Public holidays and weekend days come from a per-jurisdiction calendar, and where no calendar exists, the table says so rather than presenting an unverified streak as fact.
Governance on the record
Disagreements live on the client, not in an inbox.
- Do-not-contact blocks. The relationship manager can block outbound chasing with a mandatory reason, recorded with who set it and when.
- High-risk flags. Risk can flag a blocked client to ask that the block be lifted, so the disagreement is visible on the record.
- Append-only contact log. Every chase, block, unblock, and flag is written with the deficit and streak as they stood at the time.
Deficit spellbusiness days
Next chase dueday 8
Contact blockedwith reason
Contact logappend-only
Analytics
Your own trading data, read every day.
Two client boards built on a pre-aggregated daily roll, scoped to an account group, drillable to a single account, and denominated in that group's own preferred currency.
Daily Client Activity
The "today" view. Opening cash, opening position, and excess or deficit for the chosen date, each measured against the previous business day. Below them, a twenty-two working-day trend, gross trading by day, and the largest ten trades over the same window.
A trailing-twelve-month block compares deposit in use, settlement efficiency, average monthly trade volume, largest trade size, and average monthly trade count against the prior quarter.
Client Dashboard
Trading over a chosen month, quarter, year, or custom range, always measured against a comparison period. Daily trade volume carries a least-squares trend line; volume is broken out by security type, with a bond and equity mix alongside.
Headline figures, being deposit in use, settlement efficiency and total trade volume, each pair with a bucketed mini-chart, so the number and its shape are read together.
Across every board
Focus any chart or metric full-screenFull-window presentation mode16:9 single-page PDF exportLive and demo data sourcesAccount-group and per-account scopingMixed-currency detectionBusiness-day accurate periodsDark and light themes
Work management
Collaborative tracking, wherever the work happens.
Shared boards that can be dropped into any module as an extra tab, with the minimum role and the access level set by an administrator and enforced in the database, not just in the interface.
- Four views on one board. Board with drag-and-drop columns, work-in-progress caps, and card aging; calendar; timeline; and insights.
- Flow metrics that reconstruct. Cumulative flow, burndown, card aging, lead and cycle time, replayed from an append-only event log.
- Read-only means read-only. Writes are refused at the database, however they are attempted.
Board · Calendar · Timelineviews
Insightsflow metrics
Injected into a moduleby role
Prospect → plannerone click
Process automation
Before reaching for AI, Infer looks at the everyday work your staff repeat each day and takes the routine, manual parts off their plate. There is no one-size-fits-all setup. What gets automated depends entirely on the business, its systems, and where the day-to-day bottlenecks actually are.
Enterprise controls
Governed access, by design.
Every record is scoped to a tenant, and every grant is applied in the security rules, so bypassing the interface does not bypass the permission.
Three layers of access
A company entitlement sets the ceiling; role and department grants accumulate beneath it. Access reaches individual tabs within a module, not just the module itself.
Ranked roles
Creator, owner, admin, manager, general, and guest, ordered by rank, with the roles each may edit configurable, and view and edit rights held separately.
Change tracking with rollback
Every edit to a user, role, company, or department is logged with who, when, which field, and from what to what. Individual fields can be rolled back, and the rollback is logged in turn.
Client data ingestion
A JSON upload is previewed as a dry-run plan: clients, accounts, deposits, dated records and trades, with duplicates and dropped rows counted before anything is written.
Business calendars
Weekend days and public holidays maintained per jurisdiction, because not every market breaks on Saturday and Sunday, and a streak is only as honest as its calendar.
Tenant mail routing
Sender name, address, reply-to, standing cc, and signature configured per company. Messages are resolved and queued with a delivery state against the client they concern.
One administration console
Companies, users, roles, departments, module entitlement, custom collections, planner injection, business calendars, client data, mail routing, and inbound feature requests are all managed from a single place, with custom collections letting you define your own schema and capture records against it without waiting for a release.
See the platform against your own workflow.
We'll walk through the modules that matter to your desk and how a bespoke deployment would fit.