Pass-through integration for local government · records are never stored System status1-559-251-7767Sentra familySign in
SentraBridgeIntegration platform
Utility billingSolution

Payments in. Exports out.
No spreadsheet in between.

Load lockbox and bank payment files into the billing database, send billing exports where they need to go, and follow up with customers who missed their place in line.

This solution

Utility billing

StartsOn a schedule · Weekdays at 6 am
SystemsSFTP server, Microsoft SQL Server, SentraQueue, Twilio SMS…
Templates3 ready-made flows to start from3
Stored recordsNone: pass-through, in memory only0
Preview any template on your own data before it writes anything.
§ The problem

What it looks like today.

Lockbox files

Payment files arrive by SFTP in CSV or XML and need checking before they post.

Exports for vendors

The bill print vendor wants a file every night in their format.

The counter line

Customers called at the counter who didn't show need a way back in.

§ How it works

How it works: Utility billing

  1. 01Read payment filesCSV or XML from SFTP
  2. 02Check rowsAccount, amount, date
  3. 03Post to billingInsert or upsert
  4. 04ExportFiles to vendors over SFTP
§ 01 / Payments

Checked before they post.

Payment files are read from SFTP, cleaned and checked row by row, loaded into the billing database, and archived. Rows that fail go to finance by email.

  • XML record element for lockbox formats
  • Value maps for fund or payment codes
  • Archive or delete after a good run
Flow diagram: Load the bank's daily payment file into the city databaseEvery 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 files. Bad rows are emailed to finance.Weekdays at 6 amOn a scheduleRead payment filesRead files · SFTPClean and checkApply rulesLoad intoutility_paymentsWrite to database · PostgreSQLEmail bad rows tofinanceSend emailInvalid
Load the bank's daily payment file into the city database · 5 steps · a real SentraBridge template
§ 02 / The lobby

Missed your turn? Here's a link.

Every hour, visitors SentraQueue called who didn't show get an email with a link to rejoin the line.

  • Only visitors with an email
  • Runs hourly
  • No visitor data kept by SentraBridge
Flow diagram: Follow up with SentraQueue no-showsEvery hour, emails visitors who were called but didn't show, with a link to rejoin the line.Every hourOn a scheduleEvery hour (workspace time zone)Changed visitsGet records · SentraQueueReads Visits (tickets) from SentraQueueNo-shows with an emailFilterKeeps only records where state is no_showand email is not emptyEmail each visitorSend emailEmails {{email}}: “We missed you at CityHall”
Follow up with SentraQueue no-shows · 4 steps · a real SentraBridge template
§ Systems

Works with

Pre-built connectors used in this solution. Anything else with an API, a database or SFTP works too.

See your own systems connected.

We'll set up a workspace with your systems in a sandbox and build your first flow with you.