ATS Guides

Mercury xRM CV Formatting Guide for Recruitment Agencies

Learn how to fix CV formatting and parsing issues in Mercury xRM ATS to ensure smooth uploads and accurate data. Get the guide.

By Xabi Errotabehere, founder, Distill · Updated 18 July 2026

If you're using Mercury xRM ATS in your recruitment agency, you know CV formatting and parsing can be a headache. Poorly formatted CVs cause errors, slow down uploads, and frustrate hiring managers. This guide explains what you need to watch out for and how to fix common issues to get the most out of Mercury xRM.

TL;DR

Mercury xRM struggles with CVs that use tables, complex layouts, or embedded images. Keep formatting simple—avoid tables and text boxes. Watch out for parsing errors caused by unusual fonts or hidden characters. Upload failures often happen because file size limits or unsupported formats aren't met. Distill can clean and reformat your CVs automatically before upload, saving time and reducing errors.

What you need to know about CVs in Mercury xRM

Mercury xRM is built on Microsoft Dynamics, making it a powerful ATS for ANZ agencies. Its parsing engine is sensitive to CV formatting. It expects CVs in Word or PDF formats but works best with plain, linear layouts.

Key points:

  • Tables and text boxes: Mercury xRM often scrambles data inside tables or text boxes, mixing up contact details or work history.
  • Fonts and styles: Unusual fonts or inconsistent styles can cause the parser to misread sections.
  • File types: Word (.doc, .docx) and PDF are supported. Other formats like RTF or OpenOffice aren't.
  • File size: Large files (over 10MB) may fail upload.
  • Embedded images: Photos or logos can cause parsing failures or slow down processing.

Understanding these helps avoid wasted time reformatting or fixing errors after upload.

Formatting guide

To ensure Mercury xRM reads your CV properly, follow these formatting rules:

  • Avoid tables and text boxes. Use simple bullet points and line breaks instead. Tables break parsing; text boxes can hide important info.
  • Use standard fonts. Stick to Arial, Calibri, or Times New Roman at 10–12pt size.
  • Keep layout vertical. Mercury xRM reads top-to-bottom, left-to-right. Multi-column CVs confuse the parser.
  • Label sections clearly. Use standard headings like "Work Experience," "Education," and "Skills" on their own line.
  • Remove images. Photos and logos should be deleted before upload.
  • Keep file size under 5MB. Compress images if needed, or strip them out entirely.
  • Consistent date formats. Use "MMM YYYY" or "MM/YYYY" consistently throughout.
  • No headers or footers. Mercury xRM may ignore or misinterpret these areas.

Following these guidelines reduces parsing errors and speeds up CV processing.

Parsing errors

Mercury xRM's parser mistakes are usually caused by formatting quirks or hidden characters. Common issues include:

  • Merged or missing fields. Tables and text boxes cause data to merge, such as phone numbers blending into names.
  • Broken contact details. Line breaks or bullet points inside contact info fields can cause the parser to drop parts.
  • Dates not recognised. Inconsistent or verbose date formats confuse the timeline extraction.
  • Missing skills or qualifications. Complex formatting in skills sections can cause data loss.
  • Extra whitespace or hidden characters. Copy-pasting from PDFs or emails can insert invisible characters causing errors.

The fix — simplify formatting and paste CV text into a clean Word document before upload. Using Distill can automate this cleaning process and highlight parsing risks before submission.

For a deeper dive, see the Mercury xRM parsing errors guide.

Upload issues

Even if the CV parses correctly, uploads to Mercury xRM can fail or stall. Typical causes include:

  • File size limits. Mercury xRM often caps uploads at 10MB. Large PDFs with images hit this limit.
  • Unsupported formats. Only Word and PDF accepted. Other formats get rejected.
  • Corrupt files. CVs saved from older or non-standard software may corrupt during upload.
  • Network timeouts. Slow connections cause uploads to fail, especially for large files.
  • Special characters in filenames. File names with symbols or spaces can cause rejection.

Best practices for upload:

  • Compress or remove images to reduce file size.
  • Rename files with simple characters and no spaces.
  • Save CVs in .docx or PDF format from trusted software.
  • Re-upload on a stable network connection.

Check out the full Mercury xRM upload issues guide for troubleshooting steps.

Distill + Mercury xRM

Distill integrates with Mercury xRM workflows by cleaning and reformatting CVs before you upload them. It strips out photos, removes contact details for blind hiring, fixes formatting errors, and converts CVs into ATS-friendly Word documents.

If you're sending 20+ CVs a week to Mercury xRM clients, Distill can save hours spent fixing formatting and chasing parsing errors. It doesn't connect directly inside Mercury xRM but works as a quick pre-upload step to ensure your CVs meet the specs outlined above.

Try Distill free to see how it smooths your CV exports for Mercury xRM.

If your agency struggles with CV formatting and parsing errors in Mercury xRM, try Distill free. It automatically cleans and formats your CVs to Mercury xRM's requirements, cutting upload issues and saving your team time.