This walkthrough is for an organization completing setup itself; the separate Account Registration service provides a reviewed evidence map and guided handoff. A Google Play organization account is intended for a legal entity that will own the apps, payment profile, and publishing responsibility. The current 12-tester production-access rule is published for new personal accounts; organization accounts follow a separate entity-verification path. D&B and Google control their own review timelines.
Source boundary
Why Choose an Organization Account?
Choose an organization account when the legal entity, rather than an individual, is the publisher and long-term account owner:
- Public developer name — Google allows the developer name to differ from the legal organization name; follow the display rules shown for each field
- Separate verification path — The standard organization route uses legal-entity and D-U-N-S verification; Google documents alternatives for certain government or D&B-unsupported cases
- Publisher identity — The public developer identity aligns with the entity responsible for the app
- Team access — Add developers, marketers, and managers with granular permissions
- Category-specific evidence — Regulated or sensitive categories may add ownership, licensing, or organization checks under their applicable policy
Choose by ownership
Prerequisites
Before starting the registration process, confirm the organization's country, legal form, and current Play Console route, then gather only the inputs that route requires:
- Eligible legal entity — Confirm that the country and current account flow recognize the organization's legal form
- D-U-N-S path — The standard organization flow uses a D-U-N-S record; government organizations and eligible entities in unsupported regions can have a documented alternative path
- Google account — An organization-controlled Google Account assigned to the authorized account administrator
- $25 registration fee — Payable via Google Payments (credit/debit card)
- Representative evidence — The authorized representative supplies only the identity or authority evidence requested in the target flow
- Business documents — Current registration, address, or authority evidence when Play Console requests it
- Organization phone number — A durable organization-controlled number that satisfies the field's current verification instructions
- Organization website — A controlled public website that accurately identifies the publisher
Pre-Check
Step-by-Step Setup
Step 1: Go to Google Play Console
Visit play.google.com/console and sign in with the organization-controlled Google Account assigned to the authorized account administrator. Choose "Organization" when prompted for account type.
Step 2: Pay the $25 Registration Fee
Complete the payment via Google Payments. This fee is non-refundable.
Step 3: Enter Organization Details
Provide the organization fields shown in the current flow. In the standard D-U-N-S path, the legal organization name and address in linked Google Payments must match the D&B record; phone, website, contact, and representative fields follow their own labels and evidence requirements.
Step 4: Submit Identity Verification
The authorized representative completes the identity or authority checks shown in the account. The legal organization remains the publisher and long-term account owner.
Step 5: Submit Business Documents
Submit only the organization documents and formats requested in the target account. Keep the submitted version and case reference so any follow-up can be traced to the same legal entity.
Step 6: Respond to Verification
Google reviews the submitted details against the organization record and may request corrections or additional evidence. Track the case and respond from the same source-of-truth entity sheet.
Match the entity, not an invented punctuation rule
D-U-N-S Setup
In the standard organization path, obtain or correct the D-U-N-S record before completing account creation. Government organizations and eligible entities in D&B-unsupported regions should use Google's documented support route. See our detailed D-U-N-S Number Guide for the record workflow.
Key points:
- Official route: Request or update the record through Dun & Bradstreet for the organization's country
- Timeline: Use the estimate supplied for the actual D&B case; do not promise a universal completion date
- Check first: Your business may already have a D-U-N-S number. Search at dnb.com
Team Management Features
Organization accounts include powerful team management capabilities:
Available Roles
- Owner — Full access, can manage all settings and team members
- Admin — Can manage apps, releases, and most settings
- Developer — Can upload builds and manage technical aspects
- Marketing — Can manage store listings, screenshots, and descriptions
- Finance — Can view financial reports and manage pricing
You can add team members after your account is verified, under Users and permissions in Play Console.
Business-Type Eligibility
Eligibility varies by country, legal form, D&B coverage, and the current Play Console flow. Common candidate organizations can include:
- Corporations and limited companies recognized in the account's country
- Partnerships or sole proprietorships only where the legal form is eligible for the organization route
- Non-profit and educational organizations with the requested entity evidence
- Government organizations using Google's applicable verification route
Having a business registration or D-U-N-S number alone does not prove that a legal form is eligible. Confirm the target account's route before paying or preparing translations.
Dependency-Based Timeline
- Entity preflight: Resolve legal-name, address, domain, telephone, and representative inconsistencies before submission.
- D-U-N-S work: Wait for D&B to create or correct the record when necessary.
- Account submission: Enter only values already traced to the current source documents.
- Google review: Respond to the actual request and preserve the case history.
- Handover: Confirm client ownership, recovery controls, permissions, and unresolved external dependencies.
Our registration service prepares and checks the packet before submission. It does not sell a fixed D&B or Google decision time.
FAQ
Can a freelancer register as an Organization?
Only when the freelancer's actual legal entity is eligible for the organization route in its country and can satisfy the current Play Console verification flow. A sole proprietorship or D-U-N-S number does not create universal eligibility.
What if my D-U-N-S application is still pending?
For the standard organization path, wait until the D-U-N-S record is issued and its legal name and address are accurate before completing account creation. Government organizations and eligible entities in D&B-unsupported regions should follow Google's documented support route instead of inventing a number or another legal form.
Can I change account access or ownership later?
Account owners can manage user access through the controls available in Play Console. Before relying on a primary-owner change or account-level transfer, verify the current supported route, eligibility, and evidence with Google for that account; do not treat an app-transfer workflow as proof that account ownership can always be reassigned.
Is there an annual fee?
Check Google's current registration and payment guidance for the account's country at the time of setup. Distinguish the developer-registration charge from taxes, transaction or service fees, payment-profile costs, and any third-party operating expenses; do not infer one store's current fee model from another store.
Evidence standard
Primary references
These first-party sources support the changeable platform requirements in this guide. Your current Play Console notice remains authoritative for account-specific steps.
Review your next Play Console step
Tell us what the account shows, where the release is blocked, and what has already been submitted. We will scope the work around the evidence in your case.
Discuss Your Release