Added Amount field to Payment Batch page so that the user could easily see the total amount of Payment Entries contained within the Payment Batch.
Increased the number of Payout Items requested when calling the GoCardless api to reduce unnecessary api requests.
The New Mandate Entry Wizard allowed the user to specify the Given Name and Family Name, but the values were taken from the Contact instead.
The next release will utilise the new "Email Scenarios" functionality that is now available in Business Central.
Prevent auto posting of Payouts if a Currency Triangulation Entry has been created. Should a posting require a Triangulation Difference journal line, we decided that it would be better to let the user know, and so the user will be forced to use the "Create Journal Only" switch when posting the payout.
Add "Payment Description" field to the Payment Entry. Rather than taking the Payment Decription value from the mandate itself, we now default the value through from the Mandate but allow it to be changed before submission to GoCardless. Setting the value is mandatory. We received reports that the emails being sent from GoCardless had an empty space where the payment description should have gone. This was caused by mandates that were created outside of Astral GoCardless and imported using the "Find Missing Mandates" functionality. After importing a mandate, the user should manually add a "Mandate Description" so the value will default through to the new field on the Payment Entry.
Enable getting more then 50 Mandates when using Find Missing Mandates. There was a GoCardless api call limit of 50 records. We now page through all Mandates when trying to find ones that are not in Astral GoCardless.
The core extension now targets the version 17 release of Business Central.
There was an issue where the Payout items were not completely populating.
Added Dataverse (CDS) integration, enabling integration with Dynamics 365 for Sales.
Added automatic import of mandates that are created outside of Astral GoCardless (e.g. via the GoCardless api or via the GoCardless portal), triggered when the Metadata specifies the Business Central Customer No.
The Business Central user can now create the mandate themselves if they know the sort code and account number, without the need for emailing a PayLink. A new Wizard has been added to simplify the process of chosing how the mandate should be created (manually or via a PayLink).
A "Mark All Entries As Processed" action was added to the Notifications list. If extensive use is made of the GoCardless portal, there will be many Notifications that will not be processed, as they relate to data that Astral GoCardless doe not know about. Some users found it time intensive to clear off all the entries.
There was an issue when importing mandates. A filtering issue when trying to display a list of potential companies to map against has been resolved.
Some payouts contain Payout Items that have a zero amount. These caused an issue when trying to transfer to the Payout Journal.
Some Payouts cannot be transferred to a Cash Receipt Journal. For example, some Payouts have no Payout Items, and therefore no Payout Date. We added the ability to "Set As Posted", so the entry dissappears from the Role Centre Tile.
Resolved an issue where in some scenarios a GoCardless Payout journal would not post due to the GoCardless Creditor Payout Currency Code not being specified in the GoCardless account.
Resolved a minor issue with the Application Setup Wizard which surfaced when Merchants weren't set up for International Payments with GoCardless.
Resolved an issue when importing missing mandates from the GoCardless Merchant account. If more than one missing mandate is found, it tried to use the same Mandate No. and raised an error.
The initial release including mandate creation, payment batch creation, refunds and subscriptions. It doesn't inlcude Instalment Schedules, but this will follow shortly.
It includes Success+, which is great for reducing failed Direct Debit charges and also includes Borderless Payments, which is why Astral 365 were so keen to build this extension.