Every bank's fee statement, whatever format it arrives in, turned into data your fee analyzer can actually read.
Bank fee statements arrive in four shapes: the older TWIST BSB format, the ISO 20022 CAMT.086 that is replacing it, plain XML, and each bank's own proprietary layout. SAP added native bank-fee analysis in S/4HANA 1809, but it expects clean CAMT.086 in. The statements that arrive in any other format never reach the analyzer, so the fees on them never get reviewed.
Derived fees make it harder still: the charge that has to be calculated out of the file rather than read off it is the one a person checking by hand misses. The Bank Fee Portal sits in front, accepts every format, validates and enriches each statement, and delivers the result into the analyzer, so the fee review covers every bank rather than only the ones that happen to send clean files.
Brisken reads the fee statements, validates them, calculates the derived fees and hands over the structured result. Comparing what a bank charged against what you negotiated runs in SAP's Bank Fee Analyzer, or in whichever TMS or analytics tool you already own; that comparison also needs your bank statements alongside the fee statements. The portal is what gets every bank into it, including the ones whose format never made it in before.
Configured once per bank, the ingest then runs on its own.
| Bank Fee Portal in front of the analyzer | The analyzer alone | Manual / spreadsheet | |
|---|---|---|---|
| Input formats accepted | CAMT.086, XML, TWIST BSB, proprietary, normalized in | Clean CAMT.086 | Whatever a person can open |
| Off-format statements | Parsed and delivered into the analysis | Stall outside the app | Re-keyed by hand, if at all |
| Derived fees | Calculated during enrichment | Only what the file already states | Easy to miss by hand |
| Who runs the comparison | Your Bank Fee Analyzer, TMS or analytics | The same analyzer, on fewer banks | A person, on spot-checks |
| Banks reaching the review | Every bank that sends a statement | Only banks already on CAMT.086 | Whatever got opened in time |
| Effort per cycle | Ingest is configured once, runs on its own | Manual conversion for off-format banks | Hours of clerical work each run |
The portal sits in front of the fee analysis; it does not replace it and does not perform it. The analyzer is capable once the data is in. The portal's job is getting every bank's statement, in any format, into it.
The bank that sends a proprietary file is the bank whose fees go unchecked, however good the analyzer is. Getting that statement in, structured and enriched, is what puts it in front of the analysis at all. The portal accepts every format, so no bank is left out on a technicality.
CAMT.086 is the ISO 20022 bank-fee-statement format that replaces the older TWIST BSB. SAP added native bank-fee analysis in S/4HANA release 1809, delivered as a Fiori app that compares charged fees against expected ones, but it reads clean CAMT.086 only. Banks have not standardized on it; many still send TWIST BSB, plain XML or a proprietary layout, and those are exactly the statements the portal exists to normalize and bring in.
No. That comparison runs in SAP's Bank Fee Analyzer, or in the TMS or analytics tool you already use, and it needs your bank statements alongside the fee statements. The portal reads every bank's fee statement in any format, validates it, calculates the derived fees and delivers the structured result into that tool. Paired with an analyzer, it is what lets the comparison cover every bank instead of only the ones sending clean CAMT.086.
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 XML, TWIST and proprietary formats. A bank-fee portal reads any format, validates and enriches it, and distributes it to the analyzer, so the fee review is not gated on format.
Banks issue fee statements in TWIST BSB, the older industry format, in CAMT.086, in plain XML, and in their own proprietary layouts. SAP's native analysis expects CAMT.086, so the off-format statements stall. A format-agnostic portal parses them, normalizes them to the structure the analyzer reads, and delivers them in, so no bank is left out of the review.
A derived fee is one you have to calculate out of the statement rather than read off it, for example a margin or a volume-tiered charge implied by the underlying figures. A person checking a statement by hand sees the stated lines and misses the implied ones. The portal calculates them during enrichment, so they arrive at the analyzer as data rather than staying buried in the file.
Bring the formats your banks actually send; we will show what the portal reads and what it hands to your analyzer.