Trusted by teams at
Platform & certifications
SAP Co-Innovation Partner
Listed on the SAP Store
ISO 27001
SOC 1 Type II
of the live SAP treasury job ads describe extensive manual data plumbing into SAP.
Trusted by teams at
Platform & certifications
It is all OnePilot, Brisken's governed, no-code platform. TreasuryCentral is the treasury workspace inside it: the apps, your counterparties and your enterprise systems, on one governed layer. Click the workspace, an app, or the platform to open it.
Most SAP finance teams run several brittle, hand-built feeds to move market data, trades, bank files and remittances in and out of SAP. They break when a field changes or the person who built them leaves: no audit trail, no owner, no monitoring. TreasuryCentral takes them off your team.
The cockpitCash, investments, debt, FX, market risk management and governance on one screen, on your SAP data. It is OnePilot scoped to the treasurer; the apps run on OnePilot, which moves the data in and out of SAP, governed end to end.
Your workstation lives in it too: Mail, Teams, Calendar and Documents, on the same surface.
Cash positions roll up from every bank account and entity, reconciled to the statements already in SAP, so the group number is current instead of a Monday spreadsheet pull.
Investments, debt and intercompany loans sit on the same screen with their maturities and interest, and every figure links back to the SAP record it came from.
Spot and forward rates, yield curves and prices arrive from Bloomberg, Refinitiv, 360T and central-bank feeds, normalized once and checked for gaps and outliers before anything posts.
FX exposure by currency and entity updates as positions move, with the source and the validation recorded against each value, so a hedge decision rests on numbers you can trace.
Every value carries where it came from, who approved it and when, so an audit follows the trail without a reconstruction project.
Limits and tolerances are set once; only the records that breach them surface for a person, and a second approver signs off before a payment or a deal is released.
Each app is a job you can buy on its own; run them together and you get TreasuryCentral. All run on OnePilot, which moves the data in and out of SAP, governed end to end.
Govern rates, curves and prices from every provider into SAP from one place, no code. Ingested once, normalized, distributed into SAP TRM with an audit trail and exception alerts.
Bloomberg · Refinitiv · 360T · OANDA · CME · Deutsche Boerse
Straight-through capture from execution venue to SAP deal creation, no re-keying. Trades flow into Treasury and Risk Management as governed deals, reconciled to source.
AI reads messy remittance advice in any format, a direct link, a PDF, a CSV or an email, and posts it into SAP S/4HANA. Live today on a governed AI gate at an agricultural-sector customer.
On the same platform: Cash Flow and Exposure Hub, Bank Fee Portal, Credit Data Hub, ESG Data Hub, plus the AI Digital Workforce, and the use cases your own team builds. See the full platform →
Treasury connects to banks, markets and public bodies every day. OnePilot brings each of those feeds onto one governed layer inside the workspace: visible, accessible and reconciled, with the source and the check recorded on every value.
Banks · Central banks · Trading venues · Data providers · Exchanges · Custodians · Clearing houses · Payment networks · Credit and rating agencies · Government offices · Authorities
The systems and data it all sits on. OnePilot moves data in and out of SAP, both ways, with a full audit trail on every record, no ABAP and no custom interface for your team to own.
Market data, curves, trades and positions land in Treasury and Risk Management, governed end to end.
Bank files, remittances and exposures post into Cash and Credit Management, reconciled to source.
SAP and non-SAP sources on a clean core: nothing custom added to SAP, so nothing breaks on the next upgrade.
SAP ends mainstream maintenance for ECC in 2027, with extended maintenance to 2030. Migration is when the custom interfaces feeding market data, curves and bank files into the old system become legacy code the team has to rebuild, or replace with a product.
Buy instead of rebuild. Move the feed onto a managed hub once, at the exact moment it is on the table.
Clean core. No new custom code in SAP, so nothing breaks on the next upgrade.
Lower migration risk. Governed, monitored data from day one, instead of a script no one wants to own.
| Approach | Maintenance | Providers | Governance |
|---|---|---|---|
| Custom Datafeed config | ABAP upkeep, breaks on field changes | One at a time | Build it yourself |
| Single-vendor interface | Tied to that vendor | That vendor only | Limited |
| OnePilot | No code, third-party-managed | Multi-vendor, swap freely | Audit trail and exceptions built in |
We show OnePilot running live on Brisken's own SAP environment, not slideware. Connecting it to your SAP takes a few weeks, so the demo proves it on ours first: fifteen to twenty minutes, no preparation needed.
Book a demoSAP Co-Innovation Partner · ISO 27001 · SOC 1 Type II
Our credentials are real: SAP Co-Innovation Partner and PartnerEdge member, part of SAP Industry Cloud for Financial Services and Commodities, listed on the SAP Store, ISO 27001 and SOC 1 Type II, with data partners including Bloomberg, Refinitiv, CME Group, 360T, Deutsche Boerse and OANDA. A financial-services group on S/4HANA Public Cloud already governs several data domains from one OnePilot deployment.
The SAP-native path is a Datafeed RFC connection with per-provider function lists and translation tables, or a per-security custom interface, both of which need ABAP upkeep and break when Bloomberg changes a field. A governed market-data hub ingests Bloomberg once, normalizes it, and distributes into SAP TRM with an audit trail and exception alerts, no code.
CAMT.086 is the ISO 20022 bank-fee-statement format that replaces TWIST BSB. SAP added native bank-fee analysis in S/4HANA 1809 via a Fiori app, but it expects clean CAMT.086 in; banks still send proprietary and TWIST formats. A bank-fee portal ingests any format, enriches for analytics, and distributes to the analyzer, so the fee review is not gated on format.
Yes. Remittance advice arrives as unstructured email and PDF, which staff retype into SAP cash application. An AI-powered remittance gate reads the unstructured input, identifies and structures the data, and delivers it into SAP S/4HANA, with a monitor that trains it over time. A live agricultural-sector customer runs this on a ChatGPT-powered deployment.
Yes. OnePilot is configured, not coded, and runs as a managed product on top of your SAP landscape, so there is no ABAP build and nothing new for your IT team to own or maintain. A new feed or agent is set up on the product and goes live in weeks, which keeps the work off the IT backlog and the cost off the development budget.
It is safe when the AI runs inside your controls rather than around them. Each OnePilot process works to rules you set and approve, with four-eye release, segregation of duties and a full audit trail on every record. You keep command of policy and exceptions; the AI handles the repetitive steps, and nothing moves outside the rules you define.
Yes. A forecast is only as good as the data feeding it, and most of the delay is in collecting and cleaning cash, bank and exposure data by hand. OnePilot keeps that data current and governed in SAP, so the forecast runs on a clean, reconciled base. Treasury still owns the assumptions and the call; the AI removes the manual data work that slows the forecast down.
Yes. The repetitive work, ingesting feeds, validating, posting and reconciling, runs underneath by exception, so the team sees what needs a decision instead of working through every record. Their day shifts from re-keying and chasing data to judgment, review and the exceptions that actually need a person.