Skip to content

Create sales-tax.mdx - #804

Open
lavanya-gunreddi wants to merge 19 commits into
mainfrom
lg-tax-changes
Open

Create sales-tax.mdx#804
lavanya-gunreddi wants to merge 19 commits into
mainfrom
lg-tax-changes

Conversation

@lavanya-gunreddi

Copy link
Copy Markdown
Contributor

sales tax and tax id updates

sales tax and tax id updates
@mintlify

mintlify Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
runpod-docs 🟢 Ready View Preview Sep 11, 2026, 12:34 AM

Comment thread accounts-billing/sales-tax.mdx Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove the Notes section, I don't think we need to tell customers how they're determined in their tax region.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Promptless Work on this comment

Comment thread accounts-billing/sales-tax.mdx Outdated
If you have auto-reload enabled, tax applies to each reload in the same way it applies to manual purchases. Tax is additive to the reload amount:

- A $100 auto-reload in an 18% GST jurisdiction charges **$118** and delivers **$100 in credits**.
- A \$100 auto-reload in an 18% GST jurisdiction charges **\$118** and delivers **\$100 in credits**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right now this is built for India, which is correct but moving forward this example won't be applicable for everyone.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Promptless work on this comment

Comment thread accounts-billing/sales-tax.mdx Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the business component is a india specific thing; would change language so this can be applicable for eu or further, or we might have to remove and then just do table.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Promptless work on this comment

Comment thread accounts-billing/sales-tax.mdx Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can payment method and billing address. but i would ask greg if he even wants to have this information known. cc: pranjal when this decision is made

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Thanks for the review! We're looking into your feedback on sales-tax.mdx now and will follow up here with the updates shortly.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Thanks for all three review comments — we've got them mapped: generalizing the India-specific examples, reworking the tax-registered businesses section for a broader audience, and trimming the jurisdictions table. Drafting the edits now and will follow up here.

Address PR review feedback on accounts-billing/sales-tax.mdx:
- Frame the worked credit and auto-reload examples as illustrative
  (18% tax rate example) rather than asserting 18% GST universally
- Generalize the tax-registered businesses note beyond GSTIN/India
- Remove the Notes column from the supported jurisdictions table
@lavanya-gunreddi

Copy link
Copy Markdown
Contributor Author

@Promptless Use active voice wherever it applies. Name the actor and make it the subject:
Runpod, checkout, the console, Stripe, the API, the worker, you. Never "the
system". Keep "be + participle" only for conditions like "is enabled" or "is
deprecated". Keep sentences short: one idea each, 15 words typical, 20 max,
split at "and", "which", and semicolons. An active rewrite should be shorter
than the passive original. Cut time-anchored words: currently, recently, soon,
new, latest. Avoid "will" for product behavior. Flag any action whose actor you
cannot verify rather than guessing.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Addressed in the latest push to this branch. The worked examples in "How tax affects your credits" and "Auto-reload" are now framed as illustrations — e.g. "in a jurisdiction with an 18% tax rate…" — rather than implying 18% GST applies to every customer. The India GST table row is left intact for your tax owner to confirm.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Addressed in the latest push. The "Tax-registered businesses" section is now jurisdiction-neutral: it no longer centers on India's GSTIN and instead speaks to a valid tax ID's effect per region (e.g. EU VAT), consistent with the add-tax-id page. We kept the section rather than reducing it to a table, since it carries the "can a registered business reduce or change its tax" user need.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Done — the Notes column has been removed from the "Supported jurisdictions" table (header, separator, and the India row's Notes cell) in the latest push to this branch.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Got it — we'll do an active-voice pass over the page: naming the actor as the subject, keeping sentences short and one idea each, cutting time-anchored words, and flagging any action whose actor we can't verify rather than guessing. Will follow up here with the updates.

@lavanya-gunreddi

Copy link
Copy Markdown
Contributor Author

@Promptless Never use a dash as punctuation inside a sentence, whether hyphen, en dash, or em dash. Use a period, comma, or colon instead, or split the sentence. Hyphens inside compound words such as auto-reload and tax-registered stay.

…punctuation

Address two review directives from @lavanya-gunreddi on PR #804:
- Active voice with named actors; short one-idea sentences; drop time-anchored
  words and 'will' for product behavior.
- Remove dashes used as sentence punctuation (compound-word hyphens retained).

Preserves the three [CONFIRM] flags verbatim, all figures, the credit examples,
the India GST table, and the add-tax-id link.
@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Done — the active-voice pass is pushed to this branch. The page now names the actor as the subject (Runpod, checkout, tax, you), drops "the system"-style agentless passives (keeping conditions like "is enabled"), splits sentences to one idea each, and cuts time-anchored words and "will" for product behavior. Per your instruction, we did not guess at actors we couldn't verify: the three [CONFIRM] notes on unconfirmed tax facts are left in place for your team to confirm.

@promptless

promptless Bot commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Done in the same push. Dashes used as sentence punctuation are gone (the em dash in the intro became a period), while compound-word hyphens like auto-reload and tax-registered are kept. The structural section rules (---) are left in place as layout, not sentence punctuation.


The table below lists jurisdictions where Runpod collects tax. Runpod adds regions as it begins collecting there.

| Country | Tax type | Rate |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this time, please remove this table as we have not enabled tax yet for India.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Promptless work on this comment. Instead of removing it can you hide the text?

@promptless

promptless Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Thanks @lavanya-gunreddi — got it. Rather than removing the table, we'll hide it (comment it out) so it stays in place and can be restored once tax is enabled for India. Working on the change now and will follow up here.

Per PR #804 review, tax is not yet enabled for India, so the single-row
India GST table would be inaccurate. Comment out the section (heading,
intro, and table) in an MDX JSX comment instead of deleting it, so it
restores cleanly when tax collection goes live.
@promptless

promptless Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Done — instead of removing the "Supported jurisdictions" table, we've hidden it. The whole section (heading, intro sentence, and the India / GST / 18% table) is now wrapped in an MDX {/* … */} comment on the lg-tax-changes branch, so it no longer renders on the page but stays in the source. When tax collection goes live for India, you can restore it by simply removing the comment markers — no need to retype the table. We verified by compiling the page that the block renders as nothing and the page ends cleanly after "Receipts and invoices."

Resolve confirmed CONFIRM placeholders and reviewer-requested edits on
PR #804 across accounts-billing/sales-tax.mdx and add-tax-id.mdx:

- Drop per-region tax-ID effect (exemption vs reverse-charge) until a
  region is included; keep only 'may exempt you from tax'.
- Receipts: tax shows on the receipt email and the billing page; no
  tax-invoice-for-filing claim; heading renamed to 'Receipts'.
- Document the confirmed checkout tax-ID path (collection is live).
- Correct the account-settings nav to Settings > Account Information >
  Tax ID and retitle the section away from 'customer portal'.
- Remove the 'Tax ID added by support' and 'Validation and
  verification' sections.
- Replace the formats table with the supported-countries list.

Preserves the unresolved post-purchase timing CONFIRM (not addressed).
Per Celine Nie's request in #topic-documentation, remove the sentence
'Tax IDs apply to future purchases.' and its [CONFIRM] placeholder from
the tax ID page. The checkout-save statement is unchanged.
celine-runpod
celine-runpod previously approved these changes Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants