Invoice

Overview

Invoices are the billing documents your customers pay. Revvly auto-generates a subscription invoice on each renewal cycle, and for mid-cycle expansions, service charges, refunds, and variable usage true-ups. Renewal invoices can also be issued ahead of the renewal date by a per-period lead time you configure. Each invoice contains line items — '10 seats @ $5', 'Pro Bundle April 2026' — and tracks payment status through to collection. A plan made of several priced modules bills one line per module, named after it, rather than one combined line; the lines are still a single discount target, so a fixed amount off the plan comes off once and is spread across them. An invoice also has an issue state, separate from payment: a renewal that cannot be totalled yet — because a metered period has not sealed — is created as a Draft with no number, no dates and no payment status, so it stays out of receivables and AR aging until it issues. It picks up its number and dates at the moment it issues, which is what keeps numbers in issue order. A draft that is abandoned is voided, never deleted. A Pending or Overdue subscription invoice can be regenerated to pick up the subscription's current pricing and the client's current payment terms; settled invoices are left untouched. Regenerating a Pending or Overdue invoice that carries tax also re-checks the tax over its existing lines, so a correction to the tax setup (a client taxed in a country you are not registered in, a changed rate) reaches an invoice already issued; the tax change is recorded as a reversal and a new entry in the tax ledger rather than an overwrite, and an invoice that is part-paid, a credit note or already credited is left as it is, where a correction goes through a credit note. Unmatched invoices (e.g. from CSV import) can be linked back to a subscription after the fact. A Drive import can also reconstruct the subscriptions from a client's own invoices: the charges are clustered into the plan shapes they imply, catalog gaps can be filled from those charges, and committing a client creates both the invoices and the subscriptions rather than leaving you to invent the relationship first. Payments can be recorded in the dashboard or posted straight from your payment system through the invoice payment webhook, in full or a part at a time — a part-paid invoice tracks how much has been collected and how much is still due, and stays open until the balance clears. A credit note is an invoice too: same collection, same number sequence, same PDF, with a negative total and the type Refund. That is what lets an unapplied credit reduce what a client owes without any receivables query needing to know credit notes exist. A credit note is never chased — no due date, no aging, no dunning — and is either applied to one of the client's open invoices or refunded in cash.

How it connects

This concept highlighted in context. Click a peer to navigate.

• Belongs to one Client
• Optionally linked to a Subscription
• Imported Drive invoices can reconstruct the subscriptions they imply
• Generated from Billing Period Snapshots for variable usage
• Held as a Draft until every Usage Reading it carries is sealed or waived
• Applies active Discounts as the final step (post-pricing resolution)
• May carry credit notes raised against it, up to its own total

Key fields

What you’ll see when creating or editing a Invoice.

Example