Back to Explore
GuideVibeFix editorialUpdated Nov 15, 2026

Before Your First Cross-Border Order Lands: Sales Tax and VAT for Your Vibe Project

Cross-border sales are not one price collected worldwide: of 500 orders only 178 make it through with zero discrepancies. Ask who, where, and what first, then calculate the rate, invoice, and pay. All example projects, people, and numbers in this guide are fictional.

A real photo: a printed paper receipt on a wooden table showing SUBTOTAL, TOTAL, VAT 7.0%, and VAT INCLUDED.

Lin Zhou's "BoatBoard" is a one-person online kanban tool: drag tasks around, get a progress chart at the end of the month, subscription price 12 dollars a month. For the first six months after launch, most users were friends and peers from home, and collecting payment was simple: 12 dollars a month, and 12 dollars was what arrived. In early November, things changed: a user from the United States subscribed, a user from Germany subscribed, and a user from the United Kingdom sent an email asking: "Can you send me an invoice with a tax number? My company needs it for reimbursement." Lin Zhou opened the payment dashboard and saw that all three had paid exactly the same amount: 12 dollars. At the time he thought that was fine: same price, same money received, what could go wrong? When he reconciled the books at the end of the month, he found that the German order actually contained value-added tax, and the British one did too, which meant the money he really kept was less than the sticker price. Worse, the invoice the German user needed had to show the tax amount, the tax rate, and the seller's tax number — and he could not produce one. The user from that US state should, under local rules, have been charged sales tax on a digital service subscription in the first place, and he had collected none of it. Only then did Lin Zhou understand: selling across borders is not "set one price and collect it worldwide". It is three questions — "who are you selling to, where, and what" — and each answer points to a different tax.

Two things first. First, the walkthrough project "BoatBoard", its maker "Lin Zhou", the subscription price of 12 dollars a month, and all dates and numbers in this guide are fictional, invented only to make the process concrete. Second, the boundary: this site has already published a payment integration guide about how to connect payments and get money flowing, a multi-currency pricing guide about how to price in different currencies, an invoice and receipt guide about invoice formats and how to issue them, and a credits ledger and billing guide about ledgers and billing logic. This guide repeats none of those four. It covers only one thing — when selling digital products across borders, how sales tax and VAT are determined, calculated, invoiced, and paid. Payment integration handles "how the money comes in", multi-currency pricing handles "what price to show", the invoice guide handles "what the invoice looks like", and this guide handles "how much of this money is tax, and who the tax goes to".

A real photo: a printed paper receipt on a wooden table showing SUBTOTAL, TOTAL, VAT 7.0%, and VAT INCLUDED.

1. Sales tax is not income tax: separate the two first

Many people doing cross-border sales for the first time mix up two kinds of tax: income tax, and sales tax and VAT. Income tax is what you pay at the end of the year on the profit you made; sales tax and VAT are taxes you have to deal with on every single order, as the order happens. The biggest difference is timing: income tax is calculated once a year, while sales tax has to be faced on every order. Lin Zhou's mistake was right here: he thought "I will find an accountant and file once at year end", but the German user needed an invoice in November, and the invoice had to show the tax amount — waiting until year end was far too late. Remember one sentence: income tax looks at how much you earned in a year; sales tax looks at who you sold each order to.

Sales tax and VAT are not the same thing either, but for a vibe project they can first be understood along one rough line: the United States uses sales tax, set state by state and city by city — whether it exists at all, and how much it is — with no federal sales tax. The European Union, the United Kingdom, and many other countries use VAT, where the tax is paid step by step as goods and services move along. For digital products, both ask the same question: where is the "place of consumption" for this order? If consumption is in a US state, that state's rules apply; if it is in an EU country, that country's VAT rules apply. The first step for Lin Zhou's 500 cross-border orders was to determine the place of consumption; for any order where that could not be determined, nothing after it could be calculated at all.

There is another common misunderstanding to clear up first: whether the price "includes tax" is your own decision, not something handed down from above. The same 12 dollars a month can be "12 dollars including tax" or "12 dollars plus tax". The first means the tax is carved out of the 12 dollars, so you keep less; the second means the user actually pays 12 dollars plus the tax, which looks better on the books but has to be stated clearly in the price. Lin Zhou's first version made exactly this mistake: users in three countries all paid 12 dollars, but the German and British orders contained tax, so what he really kept was less than 12 dollars — while he had always believed he collected the full 12 dollars on every order. If the pricing basis is not written down clearly, you are paying the tax out of your own margin.

