Summary
An ecommerce business is audit-ready when every material balance can be traced from the financial statements back to legal entity, store, order, settlement, bank receipt, and inventory movement. Before financing diligence starts, freeze one reporting date, reconcile revenue and cash separately, test inventory ownership and valuation, and give every unresolved difference an owner and deadline.
What does an audit-ready ecommerce evidence chain contain?
An audit-ready chain contains six connected layers: order, fulfillment or return, platform transaction, payout, bank receipt, and general-ledger entry. Each layer needs a stable key such as order ID, transaction ID, payout reference, bank value date, journal number, and legal-entity code; a PDF total without those links is evidence of a balance, not evidence of how the balance was produced.
IRS Publication 583, revised in December 2024, gives the underlying recordkeeping test in plain terms: records should identify receipt sources, track expenses, prepare financial statements and returns, support reported items, and enable bank reconciliation. A marketplace export meets that test only when the business can preserve it, reproduce the calculation, and connect it to the accounting period.
| Layer | Minimum identifiers | Control question |
|---|---|---|
| Commerce | store ID, order ID, order date, currency | Which entity contracted with the customer? |
| Movement | SKU, warehouse, ship or return date | When did control and inventory leave or return? |
| Settlement | transaction type, fee code, payout reference | Which gross items make up the net payout? |
| Accounting | journal ID, account, period, entity code | Can the ledger be rebuilt from preserved source data? |
Why must revenue be reconciled separately from cash?
Revenue and cash answer different questions: revenue asks when control of promised goods or services transferred, while cash asks when a payment processor or marketplace released a net amount. IFRS 15 has applied for annual periods beginning on or after 1 January 2018 and uses five steps: identify the contract, identify performance obligations, determine transaction price, allocate that price, and recognize revenue when obligations are satisfied.
A payout can combine sales from several days with refunds, disputes, advertising charges, reserves, commissions, and currency conversion. Recording only the bank deposit as sales hides both the gross customer transaction and the liabilities or expenses netted before payment, making period cutoff and margin testing unreliable even when the cash account reconciles.
Management should require a gross-to-net bridge by transaction type and then test cutoff on both sides of the reporting date. An unexplained net difference is not automatically an expense: it can be an unrecorded refund, a receivable still held by the platform, a reserve release, a foreign-exchange effect, or a mapping error.
How should inventory evidence survive warehouse and marketplace differences?
Inventory evidence should reconcile quantity, ownership, location, unit cost, and valuation at one reporting date. IAS 2 states that inventory cost includes purchase, conversion, and other costs incurred to bring goods to their present location and condition, and it measures inventory at the lower of cost and net realizable value.
A warehouse count alone cannot prove that the reporting entity owns every unit, while a general-ledger balance cannot prove the goods exist. Build a roll-forward for each material SKU or tested population: opening quantity plus receipts and returns, minus shipments, disposals, and other adjustments, equals closing quantity; then connect unit costs to supplier documents and the chosen cost formula.
Net realizable value needs a separate exception test for aged, damaged, returned, discontinued, or heavily discounted goods. IAS 2 defines that value as estimated selling price less completion and selling costs, so an aging report becomes decision-useful only after expected selling outcomes and necessary costs are documented.
Which four reconciliations should management sign before diligence?
Management should sign four reconciliations before diligence: revenue to commerce data, settlements to bank, inventory subledger to general ledger, and trial balance to financial statements. Each reconciliation needs a preparer, reviewer, reporting date, source-file version, materiality rule, and open-item status rather than a spreadsheet named “final” with no approval history.
- Revenue bridge: reconcile fulfilled or otherwise earned transactions to recognized revenue, refunds, discounts, tax collected, and deferred or unsettled items.
- Cash bridge: reconcile every payout reference to bank value date, processing fees, reserves, chargebacks, and foreign-exchange differences.
- Inventory bridge: reconcile quantities and costs across warehouses, goods in transit, customer returns, write-downs, and the inventory control account.
- Statement bridge: prove that signed ledger balances populate the balance sheet, income statement, and cash-flow statement without manual re-keying.
A reconciliation is complete only when every remaining difference is either corrected or documented with amount, cause, evidence, accounting treatment, owner, and due date. A financing team can then distinguish a known timing item from a control failure instead of discovering both during the same request cycle.
How can the team triage gaps without rebuilding every period?
The team can triage gaps by testing the highest-risk intersections first: legal entity, reporting cutoff, payout currency, refund population, and inventory location. Rebuilding every order from day one is usually unnecessary when the opening balance is supportable and the current-period roll-forward can be reproduced from preserved source files.
| Finding | First test | Decision |
|---|---|---|
| Bank is lower than settlement | payout status, value date, reserve, FX fee | Timing or mapping issue before revenue adjustment |
| Revenue is lower than orders | cancellations, refunds, tax, fulfillment cutoff | Define earned population before posting a plug |
| Warehouse exceeds ledger | ownership, receipts cutoff, goods in transit | Correct the subledger or document third-party stock |
| Old stock has full cost | recent price, selling cost, damage status | Perform IAS 2 net-realizable-value review |
Scope expansion should follow evidence, not anxiety. A difference isolated to one store and two payout cycles calls for a targeted reconstruction; missing entity mappings, unsupported opening inventory, or repeated manual plugs across 12 months can justify a broader rebuild before the audit timetable is fixed.
What should be frozen on day zero of the audit pack?
Day zero should freeze the reporting date, source-file inventory, system access, chart of accounts, entity-and-store map, foreign-exchange source, and named owners. A reproducible pack needs original exports plus transformed workpapers; replacing a marketplace CSV after review begins can silently change transaction status and invalidate prior samples.
Version labels should identify system, entity, store, period, extraction timestamp, and file owner. A practical convention such as shopify-entityA-store03-payouts-2026Q2-v1.csv is more useful than “new final 2.csv,” because reviewers can connect every workbook tab to a preserved source without asking which download was used.
Access should follow least privilege and remain available long enough to answer follow-up questions. The business should also export records before closing a platform account, changing accountants, deregistering an entity, or losing warehouse access; an inaccessible dashboard is not a substitute for retained accounting evidence.
Which sources define the accounting boundary?
Three primary sources define the boundary used here, checked on 26 August 2026. IFRS 15 establishes the contract-to-revenue logic, IAS 2 establishes inventory cost and valuation, and IRS Publication 583 explains why supporting records and bank reconciliation must remain usable; the exact reporting framework and tax jurisdiction still need confirmation for each entity.
- IFRS Foundation — IFRS 15 Revenue from Contracts with Customers
- IFRS Foundation — IAS 2 Inventories
- Internal Revenue Service — Publication 583, Starting a Business and Keeping Records (12/2024)
- Related: accounting for inventory in transit
- Related: reconciling Amazon settlements with the bank
The USD amounts and file name are illustrative, not client results or official thresholds. Audit procedures, materiality, tax retention periods, and required financial statements depend on the entity, jurisdiction, reporting framework, and engagement terms.
Questions finance leaders ask before sign-off
Does a bank reconciliation prove ecommerce revenue?
No. A bank reconciliation proves cash movement, while IFRS 15 recognizes revenue through the contract and transfer of promised goods or services. A marketplace payout can net refunds, fees, reserves, disputes, advertising, and foreign-exchange effects, so revenue needs its own order-to-ledger bridge.
Do warehouse reports prove the inventory balance?
No. Warehouse reports support location and quantity, but the audit file also needs ownership, cutoff, unit cost, and valuation. IAS 2 requires cost support and lower-of-cost-and-net-realizable-value review, while goods in transit and third-party stock require separate ownership evidence.
When is a targeted reconstruction enough?
A targeted reconstruction is enough when the opening balance is supportable and the gap is isolated by store, period, currency, transaction type, or warehouse. Unsupported opening balances, missing entity mappings, or recurring plugs across 12 months are signs that the scope may need to expand.