Use WhatsApp for delivery while keeping the invoice, recipient, message and payment status in business records.

Confirm the channel
Ask which number should receive business documents and obtain any permission needed.
Keep delivery short
Name the invoice number, amount, due date and attached or linked document.
Preserve the invoice outside chat
The PDF and database record are the source; a chat can be deleted or moved.
Follow up with context
Refer to the original number and due date and confirm payment against the relevant account.
Confirm the channel in practice
A tradesperson sends invoice BZ-104 for £780 to the business number confirmed by the client. The message names the invoice, due date and attached PDF but omits internal job notes. The sent invoice remains in Billoz, so losing chat history does not remove the formal billing record or its payment status.
Follow up with context review
Verify the number and recipient before sending, especially when a client has several contacts. Keep the message concise, avoid unnecessary personal data and retain the PDF independently. A delivery tick does not prove that the correct person accepted the invoice or that payment has cleared.
Agree whether chat is an accepted billing channel and provide another way to obtain the document. Use a message that can be understood without scrolling through earlier conversation, but do not paste bank credentials or private project history unnecessarily. If the invoice changes, send the corrected formal document and identify which version replaces the earlier one. Record payment against the invoice only after checking the receiving account, amount, currency and reference. Review connected-device access regularly, revoke old sessions and keep contact consent or communication preferences with the client record.
Put the process into practice
Open the matching Billoz workflow, then use the calculator or planning tool to check the relevant figures.
Sources
Written and reviewed by the Billoz editorial team at WILLIATION TECHNOLOGIES LTD. Published 1 May 2026; reviewed 19 September 2026.