2. Three questions: who, where, and what

For every cross-border order, ask three questions before talking about rates. The first is who you are selling to: an individual, or a company? This matters most in the EU, because the same order can be treated completely differently for an individual and for a company with a tax number. Individual users are usually handled by the seller collecting and remitting the tax, with the tax built straight into the bill; a company user that provides a valid tax number can in some cases use "reverse charge", where the buyer declares the tax itself. Lin Zhou's German user was a small company that volunteered its tax number — but Lin Zhou's checkout form did not even have a "tax number" field, so the user had to ask by email. The lesson is: whether the checkout form has a tax-number field is not a "we will add it later" question; it is something to decide on day one.

The second question is where: which country — and, in the US, which state — is the buyer actually in? The place of consumption is not determined by the buyer typing "where I live", but by a set of evidence taken together: the billing address, the country that issued the payment card, and the country the IP address sits in. Of Lin Zhou's 500 orders, 69 could not be determined: the user left only an email address, no billing address, the payment card was an international card, and the IP address sat behind a proxy. Those 69 are not a small problem: without a place of consumption, the rate cannot be calculated and the invoice cannot be issued, so they have to be parked and chased up one by one. The fix is direct: make the billing country a required field at checkout, and write the billing address into the order record when payment succeeds — do not wait until the month-end reconciliation to discover the field is missing.

The third question is what you are selling: a digital service, a physical good, or something else? That decides which set of rules applies. Lin Zhou sells an online kanban subscription, which is a digital service and follows the digital-service rules; if he sold physical merchandise, the rules would be different again. More finely: is the subscription billed monthly, or bought once outright? Every billing period of a subscription has to be determined afresh — just because the first period was determined does not settle it forever. And the first paid period after a free trial — from which period does the tax start? There is no single answer to these questions; rules differ by country. But the order of asking is always the same: who first, then where, then what. Only when all three are answered is there a rate to calculate.

3. How to calculate the rate: tax-inclusive and tax-exclusive prices, do not mix them up

Once the place of consumption and the buyer type are determined, the next step is the rate. The rate is not one global number: US states have different sales tax rates, some states do not tax digital services at all, others do; EU countries have different standard VAT rates — Germany, for example, has a standard rate of 19% — and different countries and different types of service have different rate tables; the United Kingdom has its own VAT rules. Rates follow whatever the local tax authority publishes — do not write them from memory, and do not calculate this year's bills from last year's rate table. Of Lin Zhou's 500 orders, 431 had their place of consumption determined, and of those, 79 had the rate calculated wrong: some applied a physical-goods rate to a digital service, some used an expired rate table, and some mixed up the rates for "individual user" and "company user". 79 wrong calculations, each needing a credit note and a reissue at month end — far more work than getting it right the first time.

Once the rate is right, there is one more place where the arithmetic is easy to get backwards: tax-inclusive versus tax-exclusive prices. The cover photo of this guide is the best example: the receipt shows VAT 7.0%, and underneath it says VAT INCLUDED, meaning the sticker price already contains 7% value-added tax, and the total the user paid includes the tax. For a tax-inclusive price, the tax amount equals the inclusive price times the rate, divided by one plus the rate; for a tax-exclusive price, the total payable equals the exclusive price times one plus the rate. Do not mix the two formulas up, or you end up with the classic error: "sticker price 12 dollars including tax, but collected as 12 dollars plus tax". What Lin Zhou did correctly was to fix one rule for the whole site: every price states clearly "whether tax is included", and every bill shows three lines at once — "price before tax, tax amount, total payable" — so users can check it at a glance and the month-end reconciliation needs no guessing.

One more detail: exchange rates. Lin Zhou collects in dollars, but German and British tax has to be declared in the local currency, with an exchange rate sitting in between. Which day's rate — the day of the transaction, or the day of filing? Rules differ by country; a common approach is to convert at the rate on the transaction day, and to write the rate and the conversion into the order record. Do not wait until the end of the quarter to look up exchange rates from three months ago, when even the transaction-day rate is hard to recover. One extra line in the order record — "exchange rate on the transaction day" — saves half the time at quarterly reconciliation.

