A DUNS number delay in Apple Developer enrollment usually comes from one of two things: Dun and Bradstreet has not finished issuing or updating your number yet, or it has, but Apple's system has not synced the record. Apple pulls Dun and Bradstreet data periodically, so a newly issued or updated DUNS can take up to about two weeks to appear in Apple's lookup, which is the sync delay behind many enrollments that stall even though the number already exists. You can pay Dun and Bradstreet to expedite issuing a new DUNS, but you generally cannot speed up the sync to Apple. Make sure your legal name and address match exactly on both sides, and wait through the sync window before contacting Apple.
Short answer
Most DUNS delays are either Dun and Bradstreet still issuing the number, or a sync lag before Apple recognizes it. Per Apple's D-U-N-S guidance, organizations need a matching DUNS to enroll, and a newly issued or updated record can take time to appear in Apple's lookup because Apple pulls the data periodically, commonly up to about two weeks. You can expedite the issuance itself through Dun and Bradstreet's paid service, but not the sync to Apple. Ensure your legal name and address match exactly on both sides, since a mismatch also blocks recognition. If it is still not found after the sync window, contact Apple Developer Support with your details.
Why the DUNS number is delayed
A DUNS delay during enrollment has a small number of causes, and identifying which one you have decides the fix. The first possibility is that Dun and Bradstreet has not actually finished issuing or updating your DUNS number yet, so there is nothing for Apple to find. The second is that Dun and Bradstreet has the number, but Apple's system has not yet synced it, so Apple's lookup does not return it even though it exists.
A third cause is a details mismatch: if the legal name or address you enter in Apple does not match what Dun and Bradstreet has on record, Apple cannot connect the two, and the number appears not to be found. So the useful first step is to determine whether the number exists at Dun and Bradstreet at all, and whether the details align, because that tells you whether you are waiting on issuance, waiting on a sync, or fixing a mismatch.
Does the D&B database take 14 days to sync with Apple?
Roughly, yes. Apple does not read Dun and Bradstreet's database in real time; it pulls the data on a periodic basis, so a newly issued or updated DUNS number can take a period, commonly cited as up to around two weeks, to appear in Apple's lookup. During that window, the number genuinely exists at Dun and Bradstreet while Apple simply has not picked it up yet, which is exactly why an enrollment can stall even after you have the number.
This sync lag is the part you cannot speed up. Because the delay is in Apple's periodic sync rather than in issuing the number, expediting the Dun and Bradstreet side does not shorten it. So if your DUNS is newly issued and Apple does not find it, the most likely explanation is the sync window, and the appropriate response is to wait it out and re-check Apple's lookup, rather than assuming something is broken.
How to expedite the D&B issuance
If your delay is in getting the DUNS number issued in the first place, Dun and Bradstreet offers a paid expedited service that can produce a number in a few business days, which is faster than the free process. This is the lever to pull when the issuance itself is the bottleneck and you have a genuine deadline, since it accelerates the creation of the number.
Be clear about what the expedite does and does not do, though. Paying Dun and Bradstreet speeds up issuing or updating the record on their side; it does not speed up Apple's periodic sync of that record. So an expedited DUNS still has to wait for Apple to pick it up, which means the expedite helps if you have not yet obtained a number, but it does not resolve a delay that is actually the Apple sync window. Weigh the cost against which part of the delay you are actually facing.
Make sure the details match
A frequent hidden cause of a DUNS delay is a mismatch between the details in Apple and those at Dun and Bradstreet. Apple matches your enrollment to a DUNS record using your legal entity name and address, so if either differs, even slightly, from what Dun and Bradstreet has on file, Apple cannot connect them and the number appears unavailable. This can look like a sync delay when it is really a data mismatch.
Check both sides carefully. Confirm that the legal name and address you enter in Apple exactly match your Dun and Bradstreet registration and your official business records, correcting any discrepancy at the source. If your Dun and Bradstreet record is outdated, update it, and remember that the update itself then has to sync to Apple. Getting the details to match is often what resolves a delay that waiting alone would not.
When to contact Apple
Contact Apple Developer Support when your DUNS number clearly exists at Dun and Bradstreet, the details match, and Apple still does not recognize it after the sync window of about two weeks. At that point the delay is beyond the normal sync, and Apple can check the status on their side and tell you whether anything else is needed. Provide your legal entity name, address, and DUNS number so they can look it up.
Before that window, contacting Apple is usually premature, since the most likely cause is the sync you cannot speed up. So the sequence is to confirm the number exists and the details match, wait through the sync window, and only then escalate. Reaching out with the specific details, after ruling out issuance and mismatch, is what lets Apple address an actual problem rather than restate the process.
Causes and fixes
Matching the cause to a fix avoids waiting on the wrong thing. The table below pairs the common causes with their fixes.
| Cause | What is happening | Fix |
|---|---|---|
| New DUNS not yet synced | Dun and Bradstreet has it, Apple has not picked it up | Wait up to about two weeks, then re-check |
| Number not issued yet | Dun and Bradstreet is still creating it | Wait, or pay to expedite the issuance |
| Details mismatch | Name or address differs between the two | Align the details at the source |
| Outdated Dun and Bradstreet record | Old information on file | Update it, then wait for the sync |
| Wrong record used | Multiple or regional records | Use the one matching your entity |
Read the table against your situation. A newly issued DUNS that Apple cannot find is almost always the sync window, while a persistent failure after that window points to a mismatch or a record issue to correct.
Checklist
A short sequence resolves or clarifies a DUNS delay. The checklist below covers it.
| Check | Action | Done? |
|---|---|---|
| Confirm issuance | Verify Dun and Bradstreet has issued the number | [ ] |
| Match details | Ensure legal name and address match on both sides | [ ] |
| Allow sync time | Wait up to about two weeks for Apple to sync | [ ] |
| Expedite if needed | Use the paid Dun and Bradstreet service for issuance | [ ] |
| Contact Apple | Escalate after the sync window if still unrecognized | [ ] |
The step that resolves the most confusion is understanding that the Apple sync window, not the number's issuance, is often the real delay, and it cannot be expedited. Confirm the number and details, wait through the window, and escalate only if it persists.
What to take away
- A DUNS delay is usually either Dun and Bradstreet still issuing the number or a sync lag before Apple recognizes it.
- Apple pulls Dun and Bradstreet data periodically, so a new or updated DUNS can take up to about two weeks to appear in Apple's lookup.
- You can pay Dun and Bradstreet to expedite issuing the number, but that does not speed up Apple's sync of it.
- A mismatch in legal name or address between Apple and Dun and Bradstreet blocks recognition, so align the details exactly.
- Enrollment is account admin, not app security; once enrolled, scan your build with PTKD.com before you submit.
