Categories
articles Dynamics 365/AX INLOGICA products Recommended

Overestimated budget – Mistake 6 – ERP D365 implementations

6
Overestimated budget

At this point, it is again worth recalling the framework schedule. Estimating the implementation is one of the primary activities that must be performed before any work begins.

Inlogica Separator

To begin with, you need to verify the need for a particular solution in your company. Do you think it’s necessary? Is there a budget to implement an ERP solution in the organization? This is extremely important for the start of the work and the success of the entire implementation. Budgets and cost estimates have it that they often do not want to “pin down” at the final stage. There are always unforeseen expenses that should be included in the tables. And it’s hardly surprising – that’s why they are unpredictable. Hence the need to set up a budget “on top.”

In our experience, the buffer should be 10 – 20% of the value of the original assumptions.

Therefore, everything must be calculated carefully and then scaled again to the needs of a given company/plant/enterprise.

It is worth asking ourselves a fundamental question: can we afford it, will this investment bring us the expected benefits (not only purely financial ones).

As they say: budget is not made of rubber, and nerves are not made of steel.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Confidence shaken – Mistake 5 – ERP D365 implementations

5
Confidence shaken

Any cooperation is based on relationships. Often of various types: business, partnership, courteous, social, and collegial. It tends to be, that one of the evoked is involved, and it happens that all of them are together.

Either way, the basis of fruitful cooperation on the customer-implementation company line is “good relations.” “Chemistry” is expected, ideally when “something sparks” between the Customer and the contractor. Because when there is good cooperation, the best results are worked out. This is a truism – a fact. But it still works.

Good relations are built not only on trust but also on mutual respect.

Inlogica Separator

Respect for one’s and others’ work makes it possible to avoid misunderstanding. And if this is accompanied by an elementary knowledge of the scope of work of a programmer, then the job “goes like butter.” Then we will not hear comments like: “adding one column to a table, after all, cannot take a good programmer of more than 15 minutes” etc., etc.

Inlogica Separator

Building friendly relationships is helped by proven and good practices in communication:

  • it is always worth speaking clearly and directly
  • it’s not worth “wrap out”; there is no point in diluting the message
  • it is best to appreciate the whole team’s work to ensure the message is complete
  • it is necessary to keep the given promises
  • and, above all, respect each other’s time spent and the job done

Two parties must trust each other. Maybe not boundless, but at a decent level.

Both the client and the implementation contractor know their job, do it professionally, so it is enough to let the specialists quietly work, and sometimes try not to disturb them. Each stage they finish, they will certainly discuss with the client, i.e., with the people appointed to do so.

Inlogica Separator

The partnership allows for free and clear communication of the status of the work. Lack of agreement and understanding affect the time implementation deteriorates the friendly atmosphere cooperation.

Inlogica Separator

It is impossible to implement a program – especially with such a complex system – anything in 15 minutes. The work consists of various activities. In addition to pure programming there are hours of testing, consulting, and documentation…

People and relationships/interactions matter more in the work of implementation teams/companies than processes and systems. This is because people from both business sides implement strategies and techniques.

If there is no agreement between them, problems can arise during implementation.

Cooperation always starts with mutual understanding and trust.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Arbitrary decision making – Mistake 4 – ERP D365 implementations

4
Arbitary decision making

The echo of this “error” has already appeared in the points above. And as in the earlier descriptions, it is worth recalling what is at the heart of the implementation, that is a framework schedule.

Inlogica Separator

When we plan the functionalities, we want to implement, we need to define them together with representatives of all departments having contacting and working with the tool in question.

Ideally, this “brainstorming” should involve team/department managers participate. However, before this happens, managers should know the potential expectations and possible problems “their people.”

Before they take part in the brainstorming, it would be good for them to know how they can improve the work in their teams and what they should obtain at the end.

Such an “internal communication path” is critical and essential for another reason. The idea is that everyone on the team has the same state of knowledge about the implementation.

The team leader communicates to the others the key findings. So that there is no uncomfortable situation of someone making an arbitrary decision that no one else knows about. Such an action may result in complications in implementation, additional unnecessary costs, and sometimes nervous movements or even unpleasant consequences.

The internal circulation of information helps keep the course of the performance according to the established schedule without unforeseen deviations.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Over-creativity – Mistake 3 – ERP D365 implementations

3
Over-creativity (so-called whims)

Before starting the implementation process, it is worthwhile – and even necessary – to learn about the capabilities and application of a modern ERP system. Will it be helpful, and to what extent is the company ready for it, is this “the moment” for such an investment?

