Log Duplicate Invoice Errors During Polaris Invoice Creation Request Add an error message to the EDI logs wh
Add an error message to the EDI logs when an invoice fails to load into the Polaris invoice tables due to a duplicate invoice number already existing in Polaris.
This is becoming a bigger issue as Ingram has changed their invoice number scheme and they are using the same numbers as Midwest has used. There is no way to delete or edit past Midwest invoices, so this is a critical issue for figuring out why invoices aren't loading.
Current Issue
- If a duplicate is detected during the Polaris invoice creation step, no error is recorded.
- This results in missing invoices with no visible explanation in the EDI logs.
Requested Enhancement
- When Polaris cannot create an invoice because the invoice number already exists in its invoice tables, log a clear error in the EDI logs.
- Include the invoice number and file information so staff can identify which invoice failed and why.
Benefit
Provides visibility into second-stage duplicate failures, reduces troubleshooting time, and prevents silent invoice omissions during EDI processing.
Reference Ticket #08253072
Wes Osborn
shared this idea
-
Wes Osborn
commented
Yeah, I was surprised too Lynn.
At least on the Sierra side it both warns and allows you to continue with the import. That way you don't have to spend a couple of weeks in back and forth with the vendor asking them what the problem is and why their file format is borked only to find out it was your ILS all along.
-
Lynn Reynish
commented
I have to say that I find this to be a bug - not an enhancement. Silent errors are a programming fault / oversight that needs to be fixed not some new feature that customers should have to request.
If you were asking for greater logging for reporting purposes or for an audit trail then I could understand seeing it as an enhancement, but this is in no way the same thing.
-
Anne Barnard
commented
We've had Midwest for a long time. We're just starting to use Ingram so I hope we don't run into this before it is corrected.
-
Wes Osborn
commented
Even better would be the system not allowing an invoice from 10 years ago and another vendor to be treated as a "duplicate" for the incoming invoice.