Gina Hoener Sr. Consultant

Currently, after matching manually, the bank statement lines stay selected. You have to manually deselect the transactions before moving on to the next match. This causes problems if all the entries are not deselected as the user continues on with the reconciliation.

Suggestion is to automatically deselect the transactions after a match has been made.

Currently, we can select many bank statement lines and match to one bank account ledger entry even if the totals do not match. There is no notification of this. The opposite is true too. You can match one bank statement line to many bank account ledger entries that do not equal. In fact, a user can complete the reconciliation, the balance is zero and the amount matches the bank statement ending balance. There is no different. When posting an error appears that tells the user there is an amount that doesn't match.

When the Test report is printed the is a non-descript message at the very bottom of the report saying the Application is wrong. There is no additional information.

Suggestion is for an immediate message that the matching is not correct. Also, the Test report should have a more descript message at inform the user of the matched transactions that do not equal. Waiting till posting is too late and even if that has to happen, we need a report of what was matched incorrectly.

Currently, you can select a bank statement line and view the Match Details. There is no way to select a Bank Account Ledger Entry and view Match Details because whatever is selected on the bank statement line is what appears in the Match Details. There is no way to deselect a bank statement line and select just the bank account ledger entry.

Suggestion is to have the Match Details feature go both ways. Be able to select either a Bank Statement Line or a Bank Account Ledger Entry to view what it is matched to.

Currently, when unmatching bank statement lines you need to select the applicable bank account ledger entry. If there are multiple bank statement lines, they all need to be selected along with the bank account ledger entry. Also, if there is one bank statement line matched to multiple bank account ledger entries, you need to know the exact entries that are matched in order to correctly unmatch. If you don't then more transactions are unmatched than expected.

Suggestion is to be able to select the bank statement line and unmatch and have BC unmatch the applicable bank account ledger entries or vice versa. Currently there is always something selected on the Bank Statement Line and no way to select just a bank account ledger entry. When unmatching we don't always know the details if it is a one-to-many match or a many-to-one match and therefore the unmatching is incorrect.

When you dispose of an asset, the gains/loss lines inherit the dimensions from the line in the Fixed Assets G/L Journal or Sales Invoice.

It would be nice to be able to assign different or no dimension to the lines that are system generated and posted as part of the asset disposal.

With the functionality as it is today, users must ‘correct’ dimensions on General Ledger Entries after the fact to get desired results in GL. However, this creates a situation in which the Fixed Assets ledgers no longer match the GL ledger entries (since there is no built-in functionality to correct dimensions of related entries).

Thanks!

Gina Hoener

The new fixed and variable allocation accounts can be more effective if they can be used in posting groups. Then they can be used on sales and purchase orders/invoices where allocations can take place automatically.

Since standard Purchase Orders migrate using the GP to BC migration tool, it would be nice if standard Sales Orders migrated too!

Thanks,

Gina Hoener

There is a filter assigned for Sales and Purchases snapshots and no obvious indicator of that. GL trx and Item trx are not filtered by default. Would be nice to remove the filter from these snapshots too.

Thank you,

Gina Hoener

Wile the migration tool migrates current serial and lot numbers, there is no historical migration. Serial number/lot number tracing is unavailable and unless users have access to GP or an import is done for them, they have no way to do a serial number/lot number trace.

Would nice to have that history migrate too.

Thank you,

Gina Hoener

Item classes in GP migrate to Inventory posting groups in BC. It would be nice if the item class accounts migrated to General Product Posting Groups and updated the General Posting Setup.

Thanks,

Gina Hoener