The answers to the questions posed may bring a pre-implementation analysis or constructive consultation with specialists from implementation company.

If the decision is “yes,” the next step is a discussion of the needed functionalities.

Why? Because one of the main mistakes, and thus, the brakes on implementation are “whims” that arise in the course: – “and it used to work like this…” “and let’s make another such functionality…”

Inlogica Separator

Microsoft has 2 core ERP solutions: Microsoft Dynamics 365 and Microsoft Dynamics Business Central. Each of these solutions is aimed at a different group of customers.

Before starting work, you can verify which groups you find yourself in.

Start, for example, with Business Central for the Department of Finance, instead of immediately “throwing yourself” at Microsoft Dynamics 365.

Sometimes the step-by-step method more quickly will take a company to the finish line than starting a marathon implementation without adequate preparation and “over the top

It is only worth investing in solutions out of the box if we are convinced, they will improve system performance. There is not also make sense in leaving something out of pure sentiment because “it’s always been this way…”.

Inlogica Separator

A new solution should and can be tailored to the specific enterprise. Prior identification of the needed functionalities (this has to do with the prepared framework schedule) will enable effective optimization of costs and implemented solutions.

Inlogica Separator

A helpful but often overlooked step by clients is to examine whether each company area needs a “modernization” of the system. But, whether in every department: finance, production, warehouse, or sales – it will work, and so will need an ERP system, and which of its variants will be optimal.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Insufficient commitments – Mistake 2 – ERP D365 implementations

2
Insufficient commitments

Implementation – or colloquially speaking. “proving” the project depends on teamwork. And it’s not just about a dedicated, close-knit team of specialists on the contractor’s side. Success depends on fruitful and effective cooperation between both parties. When one part becomes more involved than the other, an implementation may encounter unnecessary difficulties.

Inlogica Separator

Another issue is the deep involvement in designing the assumed solutions. Unfortunately, this is impossible when no specific people are assigned to the task, and the responsibility is dispersed. The optimal solution would be to give to the project on the client’s side, such persons who can, on behalf of the principal make binding decisions, and approve subsequent stages of the work.

This often involves competence and “substantive and technical” preparation. Questions, doubts, or new ideas often need to be discussed. Then it would be best if you understood the issues and openness in the discussions of persons responsible for the project (at the Client).

For the implementation to proceed by the previously developed framework schedule, the specialists need – provided by the client – all the required data for the project.

These include the chart of accounts, suppliers, customers, product/service directories, and guidelines for VAT

As you can see, knowledge of the solutions to be implemented is essential for testing, technical and organizational arrangements throughout the implementation process.

Pre-implementation training courses can help with this. On the one hand, they will prepare the client’s team to work with the new system; on the other, they will allow us to check the “state of knowledge” of what we are implementing.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

7 Basic mistakes made in implementations ERP Microsoft Dynamics 365

Knowledge gained from over 20 years of experience and implementations of Microsoft Dynamics 365/AX for the largest companies in Poland and Europe allows us to identify the seven most basic mistakes made during the performance of these systems.

Today we would like to present them to you so that you can avoid them in your own company.

1
No schedule

The framework schedule allows you to control the budget, the course of implementation, and, ultimately, the success of the works. Failure to develop without estimating costs, the deadline for performance, and the inability to assume a time and financial reserve involves a high risk of performance. And this no one desires. Both on our side, as well as on each customer’s side.

Model implementation schedule for Microsoft DynamicsBusiness Central in the financial and accounting area

Sample implementation schedule Microsoft Dynamics

A refined schedule gives comfort in planning and carrying out the implementation.

It allows you to assign the right specialists to the work, as well as preparing for possible problems and their solution.

The schedule is strongly related to the work methodology in which the implementation is carried out.

INLOGICA, for example, implements work in agile methods, such as SCRUM.

A logically designed schedule increases the internal discipline of all involved in the implementation/project. It allows the team to work without time pressure, which naturally translates into productivity.

Inlogica Separator

A good schedule allows you to monitor the progress of the work in real-time at every stage.

Inlogica Separator

That’s why it’s crucial for implementation to reserve places in the schedule where we can check the progress of the work.

Optimally, this should occur every week or two, depending on the task.

Inlogica Separator

When creating a framework schedule, a vital prerequisite is to plan it together – the contractor and the customer. This is essential for the success of the implementation.

Top tips

Are you interested in this article? Are you looking forward to the next parts? Click here to see the full story

Categories
articles Dynamics 365/AX INLOGICA products Recommended

