How to connect incompatible systems so month-end close stops eating your week

Most businesses do not have a month-end problem. They have a between-the-systems problem that only shows up at month end. The ERP, the accounting package, the bank, the CRM and the time tracking tool each do their job. They just do not agree with each other, and nobody checks whether they do until the books have to close. Then someone spends days reconciling everything that drifted apart over the month. If you want to connect incompatible systems in a way that actually saves time, that reconciliation is the place to start: move it from once a month to every morning.

Connecting incompatible systems: what month-end reconciliation really depends on

"Incompatible" sounds like a technical issue, a missing API or the wrong file format. Those can be solved and are rarely where the hours go. At month end, four other mismatches do the damage.

Every system has its own ID

The CRM knows the customer by a customer number, accounts by a debtor number, the web shop by an email address. Your supplier lists your item under their code, your inventory system under yours. As long as a person knows that "Miller Ltd, Plant 2" and "Miller Group" are the same company, it works. A program has to be told.

Every system has its own cut-off

Goods ship on the 30th, the invoice is created on the 1st. Time tracking closes on the 25th, payroll runs to the 30th. A payment made on Friday shows up in the bank on Monday. None of these systems is wrong. Put side by side on the closing date they still show different states, and someone has to explain the gap.

Every system counts differently

A customer pays one amount for seven invoices and short-pays one of them. A supplier sends one invoice for three deliveries that sit in your inventory system as three separate receipts. One side thinks in totals, the other in line items, and a person does the matching in between.

Some information lives in no system at all

The credit note agreed on the phone. The price change buried in an email. The return the warehouse knows about and accounts does not. You only find these when a number fails to add up, and then the hunt begins.

Why it all piles up at month end

During the month nobody checks whether the systems line up, because each one works on its own. Differences accumulate, and at close someone clears them in one go, under deadline, often in the same week as the dunning run, payroll and the VAT return. You pay twice: in hours during the busiest days of the month, and in the delay before management sees figures it can rely on. Pricing decisions in October get made on September numbers that are not finished yet.

Three ways to make systems fit together

The first is to put everything into one system. A new ERP that combines inventory, accounting and CRM removes some of the breaks. It is also a major undertaking with data migration and training, and the bank, your suppliers and your customers still sit outside it.

The second is the classic interface: field A in system 1 goes to field B in system 2. That handles the clean cases well. It fails at exactly the four points above, because there is no field that maps to the other side. A lump-sum payment covering seven invoices has no one-to-one counterpart.

The third is an agent that sits between the systems and does what your accounts team does at month end, only every day. It reads from each system, translates IDs and dates, matches records, and reports what it cannot match with confidence. Your systems stay exactly as they are. How the same approach works for systems with no interface at all is covered in our article on connecting systems without an interface.

Worked example: reconciling every morning

This example is made up and does not describe a client. Picture a mid-sized company running an inventory system, accounting in DATEV, a web shop and one business bank account. Two people handle accounts, and closing currently eats several days each month.

The agent keeps a mapping table: which shop customer belongs to which debtor, which supplier item code matches which internal item. The table grows every time a person makes a call on a new case, so the same question never has to be answered twice. Each morning the agent runs four checks.

Deliveries against invoices come first. Every delivery in the inventory system needs an invoice. If one is missing, the agent flags it the next day, while everyone still remembers the order.

Then incoming payments. It splits the transfer covering seven invoices using the payment reference and the open items. If the amount does not add up, it finds the invoice the customer short-paid and shows the difference. Whether to accept the deduction or chase it is a human decision.

Next, supplier invoices against purchase orders and goods receipts. The agent matches the supplier's combined invoice to the three receipts and compares quantities and prices. If everything fits, the posting waits for approval with the document attached.

Finally, master data. If someone updates a customer's address in the CRM and accounts still has the old one, it shows up now, not when a reminder letter comes back undeliverable.

By the end of each day there is a short exceptions list, every line with a reason and a suggested fix. Accounts clears it while the details are fresh. At month end only the few cases that genuinely need a decision are left.

What we settle beforehand

The agent needs read access to the systems involved and the rules your team uses to reconcile today, including the unwritten ones: how big a difference has to be before someone follows up, which customers always pay in lump sums, which accounts apply to which cases. We write those rules down once with your accounts team, before we quote a price.

Sophera Consulting builds this agent for your particular set of systems, at a fixed price and without a subscription. Setup takes one to two days, and we test it against the real transactions from your last close in the same week. A maintenance agent is included in the fixed price and notices when one of the systems changes its format. Which reconciliation costs you the most time is what we find out in the free automation check.

Our recommendation

At your next close, note where the hours go, broken down by pair of systems: bank against accounts, inventory against invoices, supplier against goods receipt. The pair with the most hours is the first candidate for daily reconciliation. The others follow one at a time, each as its own step at its own fixed price. You do not need a new ERP for this. You need the translation between your systems done every day instead of saved up for the last day of the month.