Daily payment files
Payments arrive as CSV files on the bank's SFTP server and must be loaded, checked and archived before staff start posting.
Water, power & sanitationWho we serve
Billing files, work orders, maps.
Moving on their own.
Utilities depend on files and databases: payment files from the bank, exports from billing, work orders in the field system. SentraBridge loads, checks and routes them on a schedule, with every run logged.
§ The problem
What gets in the way.
Customer data everywhere
Account and contact data shouldn't gain another copy just because it moves between billing, payments and notifications.
Field and office out of step
Work orders created by phone or in the database don't show up in the service request system, and closures don't flow back.
§ How it works
How it works for utilities
- 01Read the fileNew payment CSVs from the bank's SFTP folder.
- 02Clean and checkFix formats; send bad rows to the Invalid output.
- 03LoadUpsert good rows into the payments table.
- 04ArchiveMove the file to an archive folder after a good run.
- 05ReportEmail finance the bad rows as a CSV attachment.
§ What you get
Built for utilities.
SFTP files, handled
Read CSV, JSON, JSON Lines and XML, archive after reading, and pin the server's host key.
Learn more →Database in, database out
Upsert into SQL Server, PostgreSQL or MySQL, and run flows when rows change.
Learn more →Checks before loading
Required fields, number and date checks, and value maps, with Valid and Invalid outputs.
Learn more →No stored copy
Customer records pass through in memory. Run history keeps counts, timings and IDs only.
Learn more →Replay by ID
Failed records are read again from the source by their ID, never re-sent from a stored copy.
Learn more →Assets on the map
Add and update ArcGIS features and build map points from coordinates.
Learn more →§ Examples
Flows that fit.
Generated from SentraBridge's ready-made templates.
SFTP server → PostgreSQL / PostGIS
Load the bank's daily payment file into the city database
Every morning, reads new payment CSV files from the bank's SFTP folder, cleans and checks them, loads them into a database table, and archives the…
PostgreSQL / PostGIS → Sentra 311Reverse sync: database work orders become Sentra 311 requests
Every 15 minutes, reads work orders created or changed in the city database and creates matching Sentra 311 requests, so phone and inspection work…
Sentra 311 → Sentra SchedulerNew pothole requests become Scheduler visits
Every 15 minutes, takes new or changed pothole requests from Sentra 311 and creates a visit for the street repair crew in Sentra Scheduler.
SentraQueueFollow up with SentraQueue no-shows
Every hour, emails visitors who were called but didn't show, with a link to rejoin the line.
§ Systems
Systems you likely run.
Each links to its connector page. Not listed? Any REST API, OpenAPI file, database or SFTP server works.
SentraQueue§ FAQ
Questions, answered
Can SentraBridge read our billing system's exports?
If the export is a CSV, JSON, JSON Lines or XML file on an SFTP server, yes. If the billing system has an API, SentraBridge can call it directly or import its OpenAPI file.
What happens to a bad row in a payment file?
Rules send it to the Invalid output. A typical flow emails those rows to finance as a CSV attachment and loads only the valid ones.
Do you store customer account data?
No. Records exist in memory only while the flow runs. History keeps counts, timings and record IDs.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.