Detailed guide

Invoices

The workspace-wide invoice index for tracking billing lifecycle, due states, and payment progress across projects.

Invoices is the portfolio billing operations queue. It allows teams to prioritize collection risk and move invoice records through lifecycle checkpoints with clear context.

Quick summary

  • Prioritize overdue and issued invoices for collections follow-up.
  • Use filters to separate one client or project billing stream from the full queue.
  • Open invoice detail for evidence linkage and lifecycle action validation.

Put it into practice

  1. Start by checking invoice status cards to identify lifecycle pressure (especially Issued and Overdue queues).

    InteractionsInvoices page top cards: review Draft, Issued, Overdue, and Paid counts.
  2. Set Status, Client, and Project filters to target the billing slice requiring action.

    InteractionsInvoices filter toolbar: choose status/client/project filters.
  3. Use search for invoice number, client, or reference details to reach a specific billing record quickly.

    InteractionsInvoices search input above the table.
  4. Open invoice detail from the table and validate terms, line values, and evidence readiness before lifecycle changes.

    InteractionsInvoices table row: open detail link on the target invoice.
    Open workflow: Invoice Workflow
  5. Return to the index and verify state movement after issue/payment actions so queue metrics remain trustworthy.

    InteractionsBack on Invoices index: refresh row state and status-card implications.

What to review

Invoice status cards

Shows Draft, Issued, Overdue, and Paid counts so collections focus starts from current exposure.

Status, Client, and Project filters

Narrow invoice set to the billing segment needing action.

Search input

Searches invoice number, client, project, status, references, PO, totals, and billing dates.

Invoices table

Displays lifecycle state, references, totals, and date context for queue triage.

Detail open action

Opens invoice detail for line-level verification, issue/paid transitions, and evidence checks.

See guide: Invoice Workflow

Guardrails

  • Invoice queue status should be consistent with detail lifecycle transitions and payment dates.
  • Totals and references should be confirmed in detail before collections escalation decisions.
  • Invoice index visibility requires invoice-view access; lifecycle-changing actions remain permission-gated in detail pages.

If it starts drifting

  • If invoices are missing, clear filters and verify current user invoice permissions.
  • If overdue interpretation looks wrong, check due-date data and status transitions in invoice detail.