Bank payment file to the database
Every morning, new payment CSVs are read from the bank's folder, checked, loaded and archived; bad rows go to finance.
SFTP is still how many banks, payment vendors, AMI systems and state agencies exchange files with cities. Finance and utility staff often download, rename and upload these files by hand every day.
SentraBridge reads and writes files on SFTP servers: CSV, JSON, JSON Lines, XML, fixed-width, ACH and BAI2. Flows pick up new files, check every row, load them into the right system and archive the file. File contents pass through memory only.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Files | CSV, JSON, JSON Lines, XML, fixed-width, ACH, BAI2, GeoJSON, Shapefile | write files (including positive pay), transfer documents | yes (new files) | Columns from the file |
Every morning, new payment CSVs are read from the bank's folder, checked, loaded and archived; bad rows go to finance.
Every weekday afternoon, AP checks issued in Munis are written as the bank's positive pay file to the outbox.
The daily Paymentus file is read, accepted payments checked against accounts and posted.
The Neptune 360 export is read each morning and suspicious reads go to the meter team.
Yesterday's changed 311 requests are written as a dated CSV for another system to pick up.
Every morning, reads the Neptune 360 export from the SFTP folder. Reads that look wrong (35 days with no flow, a skipped read or a read error) go to…
SFTP server → PostgreSQL / PostGISEvery 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…
Tyler Enterprise ERP (Munis) → SFTP serverEvery weekday afternoon, reads the AP checks Munis issued and writes the bank's positive pay file to the SFTP outbox, so the bank only clears checks…
Systems cities commonly connect with SFTP, each with its own connector page.
Yes. File steps read BAI2 and ACH, as well as CSV, fixed-width and XML, and write files such as positive pay.
Schedule a flow to read new files in a folder, check rows, write them to the target system, and archive the file. Bad rows can be emailed as a CSV.
No. Files are read into memory, processed and released. Run history keeps file names, counts and timings.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.