The following information is logged:
- Sent e-invoices (OIOUBL and Peppol)
- Receipt reception (MLR/AR) via Nemhandel
- Collections via Direct debit service
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 |
| Balance Sheet | Balance Sheet can have the following Values:
|
| Type | Type can have the following Values:
|
| Document type | Document type can have the following Values:
|
| 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 |
|
| Sent to. |
|
| Merge payments |
|
| File type | The attached document can have the following types
|
| Debtor | Debtor account number |
| Name | Debtor name |
Nemhandel eDelivery error messages
Below is a Description of the typical Error codes {0}/texts you can get 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 | In addition to the Registration in the Nemhandel Register, the Received endpoint is also registered in another Peppol SMP. This causes problems if it is not done correctly. Nemhandel has written an Instruction note on how to handle this. |
| E-APS24005 | Receiver 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 first completed in connection with Processing of a Daily batch job after the activation date. This means that, in the worst case, it can take up to {0} 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 | Receiver endpoint is not registered in the Receiver’s system (eDelivery/AS4). The Documents 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
Send e-invoices sent via Nemhandel are saved in the Log and can be viewed via the ‘Show’ 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 pressing the Show button.
It should be noted that a Document of Type Receipt (Application Response) has been received regarding the Invoices sent. Application Response is a receipt document that provides feedback on the original Invoices sent. An Error in an Invoices can result in a negative Receipt being automatically returned to the Sender, stating the nature of the error. The Sender now has the opportunity to Changed and resend the Invoices. In this example, the Sender is notified that the Invoices cannot be Received because the Receiver is missing Setup. In this case, the Receiver is a Uniconta account and you need to activate the AutoBanking module.
Collections via Direct debit service
There is an extended Log function for Direct debit service. It can be used to follow the billing history – especially useful for larger subscription customers.
One Log transaction is inserted per Invoices that are charged via Direct debit service.
In Column Message, enter the following:
Payment date: Collection date
Invoice amount: the original Invoice amount
Remaining: only filled in if part payment has been made
Merge payments: only filled in if the Invoice is part of a Merge payment
The Text that the customer receives in their Received payment overview can be viewed by pressing the View button.
Below is an example of a Merge payments.
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).
