Jobs
Create the invoice directly from the completed job record
Invoice is linked to the job and client automatically. No manual re-entry. No disconnected records.
Review recordBlueprint journey
Lesson 33 / 36
0 completed
Next best lesson: Start Here: How to use Blueprint week by week
Guided operating lesson
The Jobs–Invoices–Money Loop
Run a clean financial loop in BuilderBuddi where every job produces a correct invoice, every invoice is tracked, and payment is visible without manual chasing.
BuilderBuddi Tools and Implementation22 minIntermediate
Who this is for
BuilderBuddi users who have jobs and invoices but whose financial loop is messy — some jobs have invoices, some do not; some invoices are paid, some are overdue but unchecked.
Why it matters
A clean jobs–invoices–money loop means every job is financially accounted for. Nothing falls through the cracks. Revenue is visible. Overdue invoices surface automatically.
Lesson outcome
A working, clean financial loop in BuilderBuddi where every completed job has a matching invoice and every invoice has a tracked status.
Real-world problem
The contractor who had $14,000 sitting in uninvoiced completed jobs
A roofer did a BuilderBuddi audit and discovered 7 completed jobs with no invoice sent. Three of them were over 60 days old. Two clients had moved on and would require awkward conversations. The total uninvoiced amount was $14,200. This was not a revenue loss yet — but it was heading there. The cause: invoicing was disconnected from job completion. A clean jobs–invoices loop would have made these visible within days.
Why this happens
Invoicing happens "later" and later becomes never
When invoicing is not directly connected to job completion, it becomes a separate task that competes with site work. Busy periods push it out. Completed jobs accumulate uninvoiced.
No visibility of outstanding invoices without manual checking
Without a connected system, you cannot see which invoices are unpaid without manually cross-referencing. This means overdue invoices are invisible until they are very overdue.
Professional standard
Invoice at or within hours of job completion
The cleanest businesses invoice on the day the job is complete — often from the phone on site. Invoicing is a trigger action on job completion, not a separate task.
Review invoice status weekly
A 5-minute weekly review of invoice status in BuilderBuddi surfaces overdue items before they become 60-day problems.
Step-by-step operating system
Clean jobs–invoices–money loop
1
Invoice from the job record on completion day
When a job is complete, create the invoice directly from the job record in BuilderBuddi. This links the invoice to the job and prevents the "I'll invoice it later" gap.
BuilderBuddi: Open the completed job in BuilderBuddi and create the invoice from the job record.
2
Include all line items and any variations
Before sending, confirm the invoice includes the base scope, any approved variations, and the correct payment terms. Check it against the original quote.
3
Weekly invoice status review
Every Monday, open Invoices in BuilderBuddi and review payment status. Identify anything past due. Apply your follow-up sequence immediately.
BuilderBuddi: Open Invoices in BuilderBuddi and filter by payment status. Address overdue items.
4
Monthly reconciliation
Once a month, verify that every completed job in BuilderBuddi has a matching invoice. Any jobs without invoices are your revenue gap. Close them immediately.
BuilderBuddi workflow cards
Run the complete financial loop in BuilderBuddi
Job completion triggers invoice creation. Invoice creation triggers dispatch. Payment status is visible weekly. Overdue items are caught before they become losses.
Invoices
Weekly review of invoice payment status
Overdue invoices are visible and actioned within days, not discovered after 60 days.
Open in BuilderBuddiThe carpenter who found 4 uninvoiced jobs in a monthly check
Context: A carpenter implemented a monthly reconciliation as part of his BuilderBuddi routine. In his first monthly check, he found 4 completed jobs with no invoice.
Challenge: Two of the four were recent and invoiceable without difficulty. Two were 45+ days old and required a conversation.
Recommended response: Invoice the recent ones immediately. For the older ones, a direct, professional message: "Apologies for the delay in sending this invoice — here it is for the work completed on [date]." Most clients who received good work pay without pushback.
- • Open Jobs in BuilderBuddi and filter for completed status
- • Identify any completed jobs without an invoice
- • Create and send invoices for all immediately
- • Implement the weekly check going forward to prevent recurrence
Field notes
- • Every uninvoiced completed job is a receivable that is aging. The older it gets, the harder it is to collect.
- • Invoice on completion day — from your phone, before you leave the site.
- • A weekly 5-minute invoice review is more effective than monthly fire-fighting.
- • BuilderBuddi's linked job-invoice structure makes the loop visible — but only if you use it consistently.
Key takeaways
- Invoice on completion day — not later.
- Every completed job must have a linked invoice. Monthly reconciliation ensures this.
- Weekly invoice status review catches overdue items before they become 60-day problems.
- A connected jobs–invoices loop in BuilderBuddi makes your financial position visible in real time.
Common mistakes
Treating invoicing as a separate task from job completion
Consequence: Completed jobs accumulate without invoices. Revenue is delayed and at risk.
Prevention: Invoice from the job record at completion — make it the last step of every job, not a separate task.
Not reviewing invoice status weekly
Consequence: Overdue invoices are invisible until they are very overdue and harder to collect.
Prevention: Block 5 minutes every Monday for invoice status review. Apply follow-up immediately to anything past due.
Sending invoices without checking against the original quote
Consequence: Line items are missed or variations are not included. You under-invoice and the gap is your loss.
Prevention: Before sending any invoice, compare to the original quote and any approved variations. Confirm every item is included.
Complete this in BuilderBuddi
Implementation checkpoint
Tick these only when the real business output exists. This keeps Blueprint tied to work done, not pages viewed.
0% complete
Decision point 1: You complete a job on a Friday afternoon. When should you create and send the invoice?
Practical action
Do a BuilderBuddi reconciliation this week: open Jobs, filter for completed, and check every one has a matching invoice. Invoice any gaps immediately. Then set a weekly 5-minute Monday invoice review.
Worksheet prompt
Open your BuilderBuddi job list and count the completed jobs without a sent invoice. Calculate the total uninvoiced amount. How many days have elapsed since each was completed?
Worksheets and templates
Jobs–Invoices–Money Loop Checklist
ChecklistA weekly and monthly checklist for maintaining a clean financial loop in BuilderBuddi.
Ready for immediate use
Related operating playbooks
Next step