Error creating SharePoint folders, please forward to IT staff: {ex.Message}

A SharePoint error occurred while connecting to the server or creating the document folder.

ex = Exception returned from SharePoint.

SharePoint Error

Could not find Connector account associated with {apUDParams.EmailUser}. Please create account and retry.

The JPGAL Connector configuration entered in the user codes does not exist.

apUDParams = Auto AP Invoice process parameters.

Email Ingest Error

Found multiple Connector accounts associated with {apUDParams.EmailUser}. Please delete or change the account name of all but one and retry.

The JPGAL Connector configuration entered in the user codes has multiple matches.

apUDParams = Auto AP Invoice process parameters.

Email Ingest Error

Error getting Connector access for ({apUDParams.EmailUser}): {clientError}

An error has been returned by the server when connecting to the email server.

apUDParams = Auto AP Invoice process parameters.

clientError = Error returned by the server.

Email Ingest Error

Cannot find email inbox

Email account does not contain a valid inbox folder.

N/A

Email Ingest Error

Cannot find email Archive

Email account does not contain a valid archive folder.

N/A

Email Ingest Error

Error creating mail folder ({newFolderName}): {ex.Message}

An error has occurred creating a mail folder for use in the email ingest process.

newFolderName = folder to be created.

ex.Message = error returned by server.

Email Ingest Error

could not find sender

The email object being ingested does not contain a valid sender.

N/A

Email Ingest Error

could not find sender email address

The email object being ingested does not contain a valid sender email address.

N/A

Email Ingest Error

Cannot determine file type of attachment

Process does not recognise the file type of an email attachment being ingested.

N/A

Email Ingest Error

Attachment ({attachment.Name}) is too large ({attachmentSizeKB}KB)

The email attachment being ingested is bigger than the configured max ingest size.

attachment.Name = file name of attachment.

attachmentSizeKB = size of attachment.

Email Ingest Error

Error - attachment content is null

The email attachment being ingested contains no data.

N/A

Email Ingest Error

INVOICE HEADER CREATED - Manually complete invoice (Misc Invoice)

The Kofax data has been marked as a Misc Invoice, so the process has created an invoice header matching the ingested Kofax data.

N/A

AP Default

INVOICE CREATED AND SUBMITTED FOR POSTING

The process has found a found a collection of receipt lines that match the ingested total and has created an invoice with these lines and submitted it for posting. However, the process has not found a posted invoice yet.

N/A

N/A

INVOICE CREATED - Manually post invoice

The process has found a found a collection of receipt lines that match the ingested total and has created an invoice with these lines. However, automated posting has been disabled, so the user needs to post the created invoice.

N/A

AP Default

Document type not found - please set the Document type to either AP Invoice/Misc AP Invoice/Credit Note and reprocess

The document type field does not match any of the valid values.

N/A

AP Default

This has been marked as a credit note. Please manually create the credit note and mark it as complete.

The Kofax data has been marked as a credit note. The current process does not handle credit note creation.

N/A

AP Default

Error updating ud104, please contact IT staff: {objectPrint(ex)}

Epicor has returned an error when trying to update the review screen record. This suggests a technical problem and is not part of normal processing.

objectPrint(ex) = a readable version of the exception returned by Epicor.

UD104 Error

Supplier reference ({ipHeader.VendorRef}) not found. Please create a cross reference for the desired supplier and reprocess.

The supplier reference from the ingested Kofax data, does not match any supplier cross reference in Epicor. This should be extremely rare as the supplier reference is validated in Kofax.

ipHeader.VendorRef = the vendor reference stored in the review record.

AP Default

Cross reference ({ipHeader.VendorRef}) found but supplier not found. Please contact IT support

The supplier reference record exists but is not properly linked to a supplier. This suggests a technical problem and is not part of normal processing.

ipHeader.VendorRef = the vendor reference stored in the review record.

AP Default

Invoice Date ({ipHeader.UDInvoiceDate}) could not be parsed as a date so Process Date ({ipHeader.ImportDate}) was used instead

The unparsed invoice date could not be converted to a string. So, the process will use the ingest date as the invoice date instead.

ipHeader.UDInvoiceDate = unparsed invoice date from the Kofax data.

ipHeader.ImportDate = the date the data was ingested from Kofax.

N/A

Error calculating due date: {ex.Message}

Epicor returned an error during due date calculation. This suggests a technical problem and is not part of normal processing.

ex.Message = the message portion of the exception returned by Epicor.

AP Default

