Invoice import errors

An invoice file is imported whole or not at all, so one problem stops the whole file. For problems with the file itself, see import file not accepted.

Invoice already imported

Invoice (number) was already imported for (carrier) on (date). Duplicate invoices are not imported twice.

Cause. An invoice with this number was already imported for this carrier. Forensik refuses it so the same charges are never audited or claimed twice. The same number from another carrier is fine.

Fix. Remove the rows for invoices already imported and upload again. For a reissued invoice, ask the carrier for a credit note or an adjustment invoice with its own number.

When to contact support. If the invoice was never imported, or was imported against the wrong carrier, contact support with the invoice number.

Charge codes not mapped

Map these charge codes before importing: (codes)

Cause. The file uses charge codes Forensik has not seen for this carrier, and they were not given a type. Forensik never guesses what a code means.

Fix. On the Charge codes step (for a PDF, the same screen), choose a standard type for every code listed, and the surcharge for accessorial codes. Then import again. Your answers are saved for this carrier.

When to contact support. If the codes listed are not in your file. If you do not know what a code means, ask the carrier.

Choose the carrier

Choose the carrier this invoice is from

Cause. No carrier was chosen. A CSV or Excel file always needs one. For a PDF you may see "Forensik could not tell which carrier this PDF is from" when it matches no layout Forensik reads.

Fix. Pick the carrier in the Carrier list and select Read file again.

When to contact support. If a Toll IPEC, Hunter Express or Bluestar PDF is still not recognised. Send us the PDF.

Charge code already mapped

Charge code (code) is already mapped to (type) for this carrier

Cause. The code already has a saved meaning for this carrier, usually because someone mapped it while you were importing. Forensik never changes a mapping, as that would change how past invoices read.

Fix. Go back, select Read file again so the saved mapping is used, and import.

When to contact support. If the saved mapping is wrong. It cannot be changed from the import screen.

PDF invoice not supported

Forensik does not read (carrier) PDF invoices yet. Import the carrier's CSV or Excel invoice export instead.

Cause. PDF invoices are read only for Toll IPEC, Hunter Express and Bluestar Global Logistics. "This PDF looks like a (carrier) invoice, not (carrier)" means the PDF is from a different carrier from the one you chose.

Fix. Import the carrier's CSV or Excel invoice export instead. If the PDF looks like another carrier's invoice, choose that carrier or leave Work it out from the PDF selected.

When to contact support. If a carrier only sends PDFs, so we know which layouts to add.

An invoice row is not valid

Row (number): invoice number is required

Cause. A row could not be read: no invoice number, a date that is not day first (21/09/2026), no charge amounts, an amount that is not dollars and cents, or a postcode that is not 4 digits.

Fix. Fix the rows listed, or the column mapping if every row fails the same way, and upload again.

When to contact support. If the rows look right in the file but still fail. Send the file and the messages.