MERCHANT OF RECORD
Merchant of Record for B2B SaaS: Tax IDs, Invoices, and Global Checkout
Anyway Team
· 8 min read ·
A Merchant of Record for B2B SaaS is the legal seller for covered software transactions. It processes payment, determines applicable transaction tax, issues the buyer invoice, and pays the SaaS vendor net proceeds. The SaaS vendor continues to deliver the application and control the customer's workspace, users, permissions, and data.
Anyway provides this MoR layer through hosted checkout, recurring billing, tax handling, compliant buyer documents, and net bank payouts.
Why B2B SaaS checkout is not just a card form
A business buyer may need the purchase to pass finance review before anyone logs in. The order can require a legal company name, billing address, tax ID, correct seller identity, invoice number, currency, tax treatment, and renewal terms.
The software entitlement is only one half of the record. The commercial record must answer:
Which legal seller charged the buyer?
Which business purchased the service?
Was the buyer treated as a business or consumer for tax?
Which tax ID was supplied and how was it checked?
What period and product does the invoice cover?
Which workspace received access?
How does the order connect to the vendor's payout?
A Merchant of Record can own the buyer-facing transaction while the SaaS team owns the application relationship.
The B2B SaaS order record
Design the data model before launch. A useful record contains four connected identities:
Identity: Product customer; Example: Workspace or organization ID; Why it matters: Controls SaaS access
Identity: Buyer contact; Example: Finance or admin user; Why it matters: Receives billing communication
Identity: Legal customer; Example: Registered company name and address; Why it matters: Appears on the buyer document
Identity: Commercial order; Example: MoR order and subscription IDs; Why it matters: Connects payment, invoice, and payout
Do not merge these into one email field. The employee who pays may leave, the legal company name may differ from the product workspace, and one parent company may pay for several workspaces.
Anyway's event data can connect the covered payment to the seller's own customer and entitlement records. Keep your stable workspace ID as the product identity, then store the Anyway order and subscription references beside it.
B2B tax IDs and VIES validation
EU B2B digital-service sales often depend on whether the customer supplies a valid VAT identification number. The European Commission explains that a VAT number identifies a taxable person and can help establish customer status and place of taxation.
VIES is the European Commission search engine for checking whether a VAT number is valid for cross-border EU transactions. The Commission advises keeping a validation record in case a tax authority later reviews the decision. An invalid result may also mean the number is not activated for intra-EU transactions or that registration is still pending.
A practical checkout flow should:
collect the buyer's country and legal billing address;
ask whether the purchase is for a registered business;
collect the country-prefixed VAT number when relevant;
validate the number through the appropriate official or provider service;
retain the number, result, time, and evidence used;
apply the resulting tax treatment to the buyer document.
Never approve a tax result from the visual format alone. DE123456789 may look plausible and still be invalid.
Reverse charge needs an invoice trail
For qualifying cross-border B2B services, the customer may account for VAT under the reverse-charge procedure. This is not the same as “there is no tax.” It reallocates who reports the VAT.
The European Commission's invoicing page says EU VAT invoices are required for most B2B supplies. A full invoice generally includes a unique sequential number, supplier and customer names and addresses, the relevant VAT identification numbers, service description, dates, amount, VAT rate and amount, and any required special wording. When the customer is liable under reverse charge, the invoice should state “reverse charge.”
Anyway issues compliant buyer invoices for covered MoR orders and handles applicable transaction tax as the seller. This gives a B2B SaaS team a strong commercial document layer without building a country-by-country invoice engine inside the application.
Buyer invoice versus seller payout statement
These documents serve different relationships:
The buyer invoice records the sale from the Merchant of Record to the end customer.
The seller payout record explains the net proceeds transferred from the MoR to the SaaS vendor.
Do not send the payout statement to the buyer as its tax invoice. Do not treat the buyer's invoice total as an unexplained bank deposit in the vendor's books.
Anyway sits in the buyer transaction as MoR, issues the compliant customer document, then pays the vendor net revenue. The vendor can reconcile covered sales, tax, fees, refunds, and payouts at order level. Read SaaS invoices and receipts for document design and SaaS payment reconciliation for the finance flow.
A B2B SaaS commercial record built around validation, checkout and buyer documentation.
B2B subscriptions and entitlement control
B2B SaaS access usually belongs to a workspace, not a cardholder. Model these objects separately:
billing customer;
workspace;
plan entitlement;
subscription;
invoice and order;
payout reference.
Anyway supports recurring subscriptions, including monthly and annual plans. These intervals are common for self-serve B2B products. The seller can map the Anyway subscription state to its own workspace plan through verified events.
When a renewal succeeds, extend the paid-through date once. When a payment is pending or fails, apply the grace policy published in the contract. When a cancellation arrives, preserve access until the agreed end date if the plan is prepaid.
Procurement questions to answer before checkout
Self-serve B2B buyers often ask the same questions:
Buyer question: Who is the legal seller?; Page or process that should answer it: Checkout and terms
Buyer question: Will I receive a tax invoice?; Page or process that should answer it: Billing FAQ
Buyer question: Can I enter company details?; Page or process that should answer it: Checkout flow
Buyer question: What is the billing interval?; Page or process that should answer it: Pricing page and order summary
Buyer question: How do I cancel?; Page or process that should answer it: Account and cancellation policy
Buyer question: Is renewal automatic?; Page or process that should answer it: Pricing page and checkout
Buyer question: Who provides the SaaS service?; Page or process that should answer it: Product terms
Buyer question: Where do I get support?; Page or process that should answer it: Product support page
For covered sales, Anyway gives the transaction a clear legal seller and compliant buyer document. The SaaS vendor can keep security, privacy, service levels, onboarding, and product support in its own contract and help center.
Merchant of Record for B2B SaaS pricing
Anyway's public price is 3.9% + $0.50 per transaction, with no public monthly or setup fee. The price includes the complete MoR service described on its site, including global transaction-tax work, billing, subscriptions, buyer documents, and payout.
At a $100 monthly plan, the published fee is $4.40 per successful transaction. At a $1,000 annual plan, it is $39.50. A founder can model the transaction cost without adding a separate public tax-service subscription.
For higher-value B2B plans, also measure support time, invoice corrections, card limits, refunds, currency conversion, and the buyer's preferred procurement method. The visible checkout fee is one part of the total selling cost.
Merchant of Record for B2B SaaS implementation checklist
Keep product workspace, buyer contact, legal customer, and MoR order as separate records.
Publish the seller identity, price, interval, renewal rule, cancellation method, and refund policy.
Collect the billing fields required for the buyer's jurisdiction and invoice.
Validate tax IDs through the relevant official or provider process and retain evidence.
Link the checkout to the correct workspace before sending the buyer away from the app.
Grant access only after a verified payment event.
Make renewal, cancellation, and refund handlers idempotent.
Test the buyer invoice with a real business purchase.
Reconcile the order to the Anyway fee and net bank payout.
Give support a search path across email, workspace ID, order ID, and subscription ID.
Frequently asked questions
What is a Merchant of Record for B2B SaaS?
It is the legal seller for covered business purchases of the SaaS product. It handles payment and applicable transaction tax, issues the buyer invoice, and pays the SaaS vendor net proceeds.
Does a B2B customer always pay no VAT?
No. The result depends on the seller model, buyer and seller locations, customer status, product classification, and a valid tax ID where required. Reverse charge is a reporting mechanism, not a universal exemption.
What is VIES?
VIES is the European Commission search engine used to check whether a VAT number is valid for cross-border EU transactions. Keep evidence of the result and validation time.
Who appears as seller on an MoR invoice?
The Merchant of Record appears as the legal seller for the covered end-customer transaction. The SaaS vendor remains the provider of the product experience under its service terms.
Can Anyway handle recurring B2B SaaS plans?
Yes. Anyway supports recurring subscriptions, including monthly and annual plans, which are common choices for self-serve B2B SaaS.
What does Anyway charge?
The published Business rate is 3.9% of each transaction plus $0.50, and Anyway lists no monthly or setup charge.
Give business buyers a clean commercial record
Create a B2B SaaS product with Anyway, connect the checkout to a workspace, and test the company details, buyer document, subscription event, and payout trail before launch.
Official sources checked
Information checked on August 26, 2026. Tax and invoice treatment depends on the transaction facts and applicable law; this article is not tax advice.