An invoice with this vendor and invoice num already exists. If this invoice still needs to be created, please manually enter this invoice and mark it as complete.

A posted AP Invoice with the same VendorNum and InvoiceNum from the Kofax data already exists. So, the process cannot create an invoice based on this data and assumes it was ingested by mistake.

N/A

AP Default

This is a duplicate of a complete record and therefore cannot be processed. If this invoice still needs to be created, please manually enter this invoice and mark it as complete.

A complete review screen record with the same VendorNum and InvoiceNum from the Kofax data already exists. So, the process assumes it was ingested by mistake.

N/A

AP Default

REPLACED - A NEWLY IMPORTED INVOICE RECORD HAS REPLACED THIS ONE - PLEASE DO NOT MODIFY THIS RECORD

If the VendorNum and InvoiceNum ingested from Kofax already exists on an incomplete review record, this message and the replaced checkbox is set on the pre-existing record. Future processing should be done on the newer record.

N/A

N/A

Replaced old dashboard record

If the VendorNum and InvoiceNum ingested from Kofax already exists on an incomplete review record, this message is set on the new record. Future processing should be done on this record.

N/A

N/A

Could not attach pdf to invoice header: {ex.Message}

Epicor returned an error when trying to attach the PDF to a created invoice header. This suggests a technical problem and is not part of normal processing.

ex.Message = the message portion of the exception returned by Epicor.

AP Default

Error Creating Invoice Head: {ex.Message}

Epicor returned an error when attaching the PDF to a created invoice header. This suggests a technical problem and is not part of normal processing.

ex.Message = the message portion of the exception returned by Epicor.

AP Default

Misc AP Invoice - Header created. Please manually match lines and post invoice.

The Kofax data has been marked as a Misc Invoice, so the process has created an invoice header matching the ingested Kofax data.

N/A

AP Default

Created invoice could not be found (VendorNum: {ipHeader.VendorNum} InvoiceNum: {ipHeader.InvoiceRef}). Please contact IT staff.

Once the process has created an invoice header it searches for the created record for future changes and to confirm it was created. This error is returned if it cannot find the header in the database.

ipHeader.VendorNum = the VendorNum on the review record, ingested from Kofax.

ipHeader.InvoiceRef = the InvoiceNum on the review record, ingested from Kofax.

AP Default

Supplier marked for hold review.

The supplier has been marked with a "HOLD" attribute. Therefore, after creation it has been placed on hold for a user to review.

N/A

AP Default

INVOICE HEADER CREATED BUT HELD -

The invoice header has been successfully created but a problem was found during the after-creation checks. The invoice header has been placed on hold for a user to review.

N/A

AP Default

Error during after creation checks. Please review and post.

Epicor returned an error during the after-creation checks. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

Error creating new group {newGroupID}: {ex.Message}

While creating an invoice or moving it to a user managed invoice group, the process will create invoice groups. This is returned when an Epicor returned an error during this. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

No PONum provided - Email sent to supplier

The Kofax data has been marked as an AP Invoice but the PONum field is empty or 0. Therefore an email has been sent to the supplier. This notifies the user of that action.

N/A

AP Default

Supplier on PO does not match supplier on Invoice. Please change one and reprocess this record

The Kofax data contains a valid PONum but the purchase order contains a different supplier than the Kofax data.

N/A

AP Default

PO is {status}. Please resolve this and reprocess this record.

The PONum ingested in the Kofax data is valid but that purchase order has not been approved.

status = the current status of the PO, it could be: Unapproved, Rejected or Pending.

AP Default

PO {ipHeader.PONum} exists but has not been receipted, please receipt this PO.

The PONum ingested in the Kofax data is valid but no receipts are associated with it.

ipHeader.PONum = the PONum on the review record, ingested from Kofax.

AP Default

Receipt (PONum: {ipHeader.PONum}) does not contain any uninvoiced lines. Please add lines and reprocess or manually process invoice.

The PONum ingested in the Kofax data is valid and associated with at least one receipt but there are no receipt line associated with it that have not already been invoiced fully.

ipHeader.PONum = the PONum on the review record, ingested from Kofax.

AP Default

Receipt (PONum: {ipHeader.PONum}) does not contain any valid receipt lines. Please add lines and reprocess or manually process invoice.

The PONum ingested in the Kofax data is valid and associated with at least one receipt but there are no receipt line associated with it that have not already been invoiced fully.

ipHeader.PONum = the PONum on the review record, ingested from Kofax.

AP Default

PO ({ipHeader.PONum}) does not exist. Please add a valid PONum and reprocess this record.

