When a business publishes Android apps, the right move is a Google console developer account registered as an organization — not a founder’s personal account with the company name typed into the developer-name field. Organization accounts verify the legal entity (via D-U-N-S and business documents), display the company brand on every listing, and structure team access the way businesses actually operate. They also avoid the painful personal-to-organization migration that traps growing studios.
This guide is the company-focused playbook: when you need an organization account, the D-U-N-S and verification process in detail, how to structure teams and clients, tax and payments setup, and the governance practices that keep a business account healthy. For the general account overview, see our Google Play Console account guide.
In short: A business should register its Google console developer account as an organization, not a personal account: verification runs on the legal entity through a D-U-N-S number and business documents, the company brand appears on listings, and team access follows roles. Start the D-U-N-S request early — it can take up to 30 days — and expect one to three weeks for verification.
When Your Business Needs an Organization Account
Register as an organization if any of these are true:
- You’re a registered company (LLC, Ltd, GmbH, Pvt Ltd, etc.) publishing under the business name.
- You’re an agency or studio publishing apps for clients.
- Multiple founders or employees need durable access — personal accounts create single points of failure.
- You want the company name and logo on store listings for brand trust (users trust “Acme Inc.” more than a personal name for paid apps).
- You’re raising investment or planning acquisition — clean corporate ownership of the developer account is part of due diligence.
The trap to avoid: starting personal “because it’s faster” and planning to switch later. Google offers no conversion path from personal to organization. Switching means registering a new account, re-verifying, and migrating apps through a manual transfer process with review gates. Start as an organization if there’s any chance you’ll need it within two years.

