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

Do the two systems agree?
Find out every day.

Reconcile matches records from two systems by key and sorts them into Matched, Different, Only in A and Only in B, with control totals on both sides. It's the daily check auditors ask for between utility billing, the general ledger, payment processors and the bank.

ReconcileTwo systems are matched by key; anything that doesn't agree goes to Finance.Payments in billingRead files · CIS exportBilling vs ledgerReconcile · by accountExceptions to FinanceSend email
Control totalsthis run
Billing (A)Ledger (B)
Records66
Amount$1,042.75$1,049.00
Difference−$6.25
What came out
outputrecords
Matched4
Different1 · 132.50 vs 132.05
Only in billing1
Only in ledger1
Illustration: Matched, Different, Only in A and Only in B, with totals on both sides. Totals are kept; records are not.
§ How it works

Two systems, one daily check

  1. 01Read ABilling, payments, permits…
  2. 02Read BThe ledger, the bank, the GIS layer
  3. 03MatchBy one or more keys, with tolerance
  4. 04TotalCounts and sums on each side
  5. 05ActEmail exceptions, open tickets, or fix
§ 01 / Four outputs

Matched, Different, Only in A, Only in B.

Each record lands where it belongs, ready for the next step. Different records carry a plain list of which fields disagree and both values, so Finance can see at a glance that 132.50 was posted as 132.05.

  • Keys can ignore case, spaces and leading zeros
  • Numeric tolerance for rounding
  • Amounts like $1,234.50 and (12.00) read as numbers
A Reconcile step in the data inspector: records in A and B, matched, different, only in A, only in B, and the totals on each side.
§ 02 / Control totals

The numbers an auditor wants, every run.

Each run keeps record counts and the sum of an amount field on both sides, plus the difference and any repeated keys. They show on the canvas, in the data inspector and in run history. The records themselves are never kept.

  • Totals in run history
  • Repeated keys flagged
  • Join step for lookups between two sources
Flow diagram: Utility billing vs general ledger daily balance checkEvery morning, compares each day's payment total in utility billing with the cash receipts journal entry in Munis. Days that don't match, or have no journal entry, are emailed to finance with the difference.Weekdays at 7 amOn a scheduleUtility billing daily totalsGet records · Utility billingMunis journal entriesGet records · MunisCash posted per dayMap fieldsBilling vs ledgerReconcileEmail finance thedifferencesSend email
Utility billing vs general ledger daily balance check · 6 steps · a real SentraBridge template
§ FAQ

Questions, answered

What can I reconcile?

Any two sources SentraBridge can read: APIs, databases and files. Common pairs are utility billing and the general ledger, a payment processor's file and billing, the bank's BAI2 file and cash receipts, and permits against a GIS layer.

Are the records stored for the audit?

No. Run history keeps counts, totals and record IDs. The details of what didn't match go wherever you send them, such as an email to Finance or a ticket.

See your own systems connected.

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