A slow close is rarely a lack of effort. Inputs have no cutoff, China and U.S. times are mixed, issues lack owners, or platforms, Payroll, inventory and intercompany teams work from different versions.

1. Day 0–2: lock inputs and prove cash completeness

Start before month-end. On Day 0, confirm owners, formats and due times for banks, cards, platforms, Payroll, receivables, payables, inventory and intercompany data. Show China Standard Time and each U.S. owner's local zone. Build holidays and IRS and state filing dates into the calendar before a due date arrives with nobody online.

On Days 1–2, import and reconcile bank, card and payment accounts and lock Amazon, Shopify and Stripe settlement batches. Route unusual cash, duplicates, unknown transfers and cross-entity payments to an issue log instead of clearing them to miscellaneous expense. IRS Publication 583's recordkeeping concepts become operational when every transaction remains traceable to evidence.

  • Day 0: input list, time zones and owners
  • Day 1: bank, card and payment-account imports
  • Day 2: cash reconciliation, settlements and outstanding items
  • Every exception receives an amount, owner and due time

2. Day 3–4: close transaction cycles and Payroll

On Day 3, close payables and expenses. Collect vendor invoices, employee reimbursements, prepayments, fixed assets and related-party payments, then perform cutoff testing. Keep invoice date, service period, receipt date and payment date distinct so a China cash-basis workflow does not conflict invisibly with a U.S. invoice-based entry.

On Day 4, complete receivables, revenue and Payroll. Decompose platform activity into gross sales, refunds, fees, taxes, reserves and net cash. Reconcile the Payroll register to bank cash, wage expense, employee withholding and employer-tax liabilities. Retain the provider's source report and journal mapping for every adjustment.

  • AP cutoff, accruals, prepayments and fixed assets
  • AR aging, revenue cutoff and credit memos
  • Gross-to-net platform settlement bridges
  • Four-way Payroll register, cash, expense and liability tie-out

3. Day 5–6: inventory, intercompany and currency

On Day 5, reconcile inventory quantity and value across ERP, warehouses, FBA, 3PLs, goods in transit and the ledger. Apply approved treatment for purchase price, duty, freight and other landed cost. Returns, scrap, samples and negative inventory should be visible exceptions; a single top-side entry must not hide a location or ownership problem.

On Day 6, exchange intercompany confirmations. Match due-to and due-from, invoices, payments, allocations and currency using one transaction ID. Confirm transaction currency, book currency, period-end rate source and FX difference. China uploads support before sign-off; the U.S. owner updates the same issue ID, enabling a controlled follow-the-sun handoff.

  • Inventory location, title, transit and returns
  • Quantity-to-ledger and landed-cost bridge
  • Transaction-level intercompany confirmation
  • Common rate source, date and translation layer

4. Day 7–8: tax, adjustments and management review

On Day 7, reconcile Sales Tax, Payroll tax, estimated income tax and other state-tax liabilities, and update fixed-asset, lease, prepaid, accrual and deferred-item roll-forwards. Connect tax accounts to returns, marketplace collection reports and payment evidence. Even outside a filing month, the liability movement must be explained.

On Day 8, an independent reviewer examines balance sheet, income statement, cash flow, budget variances and unusual journals. Evidence states what was tested, the exception, conclusion and date—not merely “OK” in chat. PCAOB and SEC control materials apply to particular regulated settings, but their evidence and responsibility principles also help private cross-border teams design reviewable processes.

  • Tax-liability roll-forward to returns or agency accounts
  • Fixed assets, prepayments, accruals and key accounts
  • Large, manual, nonrecurring and cross-entity journals
  • Budget, prior-month and prior-year variance analysis

5. Day 9–10: resolve exceptions, publish and lock

On Day 9, hold a short bilingual close review limited to overdue or above-threshold issues. Decide whether each item is adjusted, disclosed, carried with a date or escalated, and record the approver. Use a fixed management package to bridge major changes in sales, margin, cash, working capital, tax and intercompany balances.

On Day 10, publish numbered reports and support, obtain sign-off and set the system close date. A late change requires a reopen request stating cause, amount, affected reports and reapproval; correct the root cause in the next pre-close. Close maturity is measured by fewer exceptions and less rework, not by unresolved items kept outside the ledger.

  • Day 9: exception decisions and management-package review
  • Day 10: versioned release, sign-off and lock
  • Late changes follow reopen and republication
  • Recurring exceptions become next-cycle improvements