Invoice Importing - Failed to Validate

Christopher Hafer

Is anyone else having issues with importing invoices in the last few months?

With increasing frequency, we are experiencing issues where Blackbaud fails to recognize account numbers, gives strange errors like "account number must be unique", "invalid code table entry", etc. These errors are inconsistent, but like said, are increasing in frequency.

Today we have a mission critical payout that needs to happen, but all 70 of my invoices failed because of an "Invalid custome field type". For some reason, Blackbaud is reading the value as "0", but it's definitely not that in the import file.

I have an open case with Blackbaud right now (case # 020594366 for Blackbaud staff that are interested), but support can't seem to figure it out. I opened the ticket on 11/5/2025, but the issue has been going on for much longer.

Anyone else experiencing similar?

Patricia Nowak

Is the import file that you are using one that you built since import was added to web view or is it one that was created in database view? I would try building the import file from scratch with a new name. I remember we had trouble using import files that were previously created in database view.

Christopher Hafer

Hi Patricia,

No, my imports were all redone from scratch when the importing feature was added to Web View. All of my new import csv templates have also been used successfully since creating them.

For the "mission critical" issue we had last week, we figured out that something happened within the settings of my import template in NXT, so certain columns of my csv weren't recognized. I don't know how the settings were changed since nobody in our organization changed them, but we changed them back and everything worked.

The issue remains though. Inconsistently, but with increasing frequency, we have been receiving unexplainable errors that are just incorrect when we import invoices.