Individual or Company developer account: individual in Poland selling a paid add-on in a free app

Paweł Giziński 0 Reputation points
2026-11-22T12:01:48.71+00:00

I am a private individual in Poland with no registered company (my sales would be taxed as "unregistered activity", a Polish form for small revenue without a business registration).

I have not opened a developer account yet and want to choose the account type correctly, because it cannot be changed from Individual to Company later.

Planned app: a free Win32 desktop app packaged as MSIX, with one durable add-on ("Full version") sold through Microsoft Store commerce.

  1. Can an Individual developer account sell a paid durable add-on (with a payout and tax profile), or is a Company account required for any paid product? The account type documentation only distinguishes publishing under your own name vs a registered business, and I could not find a policy that forbids selling on an Individual account.
  2. As a seller I will be a "trader" under the EU Digital Services Act. For an Individual account, which trader contact details (name, address, email, phone) are shown publicly on the Store listing?
  3. The app is an accessibility on-screen keyboard. To type into elevated windows it needs uiAccess="true", declared as the restricted capability "uiAccess" in the package manifest. Is this capability available to Individual accounts, and is it approved for on-screen keyboards? If it is declined, can I resubmit the same app without it?

Thank you.

Microsoft 365 and Office | Subscription, account, billing | Other | Windows
0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-11-22T12:02:56.0633333+00:00

    A Company developer account is required for this plan, because Microsoft classifies any person distributing an app in relation to their trade or profession under the Company account type—even if that person is an independent developer without an incorporated company.^1^

    Account type and paid durable add-on

    The presence of a paid add-on does not, by itself, appear to prohibit monetization through an Individual account: Microsoft documents durable add-ons as available for free apps, and its payout setup supports tax and payment profiles.^2^ However, that does not make Individual the correct account type in this case.

    The controlling distinction is whether Store distribution relates to a business, trade, or profession:

    • Individual: publishing under your own name where distribution is not related to business, trade, or profession.
    • Company: registered organizations and independent developers/freelancers distributing in relation to business, trade, or profession.^1^

    Because the app will generate commercial revenue and you identify yourself as a DSA trader, select Company. Microsoft Store policy likewise requires a Company account for “any person acting in relation to their trade or profession.”^3^

    This creates a verification issue worth resolving before registration: Company onboarding normally expects a D‑U‑N‑S number or official business documents and a work email associated with the organization.^4^ Since Polish “unregistered activity” may not provide standard formation or registration documents, ask Windows developer support which accepted evidence applies to that Polish legal status before creating the irreversible account type.

    After enrollment, configure commerce in this order:

    1. Partner Center → Settings → Account settings → Payout and tax profile assignment.
    2. Create and submit the tax profile first.
    3. As a publisher outside the United States, complete the applicable IRS W-8 form.
    4. Create the payout profile using an account in the same country/region as the Partner Center registration.
    5. Wait for validation, which can take up to 48 hours.^5^

    These Microsoft forms do not replace any Polish registration, income-tax, or VAT obligations.

    Public EU trader contact details

    For a Company account categorized as a trader, Microsoft requires customer-contact email, telephone number, and physical address for regulatory compliance. Its DSA guidance explicitly discusses these details being public and suggests alternatives such as:

    • a post-office box for the physical address,
    • a dedicated number with voicemail,
    • a dedicated email alias,
    • or an accepted registered-agent address.^6^

    The public-facing identity also includes the publisher identity/name used for the Store product. The available documentation does not establish a separate rule allowing a natural-person trader to hide their legal name while continuing to sell under an Individual account.

    Enter and review the DSA information at:

    Partner Center → Account settings → Legal Info → Developer → Contact Information for Customers

    Then check EU Digital Service Act compliance status on the same page.^6^

    uiAccess for the on-screen keyboard

    uiAccess is not documented as limited to Company accounts. It is a restricted capability, so approval depends on the application scenario and certification review rather than merely the developer-account type.

    Microsoft specifically describes uiAccess as intended for trusted applications that must interact with higher-privilege UI or secure desktop sessions, and says it is often used by accessibility tools and automation software.^7^ An accessibility on-screen keyboard therefore matches the documented scenario, but approval is not automatic.

    Declare both the execution-level attribute and restricted capability, as applicable to your manifest:

    <requestedExecutionLevel
        level="asInvoker"
        uiAccess="true" />
    
    <Capabilities>
      <rescap:Capability Name="uiAccess" />
    </Capabilities>
    

    Ensure the package declares the rescap namespace and includes it in IgnorableNamespaces. In Submission options → Restricted capabilities, explain concretely:

    • that the product is an accessibility on-screen keyboard;
    • why it must type into elevated application windows;
    • which workflows require uiAccess;
    • how testers can reproduce and verify the behavior;
    • that the capability is used only for that accessibility function.

    If certification declines it, the certification report will provide feedback. You may then create a new submission either:

    1. with a revised justification or implementation and request approval again; or
    2. with a new package that no longer declares uiAccess and has uiAccess="false" or omits the attribute.^8^

    That means the same Store product does not need to be abandoned solely because the capability was rejected; submit a corrected package version under the existing product.


    References

    1. Get started with Microsoft Store
    2. Monetization, engagement, and Store services
    3. Microsoft Store Policies
    4. Set up your Microsoft Store developer account early
    5. Set up Microsoft Marketplace payout and tax profiles
    6. What is the “Know Your Business Customer” requirement for company accounts?
    7. App capability declarations
    8. Manage submission options for add-ons
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.