Operations
Bank feeds vs file import: what to know
The trade-offs between direct custodian feeds and file-based import, and how duplicate detection keeps data clean.
The FLIORE Compliance Desk
Family-office compliance research
5 min read
Updated 2026-07-01
Key takeaways
- Direct feeds automate ingestion; file import is universal and immediate.
- Duplicate detection prevents double-counting across syncs.
- An aggregator layer bridges many banks with one integration.
The trade-off
Direct custodian feeds pull data automatically but require integrations bank by bank, or an aggregator. File import (CAMT.053, MT940) works with any bank today and needs no integration — at the cost of a manual step.
Keeping it clean
Whichever route, the same statement must not be counted twice. A stable duplicate hash across syncs detects and skips transactions already imported — the difference between a feed you trust and one that creates chaos.
FAQ
Do I need live feeds to start?
No — file import works immediately; feeds can follow via an aggregator.
Sources
- ISO 20022 CAMT
- PSD2 / open banking
Related guides
Compliance, built into the platform
FLIORE is a family office platform with KYC and compliance built into the core.
Explore FLIORE