Log

The following information is logged:

• Sent e-invoices (OIOUBL and Peppol)
• Receiving receipts (MLR/AR) via Nemhandel
• Direct debits via Betalingsservice

The log can be accessed from three places:

• Invoice journal/log
• Debtor/Log
• Main menu under Accounts Receivable/Maintenance/Log - total list of all documents sent from Uniconta

The fields in the Log overview

Field name	Field Description
Time	Date and time of sending
Status	Status can have the following values: Sent - document has been sent and received Error - sending failed Attempt - the document could not be delivered and is retried
Type	Type can have the following values: OIOUBL (sent via Nemhandel) Peppol Direct debit
Document type	Document type can have the following values: Invoice Credit note Receipt
Document number	Invoice number
User ID	User who sent the document
Error messages	Error messages and other notifications (Nemhandel eDelivery error messages are described further down in the text)
Server	OIOUBL/Peppol - web service sent to Direct debit - not used
Sent to	OIOUBL/Peppol - endpoint in the form of CVR number or GLN number Direct debit - not used
Collective payments	OIOUBL/Peppol - not used Betalingsservice - Id for a collective payment
File type	The attached document can have the following types OIOUBL/Peppol - XML Payment service - TXT
Debtor	Debtor account number
Name	Debtor name

Nemhandel eDelivery error messages

Below is a description of the typical error codes/texts you may receive when sending e-invoices via Nemhandel eDelivery. The errors below are due to problems with the recipient. You should therefore contact the recipient and point out the problem. List of typical error codes caused by problems at the receiver

Error code/Error text	Error description
E-APS24003	Problems communicating with the receiving endpoint.
E-APS24004	The recipient endpoint is registered in another Peppol SMP in addition to the registration in the Nemhandel register. This causes problems if it is not done correctly. Nemhandel has written a guide on how to handle this.
E-APS24005	The recipient endpoint has not been registered in SML. This is typically because the registration in NHR has an activation date in the future. In this situation, the SML registrations are only completed when a daily batch job is run after the activation date. This means that in the worst case, it can take up to 24 hours after the activation date before the SML registration is completed.
E-APS24006	Used if an endpoint was not found during SMP lookup for that recipient and document type
E-APR24123	The recipient endpoint is not registered in the recipient's system (eDelivery/AS4). The document has therefore been rejected.
A task was canceled	Problems communicating with the receiving endpoint. This is typically caused by an httpclient timeout

  List of typical error codes caused by problems at the sender

Error code/Error text	Error description
E-APS24007	Used if the sender is not properly registered to receive asynchronous responses MLR (Message Level Response) or AR (Application Response)

 

e-invoice/receipt

e-invoices sent via Nemhandel are saved in the log and can be viewed via the 'View' button. There will be an attached document if a value is set in the File type field. In the example above, an e-invoice has been sent and can be viewed by clicking the View button. It should be noted that an Application Response document has been received regarding the sent invoice. Application Response is a receipt document that provides feedback on the original sent e-invoice. An error in an invoice can result in a negative receipt being automatically returned to the sender, stating what the error is. The sender now has the option to change and resend the invoice. In this example, the sender is notified that the invoice cannot be received because the recipient lacks settings. In this case, the recipient is a Uniconta accounting system and you need to activate the module AutoBanking.  

Direct debits via Betalingsservice

There is an extended log function for Betalingsservice. It can be used to follow the charging history - especially useful for larger subscription customers. A log transaction is inserted per invoice that is charged via Betalingsservice. In the Message column, enter the following: Payment date: Collection date Invoice amount: the original Invoice amount Remaining: only filled in if partial payment has been made Collective payment: only filled in if the invoice is part of a collective payment The text that the customer receives in their Payment overview can be viewed by pressing the View button. Below is an example of a Collective payment. In the example above, two invoices are combined. In the 'Collective payments' column, a value will appear if a collective payment has been made (the field can then be used for filtering).