Library · Payments · How to run this
Marketplace payout is not CRM sold
Digistore24-class marketplaces pay vendors on a lag. CRM still shows sold today. Bidding the CRM line as if the payout already cleared invents float.
Pair: Marketplace payout lag on Payments. Three books: tracker vs CRM vs settled. Two locks: holdback vs reserve.
What you type
CRM sold $ for the sale window.
Payout $ that hit (or is scheduled) for those sales after the marketplace lag.
Lag days from the written vendor schedule (not a blog “typical”).
Gap = CRM − payout. That slice is still in marketplace float, fees, or hold — not bid cash.
What not to do
Do not bid CRM sold as bank. Do not invent lag days. Do not mix processor settled into this payout line. Do not skip naming timezone.
Related: Payments, tracker vs CRM vs settled, holdback vs reserve, payout delay.
Procedure
- Type CRM sold $ for the sale window.
- Type marketplace payout $ for those sales.
- Type written lag days. Bid after payout, not CRM.
Failure modes
- Bidding CRM sold as bank cash.
- Inventing lag days.
- Mixing processor settled into marketplace payout.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Payout lag
- Written days between marketplace sale and vendor payout. Typed from the schedule, not invented.
Work with us — We run this job on your accounts. Services
FAQ
- Is this tracker vs CRM vs settled?
- No. [Three books](/manuals/tracker-vs-crm-vs-settled) recon tracker, CRM, and processor. This page is marketplace vendor payout lag vs CRM sold.
- Is this holdback vs reserve?
- No. [Holdback vs reserve](/manuals/marketplace-holdback-vs-reserve) compares two cash locks. This page is when payout cash actually arrives vs CRM.
- Can I invent a typical payout lag?
- No. Type the written lag days from the marketplace schedule.