Invoices

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.

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.