Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →GitHub documents a sales tax exemption certificate upload for US-based organization and enterprise accounts that use the GitHub Customer Agreement. If your account is one of those, the owner or billing manager can upload a JPEG, PNG, or PDF certificate from Billing & Licensing. GitHub’s documentation does not describe this workflow for personal accounts, so if you bill a personal account, do not expect the same option.
Who the certificate upload covers
GitHub’s own billing guidance is specific about eligibility. The sales tax certificate page, titled “Adding a sales tax certificate” in GitHub Docs, states the condition in one sentence: “If you’re a customer in the United States with a GitHub Customer Agreement and you’re exempt from sales tax, you can upload a certificate to ensure the correct sales tax amount is calculated.” The current billing index repeats that sentence.
Read that sentence as three conditions that must all be true:
- Location: the account is US-based, and the billing country is United States of America.
- Account type: the account is an organization or an enterprise. The cited instructions do not establish the feature for a personal account.
- Agreement: the account is governed by the GitHub Customer Agreement.
The table below shows how each account type maps to the workflow, based on the documentation as checked on 8 October 2026.
#1 Best Overall
- Quick reference learning guide
- Definitions and glossary of terms
- Tax tips, and everything else you need to know about filing
- Common mistakes, understand audits
- Claiming a dependant and more
| Account type | Certificate upload documented? | What to do |
|---|---|---|
| US-based organization on the GitHub Customer Agreement | Yes, per GitHub Docs | Follow the steps below as an owner or billing manager. |
| US-based enterprise on the GitHub Customer Agreement | Yes, per GitHub Docs | Follow the steps below at the enterprise level. |
| Personal account | Not established by the cited instructions | Do not assume the Sales Tax section exists. Ask GitHub Support or your tax adviser how exemption applies to your account. |
| Non-US organization or enterprise | Not established by the cited instructions | The sentence above is limited to US customers, so this workflow is not described for you. |
Check the account before you start
Gather these items before you open the settings page. Most failed attempts trace back to one of them.
- Your role. GitHub’s billing guide says billing information is available to an owner, a billing manager, or someone with equivalent permissions.
- A valid exemption certificate in JPEG (
.jpgor.jpeg), PNG, or PDF format. - Complete billing address fields, including City and Postal/Zip code, with no errors reported.
- A billing country set to United States of America.
Upload the certificate
- Open the organization or enterprise account on GitHub, not your personal profile.
- Go to Billing & Licensing, then open Payment information.
- Correct any billing details that are wrong or incomplete. GitHub notes that missing address information or reported errors hide the upload option.
- In the Sales Tax section, select Upload certificate.
- Choose a JPEG, PNG, or PDF file and submit it.
If the Sales Tax section is missing
Work through these checks in order:
- Confirm the billing country is United States of America. GitHub says the section may not appear otherwise.
- Re-enter the address fields and clear any error messages. An address the system rejects removes the upload control.
- Confirm you are viewing the organization or enterprise, not a personal account, and that the account uses the GitHub Customer Agreement.
- If all of these are correct and the section still does not appear, contact GitHub Support rather than repeating the upload attempt.
What happens during review
While GitHub reviews the submission, it marks the account as tax exempt. If the certificate is not approved, GitHub’s instructions say to upload a new one. The cited documentation does not publish a review time, so do not plan around a specific number of days. An upload also does not create exemption eligibility by itself. The certificate has to be valid for the purchase, and the decision to accept it rests with GitHub’s review.
Rank #2
Fees, taxes, and who pays them
GitHub bills personal, organization, and enterprise accounts separately. Its billing documentation distinguishes fixed plan charges, subscription charges, and variable metered usage charges. You can review billing and usage on the account’s Billing and licensing pages, or retrieve them through the REST API.
The US Terms of Service set out who carries the cost. The Payment section states: “You are responsible for all fees, including taxes, associated with your use of the Service.” That sentence is a contract term. It does not decide whether a particular organization or enterprise qualifies for an exemption under state or local rules. The certificate workflow only applies a certificate you hold to eligible GitHub billing. Whether your business is exempt is a question for your state tax authority or a qualified tax adviser.
In practice, this means you should treat the upload as the step that tells GitHub which tax to leave off your invoice, not as a guarantee that tax will be removed. Keep a copy of every certificate you submit and of the approval notice, if GitHub sends one.
Verified on 8 October 2026 against GitHub Docs billing pages. Check the Sales Tax section again if GitHub changes its billing interface or its certificate eligibility rules.
Quick Recap
Rank #4
- Used Book in Good Condition
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
