Configure tax calculation rules

Configure tax calculation rules in Stripe — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Set up tax calculation rules for our US and EU customers before the end of quarter pricing rollout.…
Set up tax calculation rules for our US and EU customers before the end of quarter pricing rollout. Configure nexus-based rules for the five US states where we have presence and VAT rules for Germany, France, and the UK. Ensure tax is calculated per line item, add region-specific rates, and run a sample invoice for a €120 subscription and a $50 one-time add-on on Thursday.

Improve — make it easier to accept

+
Before I hand tax rules to finance, make the rule set quick to audit: show which legal entity and…
Before I hand tax rules to finance, make the rule set quick to audit: show which legal entity and nexus each rule applies to, surface the rate sources and effective dates, and flag rules that depend on customer billing address versus ship-to address. Call out any exemptions that require a tax ID and any rounding or display issues that will confuse customers.

Decide — diagnose the stuck moment

+
Finance reported German invoices with VAT undercharged for digital subscriptions last week. The…

Finance says tax was undercharged for German customers

Finance reported German invoices with VAT undercharged for digital subscriptions last week. The person in finance, Elena, says the rule appears to have used the wrong tax rate when billing EU customers on subscription proration. I don’t know whether the problem is the rule, the address used, or proration logic. What’s the most likely cause and the fastest fix to stop more undercharged invoices?

Become — change the pattern

+
We repeatedly see tax mistakes: wrong nexus, inconsistent address use, and proration edge cases…

Tax configuration keeps creating revenue leakage

We repeatedly see tax mistakes: wrong nexus, inconsistent address use, and proration edge cases that leak revenue. Where should we lock standards and who should own them? Propose a set of practices—ownership, test fixtures, and periodic audits—that will reduce errors and contested invoices by at least 80%.

Next to this one

Other payments work people do in Stripe.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.