How to Automate Trovata

The cash position is the first number of the day

Every morning a treasury team answers one question before anyone else in the company thinks to ask it: how much money do we have, where is it sitting, and in what currency. Trovata is the platform built to answer that.

For a business with one bank account it is not a question. For a company with fourteen accounts across six banks and four entities, it is a genuine morning's work, and the answer moves by lunchtime.

The people using it are treasury and finance teams, and the position they produce is not a report anybody files. It is the input to decisions being taken that day. Whether to sweep cash out of a subsidiary. Whether the payment run clears. Whether the revolver gets drawn this week or next. Whether the hedge is still the right size.

Being a day out of date is not a small error here, because somebody will act on it before it is corrected.

Treasury still opens bank portals one at a time

The traditional version of this is one person with eleven browser tabs.

Log into each bank, copy yesterday's closing balances, paste them into a workbook, convert the foreign ones at today's rate, sum by entity, sanity-check anything that looks wrong, and send the position out by nine. Then do it again tomorrow.

Around that sits everything the workbook does not cover. The bank fee that looks higher than last month, verified by going and finding last month's statement. The covenant ratio recalculated by hand from a definition written into a credit agreement PDF. The signatory list on each bank's portal, which nobody has reviewed since two of those signatories left. The intercompany funding request that came in by email and has not settled.

It is careful, repetitive work, done early, under time pressure, by the people you would least like to lose.

Trovata

A position with the exceptions attached Balances by entity and currency, with anything below its minimum or above target already named.

The banks no feed reaches The subsidiary account with a portal and no API, read the way its own accountant reads it.

Covenants watched, not recalculated Liquidity ratios measured against the levels the loan agreement actually sets, so a covenant is seen closing in rather than reported as broken.

Trovata normalises whatever the banks send it

The platform exists precisely because that work is beneath the people doing it, and it removes much of it.

Bank APIs connect directly to the banks and pull balances and transactions in, with the MultiBank Connector handling global connectivity rather than a fresh integration project per institution. What arrives is normalised into one shape, so an account at one bank and an account at another sit in the same report. Transactions are automatically classified and tagged, payroll as payroll and customer inflows as customer inflows, with machine learning suggesting tags from the patterns already in your data. Cash reports refresh on their own, real-time and prior-day, and forecasting runs short and long term with scenario modelling for a timing shift or a rate change.

That is a real answer to the eleven-tabs problem, for every bank that offers a connection.

The ceiling is everything that never arrives through a bank feed. The small overseas subsidiary whose bank has a portal and nothing else. The covenant definition in the credit agreement. The signatory register. The fee schedule you negotiated. The payment run sitting in the ERP. None of it is bank data, and all of it changes what the position means.

The morning position can arrive with the exceptions named

Read every source involved on a schedule and the position stops being a number and starts being a briefing.

Balances consolidated by entity and currency before the day starts, with any account below its target minimum already flagged, so an overdraft is prevented rather than explained. Balances above target listed as sweep candidates with the excess calculated, ready for somebody to act on.

The small subsidiary bank with a portal and no API read the way its own accountant reads it, so its balance is in the consolidated picture instead of a footnote saying data unavailable.

Bank fees compared against the pricing you actually agreed, with anything unusual, or anything on an account that rarely incurs charges, raised the same week. Covenant ratios calculated from the liquidity figures and checked against the thresholds in the agreement, flagged while they are approaching rather than after they are breached.

Last week's forecast compared with what actually moved, variance by entity and category, so the model improves instead of drifting quietly. The signatory list on each bank portal cross-checked against your current staff roster, because a leaver who is still an authorised signer is a finding somebody will make eventually.

The sweep, the hedge and the wire still wait for a person

Eleven bank portals, a credit agreement and a fee schedule all have to be read before any of that briefing exists. That is the part treasury does not enjoy and cannot skip.

WebRun is an agent that works a real Chrome browser, signed in as you. It opens Trovata, each bank's own portal and the workbook beside them, reads what each says, and puts the position and the exceptions in front of you.

It runs on your schedule in your own private environment, and you can watch a run and stop it. It does not release a payment, move cash between accounts, draw on a facility or place a trade. It prepares the pack. The instruction stays yours.

The workflows below are already built, and each one names what it opens.