Marketplaces and ticketing
Your marketplace close, prepared at transaction volume
A single sale moves money in several directions: the buyer's payment, the seller's payout, your fee, and sometimes a refund or chargeback. Accounting Agents prepare the reconciliations, revenue schedules and journal entries behind all of it, so your team reviews the exceptions and approves instead of rebuilding the workbook from exports.
Why the marketplace close is hard
Cash moves through processors before it reaches the bank
Buyer payments settle through processors in batches, net of fees, refunds and chargebacks, while seller payouts go out on their own schedule. Tying deposits and payouts back to the GL means matching lines that rarely line up one to one.
Your revenue is a share of someone else's sale
What you earn is a fee or a take rate, and partner agreements can split it again. Under ASC 606 (IFRS 15), a marketplace assesses whether it is the principal or the agent for each good or service it provides, which sets whether revenue is recorded gross or net. The calculation is rebuilt from order data every month.
The transaction detail lives outside the ERP
Orders, refunds and chargebacks usually sit in a data warehouse while the ERP holds summaries. In ticketing, a sale and its event can fall in different periods, and a cancellation can bring refunds after the cash has moved. Every close starts with exports and a workbook rebuilt for each entity and currency.
What the Accounting Agents prepare for you
Bank reconciliation: deposits and payouts matched to the GL, exceptions explained, entries drafted for fees and interest
Cash application: payments from partners and B2B customers matched to open invoices, with unmatched cash coded and a suggested resolution
Revenue sharing: each partner's share calculated from its agreement, with the entry drafted
Revenue recognition: a working paper that applies your revenue policy and timing rules, with recognized and deferred revenue tied to the GL
Intercompany reconciliation: balances matched and eliminated across entities and currencies
Flux analysis: movements in fees, refunds and payouts explained against the transactions that drove them
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
Frequently asked questions
Can Ledge reconcile high-volume marketplace transactions?
Yes. Accounting Agents pull transaction-level data from your banks, your ERP and the exports your data team produces, and match it with deterministic code that applies your rules the same way every period. Ledge connects to 11,000+ banks worldwide, and items that do not match are flagged with the reason.
How does Ledge handle gross versus net revenue and revenue share?
Ledge applies the policy your team has set; the principal or agent judgment stays with you. The Accounting Agent calculates revenue and partner shares under that policy and drafts the entries 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.
Start your next marketplace close with the payouts already tied
Your team spends the close on judgment: the take rate that moved, the refund spike, the payout that did not land.
