Home  News Release of AutoBank® for SAP® 4.2 |
|
PDF
|
| Print |
|
E-mail
|
|
Release of AutoBank® for SAP® 4.2 |
Automatic bank reconciliation in SAP has just become even more efficient: version 4.2 of AutoBank® for SAP® is here!
Many new functions and features make using AutoBank® for SAP® easier and more productive.
The new features include extensive improvements in the postprocessing, including the option to execute refunds directly from the postprocessing mask. Another innovation is the possibility to mirror master data which finally allows you, for example, to transfer data from the production system to the test system – quickly and easily. AutoBank® for SAP® can now also assign bank statements from international banks without problems and the reporting is improved as well.
Refunds from PostprocessingThe new function 'refunds' was integrated in the postprocessing mask of AutoKonto. You can refund payments that cannot be assigned to the payer account details. For this purpose, a payment request is generated in SAP. The payment is then processed in the SAP standard or, if you use them, in one of the Hanse Orga AG solutions ebXchange®, ebXGlobal® or ipcNavigator®.
This new function comes with additional safeguarding measures: In the postprocessing, you can only edit the refund in a restricted manner, neither transfer amount nor target account can be changed. Errors can thus be avoided.
Master Data Maintenance from PostprocessingThe manual postprocessing of AutoKonto provides a new function that allows you to make comments in regard to the improvement of master data directly in the corresponding data records. The key user can look at the line items with comments and the performed postings in a separate transaction and can adjust the corresponding master data directly from this view. The transaction can also display completely processed bank statement items incl. postings.
This transaction allows a quicker and more efficient reaction to improve the assignment rate - which in turn means less manual effort for you.
Mirroring Master Data – Export and ImportNew transactions allow the transfer of AutoKonto and AutoAvis master data as xml files from one SAP system (for example: production system) to another (for example: test system). A selection screen is available so you can perform individual restrictions according to company code group and/or company code, target system and, additionally, according to master data application. With this function you can now use your master data from the production system to perform tests in the test system. Testing in this manner is quicker and more efficient and the result is more meaningful. An additional import interface allows data to be added, e.g., to fill the conversion table or sending bank details beforehand.
Enhancements in SBD ProcessingWhen processing with help of the sending bank details, the inclusion of amounts could only be activated per company code to date. Version 4.2 now allows the control per company code and target system. You can now use the SBD table without matching of amount in SAP-FI and with matching of amount in the debit-side subledger (e.g., IS-U, FS-CD, etc.). It guarantees a higher assignment rate and improved posting proposals in the postprocessing.
Enhancement of Conversion FunctionalityBank statements of international banks often bring about problems when assigning payer information with help of SAP import routines and FEBEP data fields cannot be filled accordingly. A new function in AutoBank® for SAP® 4.2 provides a significant improvement for the automatic assignment of data. A new matching column in the conversion table is accessed using an abbreviated search pattern. In a second run, the classification keys of the identified entries are then crosschecked with the note to payee. The values determined in this manner can then be used, for example, to access open items. With this function, AutoBank® for SAP® provides a greatly improved assignment rate and high quality posting proposals in the postprocessing. Your manual effort is decreased significantly.
New Processing Log in the ReportingTo date, processing steps and results could only be saved dynamically which often made retracing of individual steps hard. The new processing log of version 4.2 also saves processing steps and results historically. You can now analyze the historical course of postings and use this information to determine possibly incorrect settings. The processing is logged across all levels of processing: main rules, payment types, sub rule sequences and sub rules as well as search patterns, sub rule function modules, conversion table, etc.
|
|
