How to automate JobTread invoices into Wave (draft-first)

What this automation does (and what it doesn’t)

It does

• Create a new invoice in Wave when an invoice is created/updated in JobTread.
• Default that Wave invoice to Draft status so you or your accountant can review it before sending.
• Map over key fields like:
• Customer/client
• Invoice number (or external reference)
• Invoice date and due date
• Line items (as supported)
• Notes/memo (for things like partial billing context)

It doesn’t (usually)

• Automatically reconcile expenses/receipts between JobTread and Wave. In many setups, Wave’s expense side is limited via no-code connectors, so treat expense reconciliation as a separate workflow (or a custom/API workflow).

Before you build: decide your “source of truth”

• Recommended: Create invoices in JobTread, then push them into Wave.
• Avoid “two-way invoice sync” unless you have strong deduping safeguards, because it can cause loops (each system triggers the other).

Step-by-step: JobTread → Wave invoice automation (draft-first)

Step 1: Choose your integration method

• If JobTread is available as a connector (trigger) and Wave is available as an action, start there.
• If you can’t get the fields you need (or the trigger isn’t reliable), use webhooks or a custom API step.

Step 2: Trigger on a JobTread invoice event

• “Invoice created”
• “Invoice updated”
• “Document updated” (in tools that treat invoices as documents)

Step 3: Look up (or create) the Wave customer

• First, try to match by email (most reliable).
• If email isn’t available, match by a normalized name (case-insensitive, trimmed, punctuation removed).
• If not found:
• Create a new customer in Wave, or
• Route to a manual review step (recommended if you have strict accounting controls).

Step 4: Create the Wave invoice in Draft status

• Invoice date / due date: map directly from JobTread when available.
• Line items: map line items; if line items aren’t supported, write a single line item like “JobTread invoice #12345” and include detail in the memo/notes.
• Partial billing context: if JobTread has “$5,000 of $20,000 proposal” context, put that in the invoice memo so it stays attached to the accounting record.

Step 5: Add a “mark as sent” exception flow (optional)

• Keep Wave invoice creation as draft-first.
• Add a conditional branch:
• If customer is in your “Wave-send” segment → keep as draft until you send from Wave.
• If customer is in your “JobTread-send” segment → create the Wave invoice and optionally set status to “sent/marked as sent” (only if your connector supports this safely).

Common edge cases (and how to handle them)

Duplicate invoices

• Store the JobTread invoice ID in a custom field or memo in Wave.
• Before creating a new Wave invoice, search Wave for that JobTread invoice ID.

Draft approval workflow

• Send a Slack/email notification when a new draft is created.
• Include a direct link to the Wave invoice.

Changes after the invoice is created

• Allow updates to the Wave invoice if the JobTread invoice changes, or
• Freeze Wave invoices after creation and require a manual adjustment.

Limitations: expense matching and receipts

• Upload a receipt in JobTread
• Automatically match that receipt to a credit card expense in Wave

• Confirm what Wave exposes through your automation platform for expenses
• If the connector can’t do it, consider a custom/API workflow

Key takeaway

Get help building this