Reads platform exports
The input is the export you already have, in the same document-first spirit as the rest of the Money department.
Paid and invoiced are two different lists
Your invoices live in one place. The money that actually arrived lives in your payment platform, minus fees, sometimes short, sometimes late. Comparing the two lists is the reconciliation work that quietly eats a bookkeeping day.
Payments does the comparison. Feed it the export your platform already produces, and it matches receipts to the invoices they pay.
What is left over is the interesting part: the invoice nobody paid, the payment that does not match anything, the amount that came in short. Those become things you can chase, instead of things you find at year end.
How it works
1
Export from your platform
The file your payment platform already emits. Nothing new to produce.
2
Payments reads it
Each receipt in the export is read and understood in the same workspace as your invoices.
3
Receipts match invoices
What arrived is reconciled against what you billed in Accounting.
4
The exceptions surface
Unpaid invoices, unmatched receipts and short payments are what remain, ready to be chased.
What it takes off the bookkeeping list
Reconciles against invoices
Receipts are matched to the invoices they pay, so billed and received become one picture.
Surfaces the gap
What did not match is the output: the short payment or the invoice still outstanding.
Feeds the same books
Payments works against the same workspace as Accounting and Margin, so the Money department agrees with itself.
Where it sits
Payments is part of the Money department of the Service Business OS, included on every plan. One credit allowance covers every module, so there is no per-agent pricing and no surprise line items.
Compare plansWorks with
Questions owners ask
What do I feed it?
The exports your payment platform already produces. No integration project: the file the platform emits is the input.
What does reconciliation give me?
The gap. What you invoiced sits in Accounting. What actually arrived sits in the platform export. Payments matches the two, so short payments, missing payments and unbilled receipts stop hiding between systems.
Do I have to reconcile manually as well?
The manual path always exists across the Money department, and nothing is written silently. But the matching itself is the module's job, not yours.
Close the gap between billed and paid
Payments is live now. Start the trial and it is one of the modules unlocked from day one, reading the same clients and projects as the rest of the OS.
Start your 14-day trial
Every module unlocked for 14 days. Card details at checkout, nothing charged until day 14, cancel any time before then.
What starting actually involves
- Every module unlocked for 14 days — no feature is held back for a higher plan
- Card details at checkout, nothing charged until day 14
- Cancel before then and you pay nothing
- Setup runs on your own clients and projects, not a demo dataset