Invoices and operations
Send an invoice and understand Draft, Sent, Partial, Paid, and Overdue
Deliver the correct invoice, use reminders/revocation appropriately, and interpret its status from actual ledger activity. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.
Before you begin
- Audience: Company admin, accounting manager.
- Saved invoice
- recipient
- email configuration
- send permission
- valid public link.
Sales → Invoices (#/invoices) → open invoice; public document #/public/documents/:token
Send an invoice and understand Draft, Sent, Partial, Paid, and Overdue
-
Open the workspace
In JobBuddy, go to Sales → Invoices (#/invoices) → open invoice; public document #/public/documents/:token.
-
Confirm access and starting state
Saved invoice; recipient; email configuration; send permission; valid public link.
-
Complete the main setup
Use lifecycle table for DRAFT/SENT/PARTIAL/PAID/OVERDUE
-
Review the important choices
explain send and issued document, reminders, revocation, recipient/link troubleshooting, balance recalculation, overdue timing, and separate QuickBooks badge/state.
-
Check status and follow-up
Do not suggest manually forcing a ledger-derived status.
-
Verify the result
Deliver the correct invoice, use reminders/revocation appropriately, and interpret its status from actual ledger activity.
Expected result: Deliver the correct invoice, use reminders/revocation appropriately, and interpret its status from actual ledger activity.
Troubleshooting
The page, control, or action is unavailable.
Confirm the required access and starting state: Saved invoice; recipient; email configuration; send permission; valid public link.
The result is incomplete or unexpected.
Status is partly derived from balance and due date; send/remind/revoke affect communication/link state, while payments affect Partial/Paid and time affects Overdue. QuickBooks status is a separate sync dimension.
The issue remains after checking the record.
Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.
What happens next
- Deliver the correct invoice, use reminders/revocation appropriately, and interpret its status from actual ledger activity.
- Review the resulting record, status, notifications, and related history before continuing downstream work.
- Use the related guide when the next action belongs to another JobBuddy workflow.