Bank statement.
Spreadsheet.
Spreadsheet. Repeat.
Match the payment. Handle the partial payment. Handle the wrong reference number on the bank entry. Every month, by hand.
The app suggests which invoice each payment is for, and says why. Cash, bank transfer, cheque, card or UPI, recorded in one place, with balances recalculating immediately.
Match the payment. Handle the partial payment. Handle the wrong reference number on the bank entry. Every month, by hand.
Ranked suggestions in plain language: amount match, reference match, recency, same customer. Above 95% confidence the sweep books the allocation itself; between 65% and 95% it asks a person; below that it leaves it alone. One payment can be split across several invoices.
Bank statement import: CSV with saved column presets per bank, or CAMT.053 XML with no mapping. Unmatched lines sit on the left, the top three candidates with reasons on the right, and you can bulk match above a confidence you choose.
A cash-flow forecast built from how fast your own customers have actually paid, not a generic assumption. Plan your spending against real numbers.
Hosted checkout, a pay-by-link page, and refunds through the gateway. Signed webhooks record each payment without re-keying. Refunds need approval, and disputes, chargebacks and unusual payments each get their own queue.
A big keypad, customer autosuggest and camera capture, so a payment collected in the field is on the record before the rep leaves.
1099-NEC, Form 16A, Form 26Q or a generic summary, ready to download.
Payments are part of the Billing module, with sales orders, invoices and payment reminders. One price for the whole team, not per user.
We would like to count which pages people read, using Google Analytics. It tells us nothing about who you are, and the site works exactly the same if you say no.What we collect