Set up the module Continia Statement Intelligence
The module Continia Statement Intelligence contains functionality for importing bank statements from the bank for automatic reconciliation as well as creating expense entries such as fees and interest. Read more about the functionality in section Statement Intelligence module.
Before you can use the module, you must configure it. In this chapter, you will learn how to set up Statement Intelligence.
- Select the icon or press Ctrl-F3, enter Continia Statement Intelligence setup, and then select the related link.
- Below you will find descriptions of the individual settings, how to fill in fields and their meaning regarding Continia Payment Management.
- Select OK when you have completed the setup.
|Restruct. Jnl. Doc No's||When importing account statements the individual journals used by account statements are re-numbered, when this field is marked.|
|Allow partial Bank Acc. Stmt||Used only in special cases.|
A check mark in this field allows you to continue running on the same account statement in Dynamics NAV or Business Central on-premises.
This mark means that you do not have to complete an account statement to start reconciling the next one. You can also post partial bank statements so that the outstanding entries remain in the journal.
|Cash Rcpt. Jnl Lines - Create.||In this field you can specify how the system should handle all positive entries in a bank statement, primarily customer payments but can also be interest or fees. The following options are available:|
Doc Found - Payment journal entries are automatically generated if the system can find a customer ledger entry that is open based on the notification. If Statement Intelligence is in doubt about which customer ledger entry the payment relates to, the user must designate the entry/entries themselves before an entry can be created in the payment journal. This is the default setting.
None - Payment journal entries are not created automatically.
All positive on import - All positive entries will be created in a payment journal. Then you must delete the items in the journal that are not payments, e.g. if you have transferred an amount to the account, which is usually posted to a general journal.
All positive manually - Same functionality as with "Documents found", however, the proposals are not created automatically, but instead a check box appears in the column "Manual Handling", which indicates that it is possible to create an entry in the payment journal using the action Create Journal Lines.
|Lock Statement Lines||Using this field means that you can lock the reconciliation lines, so the users need certain permissions to make changes in the fields in a reconciliation line. |
If a reconciliation line contains an incorrect notification text (invoice number has been entered incorrectly) and a match cannot be found for the item, then it may be useful to be able to correct the text so that the line can be matched correctly.
The field is not normally filled in (tick removed), ie. everyone can edit in the reconciliation lines. If you want to control who is allowed to edit in the reconciliation line, then put at tick in the field. The tick then controls if the user is allowed to execute CodeUnit 6017207.
The users who must be able to edit in the reconciliation lines must be granted rights to execute CodeUnit 6017207. If in doubt, ask your Microsoft Partner how to grant the right to run a particular CodeUnit.
This completes the general setup of the module Statement Intelligence for account reconciliation.
Before you can use Statement Intelligence, your bank and each of your bank accounts must be configured so necessary information is available to make an automatic account reconciliation, as well as entries such as fees and interest.
Likewise, you can define reconciliation rules for your bank accounts, both general and bank-specific, and you can also set up merge rules so that several entries from the account statement are merged into one entry. You can also define reconciliation rules for your customers that will help you "find" manual accruals in your bank account.
What to consider:
General setup of your bank. Follow the instructions in section How to set up bank account reconciliation on a bank card.
Basic setup of all bank accounts. Follow the instructions in section Setting up bank account reconciliation on bank accounts.
General- and bank-specific reconciliation rules - If Payment Management is to create a posting suggestion automatically in the cash receipt journal when a bank entry does not have an open record, you must define these rules to make the reconciliation. Follow the instructions in section Define general or bank-specific reconciliation rules.
If Payment Management should automatically merge multiple entries into one or more entries, e.g. merge multiple credit card transactions into one entry per today, you must define rules for this. Follow the instructions in section Define merge rules.
Customer reconciliation rules - if you invoice with FIK payment slip, you will probably find that many of your customers simply make an account-to-account transfer, without specifying either invoice number or FIK number (Payment ID). In order to find and settle these entries, you have the option of defining customer reconciliation rules. Here you can, for a specific customer e.g. register that the customer always writes "From SAS A / S" in the notification text. Follow the instructions in section Define reconciliation rules for customer payments
If your company uses FIK / GIK payment slips and you did not already configure these when you installed the basic module, remember to configure the reports. Read more under section Setting up reports for printing FIK / GIK payment slips.
At the same time, when you need to use FIK / GIK payment slips, remember to fill in the fields FIK / GIRO Registration No., IK Card Type and Customer Account Statement No. during the general setup of Payment Management. Read more under section Payment Management Setup Page.
You do not need to specify a Payment ID mask if you are using Continia's standard reports, as Payment Management already know the reports' structure of the OCR (Payment ID) line.