Business Central Consultant in Poland

Who provides the Polish features in Business Central?

For Business Central, country support either ships from Microsoft or arrives as an app built by a partner firm that layers on local tax logic, reports and document formats. Which model applies to Poland, and what it covers for the version you would license, should be confirmed with Microsoft and the partner in writing. A general answer in a sales meeting is not enough.

Where a partner app supplies the Polish layer, these are the risks I examine:

• Publisher and implementer: if the app vendor is also your implementer, could you switch implementers later and still get the app supported?
• Track record: how quickly have updates followed past Polish rule changes, such as e-invoicing and statutory file revisions?
• Coverage: VAT registers, statutory files, KSeF exchange, Polish document layouts, fixed asset rules and exchange rate handling, each confirmed rather than implied.
• Licensing: whether the app is charged separately, and on what basis.
• Upgrade compatibility: how the app keeps pace with Business Central's regular update cycle.

Answers go into a short due diligence note for your CFO and the parent's IT lead. The wider questions about Dynamics in Poland, including group templates and the KSeF extension layer, sit on my Dynamics 365 in Poland page.

Posting groups that separate Polish VAT cases

In Business Central, the accounts and VAT entries behind every sales line, purchase line and inventory movement are decided by posting groups. When they are designed carelessly, Polish finance teams end up correcting VAT with manual journals, and those corrections then distort statutory files.

With your chief accountant, I design the combinations your business actually needs:

• VAT business posting groups for customer and supplier types: domestic, EU business, non-EU, and any special category your accountant identifies.
• VAT product posting groups for goods and services at different treatments, including exempt items and services subject to reverse charge.
• VAT posting setup combining the two, with the correct VAT accounts, reverse charge settings and statement mapping for every pair that occurs.
• General business and product posting groups that route revenue, cost and inventory to the right accounts by market and product family.
• Inventory and customer or vendor posting groups that keep receivables, payables and stock accounts clean.

I then run test documents for every combination your business uses and compare the VAT entries with what your accountant expects. Combinations that should never occur are left blank so the system blocks them. Your accountant owns the tax judgment; the configuration simply has to carry it out every time.

Dimensions and charts for local books and group reporting

Polish subsidiaries often need to report two ways: Polish statutory books in PLN and a monthly pack in the parent's chart and currency. Business Central offers several tools for this, and the choice should be made early.

• Dimensions: the global dimensions are the ones you filter on most often, such as plant or cost center, while shortcut dimensions add product line, project or group reporting codes. Default dimension rules on customers, items and G/L accounts keep entries complete without relying on users.
• Chart design: either a Polish statutory chart with each account mapped to a group account, or a group-led chart with local detail added. Your accountant and the parent's controllers decide which suits statutory needs.
• Financial reports built on account categories and dimensions to produce the group pack directly from the ledger.
• Consolidation features where the parent also runs Business Central, with currency translation handled per group policy.
• Additional reporting currency if the parent wants every entry also held in EUR.

These decisions are captured in a brief finance design note, with worked examples of how a typical sale, purchase and stock movement will post. That gives the partner a clear target and gives you a basis for testing. For group structures beyond Poland, read the multi-company ERP page.

Reading a partner's statement of work

Licenses and most project delivery for Business Central come through firms in Microsoft's channel. Because I sit outside that channel entirely, with nothing to sell, I can read a statement of work with only your interests in mind. The questions I ask of a Polish project:

• Scope by process: are selling, buying, stock, production, fixed assets and the month-end close described with what is included, or only module names?
• Apps assumed: which localization, e-invoicing, banking and reporting apps the proposal relies on, who publishes them and whether their cost is included.
• Data migration: which records are migrated, how many years of history, who cleans data, and who signs off reconciliations.
• Testing: whether the partner tests only its own build, or supports your acceptance testing with Polish scenarios, and who writes the scripts.
• Language: who provides Polish-language document layouts and user training.
• Assumptions and exclusions, often where cost grows later, such as integrations, custom reports and statutory changes after go-live.
• Change control and support after launch, including how localization updates are applied.

I return an annotated statement of work with questions to put to the partner, and where several bids exist, a side-by-side comparison on the same requirements. My method is described under vendor proposal review.

When Business Central is the wrong shape for a Polish entity

Business Central suits many Polish subsidiaries and mid-sized companies, but I would raise questions when:

• The Polish localization app looks fragile, with a small publisher and a history of slow updates, and no alternative publisher is available.
• The entity is a standalone SME with no Microsoft-based parent, where an open platform such as Odoo in Poland might cost less to run and still meet production needs.
• The parent runs Finance and Operations and expects consolidation and shared services on that tier, which may make a separate Business Central instance awkward.
• The real problem is sales and service, not finance, where adding a CRM next to the ledger you already run could solve it.

Sessions run remotely and in English, scheduled inside the shared part of our working days, and often include people from the parent company. Training material and document layouts in Polish are produced by the implementer or bilingual colleagues on your side. For broader context, see my Polish ERP consulting page, the Poland hub and the testing and UAT service I use when it is time to accept the build.