Read the bill
What this workspace costs and why, including the allowance shown working.
The billing page makes the bill legible from inside the workspace. It states the plan, the projects being counted, the allowance applied, and what the total comes to.
The allowance, shown working
An allowance the customer cannot see is an allowance they do not trust. They count their projects, count the ones on the invoice, get a different number, and send an email to ask.
So the page states the rule first, applies the most expensive rate first and always takes the cheapest available assignment, shows the counts that rule produced, and only then shows the money.
Why no project is ticked as included
It looks as though the table should tick the projects the allowance covered. It should not, because there is no fact of the matter. A slot attaches to a rate, not to a project, and two active projects on the same plan are interchangeable. A tick against one of them would be a decision the product invented and would then have to keep, and the first time somebody archived that project the tick would move for no reason anybody could explain.
The split is shown where it is real, which is per billing stage: a project in planning and a project that is active are charged differently, and that is a fact about the project rather than an assignment the product invented.
How it is paid
A workspace admin can put a card on file from the billing page. "Set up payment" opens a Stripe-hosted checkout for the plan and term the workspace is already on; once Stripe confirms the subscription, the button becomes "Manage card and invoices", which opens Stripe's own screen for the card, past invoices, and cancellation. Card details are entered on Stripe's pages and never reach PadFlow.
The plan is still set by PadFlow, after a conversation. The card only pays for it.
What the invoice carries
The same lines the page above shows: the plan, then one line per stage for projects beyond the included count, at the rate card. On a monthly term the figures on the invoice already include the monthly premium, so each line reads as the uplifted rate rather than the rate card plus a fifth. The total is identical; the page phrases it the other way so the premium is visible as a choice.
When a project changes stage mid-term
The count PadFlow keeps is the count Stripe is told, the moment it changes. A project that goes active in month eleven of an annual term is charged one twelfth of the annual add-on for the month that is left. A project archived halfway through the term credits the rest of the year back to the account, to be applied to the next invoice. Nothing is recomputed at Stripe: the database decides what is owed for, Stripe prices it and collects it.
If a payment fails
The billing page says so, with the date. Stripe retries on its own schedule, and updating the card usually settles it. Nothing in the workspace is locked while it is sorted out.
How to
You open this when somebody asks what this workspace costs, and why.
- Billing has a route of its own rather than a section, because what a workspace costs is the one thing here you show a partner.
- The plan, the term and what is due next, with the arithmetic said out loud rather than asserted.
- The same lines an invoice carries, in the same order, so the two can be read against each other.
- Every project under the heading that decides what it costs. Samples never count.
- How many projects the plan includes, and which of yours are inside it.
- Nothing here is charged per person. Letting somebody into the workspace adds no line; what moves the bill is projects.
Related pages
Known limits
Nothing on this page changes a plan. Plans and terms are written by somebody who has had the conversation with you, and this page is where you check what was agreed. Putting a card on file is the one act it offers, and the card itself is entered and changed on Stripe's pages rather than here.