Use invoices for payment requests
Invoices support draft creation, editing, customer association, line items, sending by email, resend, status tracking, mark-paid flows, cancellation, print/download, search, filtering, and CSV export.
Use invoice status as the operating truth instead of keeping payment requests only in chat. This gives Overview, Follow-ups, and Customer Timeline better source data.
Use receipts for completed payment records
Receipts are first-class records for paid invoices, completed booking receipt flows where supported, and paid orders. Customer-facing receipt links are tokenized; merchants can search, filter, print/download, resend where policy supports it, and export receipt data.
If a receipt is connected to a store order, loyalty, gift card, or Business commerce adjustment, Helm stores snapshots so the historical document remains understandable later.
Keep tax and fee claims narrow
Helm can store and display supported fees, taxes, shipping, and payment-adjacent values where the product workflow supports them. It is not a legal or tax compliance engine.
If you need statutory tax advice, country-specific invoice compliance, or external accounting reconciliation, treat Helm records as operational documents and confirm compliance with your accountant or finance advisor.
Invoice and receipt workflow checklist
- Create one customer-linked invoice with clear line items, currency, due date, and notes the customer can understand.
- Send or resend invoices from Helm when supported so status, Follow-ups, and Customer Timeline have source data.
- Record paid work with a receipt or order receipt flow where the product workflow supports it.
- Print, download, or export documents from Helm instead of keeping the only record in chat or spreadsheets.