Business controllers are usually the people who know most about where a company makes and loses money. They are also the people with the least time to go and look.

The month takes the time. By the time the pack is finished the next close has started.

01 / 04

The close eats the month

Actuals come in from the ERP. The 3PL invoice arrives late and in its own format. The freight forwarder bills in a different currency. Someone accrues for the rebates and the retro discounts. Then it all gets pulled into a spreadsheet and compared to budget.

Most of that is assembly work. It follows the same rules every month and it does not need judgement, it needs the data to be in one place with the definitions agreed.

Once that is true, the pack builds itself and it is ready on day two instead of day nine. The controller starts the month with a finished pack instead of an empty file.

02 / 04

Variances can explain themselves

The question after every close is why the margin moved. Someone then spends two days working out the answer.

The answer is normally a combination of volume, price, mix, discount, cost, and currency. All of those are in the data. The bridge can be calculated automatically, down to product and account, so the pack arrives with the explanation attached.

What changes is the meeting. Instead of presenting what happened, the controller arrives with why it happened and what to do about it. The two days go somewhere else.

03 / 04

Allocation at transaction level

Most companies allocate costs with a percentage. Freight is three percent of revenue. Handling is a flat rate per order. Duty is an average across the range.

That hides the products and markets that are losing money. A heavy product going to a distant market with a bad duty rate does not cost three percent, and the average makes it look the same as everything else.

Landed cost can be built per unit now. Actual freight on the actual shipment, duty at the real rate for that code and destination, handling from the 3PL invoice, allocated down to the transaction. The numbers stop being averages and start being decisions you can make.

04 / 04

What controllers do with the time back

The work that gets skipped is the work that pays. Cost structure deep dives. Business cases for the productivity programme. Pricing analysis. Supplier negotiations with real numbers behind them.

None of that gets done when the close takes three weeks. All of it gets done when it takes three days.

This is also the part where the role gets more interesting, which matters when you are trying to keep good controllers.

The gap in most finance teams is time and tooling. The people are capable and they are spending their capability on assembly.

Fix the data underneath, automate the parts that follow rules, and the same team starts finding money instead of reporting on it.