What an offshore finance team can own, and what stays with your controller

Close week has a shape every controller recognizes. Reconciliations that have to be pulled before anything can be reviewed. An intercompany schedule that needs two systems open side by side. An accrual nobody can book until a vendor answers an email. A reporting pack rebuilt by hand because the system output has never quite matched what the board wants to see.

Most of that week is preparation. A smaller part of it is judgment. When a finance team is stretched, the two run together, and the person whose name ends up on the statements spends most of close week on the part that could have been finished before they opened the file.

What an offshore finance team can own

An offshore finance seat can own the recurring, definable preparation that the close and the reporting cycle run on. At a middle-market company that is a longer list than most teams expect.

• Reconciliations. Bank, credit card, intercompany, and balance sheet accounts, prepared to a defined standard and delivered with the support attached.
• Close preparation. The checklist run, recurring journal entries drafted, schedules built, and open items flagged before review rather than during it.
• AR and collections follow-up. Aging worked daily, dunning sequences run, disputes logged and escalated, cash application kept current.
• AP processing and vendor coordination. Invoice entry and coding to the rules you set, match exceptions surfaced, vendor statements reconciled, payment runs prepared for approval.
• The reporting pack. Monthly and weekly management reporting assembled to the same template every cycle, variances calculated and annotated, and the questions the board asked last month answered before it asks again.
• Analysis support. Budget-versus-actual build, department detail, KPI dashboards maintained, and the data pulls an FP&A lead currently does personally at eleven at night.

Two more streams belong on the list at any company that has recently converted an ERP or absorbed an add-on: chart-of-accounts discipline, and master-data cleanup on the vendor and customer side. Both are recurring, both are definable, and both tend to sit with whoever has the most context and the least time.

What every item shares is that “done” can be written down. Someone can define it in a paragraph and point at a good example of it. Work that clears that bar can be owned by a person outside your building. Work that falls short of it is not ready to hand to anyone yet, and that readiness question has its own answer in the 3C Test for choosing which stream of work goes first.

What stays with your controller

Everything that ends in a judgment somebody has to stand behind stays in-house.

• The sign-off. The controller or CFO reviews and approves the close and owns the accuracy of what leaves the building.
• Accounting judgment. Revenue recognition calls, reserve and allowance estimates, impairment, capitalization decisions, and anything where the policy has to be interpreted before it can be applied.
• Controls and segregation of duties. Approval thresholds, payment release, master-data change rights, and the design of who is permitted to do what.
• The external relationships. Auditors, tax preparers, lenders, and the sponsor's finance team. The person answering those questions should be the person accountable for the answer.
• Anything statutory. Audit, attest work, and tax filings are professional engagements. An embedded seat prepares support for them and does not perform them.
• The board and sponsor narrative. The number gets prepared. The story about what the number means is the CFO's.

None of that is a ceiling on the person in the seat. Operators recruited out of the GCCs the Fortune 500 built work at that caliber. It is an accountability boundary, and it holds because finance leadership is accountable to a board, a lender, and an auditor who are each entitled to one name.

The line is drawn by the signature

The useful test is a signature. Ask where a piece of work ends. If it ends in a prepared, reviewable artifact, a seat can own it. If it ends in a decision someone has to put their name to, it belongs to the person whose name it is.

That test holds up better than the two most teams reach for first. Sorting by seniority sends a capable operator to junior work and leaves the controller doing preparation, which is the arrangement a stretched finance team already has. Sorting by difficulty keeps the interesting work upstairs and hands off the tedium, which produces a seat nobody grows in and a controller whose week has not changed.

Preparation can be owned by the seat. Judgment stays with the signature. Most of close week is preparation.

Can an offshore finance team run the month-end close?

It can run the preparation and the mechanics of the close, and it should not run the sign-off. That distinction is worth more than it sounds. A close that arrives at the controller's desk already reconciled, with schedules built, variances annotated, and open items listed, is a different week than a close that starts there. The first is review. The second is assembly followed by review, performed by the most expensive person in the department.

There is a sequencing point underneath it. A close is monthly, and monthly work makes a poor first assignment for a new seat. Inside the close, though, the work that actually consumes the month runs weekly: AR follow-up, cash application, accrual tracking, close prep. That slice is where a first seat starts, and it is why the close usually improves before anyone has formally handed the close over.

Two adjacent questions have answers of their own. Whether a recurring finance stream belongs inside the company at all is settled by the Own vs. Rent rule. And if the volume arrived with a deal rather than with growth, where the back-office work goes after a bolt-on is this question written for the ninety days after a close.

Why the eleventh close is the one that matters

Finance work gets better with repetition, and only when the same person is doing the repeating. Someone who has closed your books eleven times knows which account always needs a manual entry, which vendor always bills late, and which branch's numbers are worth a second look before they reach the board. None of that lives in a process document. It lives in a person, and only if the person stays.

That is what Kayana builds. An embedded finance seat, recruited at the level the GCCs the Fortune 500 built recruit at, running inside your close calendar and your ERP, designed around the streams above. You define the work and what “done” means. We design and run the environment around it. Grown seat by seat, that layer is the Mini-GCC model. One of the companies we work with, a $75M PE-backed operator, grew its embedded team to 10+ seats exactly that way. Voluntary turnover across the teams we build runs 3–5% in year one, which is the part that makes the eleventh close better than the first.

Quick answers

The design principles behind an operating layer that compounds are the subject of the book. Operational Alpha →