Month-End Close When Your Bookkeeper Is Ten Hours Ahead

A close across a ten-hour gap works when it is designed as a relay, not a meeting. The offshore team does everything that needs only data and the firm's written rules while the US team is asleep. It sends one structured written handoff at the end of its day, and the US team answers the open questions in a single batch the next morning. Two conversations need to be live each month: a short kick-off on the first working day and a review of the draft close package. Everything else moves faster in writing. Most failed offshore closes fail at the handoff, not in the accounting.

The actual time difference

India Standard Time is UTC+5:30 all year, and India does not change its clocks. The gap therefore moves twice a year with US and UK daylight saving. In 2026, US clocks went forward on 8 March and went back on 1 November. UK clocks changed on 29 March and 25 October.

A 9:00 start in each city falls at these times in India, winter and summer:

• New York (Eastern): 19:30 in winter, 18:30 in summer
• Chicago (Central): 20:30 in winter, 19:30 in summer
• Los Angeles (Pacific): 22:30 in winter, 21:30 in summer
• London: 14:30 in winter, 13:30 in summer

For a firm on US Eastern time, the gap is 10.5 hours in winter and 9.5 hours in summer. In practice, a reliable overlap window is the first one or two hours of the US morning, which is early evening in India. Put both scheduled calls inside that window. Agree it in writing, and recheck it in the weeks around each clock change.

What the offshore team can finish overnight

Anything that needs only the data and the firm's written conventions should be done before the US team wakes up.

• Bank and card feeds: categorising transactions, applying rules, and matching receipts to invoices and payments to bills.
• Reconciliations: every bank, card, loan and clearing account, with reports saved.
• Standing entries: depreciation, prepayment amortisation, recurring accruals from an agreed schedule, and payroll journals from payroll reports.
• Sub-ledger checks: receivables and payables ageing reviewed for credits, duplicates and stale items; inter-company balances matched.
• The draft package: profit and loss and balance sheet, with variance commentary drafted wherever the cause is visible from the ledger.
• The question log: every item that could not be finished, written as a question the US team can answer in one line.

What has to wait for an answer

Some items cannot be finished without the firm or its client, however good the offshore team is. The aim is not to avoid these. It is to raise them early, all together, and in a form that is quick to answer.

• Unknown transactions: a payee nobody recognises, or a transfer with no description.
• Missing documents: an invoice the client has not sent, or a statement not yet available.
• Judgment calls: whether a purchase is capital or revenue, whether an accrual is needed, or how to treat something new.
• Approvals: journal entries above an agreed threshold, write-offs and reclassifications.
• Client confirmations: balances that need the client to say yes before they can be relied on.

The overnight queue and the written handoff

The handoff is the core of the process. Send it at the same time every working day, in the same format, in one place. That might be a shared document, a ticket board or a fixed channel, but not scattered emails.

A workable format has five headings:

1. Done today, by client: what was completed, in a line each.
2. Blocked, by client: what cannot proceed, and on what.
3. Questions, numbered, each answerable briefly. Write "Payment of $1,240 to ABC LLC on 14th: supplier, customer refund or owner expense?" rather than "Please look at the bank feed."
4. Decisions needed by, with the date or time after which the close date is at risk.
5. Tomorrow: what the team will work on next, so the US side knows what its answers will unblock.

The US team answers in the same place, against the question numbers, as the first task of its day. The offshore team picks up the answers at the start of its own day and works through them. Done this way, a question raised on Monday evening in India is answered on Monday morning in the US and actioned on Tuesday in India. Each question costs one day, not three.

Two rules keep the queue moving.

• Batch, never trickle. Twenty questions in one list get answered in twenty minutes. The same twenty sent one at a time across a day often take a week.
• Every answer becomes a rule. When the answer is a coding decision, add it to the conventions document. The same question should not be asked twice.

Why a daily written handoff works better than a daily call

A daily call sounds collaborative, but across this gap it costs more than it returns. It falls at the end of the offshore team's day and the start of the US team's. Nothing is written down unless someone takes notes. Questions get answered from memory, without the ledger open. And it does not scale. With ten clients, a daily call either runs long or skips most of them.

A written handoff is searchable and answerable at the reader's convenience. Once each answer is recorded as a rule, it also becomes the firm's audit trail for why items were coded the way they were.

The two calls that need to be live

1. Kick-off, on the first working day of the close. Fifteen minutes. It covers changes in scope, clients with known issues this month, deadlines that have moved, and anything the US team knows that is not yet in the ledger: a new loan, a terminated employee, a large one-off sale.
2. Draft package review, once the package is ready. Thirty to forty-five minutes. Walk through the variance commentary and the open items, agree the adjustments, and decide what goes to the client. This is where judgment is applied together, and it is worth the inconvenient hour.

Anything urgent between those two goes through the agreed escalation path, not a standing meeting.

A sample close calendar

For a firm that aims to deliver client packages by the seventh working day:

• Day 1: kick-off call; offshore team pulls statements and starts reconciliations.
• Days 1 to 3: reconciliations, standing entries and categorisation completed overnight; the first question batch is sent at the end of Day 1.
• Days 3 to 4: answers applied; remaining items chased; draft package prepared.
• Day 5: draft package review call; adjustments agreed.
• Days 6 to 7: final package issued; month locked with a closing date.

Some clients will always be later because their documents are. The calendar should say so in advance rather than treat every late client as an exception.

Where this fits

The handoff only works if the groundwork is in place: access, conventions and prior-period records. That is covered in what your offshore bookkeeper needs from you before day one.

Wissen Solutions runs month-end close for accounting firms on this model, with overlapping hours for US and UK teams, through our QuickBooks Online and offshore accounting services.

Sources

• Time differences and 2026 daylight-saving change dates calculated from the IANA time zone database (zones Asia/Kolkata, America/New_York, America/Chicago, America/Los_Angeles, Europe/London), checked 24 October 2026.