Based on both sales and purchase transactions, telebanking enables you to generate your payments and collections and interchange them with your bank electronically. This includes the export of payment and collection data that need to be forwarded to the bank as well as the import of bank statements sent to you by the bank.
In general, all financial interactions with vendors and customers are done through either purchase or sales invoices and credit memos. As soon as these transactions have been registered and posted, payments or collections can be carried out by your company.
Based on vendor and customer ledger entries, telebanking enables you to generate payment and collection proposals. This can be done for any bank that has been set up for your company. Both domestic and foreign payments and collections are possible.
You can set up Microsoft Dynamics NAV to combine payments to or collections from the same bank account automatically.
When a proposal has been agreed upon it should be processed into a payment history.
|In general, for any open vendor and customer ledger entries, a proposal can be generated if it meets a number of criteria. See Creating Proposals.|
A payment history is nothing more than a proposal except for the fact that data on a payment history cannot be modified. The payment or collection data is ready to be exported and forwarded to the bank.
For all your financial interactions through your bank, the bank can send you electronic bank statements. These statements can be imported into the Bank/Giro Journals. If you want, you can have Microsoft Dynamics NAV automatically reconcile these statements during this import process and determine whether a statement can be applied to open ledger entries for the relevant vendor/customer.
For both exporting and importing, a number of protocols have been defined of which the following ones are being supported:
Swift MT940 (import)
Rabobank mut.asc (import)
Rabobank vvmut.asc (import)
Rabobank ASCII (import)