Table · reads payment
Payments
Transactions and receipts.
Rows and columns, sortable and filterable.
How it works
- 1
Every field becomes a column; you choose which to show.
- 2
Sorting and filtering happen on the data, not just the visible page.
- 3
Values stay editable in place where the field allows it.
Best for
Comparing many records across many fields.
Not the right choice for
A phone. A table is the first thing that stops working narrow.
Questions
What data does the Payments page use?
It reads payment records the agent has collected. Transactions and receipts. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a table the wrong choice?
A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Finance
Budget
Allocations vs spend by category.
Expenses
Line-item costs with totals.
Invoices
Issued/received invoices and status.
Quotes
Estimates and proposals.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free