Apple Developer Account Setup: D-U-N-S to Banking

Updated July 12, 2026 · by the Shipzen team

Before your first app can even be submitted, your Apple Developer account has to clear a chain of setup steps — entity checks, agreements, tax forms, banking — and several of them have multi-day waits you cannot expedite. This guide covers the account setup half of shipping a first app, in dependency order, with the delay to expect at each step. (For the submission itself, use the App Store rejection checklist.)

Individual or organization?

The first fork decides everything downstream. Enrolling as an individual needs your legal name (it becomes the seller name on the App Store), an Apple Account with two-factor authentication, legal age of majority, and ideally your own credit card — enrolling on the web with someone else's card delays enrollment and triggers a government-ID check.

Enrolling as an organization requires a recognized legal entity — DBAs, fictitious business names, trade names, and branches are not accepted — plus a D-U-N-S number, a work email on the organization's domain, a functional public website associated with that domain, and legal authority to bind the organization. If you are not the owner or founder, Apple may ask for a reference confirming that authority. The organization's legal name becomes the seller name.

Solo developer with no entity? Enroll as an individual and skip the next section entirely — individuals do not need a D-U-N-S number.

D-U-N-S number (organizations only) — start this first

A D-U-N-S number is a free, nine-digit business identifier assigned by Dun & Bradstreet that Apple uses to verify your legal entity. The timing is why it goes first:

Check the D-U-N-S lookup — your entity may already have one.
A new number takes up to 5 business days from D&B, and expediting does not shorten it.
Apple then needs up to 2 more business days to receive the data from D&B before you can enroll.
Stuck past 2 weeks, or details wrong? Contact D&B support directly — profile updates also take about 2 business days to reach Apple.

Common stall: the D&B record exists but lists an old address or officer, and Apple's verification fails against it. Fix the D&B profile first; re-enrolling will not help.

Enroll in the Apple Developer Program

Enrollment costs $99 per year (local-currency equivalents vary; accredited educational institutions can apply for a fee waiver; the separate Enterprise Program is $299 and for internal distribution only). You can enroll on the web or through the Apple Developer app — via the app, the membership renews as an auto-renewable subscription. Confirmation normally lands within 24 hours of payment; if it does not, contact Apple with your Enrollment ID. Organizations should expect the verification to take longer than individuals: D-U-N-S checks, the binding-authority check, and sometimes notarized business documents.

The Paid Apps Agreement trap

Joining the Program automatically includes the free-apps license, so free apps can ship once enrollment clears. Selling anything — paid apps or in-app purchases — requires the Paid Apps Agreement, and this is where first-time submitters most often get stuck, sometimes days before a planned launch:

Only the Account Holder can sign it — no Admin, no App Manager. In App Store Connect: Business, then the Agreements tab, then View and Agree to Terms on the Paid Apps row.
Signing is not enough. The agreement moves through statuses: New (unsigned) → Pending User Info (tax or banking still missing) → Processing (Apple reviewing) → Active. Paid apps and in-app purchases are blocked until it reads Active.
It can silently fall out of Active later: an expired membership shows Expired, a new agreement version shows New Agreement Available and blocks creating new apps or IAP until accepted, and Disabled means your app is removed from the App Store until you provide what Apple asked for.
Legal-entity name or address changes require Apple Developer Support and can take up to 2 weeks to process.

Tax and banking

The Paid Apps Agreement stays at Pending User Info until the paperwork behind it is done, in this order:

Tax forms — every developer completes a US tax form regardless of country, and depending on where your account is based, Apple may require additional country forms.
Banking — you can only add banking after the agreement is signed, and Apple only processes banking once the required tax forms are in. Account Holder, Admin, and Finance roles can manage it.

Do this the same day you enroll, even if your first app is free — retrofitting it later, under launch pressure, while only one person (the Account Holder) can act, is how releases slip.

Bundle ID and the first app record

With the account clear, the app side is quick: register the app's identifier in Certificates, Identifiers & Profiles, then create the app record in App Store Connect — platform, app name, primary language, bundle ID, and an internal SKU. The record starts in Prepare for Submission, and note the quiet dependency: apps cannot be added at all until the Account Holder has signed the latest agreement in the Business section. From here, metadata, screenshots, and review notes take over — which is exactly what the rejection checklist covers.

Where Shipzen fits

Shipzen is a native macOS App Store Connect client with a first-app mode built for this maze: it detects a missing or expired Paid Apps Agreement from your account state, keeps a plain-English checklist of the D-U-N-S, agreement, banking, and tax steps, and routes you to the exact Apple page each one lives on. It connects with your own App Store Connect API key, stored in the macOS Keychain — the account-legal steps stay on Apple's site, where they belong, but you stop discovering them by surprise.

App Store Connect, the way you need to see it. One email at launch, no spam.

Join the waitlist