A multichannel retail close should reconcile each sales channel's activity, payment clearing balance and inventory movement before consolidating the results in NetSuite. Use one consistent cutoff policy while preserving channel-specific evidence. A bank deposit alone cannot explain gross sales, refunds, fees, tax and unsettled funds.
The close owner needs a bridge from operational transactions to the ledger, with separate responsibility for store operations, ecommerce, marketplaces and finance. This guide addresses the close process across channels rather than the configuration of an individual commerce connector.
List every store, website, marketplace, payment account and fulfillment location. Record which legal entity trades through each channel and which currencies it uses. Include inactive channels with open returns or unsettled balances.
Agree whether transactions enter NetSuite individually or through controlled summaries. A summarized feed still needs enough detail in the source archive to investigate tax, refunds and customer disputes. Define stable batch references and retention requirements.
Document the cutoff time and timezone for each source. A sale shortly after midnight in one system can belong to the previous business day in another. Reconcile the difference explicitly rather than treating date mismatches as integration failures.
Compare source order or till totals with the imported sales population. Identify cancelled orders, unfulfilled orders, discounts, shipping charges and other adjustments according to the approved accounting model. Do not assume every accepted order is recognized revenue.
Check completeness using record counts, monetary totals and the oldest unprocessed transaction. A total can agree by coincidence if one missing sale offsets one duplicate. Preserve both record-level checks and control totals.
Review cross-channel returns. A store may accept a web purchase, but the physical receipt, customer credit and payment refund can belong to different source systems. Retain the original transaction reference so the business does not reverse the sale twice.
For each provider and currency, explain the opening clearing balance, new activity, payouts and ending balance. Classify fees, refunds, disputes and supported adjustments. Match each completed payout to bank evidence and track timing differences separately.
Stripe's Balance report is designed around balance movement, while payout-focused reconciliation uses a different view. Shopify also exposes payout and transaction details for review and export. Choose evidence appropriate to the provider and payout method instead of forcing all channels into one unsupported settlement assumption.
Assign owners to unresolved provider balances. A missing bank deposit may be a payout timing issue, failed transfer or incorrect account mapping; the team needs evidence before deciding which explanation applies.
Reconcile sales quantities with fulfillment or store inventory movements under the selected transaction design. Review returns, shrinkage, store transfers and goods held by fulfillment partners. A payment reconciliation can be complete while the inventory result remains wrong.
Oracle's inventory valuation reports provide item quantity and value views and transaction drilldown. Use the relevant reports within a clearly defined account and location population, with separate support for balances such as in-transit stock.
Review late receipts and costing changes before finalizing margin. If a channel feed creates sales without the intended inventory effect, the error may appear as an unusually high margin rather than an obvious missing transaction.
A retailer has 100,000 currency units of gross customer charges across stores and its website during the selected period. Completed refunds total 8,000 and payment fees total 3,000. Assume no other provider adjustments and an opening clearing balance of zero.
The resulting net provider activity is 89,000. If 80,000 reaches the bank by the cutoff, the remaining 9,000 needs support as a provider balance or payout in transit. It is not automatically another sale or an unexplained loss.
The controller separately reviews which charges represent sales, tax, deposits or other categories and confirms inventory cost. These figures are hypothetical and simplify the source activity to demonstrate the bridge; actual reporting must use the approved accounting and tax policies.
Start by confirming source completeness and processing failures. Next, reconcile channel sales and returns. Then reconcile payment-provider balances and bank payouts. Complete inventory and cost review before approving final channel margin and consolidated reporting.
Some work can run in parallel, but signoff dependencies should remain explicit. The finance reviewer should know if the warehouse is still resolving a material missing shipment or if a marketplace settlement file has not arrived.
Keep an exception register with amount, channel, source reference, owner, expected resolution and accounting decision. Distinguish a supported timing difference from an unresolved error. Repeated timing explanations should be tested against subsequent settlement.
For every channel, retain:
Assign one person to confirm that all channels are included. Local teams can complete their own reconciliations while the consolidated close still omits a newly launched marketplace.
After signoff, review the causes of late or manual work. Fix recurring mappings, missing identifiers and unclear ownership at source. Measure the age and value of unresolved differences rather than rewarding speed alone.
A reliable retail close lets finance explain how every channel contributed to revenue, cash and inventory. Standardize the control questions, keep provider-specific evidence intact and make unresolved balances visible before the final reports are approved.