Does Sume offer invoice or PO billing? What is public and what is not
The Sume pricing page lists invoice and PO billing under Enterprise with custom volume pricing. What is public, what is not, and how to budget before the call.

Yes, in the sense that the Sume pricing page lists "Invoice / PO billing" as an Enterprise feature, next to custom plans and volume pricing, higher concurrency and controls, and priority support. The page gives no price, no payment terms and no minimum; the call to action is a contact address.
This post is short because the public record is short. It separates what you can read today from what a purchasing team has to ask.
What is public about Enterprise?
The pricing page, read on 2026-10-03, and its FAQ say the following about the tiers that are not self-serve.
| Item | Stated | Not stated |
|---|---|---|
| Billing | Invoice / PO billing | Payment terms, currency, minimums |
| Pricing | Custom plans and volume pricing | Any discount figure |
| Concurrency | Higher concurrency and controls | The number (the docs table shows 20 processing and 120 accepted, same as Scale) |
| Support | Priority support and account management | Response times |
| Contact | A support email address | A form or sales process |
What stays the same on invoice billing?
The pages cited here do not say, so do not assume. What the public docs do establish is the metering: every paid call reserves at submit, captures on success and refunds on failure, and GET /v1/usage with job_id, run_id or thread_id returns a summary with debited_usd_micros. That is the number an invoice would have to reconcile against, so keep the job ids from your own systems.
Top-ups are made in the dashboard, and the credits page says the public API has no top-up endpoint. Whether invoiced customers prepay or are billed in arrears is not on a page I could read, so ask before you design around either.
What should a purchasing team ask?
Write the questions before the call so the answers can be filed.
- Is the account prepaid, or billed in arrears against a limit?
- What happens to jobs when the limit is reached: the same
402 insufficient_credits, or a different path? - Are the per-unit rates on the API pricing page the starting point for the custom volume rate?
- Can usage be split by workspace or cost centre, and how does that appear on the invoice?
- What is the PO number process and the payment term?
- Who is the contact for disputes on a captured job?
How can you budget before the call?
Use the published rates as a ceiling and your own job logs as a floor. Multiply your expected units by the API rates, add a retake factor from your last month, and treat the result as the upper bound for the volume conversation. How to top up AI API credits covers the self-serve alternative, and the top-up sizing post shows what each purchase size buys.
If you will be under about $1,000 between top-ups, the self-serve wallet is enough and needs no negotiation. Invoice billing is for teams whose finance process cannot pay by card.
Sources
Related posts
More in Pricing
- Sume plans: Pro $40, Startup $120, Scale $400 and what they limit
What each Sume plan sets: monthly price, concurrent jobs, queue size and API write budget. Usage is billed at each model's rate, not by the plan.
- What a month on Sume Pro costs: $40 plan plus usage, three workloads
Sume Pro is $40 a month and usage is billed per call on top. Three workloads: $61.70, $200.25 and, on Startup, $917.50 for the month. The line items and shares.
- Sume Pro, Startup and Scale: $10, $15 and $20 per concurrent job
Sume plans are $40, $120 and $400 a month for 4, 8 and 20 concurrent jobs. That is $10, $15 and $20 a slot, and usage is billed separately at published rates.
- Sume TTS maximum cost per request: $0.95 at 20,000 characters
One Sume TTS request takes up to 20,000 characters at $0.0475 per 1,000, so the most one request can cost is $0.95. A cost ladder with the rules.
Written by Sume