Why a cost belongs to the month you got the benefit.

Rajat Gupta · 6 min read

Most reporting problems in a manufacturing finance function are not fraud, and not incompetence. They are timing. A cost lands in the month the invoice happened to arrive, or the month the payment cleared, rather than the month the business actually consumed the benefit. Fix that one habit and half of your month-to-month noise disappears.

A cost belongs to the month in which the benefit was received — not the month it was paid, and not the month the invoice reached you.

The travel example

A staff member travels in May, files the claim in June, and finance pays in July. Recorded on a cash basis, the cost appears in July — three months adrift from the activity that caused it. Multiply that across a large team and travel expense becomes a line that swings violently for reasons that have nothing to do with how much anyone travelled.

The fix is a monthly provision at the rolling average, reversed as real claims settle. The month carries a stable, representative charge rather than the accident of when paperwork cleared.

Where it shows up

• Insurance premiums charged in full to the month of payment, instead of spread over the policy.
• Freight on month-end dispatches landing in the next month, while the sale sits in this one.
• Certification and clearing charges following the invoice date rather than the service date.

None of these change the full-year result. All of them distort the month, and the month is what management actually reviews.

The discipline

Provide for what you know happened, spread what covers multiple periods, and identify any prior-period correction separately so it doesn’t contaminate the current month. It is unglamorous work. It is also the difference between an MIS a board trusts and one it quietly second-guesses.