Create sales-tax.mdx - #804
Conversation
sales tax and tax id updates
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
There was a problem hiding this comment.
Let's remove the Notes section, I don't think we need to tell customers how they're determined in their tax region.
| 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**. |
There was a problem hiding this comment.
Right now this is built for India, which is correct but moving forward this example won't be applicable for everyone.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
|
Thanks for the review! We're looking into your feedback on |
|
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
|
@Promptless Use active voice wherever it applies. Name the actor and make it the subject: |
|
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. |
|
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. |
|
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. |
|
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. |
|
@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.
|
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. |
|
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. |
2 participants
sales tax and tax id updates