Table of Contents

Linc Bank Account Enhancements User Guide

Introduction

Welcome to the user guide for Linc Bank Account Enhancements, an extension app built for Microsoft Dynamics 365 Business Central by Linc Communications (Pty) Ltd. This guide will help you set up and use the various features of the app to enhance your banking operations.

Enhancements Included

  1. Customer Preferred Bank Accounts
  2. Vendor Bank Account Enhancements
  3. Bank Account Card Enhancements
  4. Restrictions on Payment Journals
  5. Bank Account Reconciliation Enhancements
  6. Payment Reconciliation Journal Enhancements
  7. FNB Bank Statement Integration
  8. Payment Journal Export

1. Customer Preferred Bank Accounts

Setup

  1. Table: CustPrefBankAccount_BANK_LINC

    • Navigate to the Customer Preferred Bank Accounts page to add or edit preferred bank accounts for customers.
    • Specify the Customer No., Currency Code, and Bank Account No..

  2. Page Extension: CustomerList_BANK_LINC

    • In the Customer List page, use the "Preferred Bank Accounts" action to manage preferred bank accounts for selected customers.

Usage

  • Reports: Preferred bank account details will automatically be included in the following reports:
    • Standard Sales Invoice
    • Sales Credit Memo
    • Sales Order Confirmation
    • Customer Statement
    • Pro-Forma Invoice
    • Sales Draft Invoice
    • Sales Quote

2. Vendor Bank Account Enhancements

Setup

  1. Page Extension: VendorBankAccList_BANK_LINC
    • Navigate to the Vendor Bank Account List page to add or edit bank branch names for vendor bank accounts.

Usage

  • Factbox: Vendor bank account information will be displayed in a factbox on the following pages:
    • Posted Purchase Invoices
    • Purchase Invoices
    • Purchase Invoice
    • Vendor Ledger Entries

3. Bank Account Card Enhancements

Setup

  1. Page Extension: BankAccountCard_BANK_LINC

    • Navigate to the Bank Account Card page to set up the following fields:
      • Direct Tfr. Batch Limit
      • Netcash Service Key

  2. Page Extension: GeneralLedgerSetup_BANK_LINC

    • In the General Ledger Setup page, enable the use of the Bank Branch List for selecting/capturing branch codes.

  3. Page Extension: BankExpImpSetup_BANK_LINC

    • In the Bank Export/Import Setup page, specify the bank export/import file type.

  4. Codeunits: Ensure the appropriate bank export format codeunit is configured for your banking institution on the Bank Export/Import Setup page (FNB, ABSA, Standard Bank, Nedbank, Capitec, Netcash, Investec). See Payment Journal Export below for the full list of formats and how each is run.

Usage

  • Bank Account Card: Use the Direct Tfr. Batch Limit and Netcash Service Key fields to manage direct transfer limits and Netcash services.
  • General Ledger Setup: Use the Bank Branch List for accurate branch code selection.
  • Bank Export/Import Setup: Specify the correct file type for bank export/import operations.

4. Restrictions on Payment Journals

Setup

  1. Codeunit: Subscriptions_BANK_LINC
    • Ensure your app subscription is active to enable all features.
    • Configure the CheckBankEFTLimit procedure to set direct transfer limits.

Usage

  • Payment Journals: The app will enforce restrictions on payment journals based on your subscription status and direct transfer limits. Unauthorized actions will be prevented, ensuring compliance and security.

5. Bank Account Reconciliation Enhancements

Setup

  1. Event Subscriber: BankAccReconciliationLine_OnAfterValidateEvent_AccountNo

    • Ensure the Gen. Prod. Posting Group and VAT Prod. Posting Group fields are correctly set up in the Bank Acc. Reconciliation Line table.

  2. Event Subscriber: BankAccReconciliationPost_OnPostPaymentApplicationsOnBeforeValidateApplyRequirements

    • Ensure the Gen. Prod. Posting Group and VAT Prod. Posting Group fields in the Gen. Journal Line table match those in the Bank Acc. Reconciliation Line table during the posting of payment applications.