D-U-N-S Numbers: The Foundation
The D-U-N-S number (Data Universal Numbering System, issued by Dun & Bradstreet) is the anchor of organization verification. Google uses it to confirm your business is real and to match your legal name and address.
Getting one
- Search dnb.com first — your business may already have a number.
- If not, request one (free; standard processing up to 30 days, expedited options available for a fee in some regions).
- When D&B contacts you to verify details, ensure the legal name and registered address are exactly right — including suffixes (Ltd, LLC, Inc.) and suite numbers.
Keeping it clean
Your D&B record must match your business registration documents character-for-character. The most common organization verification failure is a mismatch: D&B says “Acme Limited, 12 High Street” while the certificate of incorporation says “Acme Ltd., 12 High St.” Update the D&B record before submitting to Google — resubmitting mismatched documents just burns weeks.
Start the D-U-N-S process before you need the account. It’s the longest step in organization registration, and everything else waits on it.
The Organization Verification Submission
With D-U-N-S in hand, at play.google.com/console/signup:
- Select organization account and enter your D-U-N-S number — Google retrieves your D&B record automatically.
- Upload business registration documents: certificate of incorporation, articles of organization, business license, or tax registration — the official proof of the legal entity in your jurisdiction. Screenshots and self-made PDFs are rejected.
- Provide an official company website and a domain email (team@yourcompany.com). Free email providers on an organization application signal illegitimacy.
- The authorized representative — a director, officer, or formally authorized employee — completes personal ID verification (government photo ID, same standards as personal accounts).
- Enter the company’s physical registered address (not a PO box or virtual office).
- Pay the $25 registration fee and accept the Developer Distribution Agreement.
Timeline: 1–3 weeks from submission is typical. Rejections name the specific issue — fix exactly that before resubmitting. Our verification deep-dive covers all ten common rejection reasons.
Structuring Teams on a Company Account
Organization accounts shine at team management. Set this up on day one:
- Ownership: the owning Google account should be a durable company-controlled address — ideally a Google Workspace account owned by the business, not a founder’s personal Gmail. Founders leave; companies persist.
- Admins: 2–3 trusted admins (CTO, lead developer, operations). Admin is the only role that manages users — never grant it broadly.
- Roles by function: Release managers for engineers, Marketing for ASO staff, Support for customer service, Finance for accounting. Use app-level scoping so teams only see their apps.
- Contractor hygiene: invite with expiry dates tied to contracts; remove within 24 hours of offboarding; audit the user list quarterly for ghosts.
- Client separation (agencies): clients should own their own organization accounts with you as an invited user — never publish client apps on your agency’s account. One client’s policy strike must never threaten another client’s apps.
For the full permission system, see our team and permissions guide.
The table below summarises how to structure teams on a company account:
| Area | Guidance from this guide |
|---|---|
| Ownership | Use a durable company-controlled Google account, ideally a Google Workspace account, not a founder’s personal Gmail |
| Admins | 2–3 trusted admins (CTO, lead developer, operations); Admin is the only role that manages users |
| Roles by function | Release managers for engineers, Marketing for ASO staff, Support for customer service, Finance for accounting, with app-level scoping |
| Contractor hygiene | Invite with expiry dates tied to contracts, remove within 24 hours of offboarding, audit the user list quarterly |
| Client separation (agencies) | Clients own their own organisation accounts with you as an invited user; never publish client apps on your agency’s account |
Tax, Payments, and Business Details
Organization accounts have business-grade financial setup:
- Payments profile: create it under Setup with the company’s legal name, address, and tax information. Payouts cannot flow until tax forms are complete — this is the #1 “where’s my money” cause for new company accounts.
- Tax forms: US companies complete W-9 equivalents; non-US companies complete the appropriate treaty documentation (W-8BEN-E for entities). Google’s payments system guides you, but have your tax ID ready.
- Currency: payouts go in your bank’s currency; understand Google’s conversion timing for revenue planning.
- Invoicing: download monthly earning reports for accounting — Google’s 15% service fee on the first $1M annual earnings (30% above) is already deducted.
Keep business details current: if the company moves, renames, or restructures, update both the D&B record and the Play Console account details. Stale records trigger re-verification at the worst times.
Handling Company Changes: Mergers, Rebrands, and Restructures
Businesses evolve, and your developer account must keep up — carefully, because Google treats entity changes as potential account-takeover signals:
- Rebrand (same legal entity): update the developer name (Setup → Developer account → Details) and the D&B record. Minor name updates are routine; the listings update after a short review.
- Legal entity change (new company): this is effectively a new verification event. Update D&B, submit new business documents, and expect re-verification of the organization. Plan for 2–4 weeks.
- Acquisition: the acquiring company should establish its own organization account and transfer apps through Google’s app transfer process — don’t try to morph the old account’s identity, which triggers fraud flags.
- Founder departure: ensure admin continuity before the departure — remove their user, rotate API keys they held, and confirm the owning Google account remains company-controlled.
Document every change with dates: verification events reference your history, and a clean paper trail makes re-verification dramatically smoother. Our account recovery guide covers the access-continuity side.
The table below summarises how to handle each type of company change:
| Change | What to do |
|---|---|
| Rebrand (same legal entity) | Update the developer name (Setup → Developer account → Details) and the D&B record; listings update after a short review |
| Legal entity change (new company) | Update D&B, submit new business documents, and expect re-verification; plan for 2–4 weeks |
| Acquisition | The acquiring company establishes its own organisation account and transfers apps through Google’s app transfer process |
| Founder departure | Ensure admin continuity before the departure — remove their user, rotate API keys they held, and confirm the owning Google account remains company-controlled |
Governance: Keeping a Business Account Healthy
- Document everything: which Google account owns the developer account, who the admins are, where API keys are stored, what the D-U-N-S number is. Store it where the business — not one person — can reach it.
- Succession planning: ensure at least two admins can fully operate the account. If the single admin leaves, recovery is painful.
- Policy ownership: assign one person to watch the Inbox and Policy status. Business accounts with many apps generate more policy surface — unattended warnings escalate.
- Separate dev and prod identities: use distinct Google accounts for the company’s developer account vs. employees’ personal use — never mix.
- Annual audit: verify D&B record accuracy, user list cleanliness, API key rotation, and tax document currency.
Google’s official organization requirements are documented in the Play Console Help Center.
Google Console Developer Account: Key Takeaways
A Google console developer account registered as an organization is the right foundation for any business: verified company identity, brand on listings, proper team roles, and clean ownership for the long term. Start the D-U-N-S process early, match every document exactly, and structure teams with least privilege from day one. The patience verification requires pays back in credibility.

Frequently Asked Questions
Does a company need a D-U-N-S number for a Google console developer account?
Yes — organization accounts require a D-U-N-S number for verification, with no exceptions. Request one free at dnb.com (allow up to 30 days standard). Your D&B legal name and address must exactly match your business registration documents.
Can I convert my personal developer account to an organization account?
No — Google provides no conversion path. You must register a new organization account and migrate apps through the transfer process. If you’re a business on a personal account, start the organization registration now rather than later.
Who should own our company’s developer account?
A durable company-controlled Google account (ideally Google Workspace), not any individual’s personal Gmail. Complement it with 2–3 admin users so the account survives personnel changes.
How long does organization verification take?
Typically 1–3 weeks after submission, plus D-U-N-S acquisition time (up to 30 days if you don’t have one). Clean, matching documents on the first submission are the difference between days and months.
Should agencies publish client apps on the agency’s account?
No. Each client should own their own organization account; the agency works as an invited user. This isolates policy risk — one client’s violation must never threaten another client’s apps or the agency’s own portfolio.
Conclusion
A Google console developer account registered as an organization is a business asset: verified company identity, brand on listings, proper team structure, and clean ownership for due diligence. The upfront cost is patience — D-U-N-S, documents, verification — but it eliminates the personal-account traps that ambush growing companies.
Play Console Store is an independent marketplace helping companies set up organization developer accounts — D-U-N-S guidance, verification preparation, and team structuring. Explore our Google Play services to get your business account right from day one.