Skip to content
Plain automation

Automate checking one system against another

Someone exports from two systems and compares them line by line to find what doesn't match. A daily run does the comparison and hands the team only the exceptions.

In short

Two systems that are supposed to agree, compared by hand in a spreadsheet to find the rows that do not. We build a scheduled job that pulls from both, matches records by your rules and produces only the exceptions with the reason attached. Plain automation, no AI. Usually a single-task automation, $7,500 to $25,000. First deliverable running within 14 days.

  • Free evaluation
  • Fixed quote before work begins
  • First deliverable running in 14 days, guaranteed
  • Small tasks welcome

What this costs you today

Two systems are supposed to agree: the bank and the ledger, the orders and the shipments, the vendor's statement and your records. Someone exports both, lines them up in a spreadsheet, and hunts for the differences. In the companies we meet this happens daily or weekly, and it takes hours each time.

Most of the rows match. The handful that do not are the whole point, and finding them by eye is slow and unreliable.

Call a fully loaded employee $45,000 a year, as an illustration. Reconciliation typically takes 10 to 15 hours a week. Fifteen hours is more than a third of a person, spent confirming that things match.

Typical time
15 hrs / week
That is
more than a third of a person
At an illustrative $45,000 a year
$16,875 / year

Typical figures, using $45,000 as an illustrative fully loaded cost. Your numbers go in the calculator below. If your version is a couple of hours a week, that still counts. Or open these figures in the calculator and change them.

How it works

  1. 1

    Step 1

    We write down the matching rules the person already uses: which fields, what tolerance, what counts as the same record.

  2. 2

    Step 2

    We pull from both systems by connection, export or, where needed, their screens.

  3. 3

    Step 3

    The job runs on a schedule, matches the records and logs what matched.

  4. 4

    Step 4

    Each exception is listed with why: missing on one side, different amount, different date.

What CBIT builds instead

We build a scheduled job that pulls from both systems, matches the records by the rules you already use, and produces the list of exceptions. Matched records are logged and left alone.

Each exception comes with why it did not match: missing on one side, different amount, different date. The person reviews that list and nothing else. When a rule needs a judgment call, that stays with them.

Plain automation handles most repetitive work. We use newer tools only where they clearly earn their place, and we tell you when we do. Reconciliation does not need them.

What the person gets back is the comparison. They start at the exceptions instead of at row one.

Plain automation or AI?

This is plain automation. No AI. Matching records by rule is exactly what software is for.

What business automation actually costs

One example, names left out

Before

Two exports, one spreadsheet, and a person going line by line to find what doesn't match.

After

Records processed, exceptions flagged, run before the day starts. Ran today in 0:48.

Real work from real clients, with the names left out. What matters is the shape of the problem, and how often we see it.

Price band and timeline

Usually
Single-task automation
Band
$7,500–$25,000
First deliverable running
Within 14 days

This kind of project

Sized to the rules and the exports

Two clean exports and a clear matching rule is a focused project. It grows when records match on fuzzy fields, when there are many kinds of exception, or when one system has no export and has to be read from its screens. We look at both sides before we quote.

  • Small tasks and larger workflows are both welcome. We look at what needs to happen and give you a fixed quote before work begins. No hourly meter.
  • First deliverable running in 14 days, guaranteed.
  • Changes to outside systems (a portal redesign, a vendor's API change) may require separately quoted repair work. We tell you when that happens.

All prices and the guaranteeWhat business automation actually costs

Run your own numbers.

Set to the typical figures for this task. Change them to match your team, however small the number.

What this task costs you in time

Hours a week, times the people doing it, at whatever a person costs you. $45,000 a year is an illustration; set it to your own figure.

People doing this work

1

Hours each, per week

Half an hour counts. 40 is a full week.

15

Fully loaded cost per person, per year

Salary, benefits, taxes, overhead. $45,000 is an illustration; set it to yours.

$45,000

Time spent on this task

15 hrs / week

About 780 hours a year of a person's time.

Labor value of that time
$16,875 / year
Your project price
Fixed quote after a free evaluation

These figures show the value of time spent on the task, not a project quote or guaranteed cash savings. We will help estimate what can realistically be automated.

Questions about this task.

What if the records do not match exactly?

Most reconciliations have a fuzzy edge: an amount off by a fee, a date off by a day, a reference formatted two ways. Those become rules with tolerances. Anything outside the tolerance is an exception, and a person decides.

Can it read from a system that has no export?

Yes, through its screens, using your own login, after we review that system's terms with you. It is more work than an export and it is more fragile, so we say so in the quote. Where an export or a connection exists, we use it.

How do we work the exceptions?

They come as a list, each with the reason and a link back to the record on both sides. Some teams work it in a spreadsheet, some in their system, some from a morning email. The job can also mark items resolved once you fix them.

How is this priced?

Two clean exports and a clear matching rule is a single-task automation, $7,500 to $25,000, at the low end. Fuzzy matching, many kinds of exception, or a system read from its screens move it up. The quote is fixed after the free evaluation.

How long until it is running?

The first reconciliation is running on real data within 14 days of us having access to both systems. Extra rules and exception types are added as they come up.

Tell us about the task your team keeps doing by hand.

Every morning, every Friday, or every time an order comes in. Small tasks and larger workflows are both welcome. The evaluation is free, and if we take it on, the first deliverable is running in your operation within 14 days, guaranteed.

Free evaluation. Fixed quote before work begins.