Sage Invoice Import Errors
DocuClipper has no direct Sage invoice integration — it exports your extracted invoice data as Excel/CSV, which you then import into Sage. Here's how to fix the common Sage import errors.
Last updated
DocuClipper does not push invoices into Sage directly and does not produce a Sage-specific invoice import file. For invoices, DocuClipper extracts the fields (supplier, date, amounts, line items) and exports them as a generic Excel/CSV file. You then import that file into Sage using Sage's own import feature and column mapping.
Because Sage's importer enforces its own format, most import failures come down to the spreadsheet not matching what Sage expects — not a problem with DocuClipper's output. Work through the cases below.
Direct push integrations for invoices are QuickBooks Online, QuickBooks Desktop (IIF), and Xero. For bank statement transactions (not invoices), DocuClipper does export a ready-made Sage CSV — see Import Bank Statement Transactions into Sage.
"The file could not be imported" / file won't import
Usually a CSV-format problem. Export the invoices from DocuClipper, then save the spreadsheet as CSV (UTF-8) with the column headers in the very first row — no blank rows above them and no merged cells. If you edited the file in Excel, re-save cleanly, since Excel can reintroduce formatting Sage rejects.
Missing required columns
Sage rejects the whole file if a required field is absent. For Sage's Audit Trail Transactions import you typically need at minimum Type, Account Reference (Nominal Code), Date, and Net Amount. Add or map these columns before importing so Sage's header row is complete.
Wrong or blank transaction Type code
Sage needs an explicit Type on each row and won't infer it. Fill in the column before importing:
| Type code | Meaning |
|---|---|
PI | Purchase invoice |
SI | Sales invoice |
PC | Purchase credit note |
SC | Sales credit note |
Unrecognized supplier or nominal code
Sage does not auto-create suppliers or nominal codes on import the way Xero auto-creates contacts. Make sure the Account Reference and Nominal Code in your spreadsheet already exist in Sage, or those rows are flagged.
Date or amount format mismatch
Dates must match your Sage regional format (commonly DD/MM/YYYY), and amounts must be plain numbers — no currency symbols or thousands separators. Fix the column in the spreadsheet and re-import.
Duplicate invoice numbers
Sage flags repeated references. Confirm each invoice number is unique before re-importing.
When Sage reports failed rows
Sage lists the failed row and its error message. Correct that field in the spreadsheet and re-import only the corrected rows.
FAQs
Does DocuClipper import invoices straight into Sage?
No. There's no direct Sage invoice integration. DocuClipper exports your extracted invoices as Excel/CSV, and you import that file into Sage yourself. (Direct invoice push is available for QuickBooks Online, QuickBooks Desktop, and Xero.)
Why won't my CSV import into Sage?
Most often the file format or a mapping gap. Save the exported file as CSV (UTF-8) with headers in the first row, no blank rows, and no merged cells, and make sure every column Sage requires is present.
What Type code should I use for a supplier invoice?
Use PI for purchase (supplier) invoices, SI for sales invoices, PC for purchase credit notes, and SC for sales credit notes.
Does Sage create suppliers automatically on import?
No. Unlike Xero, Sage does not auto-create suppliers or nominal codes. They must already exist, or the row is rejected.
Can I upload PDF invoices directly to Sage?
No. Use DocuClipper to extract the invoice data and export a spreadsheet, then import that into Sage.