In this guide
Approval Plus Mortgage
Service guides

GitLab payments: billing ownership, subscription seats and renewal invoices

A guide for the person paying a GitLab subscription. Match the purchase to the right group or installation, check the next seat count and keep invoice settlement separate from access administration.

Match the purchase to the right group or installation

Identify whether you are buying GitLab.com or GitLab Self-Managed. A GitLab.com subscription applies to a top-level group; being signed into a personal user account does not mean every group you can access shares that subscription. Record the intended group or installation and the company contact who will manage the purchase.

Check the selected tier, seat quantity, add-ons, contract period and final invoice currency before checkout. Keep a short purchase record explaining which team needs the paid features. This makes it easier to spot an order assigned to the wrong group without buying the subscription a second time.

Sources & further reading: [2]

Use Customers Portal to maintain the payment account

GitLab’s Customers Portal manages subscription billing. Its documentation requires a credit card on record for portal purchases and directs customers who need another payment arrangement to its sales or billing team. This is a statement of the merchant’s workflow, not confirmation that any particular Approval Plus instrument has been tested or approved.

Open Billing account settings to add or edit a method. Check the default selection, because automatic renewals use that default method. Several saved methods do not mean the most recently added one will necessarily pay your renewal. Let the authorized billing account manager make the change and retain only a masked reference in internal purchase notes.

Sources & further reading: [1]

Review billable seats before increasing or renewing them

Use the subscription’s seat-management controls to compare purchased capacity with billable users. GitLab documents a purchase summary when seats are added: it shows the full total and credits for amounts already paid, with the net change charged. Read that summary instead of multiplying a public headline price by a guessed number of employees.

Adding seats and reducing the next renewal are different decisions. GitLab documents seat reductions at renewal, so removing a user does not by itself mean the current subscription quantity or an already issued invoice immediately shrinks. Review inactive users and the required quantity before renewal. Preserve the seat-change receipt so finance can explain an extra charge within the existing contract term.

Sources & further reading: [3]

Plan funding independently of the subscription entitlement

Approval Plus Essential issuance costs US$1. Plus issuance costs US$10, with available BIN and Visa/Mastercard selection and seven-day replacement coverage from issuance. These are card issuance terms, not GitLab seat prices. Check the exact payment-method requirements before deciding which instrument to use for the account’s purchase.

Approval Plus has a US$10 minimum funding request. A request below US$300 carries a 1% top-up fee; US$300 or more, including exactly US$300, carries 0%. For example, US$100 credits US$99 after that platform fee. Network charges are additional. A request has a 15-minute payment window, and its receipt is reviewed before account credit. None of these steps activates a GitLab subscription by itself.

Sources & further reading: [1] [4] [5]

Reconcile invoice status and the next renewal together

In Customers Portal, open Invoices and match the invoice ID, amount due and payment status to the purchase you intended. A direct invoice can be paid through its payment action. Save the result rather than treating an email notification alone as proof that no balance remains.

Review the subscription’s renewal indicator and the next seat quantity as a separate check. GitLab notes that portal purchases normally enable automatic renewal and that seat counts do not fall automatically at renewal. If you bought through a reseller or cloud marketplace, use that seller for its invoice or commercial changes instead of assuming the direct-purchase workflow applies.

Sources & further reading: [1] [2]

Your questions, answered

Does one paid GitLab.com subscription cover every group I can access?

No. The documented subscription scope is the relevant top-level group. Confirm that group before purchasing or investigating access.

Does removing users automatically reduce renewal seats?

Do not assume it does. Review the billable count and the renewal quantity, and use the documented process to renew for fewer seats.

Who supplies the invoice for a reseller purchase?

Use the reseller that made the sale. GitLab’s direct Customers Portal billing workflow is not a substitute for the reseller’s invoice process.

Sources & further reading

  1. GitLab: manage billing account, payment methods and invoices ↗Checked Nov 16, 2026
  2. GitLab: manage subscriptions and renewals ↗Checked Nov 16, 2026
  3. GitLab: manage purchased and billable seats ↗Checked Nov 16, 2026
  4. Approval Plus: Essential and Plus card features ↗Checked Nov 16, 2026
  5. Approval Plus: stablecoin funding workflow and fees ↗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