JCT on a GitHub invoice means Japanese Consumption Tax. GitHub may apply it when the billing profile, customer details, product, and contracting arrangement indicate a Japan-related transaction. Japan’s standard consumption-tax rate is 10%, although the invoice and applicable transaction determine the amount. Adding a company name or tax number may improve billing records, but it does not automatically make a subscription tax-free or prove that the tax is creditable.
Start with the invoice and the account that owns the subscription. Confirm the billing country, legal customer, supplier, tax rate, and any qualified-invoice registration details before posting the cost to your books.
What JCT means on a GitHub invoice
JCT is Japan’s consumption tax, broadly comparable to VAT or GST. It may appear as a separate line or be reflected in a tax-inclusive total. Japan’s general rate is 10%; an 8% reduced rate exists for qualifying categories, but ordinary hosted software subscriptions would not normally be treated as a reduced-rate purchase. See the National Tax Agency’s rate guidance at nta.go.jp.
The invoice—not an old screenshot, search result, or simple percentage calculation—is the controlling record for the charge. Currency conversion, rounding, tax-inclusive pricing, credits, and refunds can make the arithmetic look different from 10% of a displayed plan price.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Why GitHub may charge Japanese consumption tax
Japan’s tax rules can cover electronic services supplied to customers in Japan, including services supplied by foreign businesses. The National Tax Agency discusses electronic-service taxation and distinctions between consumer and business transactions at nta.go.jp.
For a particular GitHub charge, the result can depend on:
- the billing country and address;
- whether the subscription belongs to an individual or an organization;
- where the customer is established and whether the transaction is consumer or business-facing;
- the GitHub product and contracting entity;
- whether billing is self-service, enterprise-contract, reseller, or Marketplace billing; and
- the customer information GitHub has verified.
GitHub Free upgrades, paid individual plans, GitHub Team, GitHub Enterprise Cloud, Copilot, and organization subscriptions may therefore not all follow an identical workflow. Enterprise Server purchased under contract, Microsoft or corporate procurement, reseller invoices, and third-party Marketplace services may be outside the normal GitHub.com billing flow.
Does entering a Japanese tax number remove JCT?
No automatic exemption follows from entering a company name or identifier. Updating those fields can help GitHub identify the legal customer and produce more accurate documents, but it may leave the tax unchanged. GitHub may also require a particular identifier or supporting information.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Check these facts before assuming a different treatment:
- Is the billing account owned by the company, or is an individual paying personally?
- Is the organization’s Japanese legal name and address recorded on the organization billing profile?
- Is the number a corporate number, a general tax ID, a foreign VAT/GST number, or a Japanese qualified-invoice registration number beginning with “T”? These are not interchangeable.
- Does the document identify the supplier and show the information needed for a qualified invoice?
- Was the subscription bought directly from GitHub or from a Marketplace seller, reseller, or enterprise sales arrangement?
Do not select another country to avoid tax, self-apply reverse charge, or delete a tax line without confirming that the transaction qualifies and that GitHub has corrected its records.
Where to update GitHub billing information
GitHub changes navigation labels and eligibility rules. Begin at GitHub’s billing documentation and use the account that actually owns the subscription. In broad terms:
- Sign in to GitHub.
- Open the relevant personal account or organization.
- Open Settings, then the billing section, which may be labelled Billing and licensing or similarly.
- Review billing information, payment method, billing address, tax information, invoices, and payment history.
- Save changes and check which future invoice they affect.
A personal profile update may not alter an organization’s invoice. Organization owners or billing managers may need to make the change. Enterprise or sales-managed customers should use their contract or GitHub billing contact rather than assuming self-service settings apply. Updating tax information after an invoice date may affect future documents only; ask support whether an already-issued invoice can be corrected.
How to inspect a GitHub invoice for Japanese accounting
Japan’s qualified-invoice system started on October 1, 2023. The National Tax Agency’s overview explains that a qualified invoice generally includes the issuer’s registration number, applicable tax rate, and consumption-tax amount by rate: NTA PDF.
Download the actual invoice or credit document and check:
Rank #3
- supplier legal name and required issuer details;
- any qualified-invoice registration number;
- invoice or document number and date;
- customer legal name, where required or useful;
- description and billing period for the GitHub service;
- taxable amount, tax rate, and JCT amount;
- currency and any exchange-rate information; and
- whether the file is an invoice, receipt, statement, or merely a payment confirmation.
A card receipt is not necessarily a qualified invoice. Do not label a GitHub document compliant until its contents and the supplier’s status have been checked.
Can a company claim the JCT as an input-tax credit?
A JCT line alone does not establish a credit. Under Japan’s invoice system, a general-taxation business generally must preserve accounting records and qualified invoices to claim a purchase-tax credit, subject to statutory exceptions and transitional rules. The NTA’s filing guidance is at nta.go.jp.
Your result depends on whether the purchase is a taxable business expense, the invoice information, and your filing method—general taxation, simplified taxation, tax-exempt treatment, or another regime. Simplified taxation has eligibility conditions, including the relevant base-period taxable-sales threshold of ¥50 million or less, and is not automatic for every small business; see NTA guidance.
A Japanese customer’s own qualified-invoice-issuer registration does not determine how GitHub taxes its purchases. The registration number on a supplier invoice belongs to the supplier. Foreign businesses and customers considering reverse charge need advice on their specific facts.
What to do when the JCT looks wrong
- Download the invoice and confirm the billing country, date, currency, and tax line.
- Identify whether it belongs to your personal account, an organization, or an enterprise contract.
- Check the legal name, address, and tax information that were in effect on the invoice date.
- Confirm whether the document is for GitHub itself or a Marketplace seller.
- Contact GitHub billing support with the invoice number, account or organization name, billing country, legal name, tax-registration information, and a concise explanation of the suspected error.
- Ask whether GitHub can reissue the invoice or provide a credit document. Do not assume a refund or correction is automatic.
- Keep the original document, any corrected invoice or credit memo, payment evidence, and support correspondence.
Common causes include an old address, a company subscription paid through a personal account, an organization profile that was never updated, tax information submitted after billing, a different account processing the payment, Marketplace billing, or the mistaken assumption that a tax number creates an exemption.
Special cases: Copilot, Marketplace, and enterprise billing
Copilot and standard GitHub plans
These may be billed through account or organization subscriptions, so identify the owner and inspect the invoice rather than relying on the product name alone.
Marketplace purchases
A third-party Marketplace seller may be the supplier. Its invoice, tax treatment, refund process, and support contact can differ from GitHub’s. Apply advice to the supplier named on the document.
Enterprise and procurement arrangements
Enterprise agreements, resellers, distributors, Microsoft procurement, and GitHub Enterprise Server contracts may use negotiated terms and separate invoices. The contract and issuing entity control the analysis.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Four practical examples
Japanese individual
An individual in Japan buys a paid GitHub plan with a personal account. The invoice shows a Japanese billing address and JCT. That is consistent with ordinary consumer billing; the person should retain the invoice and payment record but should not treat the tax as a business input credit without a qualifying business and documentation.
Japanese corporation using an organization
A company’s organization pays for Team or Copilot, but an employee’s personal profile contains the card. The employee should not assume that changing the personal profile changes the organization invoice. An authorized organization billing manager should review the organization’s legal name, address, tax information, and future invoices.
Recommended Free Tools
Best Value
Japanese qualified-invoice issuer
A registered Japanese business receives a GitHub invoice. Its own “T” registration does not automatically remove JCT. The business must check whether the invoice identifies the supplier and contains the information its accounting method requires before considering any purchase-tax credit.
Overseas company with Japanese staff
An overseas company pays for GitHub used by Japanese employees or contractors. Physical user location alone does not settle the result. The company should establish who contracted with GitHub, which entity issued the invoice, where the customer is established, whether the transaction is B2B or B2C, and whether reverse-charge or local registration rules apply.
Records to retain
- the original GitHub invoice or receipt;
- payment and card statements;
- subscription and organization ownership details;
- billing-address and tax-information submissions;
- refunds, credits, and corrected invoices;
- currency-conversion records used in the accounts; and
- support correspondence about tax or reissuance.
Keep records according to your Japanese bookkeeping and tax-retention requirements. Accounting software can store and classify documents, but it cannot decide whether a GitHub invoice is legally creditable.
When to ask a Japanese tax professional
Obtain advice for reverse-charge analysis, enterprise or reseller contracts, significant annual GitHub spend, cross-border group billing, Marketplace purchases, disputed historical invoices, or an input-tax-credit claim that could materially affect a return. A tax accountant can also assess whether your filing method and invoice records support the treatment you intend.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →The Bottom Line
Use the GitHub invoice and the billing profile that owns the subscription as your starting point. JCT is commonly 10% in Japan, but a company name or tax number does not automatically remove it, and a payment receipt is not automatically a qualified invoice. Correct the account details, ask GitHub about suspected errors, and obtain Japanese tax advice when creditability or cross-border treatment is uncertain.
Quick Recap
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.
