[{"data":1,"prerenderedAt":37},["ShallowReactive",2],{"$f148chu7h3675":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"html":10,"headings":11},"\u002Fdocs\u002Fcompany\u002Fbilling","Billing","Your plan, how you pay for it, what changing plan does, what is billed past what the plan includes, and what happens when a renewal fails.",null,false,[],"\u003Ch2 id=\"plans\">Plans\u003C\u002Fh2>\n\u003Cp>Every enterprise is on one of five plans: Free, Starter, Company, Scale or Enterprise. A new enterprise starts on\nFree, with no card. What each plan includes and costs is on \u003Ca href=\"\u002Fpricing\">pricing\u003C\u002Fa>, and what is held to is in\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend#plan-limits\">Plan limits\u003C\u002Fa>. Each enterprise is billed on its own: two enterprises are two plans.\u003C\u002Fp>\n\u003Cp>An enterprise that already exists upgrades from \u003Cstrong>Billing\u003C\u002Fstrong>, in the portal. A new one starts from its plan's button on\n\u002Fpricing: \u003Cstrong>Sign up\u003C\u002Fstrong> on Free and the paid plans, and \u003Cstrong>Request access\u003C\u002Fstrong> on Enterprise, which is priced for your\ncontract.\u003C\u002Fp>\n\u003Cp>The model bill stays your own. Runs use the model connections you add, with your own keys, and the provider bills\nyou for them directly (\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>). Your plan pays for the company around them: its\nmembers, runs, workspace runners and storage.\u003C\u002Fp>\n\u003Ch2 id=\"the-billing-page\">The Billing page\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Billing\u003C\u002Fstrong> shows:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>the plan, its current billing cycle, and the plans side by side, monthly or annual, each with what it includes and\ncosts;\u003C\u002Fli>\n\u003Cli>this cycle's usage of what the plan includes an amount of: members, workspace runner minutes, portal runs,\nconcurrent runs and storage;\u003C\u002Fli>\n\u003Cli>each member's inbox: its mail today against the plan's daily cap, and how long the plan keeps mail;\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Concurrent runs\u003C\u002Fstrong>, where a paid plan buys extra concurrent runs;\u003C\u002Fli>\n\u003Cli>the payment methods on file;\u003C\u002Fli>\n\u003Cli>every invoice, with its document to download;\u003C\u002Fli>\n\u003Cli>each closed billing cycle: what it used, and what was reported to be billed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>An owner sees all of it, and so does anyone allowed to see billing (\u003Ccode>billing:read\u003C\u002Fcode>). Changing anything on it takes\nthe right to change billing (\u003Ccode>billing:write\u003C\u002Fcode>). See \u003Ca href=\"#the-billing-grant\">The billing grant\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"checkout\">Checkout\u003C\u002Fh2>\n\u003Cp>Choosing a paid plan on \u003Cstrong>Billing\u003C\u002Fstrong> starts a checkout. Payments are taken by FloPay, our payment provider. Before\nanything is charged, you confirm you are buying for a business and accept the product terms. Checkout then takes the\nbusiness details (the legal business name, the billing address, the country, and a tax ID where the country has one)\nand the card, on FloPay's checkout page or in FloPay's own fields on \u003Cstrong>Billing\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>The plan moves when FloPay confirms the payment, not at the moment you check out. Enterprise is priced for your\ncontract: its card on \u003Cstrong>Billing\u003C\u002Fstrong> asks you to talk to us.\u003C\u002Fp>\n\u003Cp>When the product terms change, the next change onto a paid plan asks you to accept the new version first. Cancelling\nand withdrawing a downgrade never ask.\u003C\u002Fp>\n\u003Ch2 id=\"payment-methods-and-invoices\">Payment methods and invoices\u003C\u002Fh2>\n\u003Cp>Once the enterprise has a subscription, \u003Cstrong>Billing\u003C\u002Fstrong> lists the payment methods on file. With \u003Ccode>billing:write\u003C\u002Fcode> you can\nremove one and, where FloPay supports it for your subscription, add a card and choose which one is charged.\u003C\u002Fp>\n\u003Cp>Every invoice is listed with its amount and status, and its document downloads from \u003Cstrong>Billing\u003C\u002Fstrong>. A downloaded invoice\nshows the company's current name, including on invoices issued before a rename.\u003C\u002Fp>\n\u003Ch2 id=\"changing-plan\">Changing plan\u003C\u002Fh2>\n\u003Cp>With \u003Ccode>billing:write\u003C\u002Fcode>, choose another plan on \u003Cstrong>Billing\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Upgrade now.\u003C\u002Fstrong> A move up the plans applies at once, and FloPay charges the prorated difference for what is left\nof the current period.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Downgrade at the period end.\u003C\u002Fstrong> A move down, cancelling a paid plan included (a move to Free), takes effect at the\nend of the subscription's current period, with no refund. Until then the plan you have stays, and \u003Cstrong>Billing\u003C\u002Fstrong>\nshows the downgrade waiting and its date.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Withdraw a downgrade.\u003C\u002Fstrong> Choosing the plan you are on while a downgrade waits withdraws it. Choosing another lower\nplan replaces it, and choosing a higher one upgrades now instead.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>A downgrade deletes older history and mail.\u003C\u002Fstrong> Once it takes effect, run history and mail older than the smaller\nplan keeps are deleted at the next clean-up, and cannot be brought back. Until the period ends you can withdraw the\ndowngrade, and nothing is deleted because of it.\u003C\u002Fp>\n\u003Cp>Before a downgrade, \u003Cstrong>Billing\u003C\u002Fstrong> lists what the smaller plan cannot hold, and what happens to each from the day it\ntakes effect:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What\u003C\u002Fth>\n\u003Cth>On the smaller plan\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Members\u003C\u002Fstrong> past its included count\u003C\u002Ftd>\n\u003Ctd>On Free, the members hired first keep running, up to 2, and the rest are paused until a plan that holds them is in force. On a paid plan they keep running and are billed as extra members.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Enabled schedules\u003C\u002Fstrong> past its number\u003C\u002Ftd>\n\u003Ctd>On Free, the 3 created first keep running and the rest are paused. On Starter they keep running, and no new one can be enabled past 15.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Extra concurrent runs\u003C\u002Fstrong> bought\u003C\u002Ftd>\n\u003Ctd>Carried over at the new plan's price. Free sells none, so on Free they end. Runs past the new ceiling wait their turn.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Storage\u003C\u002Fstrong> past what it includes\u003C\u002Ftd>\n\u003Ctd>Billed per GB-month on a paid plan. On Free, new runs stop until storage is under 1 GB; nothing stored is deleted.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Run history and mail\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Kept for the new plan's period: what is older goes at the next clean-up after the move.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Nothing shrinks on a move up. Paused members and schedules run again the moment a plan that holds them is in force,\nwith nobody retrying them.\u003C\u002Fp>\n\u003Ch2 id=\"overage\">Overage\u003C\u002Fh2>\n\u003Cp>On a paid plan, work runs on past what the plan includes, and what is used past it is billed per billing cycle on the\nrenewal invoice:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A billing cycle is a month counted from the day your subscription started\u003C\u002Fstrong>, on that day of each month (the last\nday of a shorter month). An annual subscription is counted in the same monthly cycles.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When a cycle ends,\u003C\u002Fstrong> what it used past the included amounts is reported to FloPay, dated inside the cycle, and\n\u003Cstrong>Billing\u003C\u002Fstrong> shows it under that cycle. Each cycle is billed at the plan in force during it: a downgrade at the period\nend bills the next cycle at the new plan's rates.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When it is charged:\u003C\u002Fstrong> on your subscription's renewal invoice. On a monthly plan, that is the invoice at the end\nof each cycle, so each month's extra use is charged a month at a time. On an annual plan, extra use is still\ncounted month by month, and charged once a year, on the yearly renewal invoice.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Members are counted by member-days:\u003C\u002Fstrong> each day a member is in the enterprise is one member-day, and the extra\nmembers billed are the member-days past the plan's included members, as a share of the cycle's days. The COO\ncounts as a member. The CEO, the people who sign in and the OS's own tasks never do.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Workspace runner minutes and portal runs\u003C\u002Fstrong> are counted over the cycle. The OS's own tasks take no portal runs.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Storage\u003C\u002Fstrong> is billed in GB-months: the gigabytes held past what the plan includes, over the cycle.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Extra concurrent runs\u003C\u002Fstrong> are not usage. They are a number you buy under \u003Cstrong>Concurrent runs\u003C\u002Fstrong> on \u003Cstrong>Billing\u003C\u002Fstrong>, at the\nplan's price per run per month, billed with the plan: each month on a monthly plan, and twelve months of them at\neach renewal on an annual plan. More applies now, prorated as an upgrade is; fewer applies at the period end.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Free never bills overage: where Free says stop, work past it waits for an upgrade or the next month\n(\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend#plan-limits\">Plan limits\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"when-a-renewal-fails\">When a renewal fails\u003C\u002Fh2>\n\u003Cp>If FloPay cannot collect a renewal, the subscription is past due:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A banner says so,\u003C\u002Fstrong> across the portal and at the top of \u003Cstrong>Billing\u003C\u002Fstrong>: the last payment did not go through, and it\nwill be tried again. Someone without access to \u003Cstrong>Billing\u003C\u002Fstrong> is told to tell the owner.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The owners are mailed\u003C\u002Fstrong> each time a payment for the plan does not go through, with the amount due and a link to\n\u003Cstrong>Billing\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The work carries on\u003C\u002Fstrong> while FloPay tries again, on the plan you have. Update the card on \u003Cstrong>Billing\u003C\u002Fstrong> to pay.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>If the payment cannot be collected,\u003C\u002Fstrong> the subscription expires and the enterprise returns to Free, with Free's\nlimits from then on.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Once a payment goes through,\u003C\u002Fstrong> the past due mark clears and the plan carries on. After an expiry, choosing a plan\non \u003Cstrong>Billing\u003C\u002Fstrong> again starts a new subscription, and the plan comes back once FloPay confirms the payment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Deleting the enterprise cancels a paid subscription at once, with no refund\n(\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fisolation#closing-your-enterprise\">Closing your enterprise\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"the-billing-grant\">The billing grant\u003C\u002Fh2>\n\u003Cp>Who may see \u003Cstrong>Billing\u003C\u002Fstrong>, and who may change it, is part of a person's grant: seeing it is the scope \u003Ccode>billing:read\u003C\u002Fcode>,\nand changing it is \u003Ccode>billing:write\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Scope\u003C\u002Fth>\n\u003Cth>What it allows\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Ccode>billing:read\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Seeing \u003Cstrong>Billing\u003C\u002Fstrong>: the plan, usage, payment methods and invoices.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Ccode>billing:write\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Changing the plan and the payment methods, and buying extra concurrent runs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>\u003Ccode>billing:write\u003C\u002Fcode> can only be held by a signed-in person: an API token can hold \u003Ccode>billing:read\u003C\u002Fcode>, never \u003Ccode>billing:write\u003C\u002Fcode>,\nand a connected app never writes billing. Owners hold both by owning. See\n\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fpeople#the-billing-grant\">People and access\u003C\u002Fa>.\u003C\u002Fp>\n",[12,16,19,22,25,28,31,34],{"id":13,"text":14,"level":15,"planned":8},"plans","Plans",2,{"id":17,"text":18,"level":15,"planned":8},"the-billing-page","The Billing page",{"id":20,"text":21,"level":15,"planned":8},"checkout","Checkout",{"id":23,"text":24,"level":15,"planned":8},"payment-methods-and-invoices","Payment methods and invoices",{"id":26,"text":27,"level":15,"planned":8},"changing-plan","Changing plan",{"id":29,"text":30,"level":15,"planned":8},"overage","Overage",{"id":32,"text":33,"level":15,"planned":8},"when-a-renewal-fails","When a renewal fails",{"id":35,"text":36,"level":15,"planned":8},"the-billing-grant","The billing grant",1793013307889]