New: Q Bridge connects your own AI agents to TraiQ. Meet Q Bridge →
AI transformation programme

TraiQ Pathway.An AI colleague that knows your company.

Most finance functions already pay for an AI subscription. Very few have an AI they'd trust with a liquidity question. TraiQ Pathway closes that gap in seven stages: we build Orbis — your company's knowledge and systems, organised and connected for AI — inside your own environment, put the controls around it, and hand it to your team to run.

Read into Orbis Draft Your environment
Not limited to treasury

One brain across every function your treasury depends on — and beyond it.

Pathway starts in treasury, where the questions cross the most desk boundaries. Orbis is mapped to wherever the information actually lives — a system, or a folder a team keeps by hand — so legal, accounting, tax, risk, compliance and operations join on the same structure.

Source mapped into Orbis Draft for the board Team-kept folder
FROM SYSTEMS

Wherever the record is kept.

  • ERP & general ledger
  • TMS / TRM
  • Accounting subledgers
  • Contract repository
  • Bank portals
  • Market data
FROM TEAM-KEPT FOLDERS

Wherever the know-how is kept.

  • SharePoint & Teams folders
  • Policy library
  • Process notes
  • Owned spreadsheets
  • Decision logs

Orbis is mapped to the sources you already have and runs on them where they sit. Nothing is moved to us.

Orbis · the enterprise brain

Orbis doesn't add another system. It organises the one you already have.

We collect, declutter and organise what your teams know, and optimise it for AI — inside your own SharePoint or Teams. Every folder has a named owner and a review date, so it stays current after we leave.

Organised for AI Orbis, in your tools Today
WHAT GOES IN

Everything a new joiner would need to learn — written once, kept current.

Orbis is what turns a general AI into your company's AI. Each folder has a named owner on your side and a review date, so it stays current after we hand over.

  • Group structure — entities, ownership, and which sit inside the reporting group
  • Facilities — lenders, limits, margins, maturities and drawdown terms
  • Policies — treasury, hedging, counterparty, investment, liquidity and FX
  • Delegations of authority, risk appetite, limits and escalation paths
  • Procedures — month-end, cash positioning, the hedging cycle, payment approval, bank onboarding
  • The treasury calendar, bank and counterparty relationships, and a map of your systems
  • A decision log of what treasury decided and why — and a glossary of your own terms
  • A folder taxonomy and naming standard — entity, process, period, version
  • A context file per process — steps, sources, checks and owner
  • Beyond treasury, on the same structure — legal's contracts and ISDAs, accounting's close calendar and chart of accounts
The problem

Six problems every treasurer will recognise — and how we fix each one.

None of them shows up on a dashboard. All of them show up eventually — as an audit finding, a missed deadline or a resignation letter.

Key-person risk

If two people left tomorrow, treasury would stall.

"Don't touch that tab — only she knows how it works."

How the function really runs — the procedures, the workarounds, why past decisions were made — was never written down.

The costMonths to rebuild what walked out the door.
The fixStage 3 · OrbisOrbis writes the function down: procedures, roles, delegations and a log of past decisions. Each folder gets a named owner, so it stays current.
Spreadsheet risk

Board-level numbers come out of a fragile workbook.

"Which version is the final one?"

Cash forecasts, exposure calculations and hedge tracking live in linked spreadsheets that nobody can fully audit.

The costOne broken formula from a wrong board number — and an audit finding.
The fixStage 4 · NumbersCore figures move to a controlled engine — your TMS, a hardened model or Q. AI reads and explains the numbers; it never recomputes them. Every figure can be traced to source.
Fragmented data

Every answer means visiting five systems.

"Let me pull it from the TMS, the ERP and the bank portals and come back to you."

The TMS, the ledger, the bank portals, the contract drive and the policy library each hold one piece. Nothing joins them up.

The costHours per question — and an answer that's stale when it lands.
The fixStage 3 · OrbisOrbis connects read-only to your ERP, TMS, contract repository and bank portals — and to the folders your teams keep. One question gets one answer, with the sources attached.
Slow recurring work

The same packs are rebuilt from scratch every cycle.

"Board pack's due Thursday — clear the week."

Board papers, bank-meeting briefs, daily cash reports and month-end commentary are assembled by hand from the same sources, again.

