Short answer
Companies should publish apps under organisation accounts, not personal ones: Apple and Google both verify your legal entity, usually via a D-U-N-S number, and show your company as the seller. Plan one to three weeks for verification, use a shared company identity as account holder, and give agencies and freelancers scoped roles instead of credentials.
On this page
- Why the account setup matters more than it seems
- What you need before you begin
- Step 1: the D-U-N-S number
- Step 2: choose the right identity as account holder
- Step 3: enrol and verify
- Step 4: roles and access
- Step 5: signing keys and ownership
- Working with agencies and partners
- Special cases
- FAQ
- Tools from the jocapps ecosystem
Why the account setup matters more than it seems
The developer account is the legal and technical owner of your app. Whoever controls it controls the listing, the reviews, the signing keys, the revenue and the ability to remove the app. We regularly meet companies whose app is published under a former employee's personal Apple ID or an agency's account. Untangling that later is slow and sometimes impossible without republishing.
Setting it up properly takes a few hours of work spread over one to three weeks of waiting. Start before the app is finished.
What you need before you begin
| Item | Apple Developer Program (organisation) | Google Play Console (organisation) |
|---|---|---|
| Legal entity name | Must match official records | Must match official records |
| D-U-N-S number | Required | Required for organisation accounts |
| Company website | Required, on a domain tied to the company | Required |
| Contact email | On the company domain recommended | Company email recommended |
| Authority | Person enrolling must be able to bind the company legally | Identity verification of the account owner |
| Payment | Annual membership fee | One-time registration fee |
| Public details | Company name shown as seller | Developer name, and for organisations contact details, shown on the listing |
Step 1: the D-U-N-S number
The D-U-N-S number is a company identifier from Dun and Bradstreet that both Apple and Google use to verify organisations. Many established companies already have one. Apple provides a lookup tool during enrolment where you can check and, if necessary, request a number free of charge.
Typical issues:
- The registered name or address at Dun and Bradstreet differs from your commercial register entry. Correct it before enrolling, otherwise verification stalls.
- A new company has no number yet. Requesting one can take from days to a couple of weeks.
- Group structures: decide which legal entity publishes the app. It will appear as the seller and receive revenue.
Step 2: choose the right identity as account holder
Apple's Account Holder and Google's account owner have the highest level of control. Do not use a personal account of whichever employee happens to set it up. Better:
- Create a dedicated company identity, for example a shared
appstore@yourcompany.commailbox that several people can access. - Create the Apple Account and Google account for that mailbox.
- Enable two-factor authentication and register at least two trusted devices or phone numbers held by different people, so access survives holidays and departures.
- Store recovery details in your company password manager.
Step 3: enrol and verify
Apple: enrol as an organisation in the Apple Developer Program. Apple may call the contact person to verify their authority. Once approved, accept the agreements in App Store Connect, and complete tax and banking information if you plan paid apps or in-app purchases.
Google: create a Play Console developer account as an organisation, complete identity and organisation verification and the D-U-N-S check, and set up a payments profile if you will sell anything. Organisation accounts are not subject to the closed-testing requirement that applies to newer personal accounts before production access, which is a practical advantage for launch planning.
Step 4: roles and access
Never share the account holder's password. Invite people individually with the smallest role that fits.
App Store Connect roles include Admin, App Manager, Developer, Marketing, Finance, Sales and Customer Support. Access can be limited to specific apps for some roles. Separately, certificates, identifiers and profiles in the developer portal are governed by the same team membership.
Google Play Console uses account-level and app-level permissions. You can grant a user permission to manage only testing tracks of one app, for example, or to reply to reviews without seeing financial data.
A sensible split:
- Internal product owner: Admin or App Manager.
- Agency or freelancers building the app: Developer or App Manager limited to the relevant app.
- Submission partner: App Manager, so they can manage metadata, builds and review communication.
- Finance: Finance role only.
- CI/CD: an App Store Connect API key with the minimum role, and a Google service account with release permissions for the specific app, not a person's credentials.
Step 5: signing keys and ownership
On Android, use Play App Signing so Google holds the app signing key and you keep only an upload key, which can be reset if lost. On iOS, certificates and provisioning profiles belong to the team; keep track of who created them and when they expire.
Document where these live. Losing the upload key or the only admin's access is one of the most expensive operational mistakes in mobile apps.
Working with agencies and partners
If an agency built your app in its own account, request an app transfer. Both Apple and Google support transferring apps between accounts under certain conditions, keeping reviews and users. Do it before launch if at all possible.
For new projects, the rule is simple: the app lives in your account from day one, and partners get roles. That is how appsubmitter.io works: it prepares listings, submits builds, sets up CI/CD and handles rejections entirely inside your own developer accounts, so you keep ownership of everything. If you are converting a website or web app with WebViewGold, the same applies: the template is yours, and the resulting apps are published under your company.
appsubmitter.io can also guide the enrolment itself, which is useful for public institutions and larger companies where legal entities, signatories and IT policies need coordination.
Special cases
- Internal apps for employees only: consider Apple's options for private distribution through Apple Business Manager and managed Google Play, instead of public listings.
- Public sector: check which entity publishes, and whether procurement or IT security must approve account owners and two-factor devices.
- Multiple brands: one account can publish many apps, but the seller name is the same for all of them.
Next steps after setup: TestFlight and Play Console internal testing and CI/CD for AI-built mobile apps. If Google has already rejected something, see Google Play rejection reasons for web apps.
FAQ
Do I need a D-U-N-S number for an Apple developer account?
Yes, to enrol as an organisation. Individuals can enrol without one, but the app is then published under the individual's name.
How long does company developer account verification take?
Often a few days to two weeks, longer if the D-U-N-S record needs to be created or corrected. Start early.
Can an agency publish our app in its account and transfer it later?
It is possible, but transfers have conditions and can be complicated. It is better to create your own account first and give the agency a role.
Who should be the Account Holder?
A shared company identity with two-factor authentication spread over several trusted people, not a single employee's personal account.