4. What an invoice must show: one missing line can block a reimbursement

With the rate calculated, the next step is invoicing. An invoice is not a receipt where "any amount will do" — a cross-border invoice has several mandatory items: the seller's name and tax number, the buyer's name and tax number (for company users), the invoice date, the order number, a description of the goods or services, the amount before tax, the tax rate, the tax amount, the total payable, and the currency. Of Lin Zhou's 500 orders, 352 had the rate right, and of those, 63 had incomplete invoice information: some were missing the seller's tax number, some were missing the tax-amount line, and some described the charge vaguely as "service fee" instead of "subscription fee", so the German user had the reimbursement bounced by their finance team. 63 problem invoices cost far more to fix than getting them right the first time, because each one needs a credit note, a reissue, and an explanatory email to the user.

The other invoice trap is the "tax number field". As noted above, company users volunteer their tax numbers, but your invoice template needs somewhere to put them. Lin Zhou's first invoice template was auto-generated by the payment platform and showed only the amount and the date — no tax-number field — so the German user had to email again to ask for one. The right approach is to reserve two fields in the invoice template, "buyer tax number" and "seller tax number": fill them in when a company user provides one, leave them blank for individuals. At the same time, state the invoice language and currency clearly — whether a German user can claim reimbursement on an English-language, dollar-denominated invoice depends on their own company's finance rules, so writing in the help documentation "what information the invoice contains, in which language, and in which currency" saves a lot of back-and-forth email.

How long electronic and paper invoices must be kept deserves attention too: different countries require different retention periods, from a few years to more than ten. Lin Zhou's approach is to file every invoice electronically in folders by "year plus country", with an invoice-number index in the order records, so that looking up an order from five years ago takes ten minutes. An invoice is not finished when it is issued; it is finished when it is stored and can be found.

Sales-tax funnel (fictional sample): 500 cross-border orders, 431 where the buyer location was determined, 352 with the right rate applied, 289 with complete tax info on the invoice, 227 paid on time to the right jurisdiction, 178 with zero reconciliation differences

5. Funnel review: how 500 orders became 178 with zero discrepancies

Draw the process as a funnel and the numbers look like this: 500 cross-border orders, 431 where the buyer's location could be determined, 352 where the applicable rate was calculated correctly, 289 where the invoice carried complete tax information, 227 where the tax was paid on time to the right jurisdiction, and 178 with zero discrepancies at quarterly reconciliation. As conversion rates: the first step is 431 divided by 500, which is 86%; the second step is 352 divided by 431, which is 82%; the third step is 289 divided by 352, which is 82%; the fourth step is 227 divided by 289, which is 79%; the fifth step is 178 divided by 227, which is 78%; and the whole journey is 178 divided by 500, which is 35.6%. In other words, of 500 orders, only about a third make it from start to finish with zero discrepancies. That ratio looks low, but it is exactly the proof that every layer is doing its job: the 69 lost at the first step had unclear places of consumption, the 79 lost at the second had wrong rates, the 63 lost at the third had incomplete invoices, the 62 lost at the fourth were paid to the wrong jurisdiction or late, and the 49 lost at the fifth were reconciliation differences. 69 + 79 + 63 + 62 + 49 = 322, and 500 minus 178 is also 322 — the books balance.

The funnel is used the same way as in the companion guide: it tells you what to patch next. In Lin Zhou's funnel, the first step at 86% is the highest, which means place-of-consumption determination is relatively the strongest part; the fifth step at 78% is the lowest, which means reconciliation is the weakest. The 49 lost at the fifth step break down into three kinds: refunds where the tax amount was not refunded along with them, exchange-rate conversions done on inconsistent bases, and payment-platform fees mistakenly counted inside the taxable amount. The next round of fixes is then obvious: generate a negative tax record whenever a refund is issued, write the transaction-day exchange rate into every order record, and list platform fees separately, outside the taxable amount. A funnel is not there to look nice; it exists so that "what do I fix first" has a number behind it.

