Your marketplace dashboard says you earned $1,000 last month. Your bank account received $850. And the tax form the platform sends you — if it sends one at all — will show the bigger number, not the deposit you actually got to keep. If your books record only the $850 that landed, you have a mismatch sitting in your ledger that will surface at tax time, when the information return the platform filed says your revenue was 15 to 30 percent higher than what you reported.
This is the central bookkeeping problem of selling AI agents and skills through a marketplace: the platform takes its commission before you ever see the money, the payout you receive is already net, and every downstream record — your revenue, your tax return, your margin math — needs the gross figures you never touched. Here is how the AI marketplaces actually pay, how to record each payout so gross and net stay reconciled, and which tax forms to expect.
What the AI marketplaces actually pay in late 2026
Before booking anything, get clear on which payout model you are on, because the AI marketplaces do not all work the way app stores do.
The GPT Store pays on engagement, not as a percentage. OpenAI's builder program compensates creators based on user engagement with their GPTs — roughly $0.03 per conversation on average, by third-party estimates — rather than taking a 15 or 30 percent cut of a sale price. The program has stayed a limited, criteria-based rollout, and most individual creators land in the low hundreds of dollars a month unless their usage is enormous. There is no commission to book here at all: the payout is a single revenue line, and your job is reconciling the conversation count times the effective rate against what arrives.
There is also a clock running. Personal ChatGPT accounts can no longer create or publish new GPTs, and OpenAI has scheduled existing custom GPTs to retire on December 11, 2026, with enterprise workspaces on an approved deferral getting until February 11, 2027. The replacement is plugins built through the Apps SDK, whose usage-based developer payments have been discussed but not broadly deployed. If GPT Store payouts are a line on your books, plan for that line to end and to be replaced by something with different reporting.
Claude Skills has no official marketplace or revenue share. Anthropic publishes the Agent Skills standard and its own free skills, but as of this year there is no first-party store with built-in payments. Builders monetize indirectly: a branded skill that funnels users to a paid subscription tier, a skill that routes to the builder's own metered API endpoints, or skills built for enterprise clients under direct contract. Each of those is ordinary product or services revenue on your books, not marketplace revenue.
Third-party skills marketplaces do take percentage commissions — and they differ. This is where the sliding-scale question actually bites. Independent marketplaces for Claude-style skills publish their own splits: one takes 8 percent with the creator keeping 92 percent, another pays creators 70 percent of the paid skill price with payouts over Stripe Connect. List the same skill on two marketplaces and you are booking two different commission rates against two different payout schedules. The mechanics below work for any percentage; the worked examples use 15 percent because that is the most common small-seller tier across platform commerce.
The 15-to-30 percent shape comes from the app stores. Apple's standard commission is 30 percent of each sale, cut to 15 percent for developers in the App Store Small Business Program — those with under $1 million in annual proceeds. AI marketplaces borrow this tiered shape: a standard rate with a reduced small-seller tier, sometimes with the rate stepping up once your trailing-twelve-month volume crosses a threshold. When your commission rate depends on your own sales volume, every payout needs a rate check, not just an amount check — which is exactly the reconciliation loop below.
Gross or net: the one decision that controls your books
When a marketplace sells your skill for $49, keeps $7.35, and sends you $41.65, you have two ways to record it. Only one of them is right.
Record the gross sale as your revenue and the commission as your expense. Under the ASC 606 principal-versus-agent framework, the question is who controls the product before it reaches the customer. Your skill is your product: you built it, you set the price, you support the buyer. The marketplace merely arranges the sale and processes payment, which makes it the agent and you the principal. Principals report gross revenue. The platform's cut is your selling expense — the cost of distributing through someone else's storefront.
This is not an academic distinction. It changes three numbers you care about:
Your tax forms report gross. Information returns from marketplaces and payment processors show the full sale amounts flowing to you before fees. If your ledger shows only net deposits as revenue, the return you file will disagree with the forms the IRS already received, and that mismatch is one of the most common triggers for an automated notice. Booking gross revenue with a separate commission expense makes your books agree with the paperwork by construction.
Your margins stay honest. A skill that sells for $49 with a $7.35 platform fee earns you $41.65 whether you book gross or net — gross profit is identical either way. But net-only booking hides the fee inside a smaller revenue number, so when the platform raises its rate or you cross into a higher tier, the damage shows up as mysteriously shrinking revenue instead of a clearly labeled rising expense. Separate lines let you see the fee line move.
Your per-platform comparison stays possible. If you sell on two marketplaces at different commission rates, gross booking with per-platform fee accounts tells you exactly what each channel costs. Net-only booking blends the channel economics into one number you cannot decompose.
Where the commission line belongs
Book platform commissions as a selling or distribution expense, alongside payment-processing fees — not as cost of goods sold and not netted against revenue. COGS is for the costs of delivering the product itself: your API inference bills, hosting, metered upstream services. The marketplace fee is the cost of acquiring the sale through that channel. Keeping it below the gross-profit line means your gross margin reflects your product economics (price minus delivery cost), while your operating margin reflects your channel choices. When a marketplace raises its take rate, you want that to show up as a selling-expense increase you can react to — by repricing, by renegotiating, or by leaving — not as a gross-margin decline that looks like your product got more expensive to run.
The monthly reconciliation loop
Every payout, on every marketplace, goes through the same four-step loop. Do it monthly, per platform, before you close the books.
1. Pull the payout report, not just the deposit
The bank deposit is one number. The payout report behind it has at least five: gross sales, platform commission, refunds and chargebacks, any withholding or reserves held back, and the net payout. Download the report in the finest granularity the platform offers — per-transaction if available — because step 3 needs it. If the platform reports in something other than dollars per sale (conversation counts for engagement payouts, metered API units for usage-based skills), pull the usage report too: units times the contracted rate is the gross you are reconciling against.
2. Verify the commission rate before the amounts
On a tiered platform, the rate is a moving part. Check which tier each sale fell into: did any sales happen after you crossed into a higher bracket mid-period? Did a promotional rate expire? A payout that applies last month's 15 percent to sales that should have been charged this month's tier (or vice versa) is a platform error you can only catch by recomputing the fee yourself from the per-sale data. Multiply each sale by the tier rate in effect on its sale date, sum the expected fees, and compare to the fee total on the report. Investigate any gap before booking, not after.
3. Book gross, fee, and adjustments as separate lines
Record one entry per payout with the gross revenue, the platform fee, and any refunds or chargebacks as distinct postings. A refund reverses revenue — it is not an expense — and if the platform claws back its commission on refunded sales, that clawback reduces your fee expense. In a plain-text ledger the pattern looks like this (see the docs for ledger syntax if this format is new to you):
2026-01-01 open Assets:Bank:Checking USD
2026-01-01 open Income:Marketplace:Skill-Sales USD
2026-01-01 open Expenses:Marketplace:Platform-Fees USD
2026-11-01 * "Skills marketplace" "October payout, 15% tier"
Assets:Bank:Checking 850.00 USD
Expenses:Marketplace:Platform-Fees 150.00 USD
Income:Marketplace:Skill-Sales -1,000.00 USD
2026-11-15 * "Skills marketplace" "Refund, order 1042, fee clawed back"
Income:Marketplace:Skill-Sales 49.00 USD
Expenses:Marketplace:Platform-Fees -7.35 USD
Assets:Bank:Checking -41.65 USDThe payout entry shows the full $1,000 of sales as revenue, the $150 commission as its own expense, and the $850 deposit as the bank movement — three postings that tie the dashboard, the fee schedule, and the bank statement together. The refund entry unwinds all three legs. If you sell on more than one marketplace, give each its own income and fee subaccounts so the channel comparison from the previous section falls out of the ledger for free.
4. Tie the net to the bank and the gross to the usage
Two independent ties close the loop. First, the payout's net amount must equal a bank deposit to the cent — if it does not, the difference is an outstanding item (a held reserve, a delayed transfer, a currency conversion) that needs its own explanation, not a rounding plug. Second, the gross must tie back to the underlying activity: for unit sales, the per-sale report totals; for engagement or usage-based payouts, your own metered-unit count times the contracted rate. Builders who skip the second tie are the ones who discover six months later that a rate change was applied a month early. Your own usage logs are the only check on the platform's meter — keep them.
Tax forms: what arrives and what does not
Marketplace income is ordinary business income, reported on Schedule C alongside your other self-employment revenue. What differs by platform is which information return — if any — documents it.
Third-party marketplace payouts may arrive on Form 1099-K. For 2026, the One Big Beautiful Bill Act restored the classic threshold: payment processors and marketplaces issue a 1099-K only when a payee exceeds $20,000 in gross payments and 200 transactions in the calendar year. Below that, no form arrives — but the income is still fully taxable, and the gross-booking habit from the previous section is what makes your return right when there is no form to copy from. Note the threshold counts gross payments and transaction volume, so a high-volume, low-price skill catalog can trip the transaction count while a few big enterprise skill contracts never come near it.
Direct engagement payouts look more like contractor income. A platform paying you engagement-based revenue share out of its own pocket, rather than settling third-party buyers' payments to you, is closer to a payer-contractor relationship, documented — when thresholds are met — on the 1099-NEC or 1099-MISC family, whose reporting threshold rose to $2,000 for 2026. Either way, reconcile whatever form arrives against your ledger's gross revenue for that platform; the form and the books should agree before the return is filed.
State thresholds can be lower than federal. Several states impose their own 1099-K filing thresholds well below the federal $20,000 and 200 transactions, which means you can receive a state-copy 1099-K — and have the state expecting matching income — in a year the federal form never comes. If you get one, reconcile it the same way: gross on the form against gross in the ledger.
No form is not the same as no income. This is the mistake that costs small sellers real money. Engagement payouts of a few hundred dollars a month, skills sold on a marketplace that never crosses reporting thresholds, indirect income from skills funneling users to your own metered API — all of it is taxable whether or not anyone sends you a form. The sellers who sail through tax season are the ones whose ledgers already hold every dollar gross, so the return writes itself from the books instead of from a shoebox of platform emails.
Four mistakes that quietly compound
Recording the deposit as revenue. The net-only habit, covered above. It understates revenue, hides the fee trend, and guarantees a mismatch against any 1099-K. Fix it once by rebooking the year's payouts gross, and the monthly loop keeps it fixed.
Booking the platform fee as COGS. Bundling the commission into cost of goods sold makes your gross margin absorb channel costs that belong in selling expense. Your product looks less profitable than it is, and a fee increase reads as a product problem instead of a channel problem. Keep delivery costs (inference, hosting, upstream APIs) in COGS and distribution costs (marketplace commissions, payment processing) in selling expense.
Forgetting the tier crossing. On a sliding-scale platform, the month your trailing volume pushes you into a higher bracket, your effective rate is a blend — early-month sales at the old rate, later sales at the new one. Sellers who book the whole payout at one rate misstate the fee in whichever direction flatters them less usefully, and the error repeats every month they sit near a boundary. The per-sale rate check in step 2 exists for this exact case.
Running every platform through one account. One income account and one fee account for all marketplaces feels simpler until you need to answer which channel earns its keep, or until one platform's 1099-K needs reconciling against a blended balance. Per-platform subaccounts cost nothing at booking time and save hours at tax time.
This month's payout checklist
Pull your most recent payout report for each marketplace you sell on and work it end to end: confirm the commission tier in effect on each sale date, recompute the fee total from per-sale data, book gross revenue with the fee and any refunds as separate lines, tie the net to the bank deposit, and tie the gross to your own usage or sales log. Then check whether your trailing-twelve-month volume is approaching a tier boundary — if it is, you now know your effective rate is about to move before the platform tells you. That is the whole discipline: every dollar accounted for gross, every fee visible on its own line, every platform reconciled on its own terms.
