This skill checks that what your payment app — Stripe, Square or PayPal — says you were paid matches what your books say. It also catches the most common bookkeeping mistake with online sales.
You give it a month. It compares your payment app with your books, line by line, and tells you whether they agree. If they don't, it shows you where and why, and suggests the fix for your bookkeeper. It never changes anything itself.
A customer pays you $100. The payment app keeps its fee1, holds the rest for a few days23, then sends it to your bank — usually bundled with other sales. Your books have to show all three pieces, even though they happen on different days.
Your bank only ever sees the $96.80 payout, so that's often what gets recorded as the sale. The fee is never recorded at all. Profit comes out the same, which is why nobody notices.
The payment app itself keeps the sale, the fee and the amount left over as three separate figures7. In the US, the Form 1099-K it sends the IRS reports the full $100, before fees and refunds8. The IRS treats fees and refunds as amounts you subtract on your return, not as smaller sales9. Record only the payout, and your sales won't line up with that form.
Same example figures as above, scaled up: 1,000 × $3.20 = $3,200 a month, × 12 = $38,400 a year. Confirm how your accountant wants fees presented.
Then it reads your answers back — "Checking Stripe against your books for September. Go ahead?" — and waits for your yes.
The payment apps' own documentation and the IRS, as published when checked on 20 October 2026. Rates and timings change — follow the link for today's figure. What the skill does comes from the skill's own files.
This page explains merchant-and-payment-processor-rec, from the MosoFin finance skills library, MosoFin/mosofin-finance-skills on GitHub. It describes the current version, which asks five questions first and accepts uploads. Read the skill on GitHub →