Invoices

Colabmacs7/7/26About 2 min

Overview

Invoices collect billable Charges into project-level billing documents.

They sit between charge generation and team-level statements:

Usage Record
     ↓
Charge
     ↓
Invoice
     ↓
Statement

Invoices are the right level when staff need to review billing for a specific project before those amounts are rolled up to the team level.

Invoices are intended to be billable artifacts, not just intermediate calculations.

An invoice groups together eligible charges for:

Invoices may include:

Invoices are generated from Charges.

Key behavior:

Project-level invoice generation can be run directly, and team-scoped workflows can generate invoices for all projects under selected teams.

Invoice rules operate on invoice totals after charges have already been grouped.

Typical uses include:

Invoice totals therefore include:

Invoices may move from editable operational billing into locked financial records.

Important behavior:

invoices remain part of the normal billing workflow while still under review
marking an invoice as paid makes it read-only
when an invoice is paid, associated charges are also treated as locked beneath it

If an invoice is later consolidated into a statement, it still remains the project-level billing artifact inside that statement.

Until an invoice is paid and locked, it may still change when the underlying billing data changes.

For example:

This means the invoice remains the live source of truth, while any previously generated export becomes stale and must be regenerated.

Invoices support export generation.

Invoice exports:

This makes invoices useful both for project-level review and for downstream finance workflows.

For more detail on export behavior, see Exports.

Use Invoices when you need to:

The Billing Admin → Invoices tab is the primary frontend working list for invoice review.