Dynamics 365 Consultant in Poland

Who maintains the Polish localization in Dynamics 365?

This is the first question I ask on any Polish Dynamics project, because the answer shapes risk for years. For Business Central, Microsoft localizes some countries itself and leaves others to partners who publish localization apps. For Finance and Operations, country features follow a different model again. Which case applies to Poland, and what it covers, should be confirmed for the product and version you license rather than taken from a slide.

When localization comes from a partner app, I look at practical things:

• Who publishes it, and is that the same firm implementing your project?
• How quickly has it followed past Polish rule changes?
• Is it licensed separately, and on what terms?
• What happens to your support if you change implementer later?

Then I test the outputs your accountant relies on: VAT registers, JPK files, invoice content, correction documents and foreign-currency postings. A localization that produces the right files in a demo company but fails on your real document types is not finished. Results go into a fit-gap matrix that headquarters, the Polish team and the partner can all see. My ERP gap analysis page describes the format.

KSeF, JPK and the extension layer

Poland's KSeF platform receives structured sales invoices and returns an identifier, and purchase invoices can be collected from it. In Dynamics 365, support for this is likely to sit in the localization layer or in a dedicated extension. The rules have shifted more than once, so treat your tax advisor's current reading as the reference and expect the extension to need updates.

The design work covers more than sending. A Polish finance team needs to know how a rejected submission appears, who fixes it and how it is resent. Correction invoices need their own flow, because a submitted document cannot be edited. Inbound invoices should arrive in a purchase queue and match against orders and receipts, not land in a mailbox. And there must be a written procedure for platform outages at month end.

JPK files draw on the same posted data, so I trace each field back to its source, whether a sales line, a purchase invoice, an inventory movement or a fixed asset entry. Missing tax identifiers and misused posting groups are the usual culprits, and I prevent them with mandatory fields and validation. These scenarios form the core of the acceptance testing plan, and your accountant reviews sample files before cutover.

Group rollouts, shared service centers and two currencies

Polish entities on Dynamics often run on a template designed abroad. That brings real benefits, such as common items, customers, posting rules and reporting, but it also brings friction. Group charts of accounts rarely match Polish statutory needs, approval flows reflect headquarters' structure, and document layouts assume another language.

I help both sides agree a design where the group template stays intact for what genuinely must be common, while the Polish entity gets what local law and its accountant require. That usually means a local chart mapped to group accounts, Polish-language document layouts maintained by the implementer, and PLN as the local currency with reporting in EUR or the parent's currency. Exchange rate sources for VAT purposes are your accountant's call; I make sure the system applies them consistently.

Shared service centers add a twist. A Polish center may process transactions for many group companies in Dynamics, so roles, approval limits and intercompany recharges need careful design, and data access must respect each entity's boundaries. I map the center's processes and agree which steps vary by entity. Microsoft's EU data center regions and your GDPR obligations should be reviewed with your data protection officer; I translate their conclusions into access rights and retention rules. For general Dynamics guidance, see my Microsoft Dynamics 365 consulting page.

Staying independent of the vendor channel

Dynamics 365 is sold and usually implemented through Microsoft's partner network, and a Polish entity may hear from a local partner, the group's international partner, or both. My position is outside it. No license revenue, referral payment or favored implementer shapes my advice.

That independence is useful at three points. First, when bids arrive: I compare them against the same requirements, separating fixed scope from assumptions, and checking which localization and KSeF apps each one depends on. Second, during the build: I review designs, attend key workshops and keep a decision log so the Polish team's needs are not lost in a group-led project. Third, at testing: I run acceptance tests with Polish finance users and hold sign-off until the agreed scenarios pass.

I work remotely, in English, with headquarters and Polish staff on the same calls. Polish-language training and documents come from the partner or your bilingual team. ERP vendor selection explains the comparison method, and the ERP consultant in Poland page covers my wider Polish advisory work.

Polish companies that should think twice about Dynamics

Dynamics is a strong option for many Polish subsidiaries, but not every one. I would question it in these cases:

• Standalone Polish SMEs with no Microsoft-based parent, where licensing and partner costs may outweigh the benefit compared with Odoo in Poland.
• A partner-maintained localization with no clear future, for example if the publisher is small and the app has lagged behind previous rule changes.
• A group template that would need so many Polish changes that the entity would be better on a local system feeding consolidation.
• Sales-led companies whose problem is CRM, not finance, where Zoho in Poland beside the existing ledger may be enough.

I put these alternatives next to Dynamics on the same weighted scoresheet so the conversation with headquarters is based on evidence. If headquarters still prefers Dynamics after that comparison, the Polish entity at least goes in knowing which gaps it is accepting and who will close them. For context beyond this platform, visit the Poland hub.