Skip to content

Contact Info

Poland

Checking a Polish ERP before the next close goes wrong

Which areas does an ERP audit in Poland examine?

An ERP audit for a company in Poland reviews a live system, separate from the statutory audit. I trace KSeF submissions and incoming invoices, compare JPK files with VAT registers and the ledger, test payment controls such as account checks and split payment, check the exchange rate setup, review access across shared service companies and deliver prioritized findings with questions for your tax advisor. The work is remote.

Last reviewed by Vikas Saroj

Polish entities often run an ERP that was configured quickly, sometimes as a localized copy of a group template, and then left to the local finance team. Invoices reach KSeF, JPK files are sent and payments go out, yet the controller spends each close reconciling registers by hand and nobody is sure who can change a supplier's bank account.

I perform independent ERP audits remotely for subsidiaries, shared service centers and manufacturers in Poland. The audit covers configuration, controls, interfaces and reports. It is not the statutory audit performed by a registered auditor, it offers no comfort on the accounts, and your chief accountant, accounting office and tax advisor keep their responsibilities.

No vendor or implementer pays me, so the report has no reason to favor a product or extra development. The engagement runs in English; Polish screens, registers and documents are reviewed with a member of your finance team who explains them in context.

Dynamics 365 Business Central Item Ledger Entries page in analysis mode, showing an Inventory on Hand view grouped by item number with the analysis filters pane
  • KSeF statuses in and out
  • JPK totals against registers
  • Account checks and split payment
  • Exchange rate source and revaluation
  • Shared service access rights
  • Group template versus local needs
Audit Areas

What the audit examines in Poland

Findings are ranked by business risk, and tax-related points are written up for your accountant or tax advisor to decide.

KSeF Flow Review

Outgoing invoices traced to their KSeF identifiers, refused submissions and how they were corrected, and incoming invoices on the platform compared with what has actually been registered in the ERP.

JPK Reconciliation

Sample JPK files compared with VAT registers and the general ledger, with differences traced to their source in master data, document types, manual journals or warehouse postings.

Payment Controls

How supplier bank accounts are checked against the VAT payer register, where split payment is flagged, and who can create, approve and release payment batches, tested against the duties you want separated.

Currency Setup

The exchange rate source configured for PLN books, the date logic applied to foreign currency documents and the revaluation routine, compared with what your accountant has specified.

Group and Local Views

How the local chart, statutory reporting and group mapping coexist, which adjustments are made outside the system, and where a group template leaves Polish needs to spreadsheets.

Access, Interfaces, Licenses

Roles across many companies in a shared service center, dormant accounts, the payroll journal from your provider, interfaces with banks and group systems, and licenses that are paid but unused.

How I Work

The audit step by step

Plan

Agree scope with local and group

01
Request an Assessment
  • Local and group concerns
  • Entities and systems listed
  • Viewing access arranged
  • Interview list agreed

Analyze

Records compared across systems

02
Discuss Your Project
  • KSeF and ERP samples
  • JPK versus registers
  • Payment batch walkthrough
  • Roles exported and tested

Conclude

Prioritized findings with owners

03
Talk About Next Steps
  • Findings checked with owners
  • Advisor question list
  • Readout for local and group
  • Order of fixes proposed

An ERP review for Polish entities, not the statutory audit

Many companies in Poland already go through a statutory audit by a registered auditor, so it is worth being exact. This review treats the ERP as a tool the entity depends on every day. It asks whether the configuration matches how the entity operates, whether its controls stop the errors they are meant to stop, how data moves to KSeF, the tax authority, banks and the group, and whether reports can be relied on. It produces no audit opinion and no tax advice.

The request tends to come at familiar moments:

  • A new finance director or group controller wants an independent view of what the Polish entity runs.
  • Month-end in Poland keeps taking longer, and the reasons given are vague.
  • The group plans to extend its template or move the entity onto a new platform and needs a baseline first.
  • A shared service center is taking on more companies and wants to know whether its setup will scale.

I work from interviews with finance, purchasing, logistics and IT, screen-shared sessions where staff complete real tasks, and viewing rights to configuration and data. Where the group runs the system centrally, I agree access through the group IT team. Draft findings are discussed with the people concerned before they enter the report. The Polish layer described here builds on my standard ERP health check method.

Is KSeF being watched in both directions?

Poland has been moving business invoices onto the national e-invoicing platform, and the scope and timing have changed more than once, so what applies to your entity is for your tax advisor to confirm. Once a connection exists, though, the audit question is practical: does anyone act on what comes back, and is everything that arrives actually processed?

On the outgoing side I sample invoices across several weeks and check:

  • that each one carries its KSeF identifier in the ERP;
  • which submissions were refused, why, and how the corrected invoice was sent;
  • whether correcting invoices link properly to the originals;
  • what happened on days the connection was unavailable, and whether that procedure was agreed with your accountant.

On the incoming side I compare what suppliers have placed on the platform for your entity with what has been registered, matched and approved in the ERP. A gap here means costs and input VAT that are missing from the books, or suppliers paid from a PDF while the structured invoice waits unprocessed.

The audit also notes who monitors the connector, where errors are logged and whether alerts reach a person. Many KSeF problems are not configuration faults but ownership gaps. Points touching tax treatment become questions for your advisor; system causes go into the fix list. For how these flows should be designed in a new project, see my Polish implementation page.

JPK totals, VAT registers and the ledger

