Fixing import and upload errors

Use this guide when a bulk upload or an automated file feed does not process the way you expect. For the messages that appear after LHDN validation, see Why your invoice was rejected.

How imports report results

• Import Log: Open the log entry and select View to inspect a failed row or receipt.
• Return file (automated feeds): If you send files through an automated feed, JomeInvoice writes a return file back to you. It adds a status and a reason for each invoice so you can see which rows succeeded and which need fixing.
• Partial results are normal: Valid rows still process even when some rows fail. Fix only the failed rows, then send those again.

File format

The file type is not supported

Error message: Unsupported file type or Only csv/json format is allowed

Where you will encounter it: During upload, or in the Import Log for an automated feed.

What it means: The file is not in a format JomeInvoice accepts for your account.

Steps to fix:

1. Export the file in the agreed format (usually CSV or JSON).
2. Do not upload spreadsheets saved as .xlsx, .zip, or .pdf.
3. Upload the file again.

The file could not be read

Error message: Messages such as Invalid JSON format, Could not find records array, or No root element found for XML feeds.

Where you will encounter it: During upload, or in the Import Log.

What it means: The file is malformed, or the records are not where JomeInvoice expects them.

Steps to fix:

1. Re-export the file from your source system without editing it by hand.
2. For CSV, keep the header row and column order unchanged, and use the agreed delimiter.
3. Save the file as UTF-8 so special characters are read correctly.
4. Upload the file again.

Column values look shifted or garbled

Where you will encounter it: In the row preview or after processing, where values land in the wrong fields.

What it means: The delimiter or text encoding does not match what your account expects.

Steps to fix:

1. Use the exact delimiter configured for your account (a comma, unless agreed otherwise).
2. Save the file as UTF-8 without a byte-order mark.
3. Keep the header row present and unchanged.

Field mapping

Not all required fields are mapped

Error message: There are missing fields or Failed to validate CSV mapping

Where you will encounter it: The field-mapping step during bulk upload.

What it means: One or more required columns are not mapped to a JomeInvoice field.

Steps to fix:

1. Map every required field in the mapping step.
2. Confirm each source column header matches what you mapped.
3. Continue and validate again.

See Bulk upload invoices for the full mapping workflow.

Row-level validation

Failed rows are listed with a reason. These are the most common.

A required value is missing

Error message: Required field is missing or Required field is empty

What it means: A mandatory column (such as invoice number, date, or a total) is blank for that row.

Steps to fix:

1. Fill the required value for every row.
2. Confirm the column header matches exactly.
3. Send the corrected rows again.

A value is the wrong type or format

Error message: Messages such as invalid numeric format or Invalid date format

What it means: An amount contains text, or a date is not in the expected format.

Steps to fix:

1. Enter amounts as numbers only, with no currency symbols or spaces.
2. Use the exact date format agreed for your account.
3. Send the corrected rows again.

A value is not allowed

Error message: Messages such as value does not match pattern, not in valid values, or outside valid range

What it means: The value is not one of the accepted options, or it is outside the allowed range.

Steps to fix:

1. Use an accepted value for that field.
2. For codes such as payment method or tax type, send the LHDN code, not free text. See the code tables in Why your invoice was rejected.

A buyer or supplier has no identifier

Error message: A message that the buyer or supplier must have at least a name, TIN, or registration number.

What it means: The party row has none of the identifiers JomeInvoice needs to match or create a record.

Steps to fix:

1. Include at least a name, TIN, or registration number for each party.
2. Send the corrected rows again.

File placement (automated feeds)

These apply if you drop files into a folder for an automated feed. They do not apply to Direct Upload in the app.

The file was placed in the wrong folder

Where you will encounter it: The file is skipped, or it appears in an invalid folder.

What it means: The file was not dropped in the expected new folder, or the path does not match your account setup.

Steps to fix:

1. Drop files into the new folder for the correct invoice type.
2. Use the exact folder path JomeInvoice provisioned for your account.
3. Include the branch or department folder only if your account is set up that way.

The file name was not recognised

Where you will encounter it: The file appears in an invalid folder.

What it means: The file name does not match the agreed naming pattern, or it references a company or branch that is not set up.

Steps to fix:

1. Name the file exactly as agreed. Compare it with a file that worked before.
2. Use only the company TIN and branch codes JomeInvoice has set up for you.
3. Ask JomeInvoice to add a new company or branch before sending files for it.

Empty and duplicate files

The file had no rows

What it means: The file was empty, so nothing was imported.

Steps to fix:

1. Confirm the file contains data rows (and a header row if your format uses one).
2. Re-export and send it again.

The same file was sent again

What it means: A file that is already being processed will be skipped so it is not imported twice.

Steps to fix:

1. Wait for the first run to finish.
2. To reprocess, use a new file name or the reprocess option if available.

If your error is not listed

1. Open the Import Log entry and select View to read the row-level reason.
2. Copy the exact message.
3. Contact JomeInvoice support with a sanitised sample file if the file looks correct but the error continues.

Related articles

• Bulk upload invoices
• Import log
• Why your invoice was rejected