Create, review and issue an invoice
Build a draft from the correct customer and job, select the intended commercial sources, review the document and issue it deliberately.
Step by step
- Open Invoices, choose the create action and select the correct customer and job.
- Confirm the recipient, currency, invoice date and default due date.
- Choose the relevant quoted lines, approved variations, costs, labour or intentional invoice-only lines.
- Save the draft and review every line description, quantity, unit value, tax and total.
- Open the rendered document and confirm number, business identity, recipient and payment information.
- Choose Save and approve or the supported issue action only when the draft is complete, then follow delivery and sync state.
Good practice
Keep the invoice as a draft while commercial sources are still changing. Issuing is a controlled financial action, not a formatting preview.
Before you begin
- The customer and job are correct and the billable scope has been approved.
- Numbering, payment and tax defaults have been tested.
Complete workflow
How the workflow moves
- 01Select
Choose the customer and job that own the invoice.
- 02Compose
Bring in quoted scope, approved variations, costs, labour or intentional manual lines.
- 03Review
Check recipient, description, tax, totals, due date and rendered document.
- 04Issue
Approve and send only when the draft is complete.
Setup dependency
Settings that change this workflow
The same task can behave differently between organisations. Check these settings before treating a different result as an error.
/settings/setup/numberingControls automatic or manual invoice number allocation.
Open in SignBas3 →/settings/general/paymentProvides the normal due date used by a new draft.
Open in SignBas3 →/settings/general/financeInfluences tax and accounting treatment for the financial handoff.
Open in SignBas3 →Screen reference
What you will see

Screens show the synthetic BrightLine demonstration workspace. Your records, permissions and configuration will change the details you see.
If your workspace behaves differently, record the relevant job, client or record number and raise a support ticket so the team can investigate the exact context.