A JPK file that passes technical validation can still disagree with the ledger. When that happens, someone in the accounting team adjusts it by hand every period, which is both slow and risky. I take sample periods and compare three things: the JPK file as sent, the VAT registers in the ERP and the VAT accounts in the general ledger.

Differences are grouped by cause:

CauseTypical evidence
Master dataMissing or inconsistent tax identifiers, wrong country on customers or suppliers
Document typesDocuments posted with a type that maps to the wrong part of the file
Manual journalsEntries on VAT accounts that bypass the register logic
TimingPurchase invoices registered in a different period from the one used in the file
WarehouseStock movements and invoices that do not agree on value or date

For each cause the report shows how often it occurs and where it should be fixed, ideally at entry, with mandatory fields or posting controls. Whether a given item belongs in a particular period or section is decided by your accountant or tax advisor, not by me.

This is often the most valuable section for the chief accountant, because it turns a recurring manual adjustment into a short list of system changes. Lighter follow-up belongs under ERP optimization.

Payment controls, account checks and exchange rates

Payments carry specific Polish controls that an ERP should support rather than leave to memory. I walk through a payment batch from proposal to release and check:

  • whether supplier bank accounts are checked against the VAT payer register before payment, and how mismatches are handled;
  • where the split payment flag is set on invoices and whether it flows into the bank file;
  • who can create a supplier, change its bank account, approve invoices and release the batch, and whether a single employee holds every one of those steps;
  • whether the bank portal's approval rules match those in the ERP, or whether one bypasses the other.

The rules on which invoices require these controls are for your tax advisor; the audit shows whether the system applies the rules they have set.

Exchange rates get a separate look. Polish books are kept in PLN, while many entities invoice or buy in euros. I check which rate source is configured, which date the system uses for each document type and how revaluation is run at period end, then compare it with what your accountant specifies. A generic rate setup inherited from a group template is a common source of small, recurring differences.

Where the fixes involve the bank interface or group systems, they connect to my ERP integration work.

Shared service access, group templates and the written findings

Shared service centers in Poland often run one ERP across many companies, with staff holding roles in several of them. Over time access spreads: a team lead covers for a colleague, a project account stays open, a consultant from the implementer keeps administrator rights. I export roles per company and test them against the duties your management wants separated, then list dormant and shared accounts. Access to salary data and other personal records is reviewed with GDPR in mind, leaving interpretation to your data protection officer.

Group templates get a fair assessment. I list the Polish needs the template covers, those handled by local extensions and those left to spreadsheets, so the group and local teams can discuss gaps on facts. The payroll journal from your payroll provider or accounting office is checked for mapping and reconciliation, and licenses are compared with real use.

The report brings it together: a summary for local and group management, findings ranked by business risk, a question list for your accountant and tax advisor, and a proposed sequence of fixes. I present it online during the Polish morning; meeting in person can be arranged. If the findings point to deeper trouble, my ERP rescue service in Poland follows on. The Poland hub and my Polish ERP consultant page cover my other services for Polish companies.

Not sure where to start?

Tell me about your business and current systems. I’ll suggest the most sensible first step.

Book a Consultation
Related

Related Services

  • ERP Health Check
  • ERP Optimization
  • ERP Integration
  • Independent ERP Second Opinion
  • Microsoft Dynamics 365
Poland

More for Poland Businesses

  • Poland overview
  • ERP Consultant
  • Freelance ERP Consultant
  • ERP Business Analyst
  • ERP Requirements Consultant
  • ERP Selection Consultant
  • ERP Implementation Consultant
  • ERP Rescue Consultant
  • CRM Consultant
  • System Integration Consultant
Other Markets

ERP Audit Consultant Elsewhere

  • USA
  • UK
  • UAE
  • Saudi Arabia
  • Qatar
  • Oman
  • Kuwait
  • Bahrain

Not sure which ERP you need?

Do not choose software first.

Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.

  • Independent ERP advice before you invest - I do not resell software
  • Work directly with Vikas - no account managers or junior handoffs
  • Business analysis before software implementation
  • One consultant who understands both your business and the technology
FAQ

Questions About ERP Audit Poland

No. A registered auditor's work ends in an opinion on the financial statements. The ERP review examines configuration, controls, interfaces and reports, and gives no assurance on the accounts. The two do not overlap, although control weaknesses found in the ERP review, such as unreconciled JPK files, can be useful context for the auditor and your accountant.

No. Whether your setup meets current obligations is for your tax advisor to judge. The audit shows how the flow behaves: identifiers stored, refusals handled, incoming invoices registered, outages managed and monitoring owned. Each tax-related observation is written as a question for your advisor, and system causes go into the list of fixes.

Yes. Access is arranged through the group team, and the audit looks at how the template serves the Polish entity: what it covers, what local extensions add and what is left to spreadsheets. The findings give local finance and group IT a shared, factual list to plan from.

No. Its scope is your own ERP plus the files passed to and from the accounting office or payroll provider, such as the payroll journal or exported registers. I check how those files are produced, imported and reconciled, but I do not inspect the office's own software or working papers.

Still have questions? Let’s talk them through.

Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.

Book a Consultation
Vikas Saroj seated at a meeting table with a laptop and notebook
Working Model Remote · Worldwide
Email Address hello@vikassaroj.com
Book a Consultation

Let’s Discuss Your ERP Audit Poland Project

Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.

Chat on WhatsApp