The costYour most senior people assembling, not analysing.
The fixStage 5 · WorkflowsThe agent drafts board pack sections, month-end commentary and bank-meeting briefs into your output folders. Your team reviews and signs off instead of building from scratch.
Manual compliance

Policy breaches are caught by eye — or not at all.

"I think that's within delegation. Let me find the policy."

Limits, delegations of authority and hedging-policy adherence are checked by someone reading the document, when they have time.

The costA breach found by the auditor, not by treasury.
The fixStage 6 · GovernYour policies, limits and delegations sit in Orbis, so the agent checks a proposed deal against them before it goes ahead and flags limits running short.
Stalled AI

The AI pilot gives generic answers nobody trusts.

"It doesn't know our facilities, so we stopped using it."

A general-purpose AI tool has no knowledge of your company and no controls around it — so it can't be relied on for treasury work.

The costSpend with no return, and a team sceptical of the next attempt.
The fixStages 1 · 3 · 6Your AI, given your company: Orbis supplies the context, training builds the habit and governance supplies the trust — access controls, a full audit trail and an AI SOP for each use case.

The fix isn't another tool. It's giving AI the company context, the system access and the guardrails a treasurer would insist on.

The programme

Seven stages. Knowledge and controls first.

AI workflows switch on once the knowledge is organised and the numbers are trusted. Training and governance run through the whole programme — never bolted on at the end.

Training · runs throughout Governance · runs throughout
  1. 1
    Runs throughout

    AI education and team training

    The team can use AI well, check it properly and own the result.

    • Role-based training on your own tools
    • Reviewer checklists and quick guides
    • Named AI champions
    • Leadership sessions that set the red lines
  2. 2
    Start here

    Discover the function

    Map what the function actually does before any tool is chosen.

    • Map of key recurring outputs
    • Spreadsheet register, with a treatment per file
    • Key-person risk register
    • Baseline of where the time goes
  3. 3
    Orbis

    Build Orbis, the enterprise brain

    Knowledge moves out of heads and inboxes into one owned structure, mapped to your systems and team folders.

    • Folder taxonomy and naming standard
    • A context file per process
    • Policy and facility library
    • Read-only connectors, within existing permissions
  4. 4
    The numbers

    Put the arithmetic under control

    Core figures come from one controlled, reconciled, auditable source.

    • Riskiest engines under control — your TMS, a hardened model or Q
    • One position dataset
    • Reconciliation and audit trail
    • Plumbing spreadsheets retired
  5. 5
    Workflows

    Switch on the first workflows

    AI drafts and analyses; people review, decide and send.Examples — the first workflows are confirmed at discovery.

    • Daily cash position commentary
    • Forecast variance analysis
    • Covenant and limit early warning
    • Board pack first draft
  6. 6
    Runs throughout

    Govern it like any other control

    Every AI output owned, reviewed, traceable and defensible to audit.

    • AI-use policy: what AI may draft, and may never do
    • An AI SOP per use case
    • Audit evidence pack
    • AI vendor chosen with your IT and risk teams
  7. 7
    Handover

    Hand it over

    You run, maintain and extend it — without us.

    • Runbooks for live workflows
    • Orbis owner's guide
    • System owner's guide
    • New-joiner starter pack
The rule

AI never does the treasury arithmetic. It reads the controlled numbers and explains them.

What we build

Four layers. Orbis is the first two.

Every engagement delivers the same four layers, sized to your function. Orbis is layers one and two — the knowledge and the connections everything else rests on.

Read from systems and folders Delivered to your team
When we leave

You run it, change it and teach it.

Handover is a stage of the programme, not an afterthought. Your team is taught as it's built, so your knowledge holders become Orbis owners and the build stops depending on us.

RUNBOOKS

A runbook for every live workflow

What it does, what it reads, who reviews it and how to change it.

ORBIS

An Orbis owner's guide

Who owns each folder, and the routine that keeps it current.

SYSTEMS

A system owner's guide

Your systems lead and IT run the connectors, access and the AI account.

PEOPLE

A new-joiner starter pack

How the function works with AI, from day one.

Feature · Q Risk Management Platform

Plug in Q, and Orbis gets a treasury risk engine.

Orbis calls Q's treasury calculations through Q Bridge — liquidity, exposures, rate and FX shocks — read-only, with every figure stamped with its source. Pathway runs with or without it.

Meet Q Bridge →

Start with half a day.

One workshop with your treasury team: where AI earns its place, what it would take, and what you'd have at the end of each stage.