The fourth step deserves a sentence of its own: 227 orders paid on time to the right jurisdiction means 62 went wrong, in two ways — paid to the wrong place, or paid late. The classic wrong-place case is paying one EU country's tax to another country; the classic late case is missing a filing deadline. The cures are different: paying to the wrong place is fixed by the first step's place-of-consumption determination, while paying late is fixed by calendar reminders and a filing schedule. Lin Zhou's method is to write every jurisdiction's filing deadline into the calendar with a reminder 7 days ahead, and to pay as soon as the deadline arrives rather than dragging it to the last day. Tax can be learned slowly, but a deadline waits for nobody.

6. File it yourself or use a merchant of record: choosing between two routes

Once the tax is understood, there is a route question: do you register, file, and pay the tax yourself, or hand it to a merchant-of-record service? A merchant of record means the payment provider acts as the seller of record: it calculates the tax, collects it, and pays it, and you receive the net income after tax. Filing it yourself means registering a tax number in every jurisdiction where you owe tax, filing on schedule, and paying from your own account. Neither route is absolutely better; it is a trade-off.

The advantage of a merchant of record is that it saves effort: no registering tax numbers in a dozen jurisdictions, no remembering a dozen deadlines, and the rate tables are maintained by the provider. The cost is twofold: first, the provider charges a service fee, which has to be built into the pricing; second, the invoice and bill formats are set by the provider, and there is limited room to customize. Lin Zhou did the arithmetic: with fewer than 200 cross-border orders a month, the merchant-of-record fee was far cheaper than hiring an accountant and registering tax numbers in a dozen jurisdictions himself, so he chose the merchant of record. But he kept one safeguard: the contract states clearly "who maintains the rate table, who is responsible for the tax-number field on invoices, and who pays first when something goes wrong". Without those three lines written down, saving effort turns into arguing later.

The advantage of filing it yourself is control: invoice formats, rate decisions, and filing rhythm are all yours to set. The cost is workload: every jurisdiction needs registering, every deadline needs remembering, and every record needs keeping. When is it worth filing yourself? Usually when order volume is large enough that the service fee exceeds the cost of doing it yourself, or when your business model is unusual and merchant-of-record services do not cover it. There is another rule of thumb: if your users sit in 3 or fewer jurisdictions, filing yourself is still manageable; if they sit in 10 or more, do not file yourself — a merchant of record is the better deal. Lin Zhou's users sit in 3 markets — the United States, the EU, and the United Kingdom — but inside the United States there are several states, so the real jurisdiction count is far more than 3, which is another reason he chose the merchant of record.

Whichever route you take, two things are the same. First, the order record has to be complete: buyer type, place of consumption, rate, tax amount, exchange rate, invoice number — if any one of them is missing, the month-end reconciliation has to rely on guessing. Second, somebody has to maintain the rate table: rates change, exemption rules change, thresholds change, and the maintainer can be you, an accountant, or the merchant-of-record provider — but it cannot be "nobody". Lin Zhou spends half a day a month on a single task: sampling 20 orders from the month and checking each one's rate and invoice line by line, then writing one line of record after the check. After two quarters of this habit, his reconciliation discrepancies fell from 49 to 11.

7. Thresholds and registration: when a tax number becomes mandatory

Many beginners ask: I have only sold a few orders — do I need to register? The answer depends on thresholds. A threshold means: a jurisdiction sets a figure, and only when a seller's sales in that place pass it does registration — and payment — become mandatory. Below the threshold, registration can wait, but the tax still has to be handled by somebody: either the merchant-of-record provider handles it, or registration is scheduled before the threshold is crossed. US states set different thresholds — some look at sales volume, others at the number of transactions; the EU has a one-stop-shop scheme, where a seller registers in one country and files for several EU countries through it; the United Kingdom has its own registration bar. Thresholds follow whatever the local tax authority publishes — do not take a figure from somebody else's article and apply it straight to your own books.

Lin Zhou's method is to keep one small card per market: the market name, what the threshold is, how far current sales are from it, who to contact for registration once it is crossed, and what documents registration needs. The cards are updated once a month, and registration starts 30 days before sales approach a threshold — never in a panic after crossing it. One more easily missed point: a threshold is calculated on "sales in that jurisdiction", not on "global sales". Sales in one US state being below the threshold says nothing about the EU. One card per jurisdiction; do not mix them together.

