Ecommerce and consumer

Your ecommerce close, prepared from payout to COGS

Payouts from every processor and marketplace, returns, inventory and cost of goods all land in the same close. Accounting Agents prepare that work inside your close checklist, so your team reviews and approves it, then turns to margin by channel and product.

Why the ecommerce close is hard

What customers pay rarely matches what lands in the bank

Processors and marketplaces deposit net of fees, refunds, chargebacks and reserves, each on its own schedule and export. Tying gross sales to each deposit means matching settlement files line by line.

Returns, promotions and gift cards move revenue

Refunds, store credit, discounts and unredeemed gift cards change what you recognize and what you owe, and subscription or prepaid orders add deferred revenue to roll forward. Under ASC 606 and IFRS 15, revenue is recognized net of expected returns, with a refund liability for the amount you expect to give back.

Inventory detail lives outside the GL

Stock sits across warehouses, 3PLs and the fulfillment platform, while the GL holds one balance. Proving COGS matches what shipped means pulling order, fulfillment and 3PL data into one workbook, and returns that come back to stock move it again.

What the Accounting Agents prepare for you

Bank reconciliation: processor and marketplace payouts tied to the bank and clearing accounts, fees, refunds and chargebacks broken out, and entries drafted for missing items

Cash application: wholesale and retail customer payments matched to open invoices, including short payments and deductions, with unmatched cash coded and a suggested resolution

Deferred revenue schedule: subscription and prepaid balances rolled forward and recognized on schedule, with gift card balances rolled forward alongside

Inventory reconciliation: warehouse and 3PL stock reports tied to the inventory subledger and the GL by SKU and location, with each discrepancy flagged

Cost of goods sold reconciliation: COGS matched to inventory relief and shipments, with gaps such as a shipment without relief surfaced for review

Flux analysis: variance commentary on revenue, returns, shipping and margin, tied to specific transactions

How it works

1

Connect your ERP and data.

Ledge connects to NetSuite or Sage Intacct and your banks through 150+ native integrations, and works from the exports and schedules your team already keeps.

2

Accounting Agents prepare the work in your logic and format.

Each Accounting Agent runs deterministic code built around your rules and workbook layout, and builds working papers with live formulas, every figure traced to source, the same way every period.

3

Your team reviews and approves.

You're in control. You review the exceptions, and the Accounting Agent drafts the entry and posts it to your ERP once you approve.

Customers

FabFitFun

FabFitFun's finance team uses Ledge.

Frequently asked questions

Can Ledge reconcile processor and marketplace payouts to the bank?

Yes. An Accounting Agent matches each payout to the bank deposit, separates fees, refunds and chargebacks, and flags what it cannot match with a suggested resolution instead of forcing it.

Can Ledge tie inventory and COGS across warehouses and 3PLs?

Yes. Accounting Agents compare each warehouse and 3PL stock report with the subledger and the GL by SKU, check COGS against inventory relief and shipments, and route every gap to your team for review.

Which ERPs does Ledge work with?

Ledge connects natively to NetSuite and Sage Intacct, reading your ERP data and posting approved journal entries back to it. If your team runs another ERP, join the waiting list and we will email you the moment Ledge supports it.

Do Accounting Agents post journal entries on their own?

No. Every Accounting Agent runs deterministic code configured to your logic, waits for your approval before anything reaches the ERP, and logs every step for your auditors.

Start your next ecommerce close with payouts and COGS already tied

Ledge

Ledge prepares the financial close, so accounting teams review instead of rebuild.

Ledge