When Mercury xRM won't accept a CV, the cause is usually the file itself — size, format, or something Dynamics's attachment handling doesn't like. This guide helps you clear upload failures quickly.
TL;DR: Mercury xRM upload problems come from oversized files (embedded images), unsupported formats (legacy .doc, scans), special characters in filenames, and Dynamics attachment size limits. Use clean .docx files under a few MB with plain filenames. Distill automates the prep.
Quick diagnosis: what's blocking the upload?
| Symptom | Likely cause | Quick check |
|---|---|---|
| File rejected outright | Unsupported format | Is it an old .doc or a scanned image? |
| Upload slow or times out | Large file with images | Is the file over ~2MB? |
| Attachment error from Dynamics | File exceeds attachment size limit | What's your environment's attachment cap? |
| Error on a valid-looking CV | Special characters in the filename | Any symbols or accents in the filename? |
Root causes ranked by frequency
Large files with images Photos, logos, and design elements bloat CVs past comfortable upload sizes. Dynamics environments also enforce attachment size limits — a designed PDF can hit them.
Unsupported or legacy formats Old .doc files and scanned images are rejected or fail during processing. Use .docx or a text-based PDF.
Special characters in filenames Symbols, emoji, or heavy diacritics in filenames can trip attachment handling. Use plain alphanumeric filenames.
Batch overload Pushing a large batch through at once is less reliable than smaller groups, especially over slower connections.
Step-by-step fix
- Strip images and compress. Remove photos and logos; keep files under ~2MB.
- Convert to .docx. The most reliable format for Mercury xRM.
- Rename the file. "Firstname Lastname - Role.docx" — plain characters only.
- Split large batches into smaller groups.
- Check your environment's attachment limit with your admin if errors persist on files that look fine.
- Re-test with one clean file before re-running the batch.
How to prevent Mercury xRM upload issues
- Standardise on compact .docx output for every CV entering your workflow.
- Strip images at intake; re-apply client branding on the way out.
- Keep a team-wide filename convention.
- Batch-prep with Distill so every file is small, clean, and consistently named.
When to automate this
- You upload 20+ CVs weekly into Mercury xRM.
- Upload failures interrupt work more than once a week.
- You also need reformatting or anonymisation before client submission.
Distill outputs compact, clean, consistently named .docx files that clear Mercury xRM's upload checks first time.
FAQ
Q: Why does Mercury xRM reject my CV file? A: Usually format or size. Convert to .docx and strip embedded images.
Q: I get an attachment error from Dynamics. What does it mean? A: The file likely exceeds your environment's attachment size limit. Compress it, or ask your admin what the cap is.
Q: Can I upload scanned CVs? A: They may attach, but they won't parse into the record. Convert to a text-based file first.
Q: Does Distill upload to Mercury xRM for me? A: No. It prepares clean files that you upload as normal.
If failed uploads are eating recruiter time, Distill preps every file to Mercury xRM's liking automatically. Try Distill free.