Nearshore vs offshore for accounting work: how to tell which one a role needs

A controller looking for a senior accountant hears two words for what sounds like one idea. Nearshore usually means the seat sits in Latin America, in a time zone next to yours. Offshore, for a US company, usually means the seat sits in the Philippines or India, on the other side of the day. The words describe distance. The decision does not.

The thing distance is supposed to settle, whether the operator is present while your business is running, gets settled before geography enters. An embedded seat works your hours wherever it sits, and a seat that does not is a different product with a different name. So the comparison has to be made on what is left once presence is off the table. That is a shorter list than the search results suggest.

What nearshore and offshore mean for an accounting seat

Nearshore and offshore differ in whose daytime the seat runs on, and in very little else the accounting work can feel.

With a nearshore seat, the operator's own daytime and yours coincide. A person in Mexico City or Bogotá is at their desk during your close because that is when their day happens. With an offshore seat run at full overlap, the operator's working day is your working day, and the local clock is doing something else. The Philippine ecosystem formed around exactly that arrangement. We have written about how that ecosystem was built, and how it differs from India's, so this piece will not retell it.

From the controller's chair, the two look the same. Someone is at the desk when a reconciliation is needed before review. An invoice coded to the wrong account gets fixed today and posted today. A reviewer's question gets answered while the reviewer is still looking at the page. Presence is what both geographies deliver.

Where nearshore is the better answer

Nearshore is the better answer whenever the role needs something only the geography can supply, and there are three of those.

• A language. If the seat talks to customers, vendors, or a subsidiary's finance team in Spanish or Portuguese, a collections seat working Spanish-speaking accounts, say, or an AP seat coordinating with vendors in Mexico, the geography is doing real work. Build the seat where the language lives.
• A body in a building. Some roles need a person on site on a cadence: a quarterly week at the plant, a physical count, a walk through a warehouse. A flight measured in hours rather than a day is a structural fact, and it points nearshore.
• A Latin American entity. If the company runs a plant or a subsidiary in the region and the seat keeps that entity's books under local rules, the seat belongs near the entity and near the people who answer for it.

If any of the three is true of the role, the case for nearshore is structural and we would say so in the first conversation. Most accounting seats a US middle-market controller is trying to fill need none of the three, which is when the decision moves to the harder question.

Overlap is settled before geography is

All of it, to start. We have written separately about how much time zone overlap an offshore team needs, and the conclusion is the one this piece runs on. Start at full overlap. Treat less than that as something a company earns later, once it has built the management layer that stands in for the shared hours.

Accounting work makes the case on its own. Close week runs on a calendar, and the preparation that fills it has to be ready when the reviewer sits down, which means it gets built during the same day the questions arrive. We have set out which parts of the close an offshore finance seat can own and which stay with the controller who signs. Every item on the owning side is done live.

That is why overlap does not separate nearshore from offshore. Both keep the operator on your clock all day. What separates them is the three items above, and, once those are cleared, the shape of the work.

Past the three, the shape of the work decides

Once a role clears the three tests, the deciding axis is the shape of the work, and cost is not it.

Whether nearshore costs more than offshore gets asked in every one of these conversations, and we would not decide on it. Rates move by role, by seniority, and by year, so a seat chosen on rate has been chosen on the variable that changes fastest. The shape of the work does not change. A senior accountant's seat inside one company is made of work that repeats every cycle, can be written down, and gets done live against a close date, and it holds context from one cycle to the next. That work cannot be specified once and sent away to be finished, and it cannot be parceled out between clients without losing what made it valuable.

Of the two offshore ecosystems, the Philippine one took its shape from this kind of work. Philippines or India is a separate decision inside offshore, and the piece linked above makes it. Which stream of accounting work should go into a first seat is a third question with its own test.

Geography decides a role only when the role needs something only a geography can supply. Past that, the shape of the work decides.

Why Kayana builds accounting seats in the Philippines

Kayana builds in the Philippines because the accounting seats our clients define are embedded, recurring, and live, and that is the shape of work the Philippine ecosystem formed around. The seat runs on the client's day from the first hour to the last, nine to five Central unless the client sets a different window, embedded in one company and never split between clients. The Seat is yours, and so is the definition of done. Everything around it is ours to run: the window, the cadence, the community, the stewardship.

A company that keeps defining seats like that ends up holding the Mini-GCC model, a GCC without the entity, the real estate, or the multi-year build. The geography decision is made once and lived with for years, and it only holds if the operator does. Voluntary turnover across the teams we build runs 3–5% in year one.

Quick answers

Where a seat sits is one of the design decisions the book works through. Operational Alpha →