Billing
Everything about what your organisation pays sits on one page: Organisation, then Billing. It is a single scrolling page rather than a set of tabs, and it runs top to bottom from the plan, through what you are using, to how you pay for it.
Each organisation has its own subscription, its own billing cycle, its own payment methods and its own usage. Belonging to two organisations means two billing pages.
If you hold permission to view billing but not to manage it, the page opens read-only with a notice at the top saying so, and every control on it is disabled rather than hidden. That is deliberate: you can see the whole picture and check a figure without being able to change anything.
Your subscription
The first section names your plan, Host Plan or Guest Plan, with an Active badge beside it while the subscription is live.
For a host it also shows the base fee, the included active project value, the current billing period's start and end dates, and an estimated next bill. The estimate is the base fee plus whatever project value overage has accrued so far, and it moves during the month as projects start and finish. See Plans and entitlements.
For a guest it says what it is: free, no base fee, storage and SMS under fair-use limits.
Change subscription plan opens a side-by-side comparison and switches you.
Current usage
Three cards, and only one of them is billed.
Storage shows what the organisation is holding, with a document count under it and an expandable breakdown per project. It carries a Fair-use badge, because it is capped rather than charged.
Active Project Value appears for hosts only. Under the allowance it shows a progress bar and a Within limit badge; over it, the figure splits into the included amount, the amount over, and the estimated monthly charge on the difference. It expands to a per-project breakdown, and a project with no end date is marked as such in that list, because it is being counted at its full declared value rather than its annualised one.
SMS Sent counts broadcast site messages for the current calendar month. Fair-use as well, with a breakdown by message type.
Underneath, an estimated charges card appears only when there is something to estimate, and it repeats the two things people most often assume the other way round: the charge is based on the daily average, not the peak, and storage and SMS are not billed at all.
Usage history
A chart of the daily snapshots taken through the current billing cycle. It is the working behind the average the bill is calculated on, and it is the quickest way to see when a figure moved and which day it moved on.
Snapshots are taken once a day, so a project created this morning shows up tomorrow.
Cost control
Configure opens a panel with two settings in it. They are not in the same state as each other, and this is worth knowing before you rely on either.
Project value alerts
These work. Three thresholds against your included allowance, each switchable on or off. When the daily usage job finds you past an enabled threshold, it emails a warning naming the current figure, the included amount and the overage rate. Two conditions apply and both are easy to miss: the alert goes to the billing email and nowhere else, so with that field empty nothing is ever sent, and each threshold is limited to one email a day so a sustained overage does not become a daily nuisance.
The spend cap does nothing
The panel offers a maximum monthly spend and a choice between "Notify only" and "Block usage (hard limit)", and the setting is stored and read back to you correctly. Nothing enforces it. The cap dates from a period when storage and SMS overage were billed by usage; since those became fair-use caps, the only billed dimension is active project value, which is not something an upload or a send can push you past. Setting it is harmless and does nothing, in either mode. To control what a project costs, set its declared value correctly and archive it when it finishes.
Past invoices
Listed newest first, with a date, an invoice number, an amount and a link to the invoice itself. The five most recent are shown, with a note saying how many there are in total.
You get an invoice each time your monthly cycle resets, and each time you change plan. So a mid-month upgrade produces one immediately rather than waiting for the next cycle.
Payment methods
Cards are held by Stripe rather than by Teralo, and the page shows the last four digits, the brand and the expiry. One is marked Default, and the default is the one your subscription is charged to.
Add new card adds another; Set default switches which one is charged. On a phone the add-a-card flow uses the native payment sheet rather than an inline form.
Remove a card
You cannot remove your last card while a Host subscription is active. The delete control is disabled with a tooltip saying so. Add the replacement first, make it the default, then remove the old one.
Credit balance
Credits are applied to future invoices before your card is charged, and the card is only touched once the balance runs out. It is where a refund or a goodwill adjustment lands.
The Top Up button is disabled. There is no way to add credit yourself; a balance gets there because Teralo put it there.
The billing email
One field, and it does more than it looks like it does.
Every piece of billing correspondence goes to this address: the invoices, the payment failures, and the project value alerts described above. It is separate from any individual's account email precisely so that invoices can go to accounts payable rather than to whoever happened to set the organisation up.
Set it. An empty billing email means invoices fall back to the address of whoever created the organisation, and it means the usage alerts are never sent at all.
Billing address and tax ID
The name, address and tax number printed on your invoices. Changes apply to future invoices only; invoices already issued are not rewritten, which is what you want and also why it is worth getting right early.
The tax ID is only needed for a registered business. In Australia it is the ABN.
Cancel a subscription
Cancel subscription sits under the plan card, and the confirmation says your account will be downgraded to Guest at the end of the current billing period.
In practice the downgrade happens immediately. Stripe stops billing at the end of the period, so you are not charged again and you have paid for the rest of the month, but the organisation becomes a Guest organisation as soon as you confirm. From that moment it cannot create projects, and the host-only surfaces on the projects it already hosts behave as they do for a guest.
So cancel at the point you have actually finished, not at the start of the last month you have paid for. If you cancel early and need the rest of the period back, that is a support request.
Cancelling does not delete anything. Your projects, documents and records stay exactly where they are and stay readable. Deleting is a separate and irreversible action on the organisation settings page. See Setting up your organisation.
Invoiced rather than charged to a card
An organisation on an enterprise agreement is billed by invoice on thirty-day terms rather than by card, so the card section is not part of its signup and its plan is not changed from this page. Teralo administers it against the agreement, and the page says so rather than quietly rebuilding the subscription.
The product scope that agreement covers is shown when the code is entered, and afterwards it shows up only as which tools the organisation has. See Plans and entitlements.
Who can do what
Two permissions.
Viewing billing opens the page read-only. Give it to anybody who needs to check a figure or pull an invoice.
Managing billing enables everything: the plan change, the cancellation, cards, the spend cap and alerts, the billing email and the billing address. It implies viewing, so it is granted on its own.
Organisation administrators hold both automatically. Billing is also on the small floor of pages no plan may withhold, because an organisation that cannot reach its own billing page cannot administer its own account.