Trust accounting without the spreadsheet: balances that sync from the bank

If your agency holds client money, you already know the job: the trust balance has to be right, and you have to be able to show it is right. For many agencies that still means exporting bank activity, pasting it into a spreadsheet, matching it line by line against what the agency system says, and chasing down the differences.

We shipped three changes that remove much of that manual work.

• Trust balances now sync automatically from bank account data.
• Paid-out card purchases now move from operating to trust by ACH debit.
• A nightly funds-held checkpoint with proofs supports reconciliation.

This post covers what each one does, how they work together, and why they matter for anyone accountable for money that does not belong to the agency.

The problem: two records that drift apart

Trust accounting breaks down where two records meet. The bank holds one version of the balance. Your agency system holds another. Between them sit card payments, transfers and timing gaps.

When those records are reconciled by hand, the work is slow, and it is also opaque. A spreadsheet shows the numbers someone typed in, not where they came from. If a balance is off, finding out why means rebuilding the trail after the fact.

That is the same weakness we see across insurance data more broadly: when you cannot see where a figure came from or who touched it, you cannot trust it. Our approach is the same here as everywhere else. Every record has an owner, every access is visible and logged, and the source of a number should be something you can check rather than something you take on faith.

Balances that come from the bank

The first change is the foundation. Trust balances in InsurEco now sync automatically from bank account data.

In practice, the trust balance you see is drawn from the bank account itself rather than keyed in or uploaded from an export. The figure you work from starts with the institution actually holding the funds.

For the person doing reconciliation, this changes the starting point. Instead of building the bank side of the comparison by hand each period, you begin with a balance that is already sourced from the bank. Your attention goes to the exceptions, not to re-entering data that already exists somewhere else.

Card purchases: from operating to trust by ACH debit

Card payments are where trust and operating funds tend to get tangled. A client pays by card, the funds land in one place, and someone has to make sure the right amount ends up where it belongs.

With this release, paid-out card purchases now move from operating to trust by ACH debit. Once a card purchase has paid out, the corresponding amount is moved into trust through a standard ACH debit rather than a manual transfer that someone has to remember to make.

The mechanism matters because it turns a recurring manual step into a defined, repeatable movement of funds. Each transfer follows the same path, and each one leaves a record you can point to when you reconcile.

A nightly funds-held checkpoint, with proofs

The third change ties the first two together. Every night, InsurEco records a funds-held checkpoint, and that checkpoint comes with proofs that support reconciliation.

Think of it as a fixed reference point for each day. Rather than reconstructing what the trust position looked like on a given date from scattered records, you have a checkpoint that was recorded at the time, with proofs attached. When you reconcile, you are comparing against something that was captured on schedule, not assembled later from memory and exports.

This is where transparency becomes practical. A balance is useful. A balance you can verify, tied to a specific point in time, is what you need when someone asks you to show your work.

How the three fit together

Taken one at a time, each change removes a manual step. Together they describe a simpler flow:

1. The trust balance is sourced from bank account data.
2. Paid-out card purchases move from operating into trust by ACH debit.
3. Each night, a funds-held checkpoint with proofs records where things stand.

The result is that the bank side, the card side and the daily position are each handled by a defined mechanism rather than by a person with a spreadsheet. Reconciliation becomes a review of a record that already exists, not the construction of one.

Why this matters for agencies holding client money

Agencies that hold client funds carry a specific kind of responsibility. That money is not operating cash, and the people who handed it over are trusting you to keep it separate and accounted for.

Manual reconciliation does not fail because people are careless. It fails because it depends on repeated, tedious steps done the same way every time, often at the end of a long week. Every manual step is a place where a number can be mistyped, a transfer can be missed, or a timing difference can be mistaken for a shortfall.

Moving those steps onto defined mechanisms does three things:

• It reduces the hand-keyed work. Balances come from the bank, and card funds move to trust on a set path.
• It makes the trail visible. Each movement and each nightly checkpoint is a record you can look at, not a cell in a file someone edited.
• It shifts the work to judgment. Your team spends time on the items that actually need a decision, instead of rebuilding the baseline.

None of this removes the need for someone at the agency to own trust accounting. It gives that person better inputs and a clearer record to stand behind.

What this is part of

We are building InsurEco around a simple idea: insurance data should be trusted because it can be checked. That applies to policy and claims data shared across the industry, and it applies to the money an agency holds on behalf of its clients. Opaque data, whether it is resold without the owner's knowledge or reconciled in a spreadsheet nobody else can follow, erodes trust in the same way.

Trust balances that sync from the bank, card funds that move to trust by ACH debit, and a nightly checkpoint with proofs are one more step toward records that every party can see and verify.

Secured on InsureBio, the insurance data chain.