2.4.3. Incoming Transactions

This module supports the following incoming payments:

1. Customer order payments

2. Supplier order credit notes

Normally, the module tries to auto-connect the transaction to the invoice by auto-creating the payment and the bank line. There are also some manual options, in case that is needed. More examples are presented below.

2.4.3.1. Customer order payments

Firstly, you need to have a customer order. A sample is shown in the next picture.

Customer order example in Dolibarr.

After this, you of course also need to create an invoice. The payment method must be Bank transfer and it must match the bank account you chose during configuration.

Customer invoice configured for bank transfer.

As soon as you create and verify the invoice, you will see the invoice reference number, label 1 in the next image. Then you can ask your customer to pay it.

Verified customer invoice with invoice reference.

As part of this tutorial, we will act as the customer. For this, we use the special tutorial/demo screen. Press the LibEuFin Connector top navigation bar button, label 1, then press the Tutorial button, label 2. After this, make sure to input all the correct data into the fields, label 3, and press Create fake incoming, label 4.

For the tutorial, I will showcase 2 possibilities:

1. The reference includes the correct number to match.

2. The reference includes an incorrect number, and the system cannot match it automatically.

Starting from the correct number and auto-matching: this is pretty much assured by using the IN2604-0001 string in the Ref. block. For testing, I am also adding a #2 payment, which is a second partial payment.

Creating fake incoming payments with a matching invoice reference.

Now that both payments are created, we can go to the Transactions page, label 1, and press Stage incoming fetch, label 2. As soon as you press the button, the page reloads. When it is done, notifications show up, label 3, notifying you how many objects are there. Check the next picture.

Incoming transaction fetch with automatically matched payments.

Now we can go and create the payment whose reference does not contain the invoice reference.

Creating a fake incoming payment without a matching invoice reference.

Run Stage incoming fetch again. As soon as the reload happens, the notifications show up, telling you that there are unmatched transactions. For this, press the link at label 2, and the transaction page will open.

Notification about unmatched incoming transactions.

A page like the next one will open. To match it, scroll down to the manual connection and select the object against which you want to make a link:

1. Invoice/credit note

2. Payment

3. Bank line

Now I select the invoice and press the save button, label 1 in the next picture. After pressing this button, links appear in the region labeled with 2.

Manual matching of an incoming transaction.

What we now want to verify is that this object has actually counted for the invoice amount. For this, return to the order invoice. There you can find payments, label 1 in the next picture, that were done by the customer, or in this case by us acting as the fake customer.

Customer invoice showing linked payments.

We can as well finish it by creating the final payment, in my case #4, and fetching it.

Creating the final incoming payment for the customer invoice.

After updating the customer payment, we can see that the order is paid. Afterwards, you can follow your internal business steps to verify the payment and finalize the order.

Customer invoice marked as paid after incoming transactions.

2.4.3.2. Supplier order credit note

This logic is added to support cases where the company that you bought something from is supposed to send you a refund by bank transfer. For this showcase, we use a supplier order from the Outgoing Transactions tutorial.

The logic is quite similar to the customer order invoice.

Firstly, you have to create a credit note for the supplier invoice.

Supplier invoice credit note in Dolibarr.

After this, similarly to the customer invoice, go to the tutorial page and create a payment for this credit note. Check the next picture for how to do it.

Creating a fake incoming payment for a supplier credit note.

Navigate to the Transactions page, label 1, and press the Stage incoming fetch button, label 2. After some time and a page reload, a note appears notifying you that the incoming transaction was auto-imported, label 3.

Auto-imported incoming transaction for supplier credit note.

After adding a couple more incoming payments, we can go to the credit note page and investigate that it was paid out. As previously, it is up to business rules to decide how to proceed forward and make the full resolution. As well as in the previous user example, you can make a manual match against the credit note, as previously we did for the customer invoice.

Supplier credit note after incoming payments.

2.4.3.3. Next step

As you have observed how incoming transactions work, you are really welcome to check the Outgoing Transactions tutorial. If you still have not installed the module, check Install and Configure.

For details on the standard Dolibarr objects used here, also check the official Dolibarr documentation for customer invoices and supplier invoices.