When should you send an invoice for a digital product?

A customer buys your workbook at 10.14 on a Tuesday. Another asks for six coaching sessions and wants an invoice addressed to their company. A third downloads a course and needs a receipt for their records. These are all payments, but they do not need the same billing process. The useful question is not simply whether to send an invoice. It is when an invoice helps, when an automatic receipt is enough, and when manual billing creates unnecessary work.

Start with the type of sale

A digital product sold from a public checkout has a different administrative shape from a private service agreement. If someone chooses a price, pays online and receives a file or access automatically, the transaction itself creates much of the record you need: the product, amount, date, customer details and payment status. Sending a separate invoice after every purchase can duplicate that work.

An invoice becomes more useful when the buyer needs to approve the purchase before payment, when several items are bundled into one engagement, or when you have agreed terms that do not fit a normal checkout. That might include a deposit, a balance due later, a fixed number of coaching calls or a project with a defined delivery date.

When an automatic receipt is enough

For a low-touch product, the best moment to send a receipt is immediately after successful payment. The customer is expecting confirmation, and the message can connect three things: what they bought, what they paid and how they get access. For a download, that may mean a file link. For a course or membership, it may mean an access instruction rather than an attachment.

This approach works because the checkout is both the order form and the payment record. It also avoids a common mistake: calling a payment confirmation an invoice when it does not contain the information the customer or their finance team requires. Check what your payment setup produces, then use accurate language such as receipt, order confirmation or invoice.

A storefront can keep this process in one place. With store.fan’s digital downloads, for example, a buyer can purchase a file through your storefront rather than waiting for you to confirm an email manually. store.fan takes 0% of sales, while Stripe’s own processing fee still applies, and the money goes directly to your Stripe account.

When to send an invoice before payment

Send an invoice before payment when the client needs a document to authorise the spend. This is common with companies, charities, schools and larger teams. Their process may require a supplier name, billing address, purchase order reference, payment deadline and a description of the work before money can leave their account.

1. 1Agree what is being sold, including the deliverables, number of sessions or access period.
2. 2Confirm who the invoice is addressed to and whether the client has a purchase order or internal reference.
3. 3Set the payment terms in plain language: the amount due, currency, due date and what happens if the work is delayed or cancelled.
4. 4Send the invoice before starting work if the project is substantial, or before each agreed stage if payment is split.
5. 5Mark it as paid only after the payment has cleared, then keep the invoice, agreement and payment record together.

Coaching needs more than a payment document

Coaching is often sold as a product but delivered as a service. That distinction matters. A checkout can collect money for a package, but your client may also need to know how sessions are booked, how much notice is required to reschedule, whether unused sessions expire and what happens if either side ends the arrangement.

For a single call, a straightforward checkout and confirmation may be enough. For a six-session package, an invoice can make the scope and payment schedule visible before the first session. Your accompanying terms should do the rest. The invoice is evidence of what was charged; it is not a substitute for an agreement about delivery.

The same logic applies to a cohort, webinar or membership with a company sponsor. If access is automatic and the customer pays the listed price, the checkout record may be sufficient. If you are negotiating seats, dates or private delivery, treat it as a client engagement and document the arrangement before taking payment.

Build a process you can maintain

Manual invoicing feels manageable when you have three clients. It becomes fragile when you have three different payment dates, two currencies, a deposit, a refund and several overdue messages to remember. Before choosing a process, write down the events you need to track: invoice sent, payment due, payment received, product delivered, access revoked, refund issued and follow-up required.

For public digital sales, reduce the number of hand-offs. Put the offer, payment and delivery together, and use your payment records as the source of truth. For negotiated work, keep a simple invoice number and status for each client. A spreadsheet can be enough at small volume if every row has an owner and a next action.

The tool should match the work, not the other way round. store.fan can act as the public storefront for products and access-based offers, with Stripe handling the payment connection. If you sell from your phone, the store.fan iOS app can provide instant sale alerts, which helps you notice successful purchases without checking your dashboard repeatedly.

Questions to settle before you send anything

A useful rule is to invoice when the buyer needs an agreement to approve the spend, and to use an automatic receipt when the buyer has already chosen and paid for a clearly defined product. Review the process whenever your offer changes from a file to access, from access to service, or from an individual buyer to an organisation.