This is a very predictable outcome when a requirements doc is tossed over the wall followed by patient waiting for the output.
Again, it happens all the time so maybe this advice isn't enough or practical or something, but there is a well recognized solution and I would wonder whether it was done in this project.
The people saying Devs dont do enough effort to understand the domain are the same people who try to keep the "domain" overly complicated to justify their jobs/positions
I think the fault is actually the split between IT (a support function) and the product group, which often doesn't have/isn't allowed embedded devs.
IT managers are often toxic for delivering, never take ownership, SLA bullshit, too much PRINCE2 and ITIL.
If you can get developers embedded, huge wins are possible. But they have to bring the client with them, not code away in isolation.
I have many similar annecdotes. Having a good understanding of the underlying domain and what numbers to expect is critical to writing correct models and too often I see dev teams in banks that have no understanding or curiosity of what they work on.