The CRM Payments report lists money received — one row per payment, with the customer, the tender, the amount, and how much of it has been applied to charges. It is the simplest view of what came in over a period.
This article assumes you already know the basics of the Sharper reporting module — the Name, Token, Subtotal, column picker, and filter fields. For a full walkthrough of the reporting form itself, see the Sharper Reporting Reference Guide. This article only covers what's specific to the Payments report.
Why This Report Matters
Daily banking, card reconciliation, and "did that payment go through?" are all payment questions rather than invoice questions. Because this report gives one clean row per payment, it is the right tool for:
Reconciling a day's takings by tender against your bank or processor
Finding payments that failed or were declined
Identifying money received but not yet applied to any charge
Reviewing what each staff member or register took
Settled and Unsettled Amounts
Three amount columns describe the same payment at different stages, and the distinction is where most of this report's value lies:
Column | What It Represents |
Payment Amount | What the customer handed over — the figure to total for money received |
Payment Settled Amount | How much of it has been applied against invoices or deposits |
Payment Unsettled Amount | How much is still sitting unapplied on the customer's account |
A payment with an Unsettled Amount greater than zero is money you have taken that is not reducing anybody's balance. This is the usual explanation for a customer who insists they have paid while their account still shows due — and it will keep showing due until the payment is applied. Review this regularly rather than waiting for the complaint.
For the detail of which invoice lines a payment settled, use the Settlement Details report — this one tells you how much was applied, not what to.
Building a Payments Report
Go to Reports → CRM → Payments in the left sidebar.
If a shipped report is close to what you need, use the ⋯ menu → Copy first — shipped reports can only be edited by the Sharper team.
Otherwise click + New and give it a Name, such as "Daily Takings by Tender."
Add the columns below from the Available panel.
Set Subtotal to Payment Amount.
Turn on All Outlets if you bank more than one location together.
Click Save, then Get Report to set a date range and run it.
Recommended Columns
Field | What It Shows |
Payment Date, Payment Time | When the money was taken — the columns to filter a banking day on |
Payment Status | Whether the payment succeeded. Include this on any report you total, or declined and voided attempts will inflate your takings. |
Payment Type, Payment Method | How the customer paid — cash, card, check, ACH. Group on these for a takings-by-tender summary. |
Payment Amount, Payment Settled Amount, Payment Unsettled Amount | The value columns described above |
Customer Name, Cust Email, Cust Phone | Who paid |
Check Number | The check reference, for matching against a deposit slip |
Credit Card Last 4, Credit Card Auth | Card references for matching against your processor's statement |
Credit Card Response | What the gateway returned — the first place to look on a failed card payment |
Gateway Transaction | The processor's own transaction reference, for raising a query with them |
Register Name, POS Transaction | Where a point of sale payment was taken |
User Display Name, User Email | The staff member who took the payment |
System User | Marks payments taken automatically rather than by a person — AutoPay runs and online payments |
Payment ID | The payment's reference in Sharper |
Note: Use System User to separate automated collections from over-the-counter takings. An AutoPay run and a card taken at the desk look identical on every other column, and mixing them makes a till reconciliation impossible to balance.
Useful Filters
A day's takings by tender: Field Payment Date set to the day, grouped by Payment Type, subtotalled on Payment Amount, with successful statuses only.
Unapplied money: Field Payment Unsettled Amount, operator >, value 0.
Failed payments: Field Payment Status, set to your declined or failed status — worth reviewing after every AutoPay run.
Counter takings only: Field System User, set to No.
One register's payments: Field Register Name, set to the register.
One customer's payment history: Field Customer Name, set to the customer.
The failed-payments filter is worth running the morning after each AutoPay run — a declined card caught the next day is usually fixed with one call, while one caught a month later has become a collections problem.