Table · reads invoice
Invoices
Issued/received invoices and status.
Rows and columns, sortable and filterable.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Overdue is computed from the due date every day. Nobody has to mark it, so nobody forgets to.
Terms known from Contacts or Companies set the due date automatically — thirty days means thirty days from issue, not from when someone remembers.
A payment mentioned in conversation settles the invoice, and matches against Payments when both exist.
The overdue list is the one that matters, and it is the default view rather than something to filter for.
How it works
- 1
An invoice is mentioned or created; the agent records it as Draft or Sent.
- 2
Due is taken from what was said, or from the terms Contacts or Companies holds for that client.
- 3
Overdue is computed daily from Due against today. It is never something anybody has to mark.
- 4
A payment mentioned in conversation moves it to Paid. If Payments exists, the two are matched on amount and client.
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.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Invoicerequired | text | A reference if one is given; otherwise the agent issues the next in sequence. |
| Clientrequired | text | Who it is addressed to. Matched against Contacts when that module exists. |
| Amountrequired | money | The total. An invoice without one is a note, so the agent asks rather than storing a blank. |
| Duerequired | date | A stated date, or computed from terms — "thirty days" against the issue date. |
| Statusrequired | choiceDraft · Sent · Paid · Overdue · Written off | Set on creation and changed when payment is mentioned. Overdue is derived from Due, not stated. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- It records invoices; it does not produce them. There is no PDF, no numbering guarantee, and nothing is sent.
- No VAT or tax handling. Amount is one figure, and a gross/net split has to live in two modules or a note.
- Partial payment has no first-class state — it is Sent with a lower Amount, or two rows, both of which lie slightly.
- Written off is a status, not an accounting event. Nothing downstream knows the money is gone.
Before it works
What you have to provide, if anything.
- Nothing required.
- Better with Contacts or Companies: without them, Client is free text and the same customer can appear three ways.
In practice
A freelancer with five active clients and a habit of not chasing.
“Invoiced Maison Lauret 3,200 today, thirty days.”
What the agent built
INV-0148 at 3,200, due in thirty days, status Sent — the terms came from the client record.
What changed
Six days after the due date the agent brought it up unprompted. It was the first invoice that year chased in the week it went late rather than the month.
Better with
These do a different job on the same data. An agent can have all of them.
Payments arrive by several routes and the net figure never quite matches what was invoiced.
Almost any agent that talks to more than one person and needs to remember who they were. The default people module when nothing more specific fits.
Work is won by quoting, and revenue depends on following up the ones that went unanswered rather than writing more.
Who uses this page
Freelance developer
Filters the enquiries worth your time and scopes them before the first call.
Consultant
Qualifies the engagement and captures the problem before the first conversation.
Plumber, electrician or builder
Answers the phone you cannot answer, and takes the job details while your hands are full.
Translation agency
Scopes a job on language pair, word count and deadline before a project manager reads it.
Questions
What data does the Invoices page use?
It reads invoice records the agent has collected. Issued/received invoices and status. 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.
Quotes
Estimates and proposals.
Revenue
€24,180
+12%
Outstanding
€5,250
−31%
Average order
€412
+4%
New customers
17
−2
Revenue KPI
Headline financial metrics.
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