AI for GovTech

Balancely by Datics AI

When a batch does not balance, balancers see which payments caused it and approve the fix.

Balancers stop searching files line by line when a batch is off. Balancely matches each payment to its notice, explains every difference with the file line behind it, and waits for the balancer to approve the correction.

Built into your codebase and shipped under your name, on an engine we license to you.

civara.example/harlow-county/tax/batches/today

Harlow County Tax Office · Balancely

Demo

The lockbox batch is off by $1,284.10. Why?

1 correction waiting for the balancer

  • 214 lockbox lines matched to their notices
  • 2 payments on the wrong notice, with the file lines shown
  • Posted only after the balancer approves

214 lines matched2 differences explainedBalancer approves

Try it step by step

Illustrative demo on a fictional county. Not client work.

Try it step by step

Balancely on a fictional agency.

Harlow County Tax Office (fictional). Step through the conversation, then see what Balancely hands back, the way your Build Sprint would build it on synthetic data.

civara.example/harlow-county/tax/batches/today

Harlow County Tax Office · Balancely

Demo
  • The lockbox batch is off by $1,284.10. Why?

Step 1 of 5

Illustrative demo on a fictional county. Not client work.

What it hands back

civara.example/harlow-county/tax/batches/today

Batch check · Lockbox, November 9

Harlow County Tax Office · bank lockbox file

Balancely
Lines in the file
214 · all read
Done
Matched to their notice
212 · amounts and parcels agree
Done
Lines 41 and 42
Parcel 07-118-3 posted to 07-181-3 · $1,284.10
Check
Correction
Move both to 07-118-3 · balancer to approve
Waiting
Batch after the move
Balances to the cent
Done

Balancely drafts the correction. The balancer approves it, and month close stays with the office.

Illustrative demo on a fictional county. Not client work.

What it does

What Balancely can do.

Batch and month close checks for property tax, fines and payment platforms: every payment matched to its notice across counter, mail, lockbox, mortgage files, card swipers and the online portal, each difference explained with the file line behind it, and a correction a balancer approves before anything posts.

Every channel matched to its notice

Counter, mail, lockbox and mortgage servicer files, swipers and portal payments matched to the notice they belong to.

Differences explained

Each gap named with its cause, such as a payment on the wrong parcel, a duplicate swipe or an ACH reversal not yet posted.

The file line behind each match

Every suggested match shows the lockbox line, gateway record or receipt it came from.

Corrections the balancer approves

Moves, voids and reversals are drafted for the balancer; nothing posts until they approve it.

Month close, checked first

Before distribution, a check that every batch balances and every receiving entity's share adds up.

How it works

Balancely reads each batch with the files and gateway records behind it, matches every payment to its notice by parcel, amount and reference, and explains any difference in plain words with the line it came from. Corrections are drafted through your platform's own move, void and reversal actions, and post only after the balancer approves.

Built on the multi-office property tax collection platform we modernized for a government payments software company; the matching and explanations are what a Build Sprint adds.

Government payments software company

Tax collection · Every channel on one notice

Tax offices collect from every channel and balance each month to the cent

Offices ran tax season on an old desktop system. Now one web back office takes every channel, disburses each dollar and closes the month.

ModernizationMulti-tenantIntegrations
Read case study

Government payments software company

Tax collection · Handover without stopping

Tax offices kept collecting while our engineers moved into the new owner's team

A change of owner can stall a live product. Offices kept collecting while we moved the code to the new owner and joined its sprints.

Forward deployedInside a live productMulti-tenant
Read case study

Government payments software company

Fines and fees · Payment portals

Sheriffs and courts take fines online and at the counter on one portal

Fines were paid at the counter in cash or check. Now each agency has its own branded portal for card, bank and front desk swiper payments.

ModernizationMulti-tenantInside a live product
Read case study

Why it sells

What Balancely does for your business.

What your agencys get, and what it does for your renewals and pricing.

Faster month close

Balancers spend their time approving fixes, not finding them.

Offices stay in control

Every correction is the balancer's to approve, under their name.

Findings caught early

Differences are explained the day they appear, not at the audit.

Controls

What Balancely touches, and who approves.

Your agencys' data is not used to train models for anyone else and stays in your cloud. Built and tested on synthetic or test data.

  • Who uses it

    Collectors, balancers and office admins

  • What it connects to

    Your notices, payments, batches, gateway and lockbox files, through your platform's APIs

  • What a person approves

    The balancer approves every correction; month close stays with the office admin

  • Switch per agency

    On or off for each agency, with data settings their admins control.

See all controls and how we handle public records and agency data

How to get it

Two steps to a finished Balancely.

Start with a three-week Build Sprint. Add more only if you want it.

  1. First · Build Sprint · $10,000 fixed

    Balancers see why a batch is off and approve the fix

    • Every channel matched to its notice
    • Differences explained
    • Corrections the balancer approves
    • In your staging, behind a feature flag
    • Delivered as pull requests
    • A test set your team reviews
    1. Week 1Setup
    2. Weeks 2 to 3Build
    3. You getBalancely in your staging and a fixed production quote
    Your time
    About 2 to 3 hours a week from a product owner
    Data
    Synthetic or test data, never your agencys' customers
    The fee
    Counts toward production
  2. Then · Live in production

    A finished product, yours to run

    • Fixed quote
    • Tested before launch
    • Switch per agency
    • A finished, working Balancely in your product
    • Runs in your cloud, under your name
    • Fixed quote, agreed before we start
  3. Optional · Add more later

    Only if you want it

    More of Balancely:

    • The file line behind each match
    • Month close, checked first

    Another module:

    • Each one quoted on its own
    • Nothing ongoing unless you ask

Already built or tried AI? Get it scored with the AI Scorecard. Need something else? Start with a Planning Sprint.

FAQ

Questions about Balancely.

Can Balancely post a payment or close the month?

No. It matches and explains, and drafts corrections through your platform's own actions. The balancer approves each one, and month close stays with the office admin.

Which payment channels does it read?

Whatever your platform already records: counter and mail payments, lockbox and mortgage servicer files, card swipers, the online portal and gateway records such as ACH reversals. The first Sprint starts with one channel.

Does each office keep its own rules?

Yes. Matching follows each office's own settings, fees and interest rules, and one office's records are never used for another.

See Balancely on your own product.

Bring your product and one workflow. In 30 minutes we look at where Balancely fits, what it would cost to serve and what your agencys' security review will ask.

Calls run in US Central time. No generic AI presentation: we discuss your product, users and production constraints.