Why IT belongs in your reconciliation

Most reconciliation problems start in the integrations between systems. That makes IT and data teams part of the close, whether anyone planned it or not.

The Actuals teamActuals · 2 min read

A new payment gateway goes live on a Monday. Checkout works, the project is closed, and IT moves on to the next ticket. A few weeks later, finance finds that the transactions from the new gateway do not line up with what the ERP shows.

Nobody did anything wrong. The gateway was connected, just not in a way finance could reconcile.

In a high-volume business like e-commerce or parking, transactions never stop. Finance can only reconcile the data the systems hand over. Whether that data is usable is decided by the people who build and run those systems. Think of IT managers and CTOs, but also application specialists, finance system owners and data professionals.

Where IT and finance meet

Three things sit on both desks.

Integration. Each new payment gateway is another link to the ERP, and each one can bring delays and errors. At a large e-commerce company, IT has to make sure the sales platform updates the accounting software on every transaction. If it does not, finance finds differences between the order data and the financial records.

Data accuracy. A finance system manager at a telecoms company has to make sure billing reflects actual usage. If it does not, customers are overcharged or undercharged, and the reported revenue is wrong with them.

Upkeep. Keeping systems updated and secure takes real time and expertise. Data has to keep its integrity through every stage of processing and reporting, not just on the day the integration goes live.

When regulation sets the pace

For some businesses, reconciliation is also a regulatory duty, and much of how it is met sits in the systems IT runs.

  • In the United States, the Sarbanes-Oxley Act (SOX) demands strict financial controls and regular reconciliations.
  • In the United Kingdom, FCA rules on client money (CASS) emphasise daily reconciliation, under CASS 7 among others. IT teams there make sure client money reconciliation is automated and secure.

Falling short can mean financial penalties, regulatory sanctions and reputational damage.

Three questions to answer together

The friction comes from one place. Each system has its own data model, so a change in one of them shows up later as a difference in finance. That makes reconciliation a shared job, and the questions below are best answered with finance and IT in the same room.

  1. Which systems feed the ledger, and who owns each connection?
  2. What happens in finance when a provider changes its file format or a new payment method goes live?
  3. Which reconciliations does your regulator expect, and how often?

Actuals takes much of that load off both teams. It sits between your operational systems and the ERP, brings every source into one format and matches the transactions daily.

Answer the three questions before your next gateway goes live, not after the first close that does not tie out.

In practiceNew country, new PSP, new currency. Same close?

Written by

The Actuals teamActuals