I’ve seen this play out many times. Finance processes like invoicing, payments, and reporting get moved to a central team (GBS) to save cost and improve efficiency. On paper, it works. But in reality, many organizations end up moving the same problems just to a different location. If a process is slow, manual, and full of errors in one place, moving it without fixing it doesn’t solve anything but it simply relocates inefficiency at scale. The better approach is simple, first simplify the process, then standardize it, automate where possible, and only then move it. That’s how you move better work and not broken work.
Another common issue is treating finance activities as separate pieces. Payments, collections, and accounting are all connected but many GBS setups handle them in silos. The result? Missed opportunities and ongoing inefficiencies. When done right, these processes should work together faster invoicing improves collections, better collections improve cash flow, and accurate accounting improves reporting. Without this end-to-end thinking, organizations fix parts of the problem, but never the whole system.
Finally, most GBS setups focus on doing the same work faster and cheaper. But today, finance is expected to do more than just process transactions. It needs to support better decisions. That means giving clear visibility on cash, identifying risks early, and providing insights that leaders can actually use. Setting up a Finance GBS is not just about cost savings but it’s about building a system that works smarter.
Don’t just move processes: fix them first
Don’t just centralize work: connect it end-to-end
Don’t just focus on efficiency: focus on usefulness