The PONum ingested in the Kofax data does not exist as a purchase order in the database.

ipHeader.PONum = the PONum on the review record, ingested from Kofax.

AP Default

Error finding matching receipt lines: {ex.Message}

This encapsulates all errors returned by the matching algorithm while it is building the data for matching and performing the search for a match

ex.Message = the message portion of the exception returned by the matching algorithm.

AP Default

No uninvoiced receipts found

This error occurs when the matching algorithm is building the list of receipts for matching but can't find any uninvoiced receipts. This should be rare as it is the second time the check is performed.

N/A

AP Default

No remaining receipt lines after filtering

After building a raw list of receipt lines for matching it filters the date down to only valid choices (e.g. matches the PONum provided and standalone value is less than the upper limit of matching target).

N/A

AP Default

A combination of receipts cannot be found if zero value receipt lines exist

A receipt line with a total value of zero exists in the list of valid lines for matching, there is no way for the algorithm to determine if this line should be receipted. Therefore it throws this error.

N/A

AP Default

Unexpected error occurred during line match up: mAPUninvoicedRcptLines null. Please contact IT staff.

An errored occurred while the matching algorithm was running. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

Multiple single lines can match within variance total.

There are multiple single line values that are valid choices to match with.

For example:

N/A

AP Default

Too many possible receipts ({APUninvoicedRcptLinesList.Count}>{apUDParams.MaxSampleSize}), please manually process this invoice.

The number of candidate receipt lines is greater than the configured maximum.

APUninvoicedRcptLinesList.Count = the number of candidate receipt lines.

apUDParams.MaxSampleSize = the configured maximum number of receipt lines that can be used as candidates simultaneously.

AP Default

Down Limit: {_p.DownLimit} is bigger than set sum {setsum}, no solutions exists

The total value of all the candidate receipt lines added together is less than the bottom of the valid total range.

_p.DownLimit = the bottom of the valid total range.

setsum = the total value of all candidate receipt lines added together.

AP Default

Recursion algorithm timed out.

The matching algorithm took longer than allowed.

N/A

AP Default

No match could be found

The matching algorithm searched all possible candidates but could not find a combination of receipts that total was within the valid range.

N/A

AP Default

More than one match can be found

The matching algorithm searched all possible candidates and found multiple combinations of receipts that total was within the valid range. However, it has no way to determine which is the correct combination.

N/A

AP Default

Cannot parse matching results.

Process could not parse the results returned by the matching algorithm. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

No valid receipt lines found

The receipt lines returned by the matching algorithm are invalid. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

INVOICE HEADER CREATED - Matching Error. Please manually complete invoice ({opError})

The matching algorithm has returned an error but the process has created an invoice header to work from.

opError = error returned by the matching algorithm.

AP Default

Gross target total ({ipHeader.GrossVendorAmt}) is greater than the created total ({ipHeader.MatchedAmt}) but within variance.

The target total is greater than the created total but still within variance.

ipHeader.GrossVendorAmt= ingested target total, including tax.

ipHeader.MatchedAmt = total value of created invoice.

AP Default

Gross target total ({ipHeader.GrossVendorAmt}) is less than the created total ({ipHeader.MatchedAmt}) but within variance.

The target total is less than the created total but still within variance.

ipHeader.GrossVendorAmt= ingested target total, including tax.

ipHeader.MatchedAmt = total value of created invoice.

AP Default

Created total ({ipHeader.GrossVendorAmt}) is above variance limit ({upLimit}). Please review tax configuration and post.

When a match has been found an invoice is created with the matched receipt lines.

The process then calculates a upLimit and downLimit based on the total of the created invoice and configured tolerance levels. This upLimit and downLimit create a new valid range. The process then checks if the ingested gross total is in this range, if it is above that range it returns this error.

The error points towards the tax configuration, as the automated process created the lines without tax, allowing Epicor's tax engine to calculate the tax. So, a discrepancy in the tax configuration is a likely cause for the variance.

For example:

ipHeader.GrossVendorAmt = ingested target total, including tax.

upLimit = the top of the valid total value range.

AP Default

Invoice total ({ipHeader.GrossVendorAmt}) is below variance limit ({downLimit}). Please review tax configuration and post.

When a match has been found an invoice is created with the matched receipt lines.

The process then calculates a upLimit and downLimit based on the total of the created invoice and configured tolerance levels. This upLimit and downLimit create a new valid range. The process then checks if the ingested gross total is in this range, if it is below that range it returns this error.