JPK-FA(4) – changes to the Polish single audit file for reporting sales invoices

The Polish Ministry of Finance has published the fourth version of the JPK-FA single audit file structure. By way of reminder: the tax authorities may request the presentation of a JPK-FA(4) file, alongside other single audit files, in order to carry out formal checks, tax audits, or to conduct fiscal proceedings. Once requested to do so, the company will have 3 days to produce to the authorities a sales invoices file generated in accordance with the required structure.

When will the new JPK-FA(4) structure become mandatory? On 1st April 2022.

What has been changed for the new JPK-FA(4)? The structure now contains, among others, an updated glossary of EU member state codes and an updated currency code glossary. The node containing identification details for non-natural persons has been expanded to contain identification numbers for OSS and IOSS purposes (EUPLVATID and IMPLVATID). Several descriptions of structure elements have received an update, too. More detail can be found in the Ministry of Finance’s JPK_FA(4) Information Brochure.

We invite all users, whether of the earlier ERP Microsoft Dynamics AX systems or of the latest Dynamics 365 apps, to take full advantage of INLOGICA’s JPK module.

We keep tabs on the changes – we give accountants peace of mind.

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Payment backlogs in commercial transactions

How to avoid a paralysis of the Finance Division when preparing the next report on payment practices and performance in commercial transactions?

We have been hearing rumours across the industry in Poland that some companies, all of which were preparing reports on payment practices and performance, i.e. on payment backlogs, for the first time ever took over 2 weeks to get them done. It appears that finance specialists dedicated all their efforts to satisfying statutory reporting requirements only. How did that happen? Probably because they lacked tools fit for the job.

Can a payment backlog report, therefore, be prepared in a matter of hours?

It certainly can. All it takes is a suitable functionality which enhances the existing ERP system in such a way as to support the process of generating the necessary data. Microsoft Dynamics 365/AX system users can now use a proprietary solution developed by the INLOGICA team for this purpose. The payment backlog functionality in its standard version makes it possible to quickly generate a Payment Backlog report which includes the financial information required of a report on payment practices and performance.

The report itself is just one aspect of the payment backlog functionality.

It is just as necessary to closely watch the in-house payment practices too, as exceeding the statutory threshold of outstanding or late payments during a period of 3 subsequent months is considered as causing so called “excessive payment delays”. The threshold is currently set at PLN 5 million, and exceeding it can lead to serious consequences. They can range from having proceedings launched against the organisation by the Polish Office of Competition and Consumer Protection to high fines, the amount of which depends on the sum of delayed payments and the period of delay. The threshold beyond which the provisions on excessive payment delays apply will be decreased to PLN 2 million as of January 2022.

How to keep it in check?

By regularly monitoring payment practices. The extended version of INLOGICA’s payment backlog functionality for Microsoft Dynamics 365/AX is equipped with analytics and regular monitoring of payment delays in commercial transactions using defined system alerts.

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Reports on payment practices and performance functionality for Microsoft Dynamics 365/ AX

Due to changes in Polish legislation which came into force as of 1 January 2021, some businesses are now obliged to report on payment practices and performance.

Following significant demand from Microsoft Dynamics 365/ AX users, the INLOGICA team have developed a solution which supports, facilitates and automates the process of generating data required to compile the report.

The functionality will be available in two variants: standard and extended ones.

The standard version makes it possible to generate, directly from the Microsoft Dynamics 365/AX system, the financial data necessary to submit the annual report on payment practices and performance in commercial transactions via the biznes.gov.pl platform.

The extended version, in addition to the basic function of generating report data, also enables regular monitoring of payment backlogs, shielding the business against crossing the statutory “excessive payment delays” threshold.

The user is free to define system rules, the violation of which will trigger a system alert, thus minimising the risk of involuntary exposure to the consequences drawn by Polish authorities.

Categories
articles Dynamics 365/AX INLOGICA products Recommended

Birax – a solution dedicated for the Dynamics AX system

A tool dedicated for Microsoft Dynamics AX, available for system versions:

  • AX 4, 2009 and 2012

The tool allows automatic customer/ vendor data completion based on integration with the REGON 1 Online Database maintained by Statistics Poland.

After entering the tax identification number (NIP), the system automatically fills in the remaining counterparty’s details, such as: the name, address, registration data. At the same time, the customer’s/ vendor’s account is being created or updated.

It is possible to enhance the tool by adding a functionality for verifying the counterparty against the VAT Payer Register.

This allows the user to check whether the buyer of goods or services is registered for VAT (i.e. as an “active” VAT Payer).