Key takeaways
- Technical skill gets you into the room; being able to explain a number in plain language is what keeps you there.
- Controls work best when the people who own the process helped design them, not when they are imposed from outside.
- Understanding the operations behind the ledger — the factory floor, the shipment, the vendor — changes the quality of every report you produce.
- Automating the repetitive 80% of the job is what creates room for the 20% that actually needs a finance leader's judgment.
I started my finance career the way most people in Bangladesh's manufacturing and export sector do — learning the chart of accounts, closing books month after month, and slowly earning the right to sit in rooms where decisions were made rather than just reported on. Sixteen-plus years later, across FP&A, budgeting, cost control, internal control, audit, tax, VAT, SAP FICO, Tally ERP, Power BI and export-oriented operations, a few lessons kept repeating themselves regardless of the company or the system I was working in. This post is the version of those lessons I wish someone had told me on day one.
1. A correct number is not the same as a useful number
Early in my career I was proud of accuracy for its own sake — a trial balance that tied, a reconciliation with zero variance. That is necessary, but it is not sufficient. The moment that changed how I worked was watching a factory general manager stare at a P&L I had prepared and ask, "So what do I do differently tomorrow morning?" I did not have a good answer. A report that is correct but cannot be acted on has done half its job. Since then, every dashboard and every close pack I build starts from that question: what decision does this number need to support, and for whom?
2. Controls are a partnership, not a policing function
Internal control and audit work only when the people who run the process see the control as protecting them, not accusing them. On SAP FICO implementations and control-strengthening projects, the fastest way to get a reconciliation or an approval workflow ignored within a month is to design it without the process owner in the room. The controls that actually survived contact with daily operations were the ones built together with procurement, warehouse, sales and production teams — where the finance team explained the risk being addressed, and the operational team explained where the theoretical control would break in practice.
3. Know the factory floor, not just the ledger
Working across apparel and garments manufacturing, sourcing and export operations taught me that the most useful finance professionals are the ones who understand what is physically happening behind every journal entry — how a shipment cut-off actually works, why a supplier's invoice might be timed the way it is, what efficiency and standard time mean on a production line. That operational fluency is what let me build models like a workforce productivity-to-profitability framework that connects attendance, efficiency and output directly to cost and profit, rather than treating labor cost as a single abstract line item.
4. Automate the boring 80% early
Every finance career has a point where the manual, repetitive work — data extraction, recurring journals, reconciliation formatting, status chasing — either gets automated or quietly caps how much value you can add. Power BI, Power Query and, more recently, AI tools changed what was possible for me here. The specific tools matter less than the habit: constantly asking which parts of a monthly cycle are pattern-following rather than judgment-requiring, and moving those parts out of manual hands as soon as the underlying process is stable enough to automate safely.
5. Credentials open the door; communication keeps you in the room
My MBA, BBA and postgraduate diploma in ICT — plus the CMA qualification I have been completing in stages alongside full-time work — gave me the technical grounding and, honestly, the credibility to be considered for senior roles. But credentials answer "can this person be trusted with the numbers." They do not answer "can this person explain the numbers to a non-finance leadership team under time pressure." That second skill is trained separately, usually the hard way — in monthly business reviews, in board packs, in moments where a variance needs a two-sentence explanation, not a ten-slide appendix.
Why I write this down
I write the technical Finance Insights articles on this site because I think structured, anonymized case studies are useful to other finance professionals. I am writing this post because the lessons above are less structured and more personal — the kind of thing that usually only gets passed on in a one-to-one conversation with someone earlier in their career. If any of it is useful to you, that is the point of putting it here.
Written by Liakat Hossain
Finance and accounts professional with experience in FP&A, SAP FICO, Power BI, internal control, reporting, audit, tax, VAT and export-oriented business operations.
This is an original blog post written by Liakat Hossain, drawing on his own professional and personal experience. It is a personal reflection, not regulatory, tax, legal or investment advice; verify any technical or professional point against current standards before relying on it.