Truist
The Truist integration is available today.
Truist commercial account data reaches LORIQ through industry-standard bank information reporting formats — BAI2, ISO 20022 camt, and MT940 — the same files Truist already produces for treasury workstations.
This file-based path works without waiting on bank API onboarding: your team can upload reporting files directly, or schedule secure file transfer where your banking agreement supports it. Exact formats and delivery options are governed by your treasury services agreement with the bank.
Supported data
Opening, closing, and available balances for your Truist commercial accounts, as reported in your bank files.
Detail and summary transaction records for cash visibility across operating and reserve accounts.
BAI2, ISO 20022 camt, and MT940 information reporting files.
Security
Every LORIQ integration — including Truist — runs on one shared, hardened connectivity framework rather than per-integration plumbing:
- Credentials are stored in an encrypted, per-connection vault and are never exposed to browser sessions or logs.
- Every synced record is scoped to your organization — tenant isolation is enforced at the query layer and verified by automated guard tests.
- All incoming files pass malware scanning before storage; unscanned bytes are never persisted (fail-closed by design).
- Imports land as drafts for review — synced data never silently overwrites your records.
- Every sync, import, and connection change is captured in the platform audit trail.
- No online banking credentials are ever shared with LORIQ — connectivity is based on reporting files, not screen access.
Authentication
Truist connectivity is file-based (Bank file standards (BAI2, ISO 20022 camt, MT940)). No credentials for your source system are shared with LORIQ for manual uploads; scheduled transfer connections store only the transfer credentials you provision, held in LORIQ's encrypted vault.
Files are checksummed for duplicate detection and pass malware scanning before any content is stored.
Setup guide
- 1Confirm reporting files
Ask your Truist treasury contact which information reporting formats (BAI2, camt, MT940) your agreement includes — most commercial accounts already have them.
- 2Upload or schedule
Upload files directly in LORIQ, or configure scheduled secure file transfer if your bank supports automated delivery.
- 3Review
LORIQ parses each file, deduplicates by checksum, and presents balances and activity for review before they enter your cash picture.
Frequently asked questions
Does LORIQ log into our Truist portal?
No. LORIQ never accesses your online banking portal or credentials. Connectivity is built on the standard reporting files banks produce for treasury systems.
Which file formats are supported?
The design targets BAI2, ISO 20022 camt, and MT940 information reporting files, plus NACHA return files — the formats effectively all commercial banks can produce.
Can delivery be automated?
The design supports automation where your banking agreement allows scheduled file delivery or pull via secure file transfer, with manual upload as the universal baseline.
Expanding capabilities
- Direct API connectivity for Truist where the bank's API program and your banking relationship support it.
- Expanded automation of scheduled file delivery.
See Truist + LORIQ in action
Walk through the integration with our team and see how your data flows into a single commercial credit workspace.
Request a demoMore in Commercial Banking & Treasury
Account balance and transaction connectivity for Wells Fargo commercial accounts via industry-standard bank reporting formats.
Account balance and transaction connectivity for Bank of America commercial accounts via industry-standard bank reporting formats.
Account balance and transaction connectivity for JPMorgan commercial accounts via industry-standard bank reporting formats.