---
title: "Service Location Import Error: Invalid Client Division or Level"
description: Fix the service location import error in Otuvy QM for invalid Client Division or Level by checking hidden whitespace, pasted characters, and optional Level field issues.
---
[Skip to content](https://help.otuvy.com/kb/service-location-import-error-invalid-client-division-or-level#main-content)
[More support](https://help.otuvy.com/kb/kb-tickets/new?hsLang=en)
Open main navigation
Close main navigation
- [More support](https://help.otuvy.com/kb/kb-tickets/new)
- [Contact us](mailto:vip@otuvy.com)
[Contact us](mailto:vip@otuvy.com)
How can we help you?
- There are no suggestions because the search field is empty.
1. [Otuvy Knowledge Base](https://help.otuvy.com/kb?hsLang=en)
2. [Otuvy QM - Setup & Administration](https://help.otuvy.com/kb/otuvy-qm-setup-administration?hsLang=en)
# Service Location Import Error: Invalid Client Division or Level
## If your service location import stops with an invalid Client Division and/or Level error, the values may look correct in the spreadsheet and still fail validation.
In most cases, the issue is not the visible text. It is hidden formatting in the spreadsheet cell, such as leading or trailing spaces, pasted characters that do not match the expected text exactly, or a non-standard character that looks identical on screen.
### What this error usually means
The import tool checks the **Client Division** and **Level** values against expected values. If either value contains hidden whitespace, an unexpected character, or a pasted value that is not an exact match, the import can fail even when the cell appears correct.
### How to troubleshoot it
Work through these checks in order:
1. **Check for hidden whitespace in Client Division**
Click into the Client Division cell and review the full value in the formula bar. Look for extra spaces before or after the text.
2. **Re-type the Client Division value**
Do not rely only on what is visible in the grid. Edit the value directly in the cell and confirm the formula bar shows the exact expected text.
3. **Check for hidden or non-standard characters**
If the value was copied from another source, it may contain characters that look correct but are not valid matches. This can include non-Latin characters such as Cyrillic characters.
4. **Replace the value with a fresh copy**
Copy the cell value from the spreadsheet, edit the division name, then select all and paste the corrected value back into the cell. Save the file before trying the import again.
5. **Check the Level field for whitespace**
Review the Level cell the same way. Even a trailing space can cause the import to fail.
6. **Remove the Level column if it is not required**
If the import does not require the Level column for your use case, delete that column and rerun the import. This can help isolate whether the issue is tied to the Level value rather than Client Division.
7. **Clear Cache and Cookies**
If you verified already that the cell exactly matches the division name by already replacing the division name with what's in the cell in the spreadsheet, be sure to:
1. Clear your cache and cookies
2. Log out and log back in
3. Try again
Sometimes that can correct the issue
### Fastest fix
If the values look right but the import still fails, the fastest path is usually:
- Re-type the **Client Division** value
- Re-type or clear the **Level** value
- Remove the **Level** column if it is optional
- Save the spreadsheet and import again
- Clear Cache and Cookies and try again
### Why this happens
Spreadsheet imports are exact-match processes. A value can appear correct to a person and still fail if the underlying cell contains:
- leading or trailing whitespace
- hidden pasted characters
- lookalike characters from another alphabet
- formatting artifacts from copied data
Troubleshooting note to add to an existing article
If you want to add this to the bottom of an existing knowledge base article, this section should fit well under **Troubleshooting**:
### Import fails with invalid Client Division or Level
If the import reports an invalid **Client Division** or **Level**, first check both cells for hidden whitespace in the formula bar. If the values were pasted from another source, re-type them or replace them with a clean pasted value. Also check for non-standard lookalike characters. If the issue continues, remove the **Level** column if it is not required and retry the import.
If you're still experiencing issues, please contact us at [vip@otuvy.com](mailto:vip@otuvy.com)
- [Otuvy QM - Getting Started](https://help.otuvy.com/kb/otuvy-qm-getting-started?hsLang=en)
- [Otuvy QM - Setup & Administration](https://help.otuvy.com/kb/otuvy-qm-setup-administration?hsLang=en)
- [Otuvy QM - Contact Access](https://help.otuvy.com/kb/otuvy-qm-contact-access?hsLang=en)
- [Otuvy QM - Inspections](https://help.otuvy.com/kb/otuvy-qm-inspections?hsLang=en)
- [Otuvy QM - Work Orders](https://help.otuvy.com/kb/otuvy-qm-work-orders?hsLang=en)
- [Otuvy QM - Mobile App](https://help.otuvy.com/kb/otuvy-qm-mobile-app?hsLang=en)
- [Otuvy QM - Reports & Dashboards](https://help.otuvy.com/kb/otuvy-qm-reports-dashboards?hsLang=en)
- [Otuvy QM - Advanced Features](https://help.otuvy.com/kb/otuvy-qm-advanced-features?hsLang=en)
- [Otuvy Frontline](https://help.otuvy.com/kb/otuvy-frontline?hsLang=en#main-content)
- [Getting Started](https://help.otuvy.com/kb/otuvy-frontline?hsLang=en#getting-started)
- [Mobile App](https://help.otuvy.com/kb/otuvy-frontline?hsLang=en#mobile-app)
- [Admin Portal](https://help.otuvy.com/kb/otuvy-frontline?hsLang=en#admin-portal)
- [Uncategorized](https://help.otuvy.com/kb/uncategorized?hsLang=en)
[](https://www.otuvy.com/)
[mailto:email@email.com](mailto:email@email.com)
Copyright © 2026, Otuvy, Inc.