Skip to main content

Invoices failing to load from Mosaic Provider Portal or Abacus

In this article, we explain why invoices may fail to load from Mosaic or Abacus and how to resolve error 515 in the import table.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

Erorr:
โ€‹'ERROR: 515 Cannot insert the value NULL into column 'VAR_REASON', table 'MosProd.dbo.VARIATIONS'; column does not allow nulls. INSERT fails. at line 991 in p_insert_invoices_pkg_p_create_invoices_record'

When Provider Portal sends invoices to Mosaic, it uses the E-invoices import. This import validates the provided data and logs any errors if validation fails. You should always run the E-invoice Import Report after an import to check for errors.


Youโ€™ll find the report in the report's repository under Mosaic Reports > Finance > E-Invoices. Look for the one named E-Invoice Import Report.


The report asks for the import ID, which you can find in the Failure 1 file. When logging a case with The Access Group, always include a copy of the Import Report.

Error

Reason

DUPLICATE_REF

Duplicate invoice reference found on the system for the supplier. This will happen when a batch has been re-sent from Provider Portal. Resending creditor batches from Provider Portal should only be necessary following advice from The Access Group.

NO_COMMITS

There are no real_commitments for this PO, i.e. PO is cancelled. This is caused when an Invoice has been verified in Provider Portal and was unpaid when that PO was cancelled in Mosaic. The invoice will no longer be for a current PO with commitments by the time it gets imported into Mosaic.

SOME_COMMITS

There are some commitments that have been paid but subsequently all elements cancelled for this PO.

MULTIPLE_PC

The interface will try determining the Payment Cycle to use based on the invoice dates, and Provider Portal Contract and this error means that more than one payment cycle type matches those criteria.

NO_PC

No payment cycle type attached to service, or services for the specified payment cycle type do not exist for this invoice.

CREDREF_MISSING

The invoice cannot be checked because the payee does not have a creditor reference entered in the system. This means that the invoice cannot be created because the auto check rule on the payment cycle is set to Always.

GEN_PAYMENT

An error has occurred trying to run procedure p_generate_payments. Log a new case with The Access Group.

NO_PAYMENT

No Payments were generated or included for the invoice that was created. This happens where the commitment for this purchase order and invoice dates has already been used on a previous invoice.

INVOICE_NOT_CREATED

The data passed validation checks, but the invoice was not successfully created by the interface. Please log a new case with The Access Group.

UNDEFINED

This error type is a catch all for exceptions in processing. The error message provided in the import report will give more details of what happened. Log a new case with The Access Group

If you've sent invoices from the Mosaic Provider Portal (Abacus) to Mosaic and can't see the invoices on a cycle to be matched, please raise a new online case and reference the title of this article.
โ€‹
To help us investigate, could you please provide the following information:

  • A copy of the Import Report.

  • The affected Payment Cycle ID(s).

  • What time the job from Mosaic Provider Portal (Abacus) would have started it's export (if known).

  • A service user ID or payee organisation ID that you expected to be pulled across but wasn't.

Did this answer your question?