8. The pre-flight checklist: tick every item before the first cross-border order lands

Before the first cross-border order lands, go through this checklist item by item, and start selling only when everything is ticked. First, is the pricing basis fixed: does the whole site state clearly "whether tax is included", and does every bill show the three lines "price before tax, tax amount, total payable"? Second, does the checkout form have "billing country" and "tax number" fields, so company users can enter a tax number smoothly? Third, does the order record carry all six items — buyer type, place of consumption, rate, tax amount, transaction-day exchange rate, and invoice number — with any gap filled? Fourth, does the invoice template carry the seller's tax number, the buyer's tax number, the tax rate, the tax amount, and the currency, with the language and currency stated clearly? Fifth, is the route chosen — file it yourself or use a merchant of record — and does the contract state who maintains the rate table, who owns the tax-number field on invoices, and who pays first when something goes wrong? Sixth, are threshold cards built for every market, with the distance to the threshold tracked and updated monthly? Seventh, is every jurisdiction's filing deadline in the calendar, with a reminder 7 days ahead? Eighth, are 20 orders sampled every month and checked line by line for rate and invoice, with one line of record written after each check? Ninth, are electronic invoice copies filed by "year plus country", with retention periods following local requirements? Tenth, for complex cases, ask an accountant: before entering multiple jurisdictions, before company users become a large share, or before entering a new market, one question to a professional costs far less than paying back tax later.

One last honest point: the hard part of sales tax is not the arithmetic, but the patience of "asking the questions on every single order". Lin Zhou's first version was wrong not because he did not understand tax, but because he believed "one price, collected worldwide" would be enough; his second version was right not because he became a tax expert, but because he wrote the three questions — "who, where, and what" — into the checkout flow, wrote "rate, tax amount, exchange rate, invoice number" into the order record, and wrote "reminder 7 days before the deadline" into the calendar. Tax is not solved by being clever; it is solved by process. With the process in place, 178 of 500 orders can travel the whole way with zero discrepancies; without it, maybe not one of the 500 lines up.

One reminder: this guide is a hands-on product guide, not tax advice. Tax law differs a great deal between countries and regions, and rates, thresholds, and filing deadlines follow whatever the local tax authority publishes — and they change. If your business spans multiple jurisdictions, or company users make up a large share, having a professional accountant or tax adviser look it over once is far cheaper than guessing on your own.

Views 6Comments 0

Comments (0)

ME
0/1000
Loading comments...
Browse projectsPublish your project

Related articles

A young woman seals a cardboard shipping box with a red tape gun in a bright home office, shelves of shipping boxes behind her, a laptop on the desk
News
The Code Is Done. The Business Is Just Starting: Replit Agent Can Now Buy Supplies and Run Your Ads

On 12 November 2026, Replit gave Replit Agent two new jobs: buying supplies for your business and running your Google Ads. Purchases go through Stripe's Link wallet and Visa's rails; ads go through Google Ads. The common thread: the agent can only prepare the work — money moves only when the founder approves, with checks enforced in code, not left to the model.

Payments & MonetizationProduct LaunchAI Coding
Real photo: a bank of light gray metal filing cabinets with one drawer pulled open, revealing rows of hanging file folders inside
Guide
A real database inside the browser: IndexedDB local storage, explained plainly

localStorage only stores strings and has no indexes. IndexedDB is a real database in the browser: structured data, far larger capacity, indexes, and transactions. Following MDN's Using IndexedDB, IDBDatabase, and IDBObjectStore: the five-step routine, opening, upgrades, keys, indexes, transactions, add versus put, get, cursors, ranges, and multi-tab upgrades.

Tool TipsData WorkflowsFrontend Engineering
Real photo: hands typing on a MacBook Pro showing JavaScript code that changes HTML content, with a white mouse, papers, and binders on a white desk
Guide
Functions without the confusion: JavaScript functions, parameters, and arrow functions, explained plainly

You already call functions every day; this guide names what you have been doing. Following MDN's Functions, Arrow function expressions, and Rest parameters: declarations versus expressions, parameters and arguments, default values, rest parameters, spread syntax, return values, arrow function shorthand, the this trap, callbacks, and scope.

Tool TipsFrontend EngineeringAI Coding