Every payment that arrived, on one page.

The same dollar can appear three times and look like three dollars.

A card payment exists as a gross charge in your platform, as a net deposit at the processor, and again as a deposit in your accounting system. Add those together naively and a good month looks extraordinary. We know because we did exactly that and overstated a single month by tens of thousands of dollars before catching it.

The payments view is deliberately read-only and deliberately does not sum across sources. It shows every payment that arrived and where it came from, so a bookkeeper can see the whole picture without a number quietly appearing more than once. Processor fees are recorded against the payment, so a card payment can show what you actually kept rather than what the customer was charged.

It closes nothing. Closing money is a person's decision — an automatic closer will eventually close the wrong thing at the worst moment, and there is no undo that fixes a customer who was told they were paid up when they were not. A held check counts as new money for its own amount, not for the invoice's lifetime total.

• Card, check and accounting-system payments in one view
• Read-only by design — the page reports, it never settles anything
• Processor fees recorded, so a card payment shows what actually landed
• No naive summing across sources, so one dollar is never counted three times
• A held check contributes its own amount, not the invoice's lifetime total
• Invoices matched against your accounting system by exact total, never by invoice number alone
• An invoice can show which accounting line it is missing, and take it