Why Does IngramSpark Say My ISBN and Account Don’t Match?
A mismatched name at Bowker isn’t a sign your ISBN needs replacing. It’s usually a sign someone at IngramSpark just needs to look at it.
You’re adding an already-published title to IngramSpark, and the upload gets blocked on “ISBN and account information do not match.” Most of the time, that’s not a KDP holdover or a bad ISBN — it’s the publisher name registered to that ISBN at Bowker not matching your IngramSpark account.
My name is Daniel J. Middleton, and after close to two decades in book design, the mistakes I see most often aren’t about talent — they’re about a process nobody explained.
This one has a fast, low-cost fix that most authors skip past on their way to a more expensive one, so that’s where this article starts.
What Does “ISBN and Account Information Do Not Match” Actually Mean?
IngramSpark checks the publisher name registered to your ISBN at Bowker against the identity on the IngramSpark account uploading it. If those two names don’t line up, the system blocks the title rather than guessing which one is correct.
That’s a Bowker-registration issue, not a file problem. Nothing about your manuscript, cover, or metadata triggers it.
Why the Obvious Explanation (a KDP Tie-Up) Is Usually Wrong
If the ISBN has ever been used on KDP, the natural first guess is that it’s somehow still tied up by that prior use. It’s a reasonable guess. It’s also usually wrong.
A client of mine ran into exactly this while adding three already-published titles to IngramSpark for distribution beyond Amazon, without pulling the KDP editions. All three threw the same mismatch error. Two of the three had never touched IngramSpark before at all, which ruled out any real KDP-to-Ingram platform conflict. The actual cause, confirmed in all three cases, was the Bowker-registered publisher name not matching her IngramSpark account name.
What’s the Fastest Way to Fix an ISBN and Account Mismatch on IngramSpark?
Contact IngramSpark support directly and ask them to manually review the mismatch before doing anything else.
That’s the move that resolved my client’s case. She emailed support about the error, and IngramSpark reviewed it and manually accepted the original ISBNs exactly as they’d been used at first publication.
No new ISBNs. No changes to her Bowker registration. Just a human on the other end confirming the ISBNs were legitimately hers.
A mismatched name at Bowker doesn’t automatically mean your ISBN needs replacing — it often just means someone at IngramSpark needs to look at it.
Support can’t always resolve every case this way, but it costs nothing to ask first, and it’s the option most authors skip in favor of a fix that takes more time and, if new ISBNs are involved, more money.
What If IngramSpark Support Doesn’t Resolve the ISBN Mismatch?
If support can’t clear the mismatch, there’s a legitimate DIY route: add a second imprint under your existing Bowker account (not a new account) so the registered publisher name matches your IngramSpark identity, then apply new ISBNs under that imprint. This lines up with Bowker’s own guidance on handling multiple imprints under one account, though it’s worth confirming against Bowker’s current documentation, since account and imprint rules do shift over time.
Worth knowing as a backup. Not worth reaching for first, since it costs new ISBNs and account changes that a manual review might make unnecessary. If you’re still deciding how to register ISBNs in the first place, that’s a decision worth getting right before you publish anywhere, since it’s the same registration data that causes this exact error later.
What Should You Do First When Your ISBN and Account Don’t Match?
If IngramSpark tells you your ISBN and account don’t match, don’t assume it’s a KDP holdover and don’t reach for new ISBNs yet. Email support, ask for a manual review, and give them the chance to clear it the way it actually got cleared for my client — before spending money or touching your Bowker registration at all.
If you want a second set of eyes on an ISBN or account issue that isn’t resolving cleanly, start here.

