Quick Answer
Paddle acts as Merchant of Record for approved software sales and handles buyer sales tax and VAT. Configure accurate product tax categories, price tax modes, and buyer data; test checkout and manual invoices; keep original transactions and separate adjustments; and reconcile payout movements to seller statements and bank receipts. Your own business taxes and direct sales remain separate.
Key Takeaways
Start with the merchant-of-record boundary#
Paddle resells your eligible software as Merchant of Record and takes responsibility for the sales tax and VAT on its sales to buyers. Your team still configures the catalog, supplies accurate customer information, delivers the product, and reconciles seller proceeds.
This guide is for small SaaS teams selling across borders who want clearer cash-flow visibility and cleaner month-end operations. The goal is to define a clear split between what a Merchant of Record executes and what your team still owns.
Step 1 Define what Paddle is actually taking off your plate#
A Merchant of Record (MoR) is the legal entity that sells to the end customer, so write the scope down early.
| Paddle responsibility on covered sales | Your operating responsibility |
|---|---|
| Buyer sales tax and VAT | Maintain accurate product categories and customer inputs; investigate mismatches with Paddle. |
| Payment processing and its PCI scope | Check your integration’s own security and data responsibilities. |
| Refund and dispute processing | Keep approval decisions, adjustment references, and delivery evidence. |
| Buyer invoices and seller payout records | Reconcile fees, tax, adjustments, balances, and receiving-bank cash. |
If your biggest friction is payment operations and sales-tax execution across markets, this model is usually worth serious consideration. Your checkpoint here is simple: write down the exact jobs you expect Paddle to handle so ownership is clear before reconciliation or audit questions show up.
Step 2 Name the responsibilities that do not disappear#
Buyer transaction tax and your business taxes are separate. Keep an adviser responsible for your income or corporate tax, the treatment of your supply to Paddle, and any sales made directly outside Paddle.
Keep four controls owned internally:
- Validate product and checkout configuration against what you sell.
- Make sure reporting is detailed enough to review outcomes by market.
- Assign a named owner for exceptions, support follow-up, and evidence storage.
- Revisit assumptions when packaging, flows, or rules change.
Record which sales Paddle resells and which your business sells directly. Do not apply the responsibilities of a tax calculation plugin or a payment processor to Paddle’s MoR sales.
Step 3 Treat reporting as tax control, not just finance hygiene#
Reporting is part of compliance control, not just back-office cleanup.
Reporting gives you a usable view of cash flow, and analytics help you review what actually happened. Without that visibility, your team is operating blind. In practice, do not stop at "payments are coming in." Keep reporting that lets you review outcomes and trace decisions with a clear paper trail.
Decide if Paddle fits your product before you configure anything#
Check product eligibility before tax configuration. This guide covers Paddle Billing for approved software and digital products; older Paddle Classic invoicing instructions can describe different limits.
Step 1 Classify how customers receive each offer#
Identify hosted software, downloadable software, and any non-software component. Delivery method helps explain the offer, but it does not by itself choose the correct Paddle tax category.
| Offer type | Customer receives it | Handling cue |
|---|---|---|
| Hosted software | Access to a hosted application | Document the service and approved product tax category. |
| Downloadable software | Software installed locally | Document the licensed product and category rather than copying the hosted SKU. |
| Physical component | A shipped item or physical delivery | Paddle’s acceptable-use policy prohibits physical products; do not include this component in a Paddle checkout. |
For bundles, document each component and confirm eligibility. Physical delivery is an eligibility problem, not simply another taxable SKU. Review unusual digital offers against Paddle’s acceptable-use guidance and retain written clarification for borderline products.
Step 2 Confirm edge-case eligibility with Paddle in writing#
If your product may sit near restricted financial categories, pause and confirm eligibility directly with Paddle before launch. Do not rely on forum comments or older comparison posts as approval.
Keep written confirmation with your product description, checkout flow summary, and planned SKU names. Use it as a control record if your scope changes later.
Step 3 Choose based on your biggest operational risk#
Choose the model that addresses your actual risk, not the one that sounds easiest.
An MoR suits a team that wants the reseller to handle buyer transaction-tax collection and remittance. Evaluate that legal role separately from billing flexibility, supported products, supported buyer countries, fees, and seller payout requirements.
If your main risk is deep custom billing logic or catalog complexity, compare the tradeoffs before you commit. Do not assume one standardized tax setup will fit every SaaS product, and do not treat older U.S. state snapshots as current authority without validating them against current guidance and a tax professional.
Related: Paddle vs. Stripe: A Comparison for SaaS Founders.
Gather your tax and operations inputs before touching settings#
Do not start in the dashboard. Build the inputs you will validate against in production first. The goal is simple: test your real catalog, real markets, and real checkout paths, not a generic setup.
Step 1 Map every SKU by delivery type#
Create one row per SKU with offer description, delivery method, billing model, Paddle product ID, approved tax_category, price IDs, currencies, quantities, and tax_mode. Keep the business description alongside these technical fields so a reviewer can spot an incorrect mapping.
For bundles, split components that change how the buyer receives the product, such as hosted access plus a downloadable asset. Your checkpoint is whether someone outside the product team can tell if the buyer downloads, installs, or only accesses the product in a browser.
Step 2 List current and next markets explicitly#
Separate your seller account’s legal entity and payout configuration from buyer locations. List current buyer countries and the next target countries, checking Paddle’s supported-country guidance and account approval. Under each country, mark:
- where you already have paying customers
- where you plan active expansion next
- where sales are incidental for now
Use precise buyer country codes and relevant state or province details. Record sale currency and payout currency separately. A supported currency is not evidence that every buyer country or product is eligible.
Step 3 Create one dated source of truth#
Set up one shared, versioned folder before anyone changes checkout settings. Keep:
- the SKU map and market list
- the named internal owner for tax and billing review
- a short assumptions note tied to tax and billing review
- dated evidence such as screenshots, support replies, policy pages, and PDFs
Save the URL, access date, and any stated update date for the Paddle documents used in each decision. Keep account-specific support replies alongside them. Re-check the actual product version and account settings when documentation changes.
Step 4 Capture the real checkout and invoice paths#
Document exactly how buyers can pay and what document they receive afterward. If you plan to support cards, PayPal, or Apple Pay, track each as a separate path and note any invoice differences you observe by market or buyer type.
Do not assume advertised payment options are active in your implementation by default. Use a simple validation matrix with rows for payment path, invoice type, and priority market so your highest-volume paths are tested before launch.
Split responsibilities so nothing falls through the cracks#
Turn your source-of-truth folder into an owner map before you enable anything. In a Merchant of Record setup, a control without a named owner is not production-ready.
| Vendor claims or behaviors to verify and store | What your team still owns |
|---|---|
| Tax behavior for your SKU and market mix | Compare live checkout outcomes with your documented expected treatment, and name one approver for mismatches. |
| Financial corrections after issuance | Use credits or refunds linked to the original transaction; retain adjustment status and credit-note evidence. Do not overwrite the issued financial record. |
| Buyer-detail corrections | Use the supported transaction revision for permitted fields; update customer/address/business entities separately for future sales. Escalate country or amount changes rather than treating them as a name correction. |
| Any privacy and security trust materials you rely on | Confirm scope against your actual data flow and keep a dated copy of what you relied on. |
| Policy or product update channels | Assign one person to monitor updates, log changes, and decide when tax tests must be rerun. |
| Support and exception path for tax or invoice issues | Set an internal escalation rule when observed behavior conflicts with your documented expected treatment. |
Use four required fields on every control row: owner, backup owner, evidence link/file, and last verified date. If any field is blank, the control is not done.
Name a person, not a department. "Finance" or "Ops" is not ownership. One person should own review, one should maintain evidence storage, and one should handle escalation decisions.
Write the escalation rule now, before the first mismatch: pause the affected SKU or market, capture evidence, open vendor support, and resolve the conflict before you scale. Include checkout evidence, transaction or invoice records, buyer location used in testing, payment path, and the dated policy or support response you expected to match.
Configure Paddle tax settings in the right order#
The order matters. Set up products first, configure checkout and invoicing paths second, test location-driven tax outcomes third, and log every decision before go-live. This is an operational safety order, not a claim that Paddle requires this exact sequence.
Step 1 Set product records before trusting tax outcomes#
Create products and prices in Paddle Billing. Assign an accurate product tax_category; Paddle makes standard and saas categories available by default and other categories may require approval. Link each live SKU to its actual product and price IDs.
Inspect each price’s tax_mode: internal includes tax, external adds tax, location varies inclusion by transaction country, and account_setting inherits the account default. Record the selected mode and preview the resulting totals. Changing the account default does not rewrite existing prices; review them explicitly. See product and price setup and the price fields.
Step 2 Configure checkout and invoicing flows next#
Configure automatically collected checkout transactions and manually collected invoices as distinct paths. Test the same intended product category, customer location, and price tax mode in each path you offer.
| Paddle Billing input or state | Check before launch |
|---|---|
| Items and quantities | Current Billing invoices support multiple line items and quantities; confirm every intended price and quantity. |
| Customer and address | A transaction needs customer and address information to be ready; capture business details and tax identifier where applicable. |
| Tax identifiers | Validate the applicable identifier and inspect the resulting tax treatment; an identifier does not universally exempt a sale. |
| Draft versus issued | Edit a draft before issuing; issuing makes the transaction billed and creates the invoice financial record. |
| Recurring items | Issuing a manual invoice can create the related subscription before payment; apply your own documented entitlement and credit policy. |
| Fulfillment | Your application remains responsible for access and delivery. |
Do not make company name or a tax registration number mandatory for every consumer. For business buyers, collect relevant business information and tax identifiers and inspect the actual tax result. For certificate-based exemptions or unsupported cases, ask Paddle support which evidence and workflow apply before promising exemption.
Follow the current create-and-issue invoice workflow. Test readiness checks, invoice issuance, due dates, payment collection, and your access policy. Subscription creation alone is not proof that the buyer paid.
Step 3 Test location logic across jurisdiction scenarios#
Test the location information attached to the transaction: country and relevant state, province, or postal details. Compare the tax breakdown and tax-inclusive or tax-exclusive total with your documented expectation for that product and buyer.
Run controlled tests for at least two destinations with different location combinations, then compare expected and observed totals in checkout or invoice outputs. Repeat the same cart across the payment paths you offer to catch implementation-level drift before customers do.
Step 4 Record decisions in a changelog tied to legal assumptions#
Treat each configuration change as a tax decision. Log the SKU, flow used, jurisdictions and payment paths tested, observed result, evidence file, owner, and date.
Record the product category, price tax mode, buyer inputs, expected result, documentation URL, verification date, and any support decision. A dated general SaaS tax guide is background; use current Billing documentation and actual account behavior for implementation decisions.
Run scenario tests for US and EU before going live#
Validate tax and payment state across priority buyer locations and the methods available in your approved integration. Keep tax-calculation checks separate from payment acceptance and from seller payout reconciliation.
Use this as a launch gate for priority markets. If expected and observed results do not match in a market you plan to launch first, treat that as a blocker for that market until you resolve the gap.
Step 1 Build a compact matrix in Sandbox (Test Mode)#
Use a compact sandbox matrix for buyer location, business versus consumer inputs, product category, price tax mode, quantities, and offered payment paths. Sandbox demonstrates integration behavior; it does not prove live eligibility, actual funds movement, or bank receipt. Plan a controlled live verification after account approval.
| Buyer location | Product setup | Payment method | Expected check |
|---|---|---|---|
| Priority United States state | Primary product setup | Default method | Sales tax result matches your documented assumption for that state and setup |
| Same United States state | Alternate setup (if applicable) | Same method | Result matches the alternate documented assumption |
| Priority European Union country | Primary product setup | Second offered method | VAT result matches your documented assumption |
| Same European Union country | Alternate setup (if applicable) | Another offered method or retry path | VAT result matches the alternate documented assumption and transaction record matches checkout output |
Step 2 Separate product setups on purpose#
If you offer product setups with different expected tax outcomes, test them as separate scenarios. Keep location and payment method constant while changing only the product setup so you can isolate mismatches.
If the result does not match your expectation, check product records, SKU mapping, and checkout or invoicing mapping before moving on.
Step 3 Add a U.S. state-level edge checkpoint#
Include at least one priority-state scenario where your internal state-level assumption needs explicit verification.
Compare observed output to the exact state and product-setup assumption in your changelog. If it does not match, treat it as a real pre-launch issue.
Step 4 Test method and retry behavior, not just first-pass totals#
Test one failed-payment or retry case using the supported sandbox path. Link attempts to the same intended purchase and inspect provider state before initiating another transaction. An unknown outcome is not evidence of failure and must not trigger a duplicate charge.
Inspect transaction and payment-attempt records available in your integration, rather than assuming processor-routing fields are exposed. Paddle’s transaction.paid event precedes completed, and fee/payout breakdown data may not yet be populated. Use completed records for that breakdown; neither state proves the seller bank received a payout.
Step 5 Save evidence with your Paddle config history#
Keep an evidence pack for each scenario so mismatches are easier to investigate later. Store it with your Paddle configuration history.
For each pass or fail run, capture:
- checkout or invoice screenshot showing tax result
- transaction ID
- buyer location used
- product setup tested
- payment method and whether retry occurred
- date, reviewer, and expected assumption
For a step-by-step walkthrough, see The Best Software for Calculating and Remitting Sales Tax.
Connect billing, records, and reconciliation so finance can trust the numbers#
Treat reconciliation as a launch requirement. If the sale, tax label, and cash movement do not tie out, month-end close can break.
Step 1 Build one traceable record per transaction
Do not rely on checkout alone. For each sale, keep one record that ties your bookkeeping entry to the source invoice and payment record from your billing system.
Keep these fields together:
- invoice number or document reference
- transaction ID
- buyer jurisdiction used for tax
- tax type label
- product variant, cloud access or download
- gross amount, tax amount, and net amount
- settlement or payout reference
- exception status
Use a small U.S. and EU sample as a checkpoint. Finance should be able to trace booked amounts back to the invoice and tax assumption without extra interpretation.
Step 2 Tag by jurisdiction and tax type before month-end
Tagging is what makes review fast and defensible. At minimum, tag by jurisdiction, tax type, product variant, and period so finance can review indirect tax without rereading every line item.
Step 3 Keep indirect-tax reconciliation separate from annual filing workflows
Keep buyer invoices separate from the seller-side documents Paddle supplies. A buyer invoice documents Paddle’s sale to the customer; a reverse invoice documents your supply to Paddle, and remittance advice records the payout amount. Your accountant decides the seller’s accounting and business-tax treatment.
Match the payout reconciliation report’s balance_movement_in_balance_currency total to the remittance amount, then match the receiving-bank credit separately. Use balance currency for the report sum, include all adjustment and deduction rows, and investigate timing or bank-fee differences. Do not sum mixed sale currencies. See payout reconciliation and seller statements.
Worked example: sale, partial refund, and seller proceeds#
Assume a hypothetical tax-inclusive buyer charge of 120 in one currency at a 20% tax rate. The base is 100 and buyer tax is 20. Assume a fee of 6 solely for this example, not as a Paddle price quote: seller proceeds are 94, and 120 = 20 tax + 6 fee + 94 seller proceeds.
A later approved partial refund of 24 contains 20 of base and 4 of tax at the same rate. Remaining buyer gross is 96, base is 80, and tax is 16. If the example fee remains 6, remaining seller proceeds are 74: 96 = 16 + 6 + 74. The seller component falls by 20, while the buyer receives 24 including the tax component. Use the actual reported fee treatment rather than assuming this example applies to every refund.
Retain the original transaction and the separate adjustment ID. Paddle adjustments preserve the original financial record; live refund requests may require approval. Pending approval does not prove money was returned. Track the final adjustment state and the refund outcome. Use a credit for the supported unpaid-invoice case, not as proof of a cash refund. See refunds and credits.
If the sale and refund are the only movements in one payout and the assumed fee is unchanged, the example net is 74. In real payouts, include all movements and their timing; a refund after a prior payout belongs in its own later balance movement. Do not revise an earlier bank receipt to make the totals look equal.
A buyer name or tax-number correction is a separate workflow from a financial adjustment. Transaction revisions permit limited customer-related changes, leave the financial record intact, and have restrictions after adjustments. They cannot change the address country, items, or amounts on a completed transaction. Update the underlying customer, address, or business entity separately so future transactions use corrected data. Adding a valid tax or VAT number can also generate a linked adjustment refunding tax where applicable. Capture that adjustment and check its status and amounts before requesting any separate tax refund, so the same tax is not refunded twice.
Step 4 Use one exception queue with clear ownership
Create one queue for mismatches and failed assumptions, with a named owner and a response SLA that fits your operation. Send missing tags, invoice and payment mismatches, conflicting tax labels, and retry-path anomalies into that queue with the transaction ID, invoice copy, expected treatment, reviewer, and resolution date.
Put recurring monitoring in place so your setup stays current#
Monitoring is what keeps a good launch from drifting into a bad operating state. Treat it as an ongoing control, not a one-time setup. A practical internal cadence is a light monthly check, then a deeper quarterly retest in your highest-revenue regions.
Step 1 Set a cadence your team can actually maintain#
Use your monthly pass to check for drift across the jurisdictions you sell into. Look for changes in checkout behavior, internal assumptions, and the metrics you use as early warning signals.
Use the quarterly pass to retest high-volume or changed regions and trace a sample of completed sales, refunds, and payout movements. Set sample sizes and escalation times for your own operation rather than importing unrelated benchmarks.
Close each monthly review with a clear outcome: no change or change found, ticket opened.
Step 2 Re-verify platform assumptions, not just tax assumptions#
Monitor the Paddle pages and materials your team relies on, and re-verify any compliance-related wording your team uses before treating it as current. If your team references items related to SOC or GDPR, treat those as assumptions that need re-verification when wording or page location changes.
Record the checkout library or plugin version, environment, account configuration, and supported integration path. A third-party article does not establish Paddle approval or the behavior of your installed version.
Step 3 Keep a "last verified" log#
When issues appear, your team should be able to confirm what was last checked, by whom, and with what evidence in minutes, not hours.
Keep one log with:
- item checked
- last verified date
- owner
- source URL or document name
- evidence, such as a screenshot, document copy, support thread, or transaction ID
- result
- next review date
Step 4 Retest after checkout or plugin changes#
Retest each affected supported integration after checkout, SDK, or plugin changes. Include buyer data capture, product/price mapping, tax totals, invoice documents, access decisions, and adjustment handling.
Run a live-like transaction on each affected path, then compare invoice details, tax label, and recorded amounts to your expected treatment. This catches small data-capture regressions before they turn into reconciliation exceptions.
Fix the mistakes that cause the biggest tax surprises#
Untested assumptions can create major tax surprises. Fix these four issues early so you can defend outcomes during filing, refunds, and reconciliation.
Step 1 Separate product and offer labels in your catalog#
Mistake: treating every SKU as the same. Fix: use clear, distinct catalog labels and apply them consistently in your product map, checkout checks, and invoice review.
This is a control step, not a legal shortcut. For each high-volume SKU, confirm the catalog label, invoice description, and your internal expected-treatment note all match.
Step 2 Use current guidance, then verify in live flows#
Mistake: relying on older guidance as proof. Fix: prioritize current provider documentation, then re-validate outcomes in live or live-like checkout flows across your key jurisdictions.
For a suspected mismatch, save the exact country and subdivision inputs, product and price IDs, tax category, price tax mode, transaction ID, and observed totals. Ask Paddle to confirm the case before changing a broad rule or treating an unsourced anecdote as a provider defect.
Step 3 Keep internal ownership even with a merchant of record#
Mistake: assuming an MoR removes all internal tax work. Fix: keep named internal owners for policy checks, evidence, and escalation.
Paddle’s reseller role includes the buyer transaction-tax responsibilities on its covered sales. Your internal owner maintains inputs and handles exceptions; this is separate from filing obligations on your business income, your supply to Paddle, or direct sales through another channel.
Step 4 Keep a proof trail for each critical decision#
Mistake: making sales-tax decisions without durable evidence. Fix: store the same proof set each time: test result, screenshot, transaction ID, config-change note, support confirmation, and last-verified date.
That proof trail can help your team resolve disputes faster and trace whether an issue came from configuration drift, stale assumptions, or platform behavior.
Copy and paste this pre-launch checklist#
Use this as a strict go or no-go gate. Do not launch until all four checks pass, even if Paddle is already configured as your Merchant of Record.
| Check | Pass condition | If not |
|---|---|---|
| Product fit with Paddle | Each live SKU maps to the product type you defined, and you have current documentation or direct written confirmation tied to your actual product. | Treat broad SaaS labels as insufficient for edge-case products or unusual categories. |
| Responsibility split | The split between MoR coverage and your internal controls is documented, with named owners for verification, evidence, and escalation. | If VAT checks, exception review, or tax-policy updates have no owner, this check is not passed. |
| Real checkout scenario tests | Expected treatment matches observed output in the exact checkout paths for your priority markets, and records are visible in analytics, refunds, and dispute workflows. | If a priority market fails, pause launch and resolve it first. |
| Monitoring and evidence plan | An owner, a review cadence, and a single audit-evidence location are set before launch. | This check passes only when the re-check process is clear and finance or support can find the evidence quickly. |
Step 1 Confirm product fit with Paddle#
Confirm each live SKU maps to the product type you defined, then confirm Paddle is a fit for that SaaS category in your target markets. Treat broad "SaaS" labels as insufficient for edge-case products or unusual categories.
Pass only when you have current documentation or direct written confirmation tied to your actual product. Store that proof with your launch records.
Step 2 Confirm the responsibility split#
Document the split between MoR coverage and your internal controls before launch.
Confirm Paddle’s MoR role for the actual approved catalog and supported buyer countries. Assign internal owners for accurate inputs, evidence, and exceptions, and keep the seller’s business-tax work separate from Paddle’s buyer-tax work.
If VAT checks, exception review, or tax-policy updates have no owner, this check is not passed.
Step 3 Run real checkout scenario tests#
Run scenario tests through the exact checkout paths buyers will use in your priority markets, including cross-border cases.
For each scenario, compare expected treatment with observed output, then confirm records are visible in analytics, refunds, and dispute workflows.
Do not accept partial passes. If a priority market fails, pause launch and resolve it first.
Step 4 Set the monitoring and evidence plan#
Set an owner, a review cadence, and a single audit-evidence location before launch.
For each critical tax decision, keep the same proof set: screenshots, transaction IDs, config-change notes, support confirmations, and a last-verified date.
This check passes only when the re-check process is clear and finance or support can find the evidence quickly.
If you compare another provider, use the same catalog, buyer-country, responsibility, and payout questions. Gruv Merchant of Record for business is one product to evaluate against those requirements.
Final takeaway and next step#
Paddle’s MoR role transfers the buyer transaction-tax work on covered sales to the reseller. Make that boundary useful by maintaining accurate catalog and buyer inputs, tracing financial adjustments, and reconciling seller proceeds to bank cash.
Step 1 Start with a controlled market cluster#
Start with a controlled market cluster, not a global rollout. A SaaS subscription can be taxable in one U.S. state and exempt in another, so avoid one-rule-for-everywhere assumptions.
Choose priority jurisdictions, confirm eligibility and product configuration, and verify tax outcomes for consumer and applicable business cases. Review economic-nexus and filing obligations separately for any sales your business makes directly; do not treat Paddle-resold buyer sales as though you are the retail seller.
Your checkpoint is not just that tax appeared. It is that tax appeared, or did not appear, for the expected reason in the expected jurisdiction, with evidence saved.
Step 2 Test jurisdiction by jurisdiction before you scale#
Test jurisdiction by jurisdiction before you scale. If tax behavior in a priority market does not match your expectation, pause expansion and fix that mismatch first.
Keep a lightweight evidence pack:
- checkout screenshots for each priority scenario
- transaction IDs tied to those screenshots
- invoice copies where available
- a short changelog of what you configured and why
- written confirmation for edge cases when available
If a mismatch is unresolved, hold the affected new-sales rollout, retain existing financial records, and escalate with transaction and configuration evidence. Correct issued amounts through the appropriate Paddle adjustment workflow rather than silently changing the historical invoice.
Step 3 Re-check when your product setup or markets change#
Keep this as an operating habit, not a one-time launch task. Re-check when your product setup, markets, customer mix, or checkout behavior changes.
Finish the checklist for the first market group, retain the evidence, and add new groups after their own cases pass. For more on the legal and operating boundary, read What is a Merchant of Record (MoR) and How Does It Work?.
Frequently Asked Questions
Is SaaS always taxable when you sell through Paddle?
No. Paddle's guidance says SaaS taxability depends on who the customer is and where they are located, and there is no standardized system across jurisdictions. Treat "SaaS" as a starting category, not a final tax answer.
Does Paddle handle both U.S. sales tax and international VAT automatically?
For covered sales, Paddle acts as reseller and handles applicable buyer sales tax and VAT. Supported-country and product eligibility still matter, and the calculated result depends on product category, buyer location and status, and valid tax information. Verify your actual configuration rather than relying on a headline market count.
What does Merchant of Record actually remove from my team's workload?
Paddle handles buyer transaction-tax collection and remittance and issues buyer invoices for its covered sales. Your team still supplies accurate data, delivers software, reconciles proceeds, handles exceptions, and addresses its own business taxes and any direct sales outside Paddle.
How do I verify Paddle is applying tax correctly in different U.S. states?
Verify tax at the state level, not with one national assumption, because each state has its own rules. Also check for cases where both state and local tax apply. For each priority state, compare expected treatment to live checkout output and keep the supporting records together.
Is Paddle a fit for every SaaS business model and category?
No. Merchant of Record coverage does not mean every SaaS model or category is automatically in scope. Confirm fit against current Paddle documentation for your exact product, especially for edge cases.
What should I check first if tax results in checkout look wrong?
Check buyer country and subdivision information, product tax category, price tax mode, and relevant business tax identifier. Compare line-item tax and totals with your saved expected case, then escalate a supported, reproducible mismatch to Paddle.
How often should a small team re-validate tax settings after launch?
There is no single cadence you can treat as mandatory. Re-validate when your markets or setup change, or when invoice or report outputs look unexpected. For subscriptions, spot-check recurring charges because tax still needs to be correct on each billing cycle.
Try a related tool
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
Includes 4 external sources outside the trusted-domain allowlist.
Educational content only. Not legal, tax, or financial advice.
Related Posts

Paddle vs. Stripe: A Comparison for SaaS Founders
For a SaaS founder, this is a three-way choice: Paddle as Merchant of Record, Stripe Payments with Billing under your own merchant responsibility, or eligible Stripe Managed Payments transactions with Stripe as Merchant of Record. Compare those configurations before comparing fees. A standard Stripe account does not automatically make Stripe the legal seller.

What is a Merchant of Record (MoR) and How Does It Work?
**A merchant of record is the merchant responsible for the customer transaction in the payment system. An outsourced MoR service can take on that role so your business can sell eligible products through its checkout.**

The Freelance Payment Penalty: A Modeled Audit of Platform Fees, FX Spreads, and Payout Delays
The money rarely disappears through a single, easy-to-spot fee. The real loss is stacked. A marketplace takes its commission, a processor adds a charge for international cards, a bank or payment company converts the currency at a spread, a platform holds the funds before release, and a wire sheds a little to intermediaries on the way in. Each layer looks defensible on its own, but the worker feels the combined result as a smaller deposit and a later payday.

