What the Invoices pages are for
From finished job to sent invoice: review the work, price the lines, send it from a company mailbox, and find any invoice later.

The gap between finishing a job and invoicing it is where cash flow goes to die. These three pages close it: a queue that fills itself when technicians finish, a review page that puts everything the reviewer needs on one screen before the invoice exists, and a grid that holds every invoice ever sent.

Billing Queue All Invoices Create Invoice

Billing Queue

Open Billing Queue
Who it is for
Whoever turns completed jobs into invoices, every day.
Without it
A finished job is a paper ticket or a note from the technician. Some get invoiced the same week, some the next month, and some never, because nobody has a list of what is done and unbilled.
What it shows
Every completed job with no invoice. Search by job number, reference number, customer, building or job type; multi-select filters for Customer, Service Type, Inspection Type, Metro and Office; each row shows the job and its technicians with a Review action. Select rows and a batch action bar appears for creating one invoice from several jobs. Review opens the job's billing page: Job Overview, the customer and contract rail, a Contract Coverage advisory, Tech Time, Inspection Results, Scope of Work, Work Performed, Files, Notes and Field Requests, Customer Sign-off, the Activity Timeline, and the editable Service Items (quantity, description, unit cost, gross margin, sell). Return to Tech and Create Invoice unlock once the reviewer has read to the bottom.
What it is worth
  • Nothing finished is forgotten. The queue fills itself the moment a job completes; the only way off it is an invoice or a return to the technician.
  • Everything the reviewer needs, once. Time, results, photos, sign-off and scope on one page, so the invoice is right before it exists.
  • A contract check before the customer makes it. The coverage advisory says whether an active agreement already covers the work.
  • Send it back, not around. Return to Tech with a reason keeps the job in the technician's hands rather than in an email thread.
Pays for itself the first job invoiced the day it was completed instead of at month end.

All Invoices

Open All Invoices
Who it is for
The bookkeeper, the office, and anyone a customer calls about an invoice.
Without it
"Can you resend invoice 1042?" means finding the PDF, and "what do they still owe?" means the accounting system. Neither is in the same place as the job.
What it shows
The invoice grid: search by invoice number or customer, with Status, Customer and Date Range filters as chips and per-row actions. An invoice opens to a header with its number and status, an info row, and tabs: Details (customer, notes, custom fields, linked jobs, and a Send Invoice panel that picks the sending mailbox), Line Items (quantity, description, unit price, tax, line total and whether a contract covers the line, with an Add Items catalog search), Payments (the ledger with a running balance), Notes for collections, and Documents.
What it is worth
  • The invoice and the job together. Linked jobs on the Details tab, so the question behind the call is answered without switching systems.
  • Sent from the company, tracked in the app. Send Invoice goes out from a configured company mailbox chosen per send.
  • The balance is always current. The Payments tab is a ledger; every payment against the invoice sits there with the running balance.
  • Collection notes where the collector looks. The Notes tab is the call log for that invoice, not a spreadsheet beside it.
Pays for itself the first customer call answered from the Payments tab while they are still on the line.

Create Invoice

Open Create Invoice
Who it is for
The office, for the invoice that does not start from the queue.
Without it
Several finished jobs for one customer become several invoices, or one hand-built invoice with the job numbers typed in, and the link back to the work is lost.
What it shows
A four-step form. Step 1 picks the customer. Step 2 lists that customer's completed jobs (job number, building, job type, completed date) to include. Step 3 sets the invoice date, payment terms, due date and an optional contract, showing that contract's rules for reference. Step 4 previews the line items (description, quantity, unit price, line total) before the invoice is created.
What it is worth
  • Many jobs, one invoice. A customer with five completed jobs gets one document, and every line still points at its job.
  • Terms drive the due date. Pick the payment term and the due date follows; it is not typed.
  • Preview before it exists. Step 4 is the whole invoice on screen before anything is saved.
Pays for itself the first month-end where a national account's twelve jobs go out as one invoice with the right terms.

Where to go next

  • Once an invoice is out, money comes back through All Payments, and what has not come back ages on AR Aging.
  • The queue's Service Type, Inspection Type, Metro and Office filters are the same ones on the Jobs grid, and they select the same jobs.
  • Work sitting in this queue shows up as Uninvoiced Work on the Cash Outlook, with what a morning of invoicing would move into the inflows.
  • Payment terms and their default are maintained under Payment Terms in Settings.

Good to know

  • Review gates are read-to-unlock. The action bar on a review activates only after the reviewer has scrolled the page.
  • Contract coverage is advisory. The review says whether an agreement covers the work; it does not block invoicing.
  • One customer per invoice. Selecting jobs for more than one customer in the queue stops before an invoice is created.
  • Payment Terms drive the due date. One term is flagged as the default and is applied unless another is chosen.
  • Send From is chosen per send. Invoices go out from a configured company mailbox picked on the Details tab.