How to officially skip the 12 testers for 14 days on Google Play
The closed testing rule only applies to personal accounts. With a registered business and a D-U-N-S number you publish straight to production — the steps, the numbers and the pitfalls.
Accurate as of August 2026. Done the hard way myself — account, D-U-N-S, published without a single tester.
Prerequisites — read this first and save yourself the time
This only works if you tick every box below. Miss even one and the rest of the article won't help you, so feel free to stop reading.
You have a registered business — a company (Ltd, plc, association, …) or a sole trader registration. Without an entity on a public register this is a non-starter. The entity is findable in a public register. Both Google and Dun & Bradstreet verify you against public sources. You're creating a new Play Console account. You can't simply flip an existing personal account to an organization — plan on a new account plus an app transfer. You're fine with your company name showing as the developer in Google Play instead of your own. As a sole trader this is a non-issue — your legal trading name is typically your own name, so that's what the store shows. You have a few days of slack. The D-U-N-S number can arrive within minutes (see below), but if D&B doesn't have you on file yet, expect days or weeks. Don't start this the day before a planned release.
No registered business and no intention of getting one? This route isn't for you. The only alternative is to round up 12 testers and sit out the 14 days.
What this is about
Since 13 November 2023 Google has required newly created personal developer accounts to put an app through closed testing before it can go to production: at least 12 testers opted in continuously for the last 14 days (originally 20; Google lowered the number in December 2024). Those fourteen days have to be consecutive — you can't add up several shorter runs. Only then can you apply for production access, and review still runs after that.
For a solo developer this is a killer in practice. Twelve real people who install the app and keep it installed for two straight weeks aren't easy to find. If one of them opts out halfway through, the counter resets.
The key point the whole approach rests on: this requirement applies to personal accounts only. Organization accounts are exempt. It isn't a trick or a loophole — it's an official distinction Google itself draws. An organization has been through identity verification (hence the D-U-N-S), so Google doesn't need a testing period as proof that a real party stands behind the app.
The price for this route: you have to be a business, and you have to have a D-U-N-S number.
What a D-U-N-S is and how to get one
D-U-N-S (Data Universal Numbering System) is a nine-digit identifier issued by Dun & Bradstreet. Think of it as a global company ID used for verification — besides Google it's used by Apple, Amazon and plenty of others.
It's free, and it can often be sorted out with a single email.
The fastest route is email, not the form
Everyone points at the online form and its "up to 30 days" turnaround. In practice it's far simpler: email your local D&B helpdesk and ask. Plenty of companies already have a D-U-N-S number without knowing it — D&B builds its database from public registers. In that case there's nothing to apply for; they just look it up.
- Email the helpdesk for your country (in Czechia that's
helpdesk.cz@dnb.com). Two sentences will do: that you'd like the D-U-N-S number for your business, plus its registration number. No attachments needed. - Wait for the reply. Mine came in six minutes — the number in the body of the email and a link to the UPIK portal to check the details.
- Verify the recorded details on the UPIK portal, where D&B shows what it holds on your company. Pay attention to the exact entity name and address — you'll have to copy them into Play Console verbatim.
- If they don't have you on file, that's when they point you to the standard application. Fill in the exact legal name, registered address, company number, line of business and contact details, all matching the register exactly. Expect days to weeks there.
- Save the number. You'll need it elsewhere too — the Apple Developer Program asks for exactly the same thing.
Never pay for a D-U-N-S. There's no shortage of resellers offering "expedited processing" for 100+ USD of something you get for free — and in my case got back over a single lunch break.
Creating an organization account in Play Console
- Go to play.google.com/console and create an account — under a different Google account than your existing personal developer one. One Google account equals one developer account.
- Pick Organization as the account type, not Yourself/Personal. You can't change this later.
- Enter the exact legal name of the organization, the address, website and contacts — again matching the register and what D&B has on file.
- Enter the D-U-N-S number. You can't create an organization account without one; Google says so explicitly. If the details line up, it verifies you automatically and won't ask for further documents.
- Pay the one-off USD 25 registration fee.
- Go through developer identity verification — for an organization both the company and the person administering the account are checked. Have an ID document ready, and possibly a register extract.
- Wait for approval. Once the account is verified, Play Console never shows the closed testing requirement for a new app at all. You publish straight to production.
Proof that it works: these aren't theoretical tips off a forum. Under the Robert Dominguez Dev account on Google Play I have these apps:
- Move-In Checklist: Inspection — property handover reports
- Interval Timer: HIIT & Tabata — interval training timer
- Who's Right? — a party game
Not one of them went through closed testing. I didn't round up twelve people or wait fourteen days — from an organization account the build goes straight to production. Note the developer name too: I'm a sole trader, so the "company name" in the store is simply my own.
What to watch out for
- The details have to match to the letter. The most common reason for rejection is a mismatch between the name at D&B, on the register and in Play Console. Reconcile them before you submit anything anywhere.
- You can't convert a personal account to an organization. Google generally doesn't allow changing the account type. The real path is: create an organization account and transfer the app via App Transfer. That needs both accounts in good standing and has conditions of its own (among others, the account can't be brand new and both fees must be paid).
- App review doesn't go away. All you skip is the 14 days of testing — Google's own review still happens.
- Your company name becomes public. The organization is listed as the developer in the store. That's usually a plus (it reads as more trustworthy), but be aware of it.
- Sole traders can do this too, though it's more delicate — both D&B and Google want to see an entity, not a private individual with a side gig. Keep your trade register entry in order and use the exact registered trading name.
- Don't buy a ready-made account. Marketplaces with verified Play Console accounts exist, and Google systematically terminates them along with their apps. You'd lose everything.
- Don't pay for a D-U-N-S. Repeating it, because someone still makes money on this.
Summary
If you have a registered business, an organization account makes more sense in most cases: same fee, first release in days rather than weeks, and your company name in the store. The one thing you give up is that testing regime — and that's an obligation rather than a perk.
Sources
- Google's own confirmation: the 12 testers for 14 days applies only to personal accounts created after 13 Nov 2023
- No organization account without a D-U-N-S — the required details per account type
- How developer identity verification works and what to have ready
- Google's official step-by-step PDF for verifying an organization account
- The original policy announcement on the Android blog (July 2023), where the rule came from