.png){kind=logo}
Detailed Description of Bankfeed Setup
- 24 May 2024
- Print
- PDF
Detailed Description of Bankfeed Setup
- Updated on 24 May 2024
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
As you already know almost all set up is done using Assisted setup, but in case you need more advanced set up, or to change something in this manual part you will find detailed description of Bankfeed' s set up pages.
Integration Setup (Bankfeed)
In this setup page basic product settings are stored.
Description of the most important fields:
| Field | Description |
|---|---|
| Fastab Journals. Setup in this fastab is related to journal lines. | |
| Use Payment Reconc.Journal | Select if you want statement to be imported to Payment Reconciliation Journal instead of Payment journal. Importing bank statement to Payment reconciliation journal Bankfeed does not apply any recognition or application. It is done by standard BC functionality. |
| Journal templates name | Specifies the payment journal template to which transactions should be imported. |
| Not Recognized Pmt. Acc. Type | Specifies the type of account which must be assigned in rows where the customer is not identified. Default value is G/L Account. |
| Not Recognized Pmt. Acc. No. | Specifies the account number to be assigned to the line where the customer is not identified. It is also possible to leave the field blank if you want to see an empty value in the Account No. field in unrecognized rows. Default value is Blank. |
| Include Vendor Payments | Tick this box if you want to import vendor entries into the payment journal when importing bank statements. If the box is unchecked, only customer payments, transfers between bank accounts, bank commissions will be imported, but rows where the account type is Vendor will be skipped. |
| Description in Journal from | Select what you want to fill in journal field Description. Available values: Default (account name) - it is used the standard BC journal field Description. The account name is filled in according to the assigned Account No. in the journal line. For example, if you assign Customer No. P0003, the description will contain its name. Payer Information - in this case the information from the Payer Information field will be filled in the Description. If you change the Account No. in journal line, the Description will remain the same. Message to Recipient - in this case, the information from the Message to Recipient field will be filled in the Description. If you change the Account No. in the line, the Description will remain the same. |
| Gen.Jnl. – E2E ID Field No. | Specify the field number in the general journal to which the information from the EndtoEnd ID field should be uploaded. Is used only together with the ECOM or other products. |
| Cust. Ledger Entry – E2E ID Field No. | Specify the field number in the customer ‘s ledger entries where the value of the EndToEnd ID field should be stored after posting. Is used only together with the ECOM or other products. |
| Fastab Parsing. Setup in this related to statement lines parsing. | |
| Include Pending Operations | Specifies whether statement lines should be created for pending operations, such as Credit card payment and etc. It is recommended not to include by default, as it may result duplicated transactions. |
| Operation Date Source | Specify which date from bank transaction should be filled to Statement lines "Book date" or "Value date". Default value is Booking. |
| Fastab Bank Charges. This setup is used only in cases when bank charges can be identified by different tags (FMLY and SUBFMLY) in statement lines. | |
| Bank Charges Transaction SUBFMLY Code | Specify statement lines field SUBFMLY value. Transactions identified by this value will be redirected to the G/L account specified in the field "Bank Charges Account No. “. |
| Bank Charges Account No. | Indicate the G/L account to which the bank charges will be directed (indicated in field Bank Charges Transaction SUBFMLY Code. |
| Bank Charges Transaction Charges FMLY Code (2) | Specify statement lines field FMLY value. Transactions identified by this value will be redirected to the G/L account specified in the field "Bank Charges Account No.(2) “. |
| Bank Charges Transaction SUBFMLY Code (2) | Specify statement lines field SUBFMLY value. Transactions identified by this value will be redirected to the G/L account specified in the field "Bank Charges Account No. (2) “. |
| Bank Charges Account No.(2) | Indicate the G/L account to which the bank charges will be directed (indicated in fields Bank Charges Transaction Charges FMLY Code (2) and Bank Charges Transaction SUBFMLY Code (2)). |
| Bank Charges Transaction Charges FMLY Code (3) | Specify statement lines field FMLY value. Transactions identified by this value will be redirected to the G/L account specified in the field "Bank Charges Account No.(3) “. |
| Bank Charges Transaction SUBFMLY Code (3) | Specify statement lines field SUBFMLY value. Transactions identified by this value will be redirected to the G/L account specified in the field "Bank Charges Account No. (3) “. |
| Bank Charges Account No.(3) | Indicate the G/L account to which the bank charges will be directed (indicated in fields Bank Charges Transaction Charges FMLY Code (3) and Bank Charges Transaction SUBFMLY Code (3)). |
| Fastab Other Functionality. | |
| Create Customer Bank Accounts | Select if you want to create new customer bank account cards while recognizing customers if they do not yet exist in BC. |
| Create Vendor Bank Accounts | Select if you want to create new vendor bank account cards while recognizing vendors if they do not yet exist in BC. |
| Max. No of days between payment initiation and finalization | Number of days tolerated between payment made in BC and the same transaction in Bank statement. Default value is 5days. |
| Customer – registration No. field No. | This field specifies which field in the system is used for the Customer ‘s company code. It can be standart BC field or custom field value. |
| Vendor – registration No. field No. | This field indicates which field is used in the system for the Vendor ‘s company code. It can be standart BC field or custom field value. |
| Change Cust.Adv.Post.Group | Select if you want to change customer posting group in journal lines which are not applied. |
| Cust.Advance Posting group | Select Customer posting group to which not posted lines should be changed. |
| Change Vend.Adv.Post.Group | Select if you want to change vendor posting group in journal lines which are not applied. |
| Vend.Advance Posting group | Select Vendor posting group to which not posted lines should be changed. |
| Fastab Integration. | |
| Isolated Storage API key | In this field, we specify the API key, through which BC will connect directly and receive bank statements. |
| Fastab No. Series. | |
| Exceeding Document Nos. | In this field default No. series for exceeding maximum length Transaction ID is set. If the Transaction ID is too long, this no series will be used. |
| Bank Account Nos. | If it is selected Create Customer Bank Accounts and/or Create vendor Bank Accounts, new created bank account cards fill be using this number series. It can be changed if needed. |
How to setup automatic import of bank statements to BC?
The import of bank statements to the system can be done manually, but much more relevant and useful is the automatic import of files to the system, which is implemented by using job queues.
For uploading and processing files in BC, there is a function Process Statement Batches (Bankfeed), which must be set up in the job queue entries.
When assisted set up Set up Bankfeed Integration is filled, it automatically creates 4 Job Queue Entries which run function Process Statement Batches (Bankfeed) 4 times per day.
But if needed Job Queue Entries can be set manually. Sometimes you may also need to adjust function running times.
- In Search, open the Job Queue Entries and click +New
- Fill in the information in the page that opens:
| Field | Desription |
|---|---|
| Object Type to run | Select a Report |
| Object ID to run | Specify 70656779 |
| Earliest start date/time | Specify the Date and Time when it is planned the first import of bank statements. |
| Report request page options | Enable this option. Once ticked, the report options window opens immediately, where you fill in the options according to your needs and click OK. For more details on the options for this report, see Function Process Statement Batches (Bankfeed). |
| Recurring job/Run on Mondays/../Run on Sundays | Tick days on which the bank statements should be imported. |
| Starting Time | Set the time at which we want to receive bank statements on previously scheduled days. |
| Ending Time | Set the ending time. |
| No. of Minutes between Runs | Set number of minutes between the runs |
Important
Sometimes, when the number of bank statement files is very large, it is recommended to set the job queue to run several times because the number of files in one upload cannot exceed 100.
- Once the job queue entries card has been filled in, in the action bar click Process -> Set status to Ready.
The status of the job queue entry is then changed to Ready, and it is ready for use. If corrections need to be made, the status needs to be changed to Hold, which is done in Process > Set on Hold.
%20(120%20%C3%97%2045px)%20(3).png)