We processed all our transactions in Microsoft Dybamics SL, for income and expenses cycles. I would say that not being an online operation makes difficult to have data always on time, because it uses batches sometimes business rules are not achieved but transactions were already made. So only thing is to correct them through sql
Pros
Reporting
Detailed Warehouse setup (bins)
Document application (ap and ar)
Cons
Online transaction register (not baches)
Validation before posting inventory transactions with missing item availability
Preview of accounting before posting.
Likelihood to Recommend
It's less suited due to high costs for managing all infrastructure IT needs
We are using it for project and crew based cost accounting in one of our utility contracting companies and are in the process of rolling out the system to another one of our largest companies. Eventually, all companies under the holding company will deploy Dynamics SL as their ERP system as well as the parent company. The parent company will perform cross company consolidations.
Pros
Provides flexibility for complex project based cost accounting
Strong and flexible allocation processer for cost allocations, markups, and pricing
A "Flexible Billing" module under the project controller series that allows for multiple billing formats ranging from fixed price schedule of values, T&M or Cost Plus, and scheduled billing.
Flexible reporting with options using Crystal Reports, SSRS, a Quick Query tool, and ability to tie into MS Office tools such as MS Access and MS Excel
Tight integration with Financials, but also the ability to integrate with modules such as Sales Order, Inventory, and Field Service
Customization abilities ranging from a VBA (visual basic for application) foundation to allow customizing existing forms to the ability to use the SDK (Software Development Kit) to build more complex customizations that integrate with Dynamics SL.
Cons
Incorporate some functionality provided by third party products into the core product.
Since Dynamics SL has strong multi company capabilities, incorporate functions to secure projects within a company to certain groups.
Improve the budgeting, forecasting, and change order interfaces so that the tools are more online.
Improve the forecasting capabilities to include more robust and integrated tie in to the project EAC/ETC (Estimate at Completion/Estimate to Complete) numbers. This would allow project revenue/margin/cash forecasting.
Expand on the subtask concept
Improve the interface for multi level rate entry for pricing and cost allocations such that more security can be applied and reduce risk of inadvertent changes.
Likelihood to Recommend
In the service series, there is a weakness in applying revenue recognition concepts which are a strong point of the project series. It is difficult to get a period sensitive WIP that could be recreated at any time for a point in time (fiscal period).
Microsoft Dynamics SL is used for project management and financial reporting. It is used across the organization. The financial modules provide general ledger details and reporting along with payroll being processed for projects and management.
Pros
Project accounting is linked to the Financial modules - there is no need to duplicate data entry. Reporting in Project Modules is extensive.
Validation of fields for data entry and solid integrity of data.
Customizations of screens for data entry for users and addition of fields.
Cons
Purchasing does not have a budget validation to warn or stop a purchase from going over budget on a project level.
Project budgeting does not have an interface with inventory ids.
Financial modules could have more quick vewing screens for example a quick way to find the check no. of an invoice.
Likelihood to Recommend
What type of business are you in and does it need the project modules?
