-
Settlement code (AP / AR / GL) to tract matching transactions
Settlement is working on 3 modules but we still have missing direct information on settlement.
Settlement code is a nice feature to add for direct visibility but also reporting.
On French localisation, Account Statement internal (FR) has a column with settlement code. (what can be called Lettrage as mainly identified by a letter - any other code can do).
the idea is
- CAPITAL letter for closed transactions (full settlement)
- Minuscule letter for partial settlement
Lot of customer will use this information and this will avoid any customization.
-
Report with Customer credit management statistics (DSO days sales outstanding)
To check DSO statistics, user need to go on customer information and refresh statistics.
But collection agent should be able to edit a report with statistics for all customers.
As for customer aging balance (run snapshot), a process can be run to stock information.Then Customer balance statistics should be possible as for Customer aged balance.
Columns should be added to have DSO / average payment day... Useful information for customer collection agent.
-
Financial tags to be kept in detail opening transaction for automatic ledger settlement
Financial tags are part of criteria for automatic settlement.
When year end close is run, the detail transactions are created to allow ledger settlement on open fiscal year.
But if information has been added on financial tags to allow automatic ledger settlement it is no more possible as information is lost on opening transactions.
Financial tags should be copied during fiscal year close to ease ledger settlement
-
Camt.054 import does not have default description populated
When importing a customer payment file (ISO20022 Camt.054), the description field is not being updated based on the automatic configurations defined in Default descriptions form setup.
Descriptions are mandatory for tax authority reporting.
Camt.054 included lot of lines and user cannot populate them manually. Default description should be possible on Customer payment, Customer but also on offset account.
Offset account will help either on bank reconciliation or bridging account settlement. Then information can help.
Same as bank transaction type that must be default from payment method.
I can find MS Bug 801221 the idea is to have the function operational for companies
-
Modern bank reconciliation : option to post or not directly transactions from bank statement
on Modern bank reconciliation is enable, vendor/Customer payment transaction can be Posted directly from bank statement.
System should allow an option to either create journal and post OR post automatically the journal.
Users want to control journal before any validation as business process may be complex.
If transactions are incorrect, all reversal will be complex and bank reconciliation a mess.
It is difficult to fully trust a system (at least at beginning) and the option to not post directly journal will help our customers.
-
Bank reconciliation: Missing Voucher on bank transaction side
on bank transaction side of bank reconciliation, there is no option to add voucher.
From customer test, information may be available on bank statement. They filtered based on voucher number. but the option is not available then they should check on transactions and with description filter.
It will be good to have voucher on bank transaction (field to add)