How to legally skip the 12-testers-for-14-days rule on Google Play

Accurate as of August 2026. Tried and done: account, D-U-N-S, app published without a single tester.

---

Prerequisites — read this first, don't waste your time

This approach only works if you tick every box below. If a single one is missing, the rest of the article won't help you and you can stop reading.

You have a registered company or sole-trader business with an official registration number (company ID / VAT ID / trade licence). Without a legally registered entity, this is a dead end.
The entity is findable in a public business register. Both Google and Dun & Bradstreet verify you against public records.
You are creating a brand-new Play Console account. You cannot simply convert an existing personal account into an organization one — plan for a new account plus an app transfer.
You're fine with your company name appearing as the developer in Google Play instead of your own name. As a sole trader this is a non-issue — your registered business name is typically just your own first and last name, so that's what the store will show.
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 to weeks. Don't start this the day before a planned release.

No registered business and no intention of registering one? This isn't for you. Your only alternative is to find 12 testers and sit out the 14 days.

---

What the rule actually is

Since 13 November 2023, Google requires newly created personal developer accounts to run a closed test before shipping to production: at least 12 testers opted in continuously for the last 14 days (it was 20 originally; Google lowered the number in December 2024). Only then may you apply for production access — and that review takes up to another 7 days.

For a solo developer this is brutal. Twelve real people who install the app and keep it installed for two straight weeks is not a trivial ask. If someone opts out halfway through, your counter resets.

The key fact the whole workaround rests on: this requirement applies only to personal accounts. Organization accounts are exempt. This isn't a trick or a loophole — it's an official distinction Google itself draws. An organization has already gone through identity verification (that's what the D-U-N-S is for), so Google doesn't need a testing period as proof that a real, accountable entity is behind the app.

The price of skipping the testers: you have to be a business, and you have to get 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. It's the global business-verification ID — Apple, Amazon and plenty of others use it too, not just Google.

It's free, and it can often be sorted out with a single e-mail.

The steps — e-mail is the fast lane

Everyone points you at the online form and its "up to 30 days" turnaround. In practice there's a much shorter path: e-mail your local D&B helpdesk and just ask. A lot of companies already have a D-U-N-S number without knowing it — D&B builds its database from public registers on its own. In that case there's nothing to apply for; they simply look it up for you.

1. E-mail your country's D&B helpdesk. For the Czech Republic that's helpdesk.cz@dnb.com; other countries have their own address, findable on the local dnb.com site. Two sentences are enough: that you'd like the D-U-N-S number for your business, plus your company registration number. No attachments needed.
2. Wait for the reply. Mine came back in six minutes — the number in the body of the e-mail, plus a link to the UPIK portal where you can check the record.
3. Verify the recorded details at dnb.com/de-de/upik.html. Pay attention to the exact entity name and address — you'll have to reproduce them character for character in Play Console.
4. If they don't have you on file, that's when they point you at the standard application. Fill in the exact legal name, registered address, business ID, industry and contact — all matching the public register. Expect days to weeks at that point.
5. 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 a whole cottage industry of resellers charging 100+ USD for "expedited processing" of something that's free — and that, in my case, arrived over the course of a single lunch break.

---

Creating the organization account in Play Console

1. Go to play.google.com/console and create an account — under a different Google account than your existing personal developer account. One Google account = one developer account.
2. Choose Organization as the account type, not Yourself/Personal. This choice is permanent.
3. Enter the exact legal name of the organization, address, website and contacts — again, matching the register and what you submitted to D&B, character for character.
4. Enter your D-U-N-S number. If it matches, Google can verify you automatically and won't ask for further documents.
5. Pay the USD 25 fee.
6. Complete developer identity verification — for organizations, both the company and the individual managing the account get verified. Have an ID document and possibly a register extract ready.
7. Wait for approval. Once the account is verified, the closed-testing requirement simply won't appear for your new app in Play Console. You publish straight to production.

Proof that it works: this isn't theory picked up on a forum. These are the apps I have on Google Play under the Robert Dominguez Dev account:

• Move-In Checklist: Inspection
• Interval Timer: HIIT & Tabata
• Who's Right?

Not one of them went through closed testing. No hunting for twelve people, no fourteen-day wait — from an organization account the build goes straight to production. And note the developer name while you're there: I'm a sole trader, so the "company name" in the store is simply my own.

---

Pitfalls

• The details must match letter for letter. The most common rejection cause is a mismatch between the name at D&B, in the register, and in Play Console. Align all three before you submit anything anywhere.
• You can't convert a personal account. Google generally doesn't allow changing the account type. The real path is: create the organization account and transfer the app via App Transfer. That requires both accounts in good standing and has its own conditions (among others, the target account can't be brand-new and both fees must be paid).
• The 7-day review doesn't disappear. You're only skipping the 14 days of testing — Google's own app review still happens.
• Your company name becomes public. The store will list the organization as the developer. Usually a plus (it reads as more trustworthy), but be aware of it.
• Sole traders can do this too, but it's more delicate — D&B and Google both want to see an entity, not a person with a side gig. Keep your trade register entry clean and use the exact registered name.
• Don't buy ready-made accounts. Marketplaces selling verified Play Console accounts exist, and Google systematically terminates them along with their apps. You lose everything.
• Don't pay for a D-U-N-S. Repeating it, because someone is still making money on this.

---

Summary

	Personal account	Organization account
12 testers / 14 days	yes	no
D-U-N-S	not needed	required
Registered business needed	no	yes
Fee	USD 25	USD 25
Time to first release	~3–5 weeks	days (the D-U-N-S can take minutes)
Developer shown in store	your name	company name

If you have a registered business, the organization account is the better choice regardless — even if the tester requirement didn't exist.

---

Sources

• App testing requirements for new personal developer accounts — Play Console Help
• Verify your developer identity information — Play Console Help
• Required information to create a Play Console developer account — Play Console Help
• Verifying your Play Console developer account for organizations (PDF)
• New policy update to boost trust and transparency on Google Play — Android Developers Blog