Export data safely
Which pages let you export, what FlowSentry does to protect each file, and how to handle exports without tipping off.
tocOn this page
Exports leave the controlled environment of FlowSentry, so the product protects them in several ways and records every one. Your part is to export only what you need and to look after the file once it is on your device.
How FlowSentry protects exports
- Masking. Identifiers such as national IDs, phone numbers and account numbers stay masked in register exports, just as they are on screen.
- Formula-safe files. In CSV exports, values that a spreadsheet could treat as a formula are neutralised, so opening the file cannot run anything.
- Watermarks. Sensitive downloads, such as STR XML files and case documents, carry a watermark that names the person who downloaded or viewed them.
- Audit logging. Every export is recorded under your name. Some exports record only counts; batch screening, for example, never writes the names into the log.
- Permissions. You can export only what you can already see. Exporting never widens your access.
Where you can export
| Page | Export | Notes |
|---|---|---|
Customers (/customers) |
Export CSV | Masked, formula-safe, recorded in the audit trail |
| Any dashboard | Export CSV, or the download icon on a widget | Whole dashboard or one widget; recorded under your name |
Pivot analytics (/analytics/pivot) |
Export XLSX | Recorded in the audit trail |
Batch screening (/screening/batch) |
Export CSV | Formula-safe; the log records counts only |
Reporting (/reporting) |
Download watermarked XML, Export STR register, Download XML bundle, Download hand-off package | STR material is for STR-privileged roles only; the hand-off needs MLRO authority with step-up |
Link analysis (/cases/link-analysis) |
Export JSON | The network you are viewing |
An ingestion run (from /integration/runs) |
Export open rows (CSV) | Quarantined rows not yet corrected or dismissed |
Designations (/screening/designations) |
Certificate as CSV | Nil or positive certificate after a rescreen |
Export responsibly
- Ask whether you need a file at all. A dashboard link or a saved pivot view can often be shared instead, and the recipient sees only what their own role allows.
- Narrow before you export. Apply filters and a period first, so the file contains only what you need.
- Use Reveal sparingly. Revealing a masked identifier on screen is recorded; copying it into another document takes it outside FlowSentry's controls.
- Store the file where your institution's policy says. Do not keep exports in personal storage or send them to personal email.
- Delete the file when you are done. FlowSentry keeps the records; you do not need a private copy.
Warning: Anything about a suspicion, an alert, a case or a suspicious transaction report must never reach the customer or anyone who might alert them. Do not attach such exports to messages to relationship managers or front-office staff, who are deliberately kept away from this material.
Tipping-off controls you can rely on
- STR material, including the STR register and goAML XML files, is visible only to the MLRO, Deputy MLRO and Auditor.
- Cases involving an STR carry the STR-restricted badge and are hidden from everyone else except the people already on the case.
- Relationship managers and executives never see alerts, cases or STR material, so exports from their roles cannot contain them.
Filing reports with the FRC
Filing with the Financial Reporting Centre is a manual upload to the goAML portal. FlowSentry prepares and validates the XML and tracks the filing. Download the bundle, upload it to the portal, then select Mark selected as uploaded and record the FIU reference so the register stays accurate.
Note: Viewing and downloading reports are both recorded in the audit trail.