AWS EMEA SARL (Amazon Web Services EMEA SARL) is the Luxembourg-based AWS entity that invoices most AWS Marketplace buyers in Europe, the Middle East and Africa, for sellers who have completed AWS’s Know Your Customer (KYC) verification. Until you have, AWS Inc. invoices those buyers. This post covers the operations, not tax or legal advice.
A buyer in Germany accepts your private offer, and their accounts payable team asks why the AWS Marketplace invoice came from AWS Inc. when the rest of their AWS bill comes from Amazon Web Services EMEA SARL. Nobody on your side chose that. AWS did, from the buyer’s location and your company’s KYC status, plus your channel partner’s on a Channel Partner Private Offer (CPPO). The same facts decide who may refund that invoice later.
How a marketplace invoicing your buyer changes your books is covered in what seller of record means on a cloud marketplace. This post is the AWS EMEA piece: which entity invoices, what KYC changes, and what to check before a transaction or a billing adjustment.
What is AWS EMEA SARL?
AWS EMEA SARL is the AWS Marketplace invoicing entity for Europe, the Middle East and Africa: “the Marketplace Operator for transactions between EMEA customers and Sellers who have onboarded to AWS EMEA.” An invoicing entity is one of the regional AWS companies, also called Marketplace Operators or MPOs, that handle a region’s “localized business needs, such as tax, reporting, disbursements, and compliance.”
- One legal entity, many branch names. AWS EMEA is established in Luxembourg, and its branches are “the same legal entity,” not subsidiaries. The buyer’s location picks the branch on the invoice: a buyer in Germany sees Amazon Web Services EMEA SARL, Niederlassung Deutschland.
- The money runs through Amazon Payments Europe, “a licensed electronic money institution in Luxembourg.” That is why KYC exists: AWS cites the Payment Services Directive (PSD 2) and the EU’s anti-money-laundering directives.
- Nothing to relist. AWS Marketplace products “are still in a global catalog.”
Which AWS entity invoices your buyer?
The buyer’s AWS account location picks the region, and your KYC status decides whether AWS EMEA SARL can act for EMEA buyers. AWS’s Seller Tax Grid: “The Buyer country is the main criteria to determine the AWS Marketplace Operator.” Until your KYC is done, “AWS Inc. will be used as the invoicing entity for the seller’s transactions in this region.” The location that counts is the AWS account’s, which AWS determines “at the moment of invoicing” from its Tax Address.
| Buyer’s AWS account is in | Who invoices the buyer | KYC it depends on | What completing it changes |
|---|---|---|---|
| EMEA, most countries | AWS EMEA SARL once you are KYC-verified; AWS Inc. until then | Your business verification | The entity on the invoice, the buyer’s row in the Seller Tax Grid, and a separate disbursement through Amazon Payments Europe |
| EMEA, through a CPPO | AWS EMEA SARL only if the channel partner and the ISV are both KYC-verified | Both companies’ business verification | The same, for that CPPO |
| Turkey or South Africa | AWS Inc., with or without KYC | None | Nothing |
| South Korea | The AWS South Korea invoicing entity | Your KYC and bank account verification | Whether its disbursements can reach you |
AWS also excludes purchases of professional services from AWS EMEA SARL. And sellers registered in Japan have a check of their own, Japan Installment Sales Act verification, “regardless of where their buyers are located.”
Your console shows this for your account. In AWS Partner Central, the Know Your Customer (KYC) tab under Marketplace settings lists “customer regions, invoicing entity, transaction status, and disbursement status.” A row marked Blocked has a Next Steps column saying what AWS needs.
What does completing KYC change?
KYC is three steps: the first changes who can invoice your EMEA buyers, the second lets you get paid, and the third lets people other than the root user handle money. After the first, AWS says, “your seller account will be KYC verified, but you must provide a bank statement on the Payment information tab before you can receive disbursements through Amazon Payments Europe.”
| Step | What AWS verifies | What it unlocks | AWS’s stated review time |
|---|---|---|---|
| 1. Business verification | Your company, its documents and its key individuals | A KYC-verified seller account, which AWS EMEA SARL needs to invoice your EMEA buyers | ”typically within 24 hours” |
| 2. Bank account verification | A bank statement matching your seller account and disbursement account | Disbursements through Amazon Payments Europe, and from the South Korea entity | ”typically takes 1-5 business days” |
| 3. Secondary user verification | Each additional person’s identity | That person can process refunds and change bank details | ”typically within 24 hours” |
Those are per-step review times, not a schedule. Compliance teams “may request additional information or documentation based on their assessment,” so plan the sequence rather than a date: finish KYC before an EMEA offer goes out. Line up two things first: a primary contact with “legal capacity to represent the company,” or a letter of authorization, and legal’s read of the AWS Marketplace EMEA Agreement and the Amazon Payments Europe Terms & Conditions, both accepted during the flow.
What goes wrong when KYC is missing?
Three things, each on a different team’s desk: the invoice your EMEA buyer receives, the CPPO your reseller quotes, and the refund your finance team tries to issue.
AWS Inc. invoices your EMEA buyers
When AWS launched self-service KYC in November 2024, it listed what completing it gives buyers: consistent VAT “across all their AWS purchases,” payment through SEPA, and “invoices for all their AWS services and Marketplace purchases from a single entity - AWS EMEA.” Without your KYC, your invoice is the exception on their AWS bill.
The tax handling can change too. The Seller Tax Grid has separate tables for sellers with and without KYC, and a buyer country’s row, including who collects tax, can differ between them. Read it with your tax advisors; the grid itself “does not constitute tax advice.”
A CPPO needs two KYC-verified companies
AWS: “both the Channel Partner and the ISV need to be KYC verified to use AWS EMEA as the invoicing entity. AWS Inc. will be the default invoicing entity if either party is not KYC verified.” Your verification does not cover your reseller’s.
The partner also owns the refund: only the channel partner, “as the seller of record, can initiate cancellation and billing adjustment requests for CPPO agreements,” so AWS’s KYC and MFA prerequisite falls on the partner’s user, not yours.
Billing adjustments need a verified person with MFA
AWS calls secondary user verification optional. For refunds it is not: “To adjust invoices issued in countries with Know Your Customer (KYC) compliance requirements, you must first complete secondary user verification and enable multi-factor authentication (MFA).” The root user gets refund rights once KYC is complete, but AWS “strongly recommend[s] that you do not use the root user for everyday tasks.” Verify more than one named person, with MFA, before the first refund on an AWS EMEA SARL invoice.
The check is per invoice. AWS announced on March 31, 2026 that KYC verification “is now only triggered for invoices that require compliance validation.” Suger’s documentation notes these are most commonly invoices issued by AWS EMEA SARL.
That rule is behind a row in Suger. Suger submits adjustments through an integration role, which can never be the verified person AWS asks for, so it tells you before you try. In the Billing Adjustment dialog, such an invoice’s checkbox is disabled and the row reads “Issued by AWS EMEA SARL — AWS requires a KYC-verified user to adjust it.” A Must be adjusted in AWS link opens the agreements list in AWS. The refunds and cancellations documentation shows each message, and the full self-service flow is in refunds and cancellations on AWS Marketplace.
What should you verify before an EMEA transaction or adjustment?
Check three moments: before the offer goes out, before you expect the money, and before anyone adjusts an invoice.
Before you send an offer to an EMEA buyer
- Read the buyer’s region in the KYC tab: invoicing entity, transaction status, disbursement status.
- Ask which AWS account will accept the offer and which country its Tax Address shows; “linked accounts do not inherit the Tax Address or TRN of the payer account.”
- On a CPPO, get the partner’s confirmation that they are KYC-verified.
- Tell the buyer’s procurement team which entity will invoice. Buyers in Turkey and South Africa, and professional services purchases, won’t get AWS EMEA SARL.
Before you expect the money
- Confirm bank account verification is complete.
- Expect two disbursements, one from AWS EMEA SARL and one from AWS Inc. AWS’s Europe FAQ points to broker details in the Seller Data Delivery Service reports for telling them apart.
Before anyone adjusts an invoice
- Check which entity issued it. For AWS EMEA SARL, a KYC-verified user with MFA submits the adjustment; on a CPPO, the partner’s.
- Approve first: “Billing adjustments are irreversible after they have been processed.”
Frequently asked questions
What is AWS EMEA SARL?
Amazon Web Services EMEA SARL is the Luxembourg-based AWS entity that invoices AWS Marketplace buyers in Europe, the Middle East and Africa, once the seller has completed AWS’s KYC verification. AWS excludes buyers in Turkey and South Africa, and purchases of professional services.
Who invoices my EMEA buyers before my KYC is complete?
AWS Inc. AWS says that until KYC is completed, AWS Inc. is used as the invoicing entity for the seller’s transactions in the EMEA region. The tax handling can differ too, so read the buyer country’s row in the Seller Tax Grid table for sellers without KYC.
Does a CPPO need the channel partner to complete KYC too?
Yes. For AWS EMEA SARL to invoice a Channel Partner Private Offer, both the channel partner and the ISV must be KYC-verified. If either is not, AWS Inc. is the default invoicing entity.
How long does AWS Marketplace KYC take?
AWS says a KYC submission is typically reviewed within 24 hours and bank account verification typically takes one to five business days, but its compliance team may ask for more documents. Those are per-step review times, not an end-to-end schedule, so finish KYC before an EMEA offer goes out.
Who can refund an invoice issued by AWS EMEA SARL?
A KYC-verified user with MFA: a secondary user who completed their own KYC, or the root user, which AWS advises against. Since AWS’s March 31, 2026 update, KYC is triggered only for invoices that require compliance validation. On a CPPO, only the channel partner can request the adjustment.
Takeaways
- The buyer’s AWS account location picks the region; your KYC status, and on a CPPO your partner’s, decides whether AWS EMEA SARL or AWS Inc. invoices an EMEA buyer.
- KYC changes who invoices; getting paid through Amazon Payments Europe also needs a verified bank statement.
- Verify named secondary users, with MFA, before the first refund on an AWS EMEA SARL invoice.
- Read tax questions off AWS’s Seller Tax Grid, in the table that matches your KYC status, with your advisors.
Suger keeps each AWS agreement, its invoices and every adjustment on one record, and flags the AWS EMEA SARL invoices that only a verified person can adjust. See marketplace billing and revenue operations in Suger.
Sources
Primary sources for the platform rules cited above. Last verified September 24, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.
- AWS Marketplace Seller Guide: Step 5: Complete the Know Your Customer (KYC) process — Regional invoicing entities (MPOs); KYC mandatory for EMEA transactions and disbursements and for South Korea disbursements; AWS Inc. invoices until KYC completes; a CPPO needs both parties verified; Amazon Payments Europe; the KYC tab's invoicing-entity table; review typically within 24 hours; the bank statement before disbursement; the three KYC steps; Japan Installment Sales Act verification
- AWS Marketplace Seller Guide: Step 6: Complete bank account verification — Bank account verification is required before disbursements from the AWS EMEA and Korea invoicing entity; the statement must match the seller account name and disbursement account; review typically 1-5 business days
- AWS Marketplace Seller Guide: Managing secondary users for Know Your Customer (KYC) — Secondary users complete their own KYC before they can process refunds or change bank details; the root user has these functions after KYC but AWS recommends against everyday root use
- AWS Marketplace Seller Guide: Refunds and cancellations in AWS Marketplace — Adjusting invoices issued in countries with KYC requirements needs secondary user verification and MFA; on a CPPO only the channel partner, as seller of record, can request adjustments; adjustments are irreversible
- AWS What's New: AWS Marketplace sellers can now self-serve refunds and agreement cancellations — Posted March 31, 2026: KYC verification is now only triggered for invoices that require compliance validation
- AWS What's New: Self-Service Know Your Customer (KYC) for AWS Marketplace Sellers — Posted November 25, 2024: self-service KYC for the AWS EMEA Marketplace Operator, and the buyer-side effects of completing it (consistent VAT, SEPA payment, one invoicing entity)
- AWS Tax Help: Marketplace Sellers Tax Grid — Separate tables for sellers who have and have not completed KYC; the buyer country as the main criterion for the Marketplace Operator; AWS EMEA as MPO on a CPPO only if both parties are KYC'd; AWS Inc. for Turkey and South Africa in both tables
- AWS Europe FAQs — AWS EMEA Marketplace, Sellers: the Luxembourg entity and its branches, which branch invoices whom, the PSD2 and EU anti-money-laundering basis for KYC, no relisting, two disbursements, and the exclusions for professional services, Turkey and South Africa
- AWS Tax Help: Account Location — AWS determines each account's location at the moment of invoicing from its Tax Address; linked accounts do not inherit the payer account's Tax Address
- Suger docs: Refunds and Cancellations — Suger product behaviour: the Billing Adjustment dialog's KYC-restricted rows, the link to adjust in AWS, and the failure message when AWS refuses an adjustment for KYC reasons
Keep reading
Stay Updated
Get the latest Cloud GTM insights, product updates, and marketplace strategies delivered to your inbox.