Usage

  • Bank Account Reconciliation: The app will automatically update and validate the general and VAT product posting groups during the reconciliation process, ensuring accurate and up-to-date financial records.

6. Payment Reconciliation Journals Enhancements

Setup

  1. Page Extension: PaymentReconJnl_BANK_LINC

    • Added fields Gen. Prod. Posting Group and VAT Prod. Posting Group.

  2. Page Extension: TextToAccMapping_BANK_LINC

    • Added fields Gen. Prod. Posting Group, VAT Prod. Posting Group, Shortcut Dimension 1 Code and Shortcut Dimension 1 Code.
    • Set values for fields to be transferred to journal lines during mapping process.
    • Added use of wildcard character: Replace unwanted text in Mapping Text field with star (*). Text before and after character will be used during mapping process.

  3. Event Subscriber: AppliedPaymentEntry_OnUpdateParentBankAccReconLineOnBeforeBankAccReconLineModify

    • Ensure field values for Gen. Prod. Posting Group, VAT Prod. Posting Group, Shortcut Dimension 1 Code and Shortcut Dimension 1 Code are correctly set on journal lines.

  4. Event Subscriber: BankAccReconciliationLine_OnAfterRemoveAppliedPaymentEntries

    • Ensure field values for Gen. Prod. Posting Group, VAT Prod. Posting Group, Shortcut Dimension 1 Code and Shortcut Dimension 1 Code are correctly reset on journal lines.

  5. Event Subscriber: MatchBankPayments_OnFindTextMappingsOnBeforeCalculateStringNearness

    • A text-to-account mapping can now be linked to a bank account. Select the bank account on the text-to-account mapping and enable ApplyLinkedTxtToAcc_BANK_LINC on the bank account card.

Usage

  • Payment Reconciliation Journals: The app will automatically update and validate the Gen. Prod. Posting Group, VAT Prod. Posting Group, Shortcut Dimension 1 Code and Shortcut Dimension 1 Code from values on Text-To-Account mappings. Enabling the ApplyLinkedTxtToAcc_BANK_LINC on the bank account card and selecting a bank account on the text-to-account mappings will ensure only mappings related to the bank account are considered.

7. FNB Bank Statement Integration

This feature retrieves bank statement transactions directly from the FNB API and populates Bank Account Reconciliation lines, removing the need to import a statement file manually.

Setup

  1. Table & Page: BankIntegrationSetup_BANK_LINC

    • Open the Bank Integration Setup page (searchable under Administration) and complete the FNB group:
      • FNB Client ID – the client ID used to authenticate with the FNB API.
      • FNB Client Secret – the client secret used to authenticate with the FNB API (stored masked).
      • FNB API Base URL – the base URL for the FNB API (the OAuth token and transaction-history endpoints are appended automatically).

  2. Bank Account

    • Ensure the Bank Account No. on the relevant Bank Account card matches the account number registered with FNB, as it is used in the API request.

Usage

  1. Page Extension: BankAccRecon_BANK_LINC

    • On the Bank Acc. Reconciliation page, use the Import FNB Bank Statement action in the Bank menu.
    • The Statement Date must be set before running the action.

  2. Report: ImportBankRecon_BANK_LINC

    • The import request page prompts for a Start Date and End Date. By default these are set to the first day of the statement-date month and the statement date respectively, and can be adjusted.
    • The End Date must be on or after the Start Date.

  3. Codeunit: FNBImport_BANK_LINC

    • Authenticates against the FNB OAuth2 endpoint using the configured credentials, retrieves the transaction history for the selected date range, and creates a reconciliation line per transaction (transaction date, description, end-to-end reference and statement amount).
    • Each line is tagged with ReconImportID_BANK_LINC (the FNB entry ID) so re-running the import skips transactions that were already imported. A message reports how many new lines were created.

