Invoicing Configuration
Invoicing is a back-office module that turns Field Tickets into billable invoices. Each invoice belongs to one Job, bills the Company attached to that Job, and pulls its line items from the Field Tickets you attach to it.
An invoice in EZ Ops:
- Belongs to exactly one Job. The customer billed is whichever Company is on that Job — you do not pick a customer separately.
- Attaches any number of Field Tickets from that Job that are not already on another invoice.
- Builds line items automatically from each attached Field Ticket's Misc Items and Other Expenses rows.
- Accepts manual line items typed directly on the invoice for anything the tickets don't capture.
- Produces a PDF with your details, the customer's details, the line items, and the total.
- Moves through Active, Completed, and Deleted states so back-office staff can see what is still open and what has been billed.
Invoicing is deliberately separate from Field Tickets. Field Tickets capture what work happened and what it cost. Invoices decide which of that work gets billed on a given piece of paper. One Job can produce many invoices over time, and each invoice can draw from any subset of that Job's unattached tickets.
Why Invoicing Matters- No re-typing. Misc Items and Other Expenses recorded in the field roll onto the invoice automatically. Nobody copies rows into a spreadsheet.
- Nothing gets billed twice. Once a Field Ticket is attached to an invoice, it disappears from the picker on every other invoice. There is no "did we already bill this?" ambiguity.
- Addresses come from your configuration. Your organization's address and the customer's address are pulled from Org Info and the Company record, then stored on the invoice so old invoices don't change when you later update those records.
- Reversible. Invoices can be edited at any point, completion can be undone, and deleted invoices can be restored.
Set these up in order. Each one gates the next.
| # | Prerequisite | Where |
|---|---|---|
| 1 | Jobs enabled — the project_page setting, shown as Job/Project Forms |
Org Configuration → Other → Org Settings |
| 2 | Invoices enabled — the invoices setting, shown as Invoices |
Org Configuration → Other → Org Settings |
| 3 | Invoices role permission granted to the roles that need it | Org Configuration → Users & Roles → Roles |
| 4 | Your organization's address and email filled in | Org Configuration → Organization → Org Info |
| 5 | Companies with billing addresses | Org Configuration → Organization → Companies |
| 6 | Jobs with a Company attached, carrying Field Tickets | Reports → Operations → Job Dashboard |
The Invoices checkbox in Org Settings only appears once Job/Project Forms is already on. If you can't find it, turn on Jobs first.
Both the org setting and the role permission are required. A user with the permission but no org setting sees the message "Invoices are not enabled for this organization." A user with the org setting but no permission never sees the menu item at all.
Where Invoicing LivesReports → Operations → Invoices, immediately below Job Dashboard. If your organization also uses Inspections, that menu group is labelled Operations & Inspections.
Everything happens on that one page:
- The invoice list, split into Active, Completed, and Deleted tabs.
- The invoice detail view, opened by clicking an invoice number — a read-only preview of what the customer will see.
- The invoice editor, opened by Add Invoice or the edit button on a row.
Step 1 — Enable the org setting
Go to Org Configuration → Other → Org Settings. Confirm Job/Project Forms is checked, then check Invoices. The setting saves as soon as you check it.
Org Settings is admin-only.
Step 2 — Grant the role permission
Go to Org Configuration → Users & Roles → Roles. For each role that should reach invoicing, check Invoices.
The Invoices permission only appears in the role editor once the Invoices org setting is on, and it is separate from the Jobs permission. Someone who can work on Jobs is not automatically an invoicing user.
Typical assignments:
| Role type | Invoices permission |
|---|---|
| Back-office and accounting staff | Yes |
| Field supervisors who review work before it is billed | Usually yes |
| Field technicians | No |
| Reporting-only users | Only if they need to see billed amounts |
Step 3 — Fill in your organization's details
Go to Org Configuration → Organization → Org Info. The Your details block on every invoice and invoice PDF is built from these fields.
| Field | Notes |
|---|---|
| Org Name | Required, and must be unique across EZ Ops |
| Street Address | Up to 100 characters |
| City | Up to 20 characters |
| Province / State | Two characters — use the code, such as AB or TX |
| Country | Three characters — use the code, such as CAN or USA |
| Zip Code / Postal Code | Up to 10 characters |
| Must be a valid email address |
Only administrators can open Org Info. Every change is recorded — use View History on that page to see who changed what.
Step 4 — Fill in each Company's billing details
Go to Org Configuration → Organization → Companies and edit each Company you invoice. The Client details block on the invoice comes from these fields.
Companies without an address can still be attached to Jobs and invoiced — the invoice simply shows blanks where the address should be.
Step 5 — Confirm your Field Tickets carry pricing
Invoicing only pays off if the tickets feeding it carry real numbers. Confirm:
- At least one Field Ticket form is live, with Misc Items and/or an Other Expenses question on it.
- Field crews are actually filling in a quantity and a rate on every row.
A line's rate is entered on the Field Ticket row itself — it is not read from the Misc Items catalog when the invoice is built. A Misc Type can carry a custom info field named rate that pre-fills the box when an operator picks that item, which is worth setting up so crews are correcting a number rather than typing one from scratch, but the row's own value is what reaches the invoice. Rows left at zero arrive on the invoice at zero.
A Field Ticket with no Misc Items and no Other Expenses rows contributes no line items. It can still be attached to an invoice, but it adds nothing to the total.
Creating an Invoice- Go to Reports → Operations → Invoices and click Add Invoice.
- Set the Invoice Date. It defaults to today and cannot be in the future.
- Pick the Job Name. The Your details and Client details blocks fill in as soon as you do.
- Open Field Ticket IDs and select the tickets to bill. Each option shows the ticket ID and how many line items it will contribute, like
#FT-1043 (6 items). - Review the Invoice Items table. Every selected ticket has dropped its Misc Items and Other Expenses rows in.
- Adjust rates, delete lines you aren't billing, and use Add Invoice Item for anything the tickets didn't capture.
- Add Notes if needed — up to 255 characters, printed at the bottom of the PDF.
- Click Save Invoice. The invoice number is assigned at this point.
- When the invoice is final, click Complete Invoice and confirm. Saving happens automatically before completion.
- Use Download as PDF to get the file to send.
The Invoice # field reads "Assigned on save" until you save. Numbers are assigned sequentially per organization and cannot be edited.
What you can and can't edit on a line
How a line got onto the invoice determines what you can change:
| Line source | Description | Quantity | Unit | Rate | Delete |
|---|---|---|---|---|---|
| From a Field Ticket | No | No | No | Yes | Yes |
| Added manually | Yes | Yes | Yes | Yes | Yes |
Ticket-sourced lines show the item description with the source ticket underneath, and are deliberately locked to what the field crew recorded. The one exception is Rate — you can reprice anything before you bill it. Manual lines are fully editable and require a description before the invoice will save.
Deleting a line removes it from this invoice only. It does not change the Field Ticket.
Attaching and detaching Field Tickets
The Field Ticket IDs picker shows every Field Ticket on the selected Job that isn't already attached to another invoice. Tickets still in draft are included — the picker does not require a ticket to be complete.
Selecting a ticket adds its lines. Clearing it from the picker, or clicking Unlink on the ticket in the Attached Field Tickets list, removes both the ticket and its lines. Manual lines you added are never removed by this.
Changing the Job Name on an invoice that already has tickets or lines prompts: "Changing the Job will unlink all selected Field Tickets and remove their invoice lines. Continue?" Confirming clears the whole invoice back to empty.
Invoice Lifecycle| Status | What it means | How to get out of it |
|---|---|---|
| Active | The working state. Every new invoice starts here. | Complete Invoice → Completed. Delete → Deleted. |
| Completed | Marked as billed and moved to the Completed tab. | Undo Complete → Active. Delete → Deleted. |
| Deleted | Removed from the Active and Completed tabs and kept on the Deleted tab. | The restore button → back to its previous tab. |
Completing an invoice is a bookkeeping marker, not a lock. Completed invoices can still be opened and edited. If you need edits to be visible as a deliberate reversal, use Undo Complete first, make the change, then complete it again. The invoice number and date are preserved throughout.
Deleting is reversible from the Deleted tab — you do not need EZOPS support to recover an invoice.
Where Line Items Come FromEvery line on an invoice has one of three origins.
Misc Items on an attached Field Ticket. One line per Misc Item on the ticket. The description is the item's description, falling back to its type. Quantity, unit, and rate are all copied from what the crew recorded on that ticket row — the catalog is not consulted at invoice time.
Other Expenses answers on an attached Field Ticket. One line per row of an Other Expenses question. Rows without both a numeric rate and a numeric quantity are skipped rather than imported at zero. Rows with no description are labelled "Other Expense". The line is labelled with the source ticket.
Manual lines. Anything you type in with Add Invoice Item — mobilization, standby, a fixed fee, an adjustment. A description is required. Quantities on manual lines are whole numbers.
The invoice total is the sum of quantity × rate across all lines. There are no tax lines, discount lines, or subtotal groupings.
An invoice total does not have to match its source tickets, by design. You can reprice any ticket-sourced line, delete lines you aren't billing, and add manual lines the tickets never carried. None of that writes back to the Field Ticket, so the ticket keeps recording what happened in the field while the invoice records what you chose to bill. Treat a gap between the two as expected rather than as an error — but if you need the ticket corrected as well, edit the ticket separately.
The Invoice PDFDownload as PDF is available from any Active or Completed invoice, either from the row in the list or from inside the editor. The file is named after the invoice number, such as Invoice_42.pdf. Deleted invoices cannot be exported.
The PDF is generated in the background, so on a large invoice there is a short wait before the download starts.
The PDF contains, in order:
- Invoice # as the heading.
- Your details — your organization's name, address, and email.
- Client details — the Company's name, address, and email.
- Invoice No, Job, Invoice Date, and Status.
- A line-item table with Item, Quantity, Unit, Rate, and Line Total, followed by the grand total.
- Note, if one was entered.
There is no logo on the PDF and no way to upload one. Amounts are formatted as plain dollar figures with no currency code.
How addresses get onto the invoice
Addresses are copied onto the invoice when it is saved, not looked up fresh each time you view it. This keeps historical invoices stable, but it means corrections behave differently depending on which address you fix:
- Fixing your organization's address in Org Info takes effect on any invoice the next time that invoice is saved.
- Fixing a Company's address only reaches an existing invoice if you change that invoice's Job. Otherwise the invoice keeps the address it was created with.
If you correct a Company address and need an already-created invoice to show it, the reliable fix is to create a replacement invoice.
Reporting- The Invoices page filters by status tab, by Job, and by a search box that matches invoice numbers and Job names. Results sort by invoice date, newest first by default — click the Date column to flip the order.
- Attached Field Tickets are consumed from the invoicing picker as soon as they are attached, so the picker for a Job doubles as a list of work still waiting to be billed.
Invoice data is not yet in the Snowflake reporting layer, so cross-Job invoice analysis isn't available in the warehouse reports yet.
What Invoicing Does Not DoConfirmed absent in this release:
- No taxes or discounts. There is no GST/PST/VAT line, no percentage discount, and no tax configuration. If you need tax on an invoice, add it as a manual line item.
- No due dates, payment terms, or PO numbers. The only date on an invoice is the invoice date.
- No emailing from the app. Download the PDF and send it yourself.
- No accounting-system integration. There is no QuickBooks, Sage, or SAP export.
- No payment tracking. Completed means billed, not paid.
- No recurring invoices.
- No multi-currency.
- Fill in Org Info and every Company address before your first real invoice. These are the fields customers actually look at, and fixing them afterwards doesn't retroactively repair invoices already created.
- Use the province and country codes, not the full names. Those fields are two and three characters. "Alberta" won't fit;
ABwill. - Attach tickets first, then reprice. Changing the Job wipes the invoice, so settle on the Job before you do any line-level work.
- Invoice on a rhythm rather than per ticket. One invoice per Job per billing period keeps the numbers manageable and matches how most customers want to receive them.
- Treat Complete as "sent". Because completion doesn't lock the invoice, the team needs a shared convention. Completing when the PDF goes out is the one most organizations settle on.
- Detach before deleting. Deleting an invoice does not release its Field Tickets — see Common Issues below.
"The Field Ticket I want isn't in the picker." The ticket has to be on the Job you selected, and it must not already be attached to another invoice. Tickets don't need to be complete. If the ticket is on another invoice, open that invoice and unlink it first.
"I deleted an invoice and now its Field Tickets won't appear on a new one." Deleting an invoice does not release the Field Tickets attached to it — they stay linked to the deleted invoice and stay out of the picker. To recover them: go to the Deleted tab, restore the invoice, open it, unlink the tickets, save, then delete the invoice again. Because of this, unlink the tickets before deleting an invoice you don't intend to keep.
"The invoice PDF is missing our address or the customer's address." Your address comes from Org Configuration → Organization → Org Info and the customer's from the Company record. Fill in whichever is blank. Existing invoices won't pick up the change on their own — see "How addresses get onto the invoice" above.
"I can't save — it says a manual invoice item requires a description." One of the lines you added with Add Invoice Item has an empty description. Fill it in or delete the line.
"I can't set a future invoice date." Invoice dates are capped at today. This is intentional.
"An attached ticket contributed fewer lines than expected." Other Expenses rows are skipped when the rate or quantity isn't a number, including blank ones. Open the Field Ticket, complete those rows, then unlink and re-attach the ticket to pull the lines in.
"The Invoices checkbox isn't in Org Settings." It only appears once Job/Project Forms is enabled.
"A user can't see the Invoices menu item." Check both gates: the Invoices org setting and the Invoices permission on that user's role.