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

Daily payment file from Paymentus posts to utility billing

Every weekday morning, reads Paymentus's payment file from the SFTP folder, keeps accepted payments, checks each account exists in utility billing, and posts the payments. Payments for unknown accounts are emailed to the billing office instead of posted.

Try it on your dataAll examples
This flow

10 steps

StartsOn a schedule
SystemsSFTP server, Utility billing (CIS)
Branches1
Stored recordsNone: pass-through
§ The flow

The whole flow, as it appears on the canvas.

Scroll sideways on small screens. Colors show the kind of step: start, read, change, decide, write.

Flow diagram: Daily payment file from Paymentus posts to utility billingEvery weekday morning, reads Paymentus's payment file from the SFTP folder, keeps accepted payments, checks each account exists in utility billing, and posts the payments. Payments for unknown accounts are emailed to the billing office instead of posted.Weekdays at 6:30 amOn a scheduleRead the Paymentus fileRead files · SFTPAccepted payments onlyFilterUtility billing accountsGet records · Utility billingTo utility billing fieldsMap fieldsFind the accountJoinAccount found?If / elseFields for: post thepaymentMap fieldsEmail unknown accountsSend emailPost the paymentSend records · Utility billingYesNo
StartReadFilesDatabaseChangeDecideWriteAct
§ Step by step

What each step does.

  1. 01 · Start · On a schedule

    Weekdays at 6:30 am

    • Cron 30 6 * * 1-5 (workspace time zone)

    Then: Read the Paymentus file; Utility billing accounts

  2. 02 · Files · Read files · SFTP server

    Read the Paymentus file

    • Reads files matching paymentus-payments-*.csv in inbox on SFTP server
    • Format: CSV, first row has the field names
    • Only files new since the last good run
    • After a good run, files move to archive

    Then: Accepted payments only

  3. 03 · Decide · Filter

    Accepted payments only

    • Keeps only records where Payment Status is ACCEPTED

    Then: To utility billing fields

  4. 04 · Read · Get records · Utility billing (CIS)

    Utility billing accounts

    • Reads Accounts from Utility billing (CIS)
    • At most 50,000 records per run

    Then: Find the account

  5. 05 · Change · Map fields

    To utility billing fields

    • Shapes each record into 7 fields: receipt_number, account_number, amount, paid_on, method, source, batch

    Then: Find the account

  6. 06 · Decide · Join

    Find the account

    • Join

    Then: Account found?

  7. 07 · Decide · If / else

    Account found?

    • Yes when ub_account is not empty

    Then: Yes → Fields for: post the payment; No → Email unknown accounts

  8. 08 · Change · Map fields

    Fields for: post the payment

    • Shapes each record into 7 fields: receipt_number, account_number, amount, paid_on, method, source, batch

    Then: Post the payment

  9. 09 · Act · Send email

    Email unknown accounts

    • Emails [email protected]: “{{count}} Paymentus payments need an account”
    • One summary email
    • Records attached as CSV
  10. 10 · Write · Send records · Utility billing (CIS)

    Post the payment

    • Creates Payments in Utility billing (CIS)
§ Systems

Connectors used

Swap any of them for another system with the same kind of data.

§ Next

Keep exploring

Example311 triage: route every request to the right systemExampleMeter reads from AMI to utility billing with zero-read checkExampleLoad the bank's daily payment file into the city databaseExampleMunis paid checks to the bank positive pay file

Run this flow on your systems.

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

Request a demoBrowse live examples