## TL;DR

Stripe lets you set custom invoice number prefixes (e.g. per entity or region) while Stripe keeps the sequence itself gapless per account. Set the prefix in your invoice settings to match your accounting convention, and know that Stripe controls the incrementing: you cannot set arbitrary numbers or reuse them. For multi-entity setups, use distinct prefixes per entity so each sequence stays clean and auditable. Some jurisdictions require gapless sequential numbering by law; Stripe's per-prefix sequences satisfy this, but document the scheme for your auditors.

## The query

```text
Stripe invoice number custom prefixes and sequencing rules
```

## Use this when

- Invoice numbers matching accounting conventions
- Multi-entity invoice numbering in Stripe
- Legal sequential numbering requirements

## Not for

- Credit note numbering (separate sequence)
- Custom invoice IDs in your own system (use metadata)

## Steps

1. Decide the prefix scheme: per entity, per region, or per brand.
   Expected output: The convention is defined before configuration.
2. Set the custom prefix in Stripe's invoice settings.
   Expected output: New invoices carry the prefix.
3. Confirm the sequence increments gaplessly within each prefix.
   Expected output: Auditors see clean sequences.
4. Check your jurisdictions' numbering laws against Stripe's behavior.
   Expected output: Legal requirements are satisfied and documented.
5. Record the scheme in your accounting manual.
   Expected output: Finance and auditors share the same reference.

## Variant phrasings

### Stripe custom invoice number prefix

### invoice numbering sequence Stripe

### gapless invoice numbers Stripe

## Root cause

Stripe owns the sequence because gapless, unique numbering is a correctness property the platform must guarantee; the prefix is yours because naming is a business convention. Splitting it this way gives you the branding without the risk of duplicate or gapped numbers.

## Edge cases

- Deleted draft invoices can leave gaps in some numbering setups; check your jurisdiction's tolerance
- Prefix changes apply to new invoices; existing numbers never rewrite

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_fURic-2ycEFUt6VE9bIlag