The link between Aspel NOI and government IMSS portals (such as IDSE or SUA) is essential for maintaining employer compliance. Registering Hires, Dismissals, and Salary Modifications (affiliation movements) on time avoids fines. However, generating the file from NOI often results in validation or export errors, or rejections when uploading it to the platform.

The Error

When attempting to generate the .txt export file for movements in Aspel NOI, or when uploading this file to IDSE, the following common errors occur:

  • “Error generating file. Incorrect structure.”
  • “The Employer Registration does not match.”
  • IDSE Rejection: “Incorrect record length.”
  • IDSE Rejection: “Invalid character in column X.”

These errors prevent processing employer movements on time.

Root Cause

The main causes for the export failing or being rejected come from data inconsistencies within NOI:

  1. Incomplete worker catalog: Essential data is missing, such as CURP, RFC, Postal Code (now mandatory for CFDI 4.0), or the Cause of Dismissal.
  2. Special Characters: The strict text file used by IDSE does not support characters like (Ñ, ñ, accents, apostrophes, or accidental tabs) in the employee’s name.
  3. Wrong Employer Registration: If multiple branches are managed in Aspel NOI, the Employer Registration in “System parameters” does not exactly match the IDSE certificate.
  4. Inconsistent Dates: An attempt is made to generate a dismissal with a date prior to the hire, or the salary modification does not correspond to the bimester.
  5. NOI Layout Configuration: The NOI export template is outdated (common if you don’t have the latest update/re-installer).

Step-by-Step Solution

Follow this guide to ensure that the generated file is immaculately structured:

1. Cleaning Worker Data

This is the number one problem to correct:

  1. Go to Workers > Workers Catalog.
  2. Filter or search for the employees you are trying to report in the movement.
  3. Edit their profiles and remove any accents and change the letters Ñ to N. For example: change MARTINEZ ORDOÑEZ to MARTINEZ ORDONEZ.
  4. Check that there are no additional trailing spaces in the First Name or Last Names.
  5. If it is a Dismissal (Baja), ensure that the Salary/History tab has the “Cause of dismissal” specified (e.g., Voluntary separation).

2. Review the Employer Registration

  1. Go to Configuration > System parameters.
  2. Under the Employer Registrations section, ensure the format is exactly 11 positions.
  3. Validate that there are no intermediate hyphens, unless the template explicitly skips them. For SUA and IDSE, it is generally continuous (e.g., A0123456780).

3. Re-generating the Movements File

Once the data is corrected:

  1. Go to the IMSS/AFORE > IDSE Link (or SUA) tab.
  2. Scrupulously select the date range. Do not mix movements from widely dispersed months or bimesters unless strictly necessary.
  3. Choose the option to generate a .txt file.
  4. Choose a short path like C:\IDSE\movements.txt.

4. Validate the TXT with Notepad

Before uploading to IDSE:

  1. Open the movements.txt file with the classic Windows Notepad.
  2. Visually verify that all rows (records) appear to be the exact same length.
  3. If any row looks obviously shorter or longer, that specific worker’s record has an error and will be rejected.

5. Update the NOI Re-installer

If you receive chronic structural errors and the IMSS portal had recent changes, your Aspel NOI must be updated.

  1. Go to Help > Online Update Service (Aspel-AL).
  2. Check if there is a new re-installer that adjusts IMSS / IDSE formats.
  3. Download it and install it (with all users out of the system).

Prevention

  • Train the Human Resources department so that the capture of new candidates does not contain accents or “ñ” from the beginning.
  • Verify and update the UMAs and minimum wages in the NOI configuration before attempting to export general salary modifications, so the system calculates the SDIs accurately.
  • Aspel NOI: Error calculating quotas: Frequently caused by outdated IMSS / UMA base tables in the system or errors in absenteeism.
  • NOI vs SUA Differences: It is recommended to run the comparative report in “IMSS/AFORE” to reconcile pennies before paying.

Summary

  • The TXT files generated by NOI for the IMSS portals are incredibly fragile and strict against Latin characters and tabulations.
  • Debugging your employees’ spelling, confirming the employer’s configuration, and ensuring you are on the latest Re-installer of your NOI version prevents 90% of export headaches.