Finished pages you can copy.

Use this operation when you already know the invoice id and need its current state. List and search are separate endpoints; this one never filters.

Signature #

GET /v3/invoices/{id}

Parameters #

Path parameters are required. Query parameters are optional and never change which invoice is returned; they only shape the payload.

Request #

No request body. The examples below fetch the same invoice with line_items expanded.

curl https://api.northwind.example/v3/invoices/inv_a1b2c3d4e5f678901234abcd \
  -H 'Authorization: Bearer sk_live_...' \
  -G --data-urlencode 'expand=line_items'

import northwind

client = northwind.Client(api_key='sk_live_...')
invoice = client.invoices.retrieve(
    'inv_a1b2c3d4e5f678901234abcd',
    expand=['line_items'],
)

Response #

A successful response returns the invoice object. Amounts are minor units of the invoice currency; never floating-point major units.

{
  "id": "inv_a1b2c3d4e5f678901234abcd",
  "object": "invoice",
  "currency": "gbp",
  "balance_due": 12500,
  "collection_stage": "overdue",
  "line_items": [
    {"description": "Monthly plan", "amount": 12500}
  ]
}

Status codes #

Further reading: List invoices and Authenticating requests with an API key.

Twelve pages in this section. Guides first, then the API reference for the same objects, so a reader who needs the "how" before the "what" stays on the same path.

Guides #

1. Working with invoices
   1. Creating an invoice
   2. Line items and tax
   3. Voiding and credit notes
2. Setting up a reminder schedule
3. Configuring reminder escalation
   1. Changing the thresholds
   2. Testing a schedule change
4. How a dispute flag pauses escalation
5. How late-payment prediction works

API reference #

1. List invoices
2. Retrieve an invoice
3. Create an invoice
4. Reminders

Finance teams told us the seven-day overdue window felt polite. What it actually did was leave a genuine dispute unanswered for three days while the system waited to escalate.

What changed #

The due-today stage stayed put. Overdue now starts on day three. Final notice still lands on day fourteen. Collections handoff is unchanged. The only deliberate move was bringing the first human-shaped nudge forward.

The evidence #

Across six hundred Northwind accounts, the share that needed a call after the overdue stage dropped once the threshold moved. The figure below is the shape of that shift, not a promise for every ledger.

What we kept #

Dispute flags still pause escalation. Prediction still ranks who is likely to slip. The schedule is still a consumer-owned calendar, not a Northwind policy dressed as product.

We assumed a longer overdue window would feel gentler. It mostly just meant the first three days of a genuine dispute went unanswered.

Further reading: How a dispute flag pauses escalation and How late-payment prediction works.

Finance teams told us the seven-day overdue window felt polite. What it actually did was leave a genuine dispute unanswered for three days while the system waited to escalate.

What changed #

The due-today stage stayed put. Overdue now starts on day three. Final notice still lands on day fourteen. Collections handoff is unchanged. The only deliberate move was bringing the first human-shaped nudge forward.

Scroll this column to drive the decorative progress bar above. The bar is aria-hidden; headings and the on-this-page list remain the accessible orientation path.

The evidence #

Across six hundred Northwind accounts, the share that needed a call after the overdue stage dropped once the threshold moved. Earlier stages recover more without a call.

The figure is the shape of that shift, not a promise for every ledger. Teams still own their calendar; Northwind only ships the mechanism.

What we kept #

Dispute flags still pause escalation. Prediction still ranks who is likely to slip. The schedule is still a consumer-owned calendar, not a Northwind policy dressed as product.

Further reading lives on the related-content page (#420), not in this progress demonstration.