What is online invoicing?

The short answer

An online invoice turns a traditional billing document into a connected digital record. An authorized business user creates the invoice, identifies the customer, adds the goods or services being billed, sets the information the platform requires, and sends or shares the invoice. The customer reviews the request and, if the provider supports online payment for that invoice, follows the hosted payment flow. Staff then confirm the current result from the authenticated business account.

Stripe's current invoicing documentation describes invoices as itemized lists of goods or services that can be sent to customers for payment and managed through a dashboard or API. Square's current U.S. support documentation describes creating, sending, scheduling, and managing digital invoices from its dashboard and supported apps. These are useful examples of the general workflow, not a universal specification for every invoicing product.

How an online invoice moves from draft to record

1. Create the customer and invoice record. An authorized user selects or adds the customer, enters the relevant line items, and includes a recognizable internal reference when the provider supports one.
2. Review the customer-facing details. Staff verify the business identity, customer, description, amount, delivery channel, and other information shown before sending.
3. Send or share the invoice. The platform may deliver the invoice by email or another supported channel, or provide a link the business can share through an established customer conversation.
4. The customer reviews the request. The customer opens the invoice, checks the details, and uses an available response or payment option.
5. The platform updates the invoice. The invoice may move through draft, open, paid, voided, or other provider-defined states as actions occur.
6. The business verifies and reconciles the result. Staff use the authenticated dashboard and approved records to confirm the current invoice and payment status.

For a closer look at the customer payment step, read how card payments on invoices work.

What an online invoice commonly contains

The available fields and labels are product-specific. A business should preview the actual customer view rather than assume that a field visible to staff also appears to the customer. Clear descriptions and consistent internal references make it easier to connect invoice activity with work orders, customer records, and accounting processes.

Online invoice, payment link, or virtual terminal?

• Online invoice: Best understood as a digital billing record with customer, item, amount, delivery, and status context. It may include a hosted payment page.
• Payment link: A shareable route to a provider-hosted checkout. It may not include the same itemized invoice record or lifecycle. Learn what a payment link is.
• Virtual terminal: A staff-facing interface where an authorized business user enters a payment. It differs from asking a customer to open and act on an invoice. Review what a virtual terminal is.
• Hosted invoice payment page: The customer-facing page associated with an invoice. It is one component that an online invoicing product may provide. See how hosted invoice payment pages work.

The right tool depends on the business process. If the customer needs itemized billing context and the business needs an invoice record, online invoicing may fit the workflow. A simpler hosted checkout or a staff-entered payment may call for a different tool.

Questions to ask before choosing a workflow

• Can the invoice show the business identity and billing detail customers need to recognize the request?
• Which delivery channels are supported, and how can staff confirm that an invoice was sent?
• What does the customer see on a phone and on a desktop browser?
• Which invoice states exist, who can change them, and how are changes recorded?
• Can staff match an invoice to a work order, customer record, or accounting reference?
• How are reminders configured, reviewed, paused, or stopped?
• What roles and permissions are available for employees who create, send, or review invoices?
• Where does the business confirm the current payment result and invoice status?

Evaluate these questions in current provider documentation and, when possible, with a provider-supported preview that uses no real payment credentials. A feature documented by Stripe or Square should not be generalized to another provider without checking that provider's current materials and the business's account settings.

Keep invoice delivery and review privacy-safe

An invoice should contain enough information to explain the request without exposing unnecessary sensitive data. Do not place full card numbers, security codes, passwords, bank credentials, complete account numbers, or secret API keys in invoice descriptions, attachments, ordinary email, text messages, shared notes, or general contact forms. Customers should enter payment information only through the provider-designated payment interface.

Give each worker appropriate individual access when the platform supports it, and remove access when duties change. Customers should also have a separate, known way to question an unexpected invoice. Staff should verify invoice and payment results inside the authenticated provider system rather than relying on a screenshot, forwarded email, or reply message.

A practical evaluation exercise

Map one representative invoice from creation through completion. Record who creates it, which customer and order details are needed, how it is reviewed, how it reaches the customer, what the customer sees, and where staff confirm its final state. Open the customer view on both a phone and a desktop browser, and check that the business name, descriptions, amount, and support path are clear.

Then compare the workflow with the business's existing records. Identify the reference that connects the invoice to a customer, job, order, or accounting entry. Document who can correct a draft, who can send it, and what staff should do when the customer questions the request. This exercise reveals whether online invoicing improves the process or merely adds another disconnected system.

Common questions