8. Payment Journal Export

The extension exports vendor payment journal lines into bank-specific payment files. Each supported bank has its own export format codeunit, and all of them read the same vendor bank account details, differing only in the file layout and how the export is triggered.

Supported export formats

Bank / Format Codeunit How it runs Output
FNB EFTExportFNB_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
ABSA EFTExportABSA_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
Standard Bank EFTExportSTD_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
Nedbank EFTExportNED_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
Capitec EFTExportCapitec_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
Netcash EFTExportNetcash_BANK_LINC Standard Export action (via Bank Export/Import Setup) Bank-specific file
Investec EFTExportInvestec_BANK_LINC Standard Export action (via Bank Export/Import Setup) BulkPayment.<yyyyMMdd>_Investec.csv
Moneycorp EFTExportMoneycorp_BANK_LINC Export to Excel action on the Payment Journal Excel .xlsx file

Shared formatting helpers (zero/blank padding, reference building, special-character stripping) are provided by EFTExportFormats_BANK_LINC. Every format processes only lines with an Account Type of Vendor, and uses the vendor's Preferred Bank Account Code to locate the Vendor Bank Account whose details are written to the file.

Common setup

  1. Vendor Bank Account Card – capture the banking details used by every format (account number, bank branch, account type). Format-specific fields are also set here (for example, the Moneycorp Account Type for Moneycorp, or the Netcash/Standard Bank notification fields).
  2. App subscription – the bank EFT export formats only run when the app subscription is active (see Restrictions on Payment Journals).

Running the standard bank formats (FNB, ABSA, Standard Bank, Nedbank, Capitec, Netcash, Investec)

  1. On the Bank Export/Import Setup page, set the Processing Codeunit to the relevant export codeunit from the table above and link it to the bank account's payment export format (see Bank Account Card Enhancements).

  2. From the Payment Journal, run the standard Export action. The configured codeunit generates the bank-specific payment file for the batch.

    For Investec, the export is a CSV file with a header record (1,2,...), one payment record per vendor line (debit account, beneficiary name, account number, branch code, currency, amount, action date, message and payment reference), and a footer record (99,...) totalling the record count, amount and sum of beneficiary account numbers. Only lines with Account Type of Vendor are exported, and any commas embedded in free-text fields (beneficiary name, message, reference) are stripped so they cannot break the column layout.

Running the Moneycorp export

  1. Table & Page: BankIntegrationSetup_BANK_LINC – open the Bank Integration Setup page (searchable under Administration) and complete the Moneycorp group:
    • Moneycorp Client ID – identifies your organisation to Moneycorp; written to the ClientID column of every exported row.
  2. Vendor Bank Account Card – set the Moneycorp Account Type field (Standard or Express); exported in the Type column.
  3. Page Extension: PaymentJournal_BANK_LINC – on the Payment Journal page, use the Export to Excel action. It runs EFTExportMoneycorp_BANK_LINC, which builds an .xlsx file (PaymentJournalExport_<yyyyMMdd>.xlsx) with one row per vendor payment line and the columns: ClientID, BankingDetailsID (preferred bank account code), Surname, FirstName (vendor bank account name), Currency (line currency, or the LCY code when blank), Amount, Type (Moneycorp account type), Payment Date, Client Reference (payment reference) and Created By. The file is offered for download as soon as the action completes.
  4. Report: PmtJnlExcelExport_BANK_LINC (alternative) – a processing-only report that produces the same Moneycorp Excel layout for a selected journal template and batch via the SetFilters procedure, for use in scheduling or automation where the page action is not suitable.

Conclusion

Linc Bank Account Enhancements is designed to streamline and enhance your banking operations within Microsoft Dynamics 365 Business Central. By following this guide, you can set up and use the app's features to improve efficiency, accuracy, and control over your financial transactions. Enjoy the benefits of a more powerful and user-friendly banking experience!