A tax-information request from a cloud marketplace can be confusing when the seller is a UK or US company and its founder lives elsewhere. The useful response is to identify the entity, the type of activity and the exact questionnaire. DAC7 concerns platform reporting and information collection. It should not be treated as a synonym for VAT, a US tax interview or a declaration of where an individual founder happens to work.
This guide helps a seller organise the process and evidence. It does not decide a company’s tax residence, permanent-establishment position or filing obligations. Use the marketplace’s current instructions for the questionnaire and take unresolved tax questions to the company’s adviser. The practical objective is a consistent, supportable submission: the right entity, the right registration and tax identifiers, and an accurate description of the activities offered.
Start with the selling entity
Write down the legal entity that owns the seller account and contracts with the customer. Include its legal name, registration number and current registered address. Do not substitute a brand name for a legal name unless a field specifically requests the trading name. When several related companies exist, avoid copying information from a different company’s earlier marketplace application. A founder’s shared email account or bank relationship does not make the entities interchangeable.
Create a private evidence folder containing the relevant company record and the documents requested by the platform. Keep a dated index describing each item and its source. This makes it easier to answer an evidence request without sending an entire collection of unrelated documents. Check that the entity in the tax dashboard matches the one in the seller account. If it does not, resolve the account mapping before completing another interview.
Distinguish information collection from reportability
The European Commission’s DAC7 overview describes the platform-reporting framework. A marketplace may need information to determine the seller’s position. Receiving a questionnaire does not, by itself, prove that every transaction will be reported under every rule. Equally, being incorporated outside the EU does not justify skipping questions that the platform requires to classify the seller and its activities.
AWS’s Marketplace tax-help page provides specific operational instructions. It identifies professional services as relevant activity for its DAC7 process and asks sellers to provide and validate identity and residency information. It also says software-only sellers still complete the DAC7 form to confirm that their offerings do not include professional services. These distinctions matter for an AI business selling both software and implementation work.
Separate software from professional services
Inventory the offers in the account. A subscription to software, an implementation engagement, training and customer support can have different commercial structures. Describe what the customer receives and compare it with the marketplace’s classification. Do not choose an answer merely because it produces a shorter form. If a company intends to sell a scoped service alongside a software card, make that intention clear when the questionnaire asks about services.
For example, an AI-assistant product can be accompanied by a workshop or deployment service. The product’s public card is not enough to determine how that separate engagement is classified. Review the service description, the acquisition route and the contracting entity together. Keep a brief explanation in the company’s records so a later team member can understand why a particular answer was given. An accurate record is more durable than a memory of the screen.
Prepare identifiers before opening the interview
The platform may request a tax identification number, business registration number and information about permanent establishments. These identifiers describe different things. A registration number establishes a company record; a tax number belongs to a tax administration; a VAT number is another identifier. Use the information requested by the field rather than assuming one number can replace all the others. Ask your adviser when the company does not know which identifier applies.
Review address information carefully. A registered office, an operating location, a founder’s residence and a banking address may differ legitimately. The problem is not simply that there are different addresses; it is entering one into a field requesting another. Read the field label, explanatory text and document requirements. Keep the submitted address with its supporting evidence. Do not change public company information only to make an unreviewed questionnaire answer look consistent.
Complete the dashboard process
AWS directs sellers to the tax dashboard in the Payment Information area of the seller portal. Its tax-information registration guide also describes the separate US tax interview. Follow the links and workspace labels shown in your account, since portal navigation can change. Treat each interview as a separate task with its own status. Completion of one should not be assumed to complete the other.
Before submission, review the legal name, numbers, addresses and activity answers as a set. Save the confirmation or reference made available by the platform. Record the submission date and whether the status requires validation or further action. Avoid placing tax identifiers in a public support forum, article or repository. Public documentation should explain the workflow; private account documents should support the individual company’s submission.
Handle missing information and follow-up requests
When a field is unclear, capture its exact wording and the account context. A focused support request should explain the selling entity, the offer type and the point where the process stops, without disclosing unnecessary personal information. Ask which document or identifier the field expects. Do not assume a generic response about another marketplace applies to the cloud-services account you are using.
After a change in company details or activities, review whether the saved information still describes the business. Keep a record of the reason for any update. Reconcile available marketplace reports with the company’s accounts and distinguish fees, revenue, refunds and bank receipts. AWS’s tax-document guide explains where available reporting documents can be accessed. The existence of a document and the time it becomes available depend on the relevant activity and reporting period.
Turn the process into a repeatable checklist
Give the company one owner for the evidence pack and a second person who can review the final answers. A useful checklist contains the seller entity, activity classification, requested identifiers, supporting documents, submission reference and outstanding action. Mark unanswered questions as unresolved rather than filling them with guesses. This reduces repeated interviews and makes accountant and marketplace-support discussions easier.
For founders building their first cloud offer, the broader lesson is to connect legal identity, product description and delivery model early. Explore the Digital Qazaqstan learning catalogue for practical technology workflows. A clear selling proposition makes the tax-information process easier to describe, even though it does not replace the company’s tax advice or the platform’s current questionnaire.