You’re offline. This is a read only version of the page.
5
Hello all!
My company is converting from QB Enterprise to D365 BC. I am concerned about two things:
1. The reporting available in BC seems very rudimentary and unprofessional looking. My supervisors need in-depth analysis such as multi-month income statements, the ability to run the IS by department, sales by item reports, sales by salesperson reports, AR aging detail and summary by 30-60-90+ past due as well as ad-hoc reporting which I am very comfortable providing from QB. Can this be done in BC and if so, how?
2. We are a subscription based company that bills 30 days in advance of service (so invoices for December service will be going out on 11/1). How can I get BC to handle the deferred revenue? We have researched add-ons but they are prohibitively expense.
General thoughts and opinions from anyone who has migrated from QB to BC would also be appreciated. I just want to confirm the system can handle our requirements.
Thanks,
Miriam
I’m not an end user but I migrated a company from QB to BC. Reporting wise they opted for Jet Reports to plug any gaps. They have some Power BI reports to create dashboards as well. These have only been used where account schedules and generic reports didn’t meet their needs. As a result of picking these up in house they are self sufficient with reporting. Learning curve on these products isn’t too steep once the system is known.
Two main options in standard for that type of billing. Use service contracts but these will create invoice lines for each period of billing i.e. if you have a 12 month contract it will create an annual invoice with a line for each month.
Other choice would be recurring sales invoices. Have a batch job running to generate these and then use a batch post function. Possible that you look at some modifications to get this process as slick and effective as needed.
Company that did this migration have felt the benefits
Share
Report
All responses (
Answers (
