Yes. You can ask Gus on WhatsApp to prepare an invoice, review the saved document and approve a supported delivery. Start with the client, work, amount and dates. Sending still depends on the recipient, consent and available delivery route. A prepared invoice is not automatically sent, and a sent invoice is not automatically paid.
A practical checklist
- Check the client, contact details, work description, currency, amounts and dates against your original records.
- Review the invoice and the proposed recipient and message before approving delivery.
- Check the delivery result separately from payment status; resolve an error before trying again.
Start with the invoice details, not a command to send
Tell Gus which client the invoice is for and what work it covers. Include the agreed amount, currency and the relevant dates, together with the item descriptions or quantities needed to explain the charge. If you are working from an accepted quote, identify that quote so the relationship is clear. Use your own records as the source of truth. A short message can begin the task, but missing details still need to be supplied. Asking for an invoice draft should give you an opportunity to review the document before a customer receives anything.
Check your business identity once, then review each document
Save your business identity and branding in the Brand Kit so later documents can use the right name, logo and colours. When no logo is uploaded, the business name can appear as text. Before sending an invoice, check that its business details and terms are appropriate for this particular transaction. Stored defaults make preparation easier; they do not establish that every saved value is still current. If your contact or payment details have changed, update the relevant settings and inspect the resulting document. Keep credential verification separate from ordinary edits to branding.
Use the review link to inspect the saved invoice
Open the item-specific review link when Gus provides one. If you need to sign in, use the supported verification flow and return to that item. Read the client name, invoice reference, line items, total and due date in the document itself. A conversation summary can help you find an item, but it should not replace reviewing the saved version. If something is wrong, ask for a change or edit the draft before finalising it. Approval applies to a particular action; signing in or opening the review screen does not itself authorise delivery.
Approve the recipient and delivery preview
An invoice needs a valid destination as well as correct figures. Check the contact shown in the delivery preview and the exact message the client will receive. A client created in the dashboard does not need to be treated as an inbound WhatsApp conversation, but using an available WhatsApp delivery route still requires the appropriate contact details and permission. Check any consent requested by the flow. Do not substitute a different person or phone number just to get past a delivery restriction. If the preview cannot be prepared, read the explanation beside the action before continuing.
Treat WhatsApp connection and delivery as separate checks
A connected WhatsApp account is a starting point, not proof that every message can be delivered. The sender, recipient, messaging window and supported template route can affect a particular send. Gus should show an actionable result when something prevents delivery. If the interface asks you to open WhatsApp or restore a connection, complete that step and return to the existing item. Check its state before repeating the send. This guide does not promise that any arbitrary message can bypass provider restrictions, or that an unsupported email or SMS route becomes available simply because the invoice exists.
Keep draft, finalised, sent and paid distinct
These states answer different questions. A draft is available for review. Finalisation records the document in its final form. A successful delivery result concerns the message or document going out through the chosen route. Payment must be established from the relevant payment or accounting record. A customer saying yes to an invoice does not, by itself, establish that money has arrived. In the same way, acceptance of a quote is a decision about the proposed work, not evidence of invoice settlement. Read the document state and the delivery or payment information together rather than treating one badge as proof of everything.
Connect Xero when you need accounting sync
You can work with local documents without connecting every available app. Xero adds a separate accounting relationship, and supported automation depends on your plan and permissions. Before connecting, check the current comparison and select the intended Xero organisation. After syncing, inspect the latest result instead of assuming the connection guarantees that every change has reached the accounting system. Keep the accounting currency and recorded payment state intact. Where review or authorisation belongs in Xero, complete it there. Gus preparing a draft is useful, but it is not permission to skip the business checks that normally apply to your accounts.
Follow up using the current balance and conversation
If the invoice remains unpaid, check for a payment, part payment or client question before sending a reminder. Use the invoice reference so the client can identify what you mean. Our reminder templates provide starting points you can personalise; they do not determine which balance is outstanding. Review the final wording and destination just as you would for the original delivery. If a client disputes the amount or asks for a correction, resolve that question against the agreed work. A consistent record of the invoice, delivery and response is more useful than sending the same generic message through several channels.
Try a small, reviewable workflow first
Begin with one genuine invoice whose details you already understand. Ask Gus to prepare it, inspect the saved document, check the delivery preview and approve only when everything matches. Then confirm the recorded outcome in the dashboard. This gives you a repeatable routine without assuming that every task must happen entirely inside a single chat message. The practical benefit is a shorter path from your instructions to a checked document. Your business still decides what to charge, who should receive it and when to approve the action.
Frequently asked questions
Does asking Gus to create an invoice send it immediately?
No. Preparing a document and approving its delivery are separate actions. Review the saved invoice, recipient and delivery preview before approving the send.
Does an invoice reply such as Accept mark the invoice paid?
No. A customer reply is not payment confirmation. Check the payment or accounting record for settlement.
Do I need Xero to prepare a local invoice?
No. Xero is optional for local documents. Accounting sync and automation have their own plan, connection and permission requirements.