GoCardless Payment Functions in TAPP Finance

GoCardless payments in the current Microsoft Dynamics 365 Finance legal entity can be viewed from the list page below.

• Enterprise Subscription Automation (ESA) -> Inquires and Reports -> GoCardless -> GoCardless payments
• Enterprise Automation (EA) -> Inquires and Reports -> GoCardless -> GoCardless payments

For example, the screenshot below shows a sample of payments which have been synchronized from GoCardless to the GBSI company of Microsoft Dynamics 365 Finance.

Records without a linked action / invoice / customer indicate that these GoCardless payments were not generated from the current environment and/or legal entity for example: these might have been generated directly from the GoCardless portal and do not contain the necessary meta-data to link them to an existing record within Microsoft Dynamics 365 Finance. Such records will also have a ? icon at the end of the grid.

The first column in the grid is an icon indicating whether the payment was successful (green checkmark), is still pending (yellow triangle) or has failed (red cross).

There is a toggle above the grid to filter failed payments only as these typically require more attention than successful payments or pending payments.

The following function buttons are available at the top of the list page:

1. Payment reconciliation – This can be used to transfer payments from GoCardless to Microsoft Dynamics 365 Finance synchronously or in batch. For more information please visit this page.
2. Payment cancellation – This can be used to cancel a payment. GoCardless only allows payments in the Pending Submission stage to be cancelled.
3. View Linked Actions – View the actions linked to this payment. This function is more useful if the LISA Enterprise Product from Bluefort is licensed in conjunction with TAPP Finance but even without LISA Enterprise it could still provide some traceability information.
4. Retry Failed Payments – This button is only enabled if a payment has failed and it will send a retry request to GoCardless. There are some limitations from the GoCardless end regarding failed payments such as that the Success+ feature must be disabled and that a payment can only be re-tried up to a maximum of 3 times. The retry counts column shows how many times a retry has been done for this payment.
5. GoCardless events – For data storage and performance reasons, the Payment reconciliation process does not synchronize all the events from GoCardless. If, for any reason, the user would like to review all the events linked to this specific payment, this button will lead to a form where there is a function to synchronize these events.
6. GoCardless payment action transactions – When a particular payment is being used to cover multiple customer transactions, this button will open another list page which will be useful to trace which transactions are being paid within the scope of this payment. This button is only enabled when the the text <Multiple invoices> is displayed in the Invoice column.

The following screenshot shows the GoCardless events list page which filters GoCardless events by the caller payment. The Synchronize events button can be used to pull the events related to this payment from the GoCardless API.

The following screenshot shows the GoCardless payment action transactions list page. In this example the payment was created for a free text invoice and another open transaction resulting from a journal posting. Other sources for customer open transactions could be LISA subscription sales order invoices, standard sales order invoices, commerce/retail sales order invoices and project invoices.