In this guide
Approval Plus Mortgage
Service guides

Bitbucket billing: separate workspace seats, build usage and payment records

A repository’s users, its pipeline consumption and the organization paying for them are related but different billing questions. Identify each before changing a card or disputing a charge.

Identify the billing location during the migration

Bitbucket’s billing documentation describes a move of usage meters into Atlassian Administration. The monthly-plan rollout starts on October 26, 2026, with allowances pooled at organization level rather than isolated by workspace. As checked on November 16, 2026, follow the migration state shown for your account instead of assuming an older workspace-only procedure still applies.

After migration, access to organization-level billing may require a billing-administrator role granted by the organization administrator. Repository or workspace administration does not necessarily provide that access. Put the organization name, workspace ID and billing period in your request so the right administrator can trace the usage without changing repository permissions unnecessarily.

Sources & further reading: [1] [3]

Separate the workspace plan from its usage meters

Review the workspace subscription and user quantity independently of usage. After migration, locate the relevant billing account in Atlassian Administration and identify the Bitbucket workspace whose plan you want to review. Compare its current subscription with the proposed change before confirming anything, so a request for one team is not mistaken for another.

Bitbucket tracks build minutes, Git LFS storage, Packages storage and Packages network separately. They represent execution, stored binary assets, stored packages and package download traffic. A runner’s size affects build-minute consumption: a five-minute step using a 2× runner counts as ten build minutes. This arithmetic explains units; it is not a quotation for a plan or an overage rate.

Sources & further reading: [1] [3]

Read annual-plan changes against their effective date

Atlassian’s current licensing page says annual-plan usage charging changes on December 3, 2026. Before that change, it describes annual plans as not billed for build-minute or Git LFS overages, with Packages unavailable to those plans. December 3 is a future date relative to this guide’s November 16 source check; do not treat the future arrangement as already active.

For a renewal or budget extending beyond that date, review the current account notice and published rates again. Keep the base subscription, included usage and any additional consumption as separate budget lines. A yearly subscription payment is not evidence that future variable usage has already been paid.

Sources & further reading: [3]

Trace a consumption spike back to pipeline runs

Use the repository’s Pipelines view to inspect the relevant run and its individual steps. Review the logs, execution details and reruns rather than relying on the final green or red status alone. The run selector helps distinguish an initial attempt from a later rerun when you investigate an unusually busy period.

Prepare a short engineering note with the repository, run reference, step, approximate duration and reason it ran. Compare that note with the billing period and the selected usage meter. It gives the billing administrator something concrete to reconcile and helps the developer identify repeated work. Changing a saved card does not explain why the same pipeline was executed several times.

Sources & further reading: [4]

Verify the payer and the invoice after a method change

For the new Bitbucket billing system, payment-method changes are made through the relevant billing account in Atlassian Administration. Open Payment method, choose Edit and verify the intended details. Record the masked identifier and date of the change, then review the actual invoice status; a saved method is not a receipt.

In the improved Atlassian billing experience, download the invoice from Invoices and match its period and line items to the charge. Keep base subscription and usage entries identifiable in your records. If the invoice is still due, investigate it as an unpaid invoice rather than marking it settled because the replacement card was saved successfully.

Sources & further reading: [2] [5]

Keep a funding allowance separate from build allowances

Approval Plus funding has a US$10 minimum, a 1% top-up fee below US$300 and no top-up fee at US$300 or more. A US$250 request credits US$247.50 after the platform fee, with network costs separate. That amount belongs in the payment budget; it does not buy a stated number of Bitbucket build minutes or change an organization’s included usage.

Use the latest invoice currency and amount when calculating the balance you need. Store the funding reference and merchant invoice separately, and reconcile them only after each record is available. This process documents spending without assuming that a particular card transaction, new plan or future usage change has been approved.

Sources & further reading: [6]

Your questions, answered

Does workspace administration automatically include the new billing controls?

Not necessarily. After migration, the organization’s billing-administrator role controls the relevant billing access. Ask the organization administrator to verify the role.

Does a yearly subscription mean usage can never generate another charge?

No. Review the included allowances and effective-date rules. Atlassian currently schedules the annual usage-billing change for December 3, 2026.

Is ten build minutes always ten minutes of elapsed time?

No. Runner size affects the measured quantity. For example, five minutes on a 2× runner counts as ten build minutes.

Sources & further reading

  1. Bitbucket: manage plans and the usage-billing migration ↗Checked Nov 16, 2026
  2. Atlassian: edit payment methods in the improved billing experience ↗Checked Nov 16, 2026
  3. Atlassian: Bitbucket licensing, usage meters and effective dates ↗Checked Nov 16, 2026
  4. Bitbucket: inspect pipeline runs and step details ↗Checked Nov 16, 2026
  5. Atlassian: understand invoices and their status ↗Checked Nov 16, 2026
  6. Approval Plus: funding fees and credited amounts ↗Checked Nov 16, 2026
APPROVAL PLUS

Your next step

Account, funding and card guidance in your language.

APPROVAL PLUS

Need a hand?

Our support team can help with your account, funding and card questions.

support@approvalplusmortgage.com