When using AI on the Bank reconciliation and wanting to create a bank ledger entry for an unmatched transaction, why is AI limiting the ability to only post to a General ledger account. For example, if I choose the alternative way via Transfer to General Journal, I could choose to apply, in this example, the receipt to a customer account. Otherwise, the feature is great including the now added Text to account mapping but restricting to only post the difference to a GL account does not make sense.
Hi, You are not doing anything wrong, this is by design at the moment, not a bug. The Copilot part of bank reconciliation is built specifically to suggest a G/L account for the residual unmatched lines, it reads the description and matches it to a G/L account name. That is the whole scope of that AI feature, so Post difference to G/L account only offers G/L on purpose, it does not do customer or vendor applying. For applying to a customer like your receipt example, the manual Transfer to General Journal route is still the right way, because there you control the bal. account type and can apply to the customer ledger. So the two are not really the same feature, one is full posting, the AI one is just the quick G/L catch-all. One thing worth trying, the Text-to-account mapping can point a description to a customer/vendor too, not only G/L, so partly it covers your case. But yes, agree the restriction feels limiting, would be good as feedback on Microsoft Ideas. Which version you on?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
709
Share
Report
All responses (
Answers (