The error points towards the tax configuration, as the automated process created the lines without tax, allowing Epicor's tax engine to calculate the tax. So, a discrepancy in the tax configuration is a likely cause for the variance.

For example:

pHeader.GrossVendorAmt = ingested target total, including tax.

downLimit = the bottom of the valid total value range

AP Default

Error filling variance gap, please manually complete invoice

If the created total value of an invoice does not exactly match the ingested total but is within variance, the process modifies one of the lines to make the total of the created invoice match the ingested total.

This message is returned when Epicor returns an error during this transaction. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

Supplier marked for review. Please review and post.

The supplier has been marked with a "HOLD" attribute. Therefore, the invoice has been placed on hold for a user to review after creation.

N/A

AP Default

CIS Supplier. Please review and post.

The supplier has been marked as a CIS supplier. Therefore, the invoice has been placed on hold for a user to review after creation.

N/A

AP Default

Error during after invoice creation checks: {blex.Message}

The invoice header has been successfully created but Epicor returned an error during the after-creation checks. The invoice header has been placed on hold for a user to review.

blex.Message = the message attached to the error returned by Epicor.

AP Default

APInvGrp does not exist

The process could not find the invoice group to be posted. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

No Invoices in the APInvGrp

The process could not find any invoices in the invoice group to be posted. This suggests a technical problem and is not part of normal processing.

N/A

AP Default

Error during submitting for posting: {ex.Message}

Epicor has returned an error when trying to post the invoice group. This suggests a technical problem and is not part of normal processing.

ex.Message = the message attached to the error returned by Epicor.

AP Default

Failed to move group: {ex.Message}

Epicor has returned an error when trying to move the invoice to a group for user processing. This suggests a technical problem and is not part of normal processing.

ex.Message = the message attached to the error returned by Epicor.

AP Default

Invoice does not contain PONum. It has been {apUDParams.ReminderGap} days since the final reminder was sent to the supplier. Please manually process invoice.

The number of configured reminders have been sent, so the record has been reassigned to the AP team.

apUDParams.ReminderGap = the configured gap between reminders in days.

AP Default

No PONum provided. Another reminder sent to supplier.

The supplier has not sent a valid PONum and the reminder gap has elapsed again but not reached the limit in number of reminders sent. this message is just for record keeping, no email is sent.

N/A

N/A

Error checking records for No PO follow ups: {ex.Message}

Epicor has returned an error when checking for supplier reminders. This suggests a technical problem and is not part of normal processing.

N/A

Supplier Reminder Error

{Calculated Supplier Email}

This is the email reminder sent to the supplier.

N/A

Supplier

COMPLETE - FOUND POSTED INVOICE

-

N/A

N/A

Error checking records for automatic completion, please forward to IT staff: {ex.Message}

Epicor has returned an error when marking review records as complete. This suggests a technical problem and is not part of normal processing.

ex.Message = the message attached to the error returned by Epicor.

Automatic Completion Error

Error adding dates to records manually marked as complete, please forward to IT staff: {ex.Message}

Epicor has returned an error when adding completion dates to manually completed records. This suggests a technical problem and is not part of normal processing.

ex.Message = the message attached to the error returned by Epicor.

Manually Complete Date Error

UNKNOWN EXTERNAL ERROR - Record has been idle for 2 days. Please review created record/invoice and manually process

An invoice that was submitted to for posting has not been posted for 2 days, so it has been reassigned to the AP team.

N/A

AP Default

Error reassigning open buyer errors, please forward to IT staff: {ex.Message}

Epicor has returned an error when checking for incomplete records. This suggests a technical problem and is not part of normal processing.

ex.Message = the message attached to the error returned by Epicor.

Reassigning Incomplete Error

Another reminder sent to buyer.

The buyer has not resolved the error with the PO and the reminder gap has elapsed again but not reached the limit in number of reminders sent. This message is just for record keeping, no email is sent.

N/A

N/A

It has been {apUDParams.ReminderGap} days since the final buyer reminder. Please manually resolve error.

The number of configured reminders have been sent, so the record has been reassigned to the AP team.

apUDParams.ReminderGap = the configured gap between reminders in days.

AP Default

Error checking records for buyer follow ups, please forward to IT staff: {ex.Message}

Epicor has returned an error when checking for buyer reminders. This suggests a technical problem and is not part of normal processing.

N/A

Buyer Reminder Error

{Calculated Buyer Email} + {Review screen record message}

This is the email reminder sent to the buyer.

N/A

Buyer