Most articles about an ICIMS resume parsing not working problem are written for job seekers, and they all say the same thing: simplify your resume. That advice helps one candidate. It does not help the admin who is looking at a week of empty profiles.
This guide is for the admin side. It covers the seven causes we check first, which ones your team can fix in configuration, and which ones depend on the file the candidate sent.
What resume parsing does in ICIMS
Parsing reads a resume file and fills fields on the candidate’s profile: name, email, contact details, education, and professional experience. It runs in three places that admins usually troubleshoot separately:
- Career portal applications. When a candidate uploads a resume, the system may populate profile fields from it. ICIMS advises candidates to upload the resume before completing other fields to get the most from parsing.
- Create Person. A recruiter selects Create > Person > Candidate, uploads a resume, and reviews parsed name, contact, education, and experience details screen by screen.
- iResume email import. Users email up to ten resumes at once to the organization’s import address to create candidates in bulk, optionally attached to a job.
Knowing which entry point the bad profile came through cuts diagnosis time in half. If profiles look wrong in ways that go beyond parsing, our ICIMS data structure explainer shows how Person profiles relate to jobs and workflows.
7 causes of ICIMS resume parsing not working
Start every ticket the same way: open the candidate’s Resume tab, download the file, and open it. If the downloaded file itself looks wrong, the problem is the file, not ICIMS. ICIMS Technical Support’s own troubleshooting guide starts with that step.
ProblemAn imported resume creates no profile, or the profile has no name.
ImpactResumes sent through email import are rejected outright, and nobody notices until a recruiter asks where a candidate went.
ExampleA designer’s resume template puts the name and contact block in the page header for styling.
FixIf the name is in the header, the system cannot parse it. Without a candidate name, email import does not create a profile and the resume is rejected. Ask the candidate for a version with the name in the body, or create the profile manually and attach the file.
ProblemThe profile is created but the fields are empty or full of fragments.
ImpactRecruiters retype data by hand, and search misses the candidate entirely.
ExampleA candidate photographs a printed resume or exports a scan to PDF.
FixParsing needs clear, legible text. Resumes scanned and saved as images may not parse correctly, especially non-English ones. ICIMS recommends an original digital document. Ask the candidate to upload a different version or format.
ProblemAn upload or import fails, or the resume does not attach.
ImpactLost candidates from agency or referral sources that send compressed files.
ExampleA recruiter forwards a .zip of twenty resumes to the iResume address.
FixThe most commonly used and recommended formats are .doc, .docx, .odt, .pdf, .rtf, and .txt. The system accepts some others, such as .html and .tif, but .zip files are not acceptable. Unzip and send files individually, ten per email at most.
ProblemResumes in German, Spanish, French, or another language parse badly or not at all.
ImpactInternational hiring programs launch with unusable profiles.
ExampleA team opens roles in a new country and starts importing local resumes on day one.
FixICIMS can support resumes in languages such as German, Spanish, French, Italian, Chinese, and Russian, but ICIMS asks you to submit a case to Technical Support before uploading them so the system can be configured. For email import, Support can also set a preferred language and locale, and users pick the language from Create > Import Resume via Email.
Profiles coming in empty or garbled?
We will trace a few bad profiles back to their entry point on the call and tell you which of these seven causes is behind them.
Book a discovery callCauses 5 to 7: import timing, short text, and duplicate matching
ProblemA recruiter emails resumes in and sees nothing in ICIMS a minute later.
ImpactDuplicate submissions, which create their own cleanup.
ExampleA coordinator sends ten emails of ten resumes each after a career fair and refreshes immediately.
FixResumes submitted by email import take at least several minutes to parse. Bulk submissions are parsed in batches and take longer. Wait before resending, and check that a full name and contact information (phone or email) are present, since those are what create a new profile.
ProblemImported candidates land in general consideration instead of on the job, or a pasted resume fails.
ImpactRecruiters cannot find new applicants on the requisition.
ExampleThe subject line reads displayid: 2026-1234 with a space after the colon.
FixTo attach imports to a job, put displayid:, systemid:, or externalid: plus the ID in the subject with no spaces, and the ID must match an existing Job profile. For pasted resumes in Create Person, the text must be at least 70 characters, and pasted text produces a text-only resume view.
ProblemA recruiter imports a resume and the candidate’s older data appears to change, or no new profile is created.
ImpactConfusion over which version of the resume is current.
ExampleA returning candidate sends an updated resume through a referral, and it lands on their existing profile.
FixWhen an imported resume matches an existing candidate (typically on first name, last name, and email), it is added to that profile. The new resume overwrites the previous version, which is archived in the Resume Log. Check the log before assuming data was lost.
The diagnostic order we use
ICIMS Technical Support publishes a three-step troubleshooting guide for resume display issues. We use the same order and add two checks of our own.
- Download and open the file from the candidate’s Resume tab. If it looks wrong on your machine, the file is the problem.
- Ask the candidate to re-upload a new version, or a different file in a different format. ICIMS has no preferred resume style; clear, legible text uploads successfully.
- Test in your test site. If you have an ICIMS Applicant Tracking test site, upload the same file to a test profile. If it displays correctly in test but not in production, submit a case to ICIMS Technical Support.
- Check the entry point. Portal, Create Person, or iResume import each have their own rules (above).
- Check the Resume Log before concluding data was lost.
What your team controls versus the candidate’s file
| Issue | Who fixes it | How |
|---|---|---|
| Name in header, scanned image, odd formatting | Candidate | New version or different format |
| Unsupported file type (.zip) | Recruiter | Send individual files in a recommended format |
| Non-English resumes | ICIMS admin with Technical Support | Case to configure languages before uploading |
| Import timing and subject line format | Recruiter or coordinator | Wait for processing; use the exact subject syntax |
| Displays in test but not production | ICIMS Technical Support | Submit a case with the file and profile |
| Duplicate matching and overwrites | ICIMS admin | Review the Resume Log and merge profiles if needed |
On the career portal side, the order of fields in your application flow affects how much parsing helps. Our ICIMS application flow optimization case study shows how a shorter flow changed completion, and our ICIMS career portals setup guide covers portal configuration.
How to keep parsing quality high
Frequently asked questions
Clean candidate data from day one
Book a discovery call and we will review how resumes enter your ICIMS instance, then hand back a fix list your team can own.
Book a discovery call
