System Integration Consultant, Poland

The integration landscape of a Polish company

I start with an inventory of every system, file and portal around the ERP. In Polish companies, especially subsidiaries, it often covers more counterparts than anyone has listed in one place.

Against every row I note the maintainer, the way a failure would come to light and what the accountant depends on it for. In subsidiaries, some links are owned by group IT abroad, which makes it even more important to name a local owner who knows when something has stopped. The inventory then feeds the ownership decisions that come before any technical choice. My wider system integration approach applies here as well.

KSeF in both directions, including the awkward cases

Sending an invoice to KSeF is the part every vendor demonstrates. The integration design has to cover the rest, and your tax advisor's current reading of the rules is the reference, because scope and timing have shifted before.

• Sending: which event triggers submission, how the KSeF number and confirmation return to the invoice record, and how a rejected invoice is corrected without breaking numbering.
• Receiving: purchase invoices are collected from KSeF on a schedule, matched to suppliers by NIP and to purchase orders or receipts, then routed for approval. Invoices that match nothing go to a review queue.
• Corrections: correcting invoices link to the original in both directions.
• Outages: the design states what happens if KSeF or the ERP is unavailable, following the procedure your advisor confirms, and how invoices issued during that time are submitted later.
• Access: the integration needs authorization in KSeF. Who grants it, which technical user holds it and how it is renewed are written down, because an expired permission can stop invoicing.

Where invoices come from more than one system, such as an ERP and a webshop billing tool, each source needs its own KSeF route or a single hub, and the choice affects JPK consistency too. The Polish ERP business analyst page shows how these cases become requirement lines.

White list checks, split payment and bank files

Payment integration in Poland carries tax consequences, so the controls belong inside the flow rather than in a person's memory.

• Account checks: before a payment run is released, each supplier bank account is checked against the taxpayer register, often called the white list, through the register's lookup service. The result and date are stored with the payment. Accounts that fail go to a named approver with the reason, and your accountant defines when an exception is acceptable.
• Split payment: invoices marked for split payment carry that flag into the bank file, so the VAT portion goes to the supplier's VAT account. Where the rules say the mechanism is mandatory is for your advisor to confirm; the integration makes sure the flag cannot be lost between approval and the bank.
• Bank files and statements: payment files follow the format each bank accepts, and statements return daily for matching. I plan a trial with each bank, including a rejected payment and a split payment.
• Supplier data changes: a new bank account on a supplier record triggers an approval and a fresh register check.

Exchange rates arrive from the National Bank of Poland on a schedule, and the ERP applies the rate type your accountant specifies for each document. A missing rate on a holiday or a late feed should raise an alert, not silently reuse an old value. The multi-currency ERP page covers revaluation in more depth.

Webshops, marketplaces, carriers, payroll and the group

Online sales. Polish webshops and marketplaces bring orders paid through instant transfers, mobile payments and cards. Payment providers settle in grouped payouts net of commission, so the mapping separates sales, fees and the net sum received. Each order must also become a document the ledger can issue: a receipt for consumers or an invoice through KSeF when a business buyer gives a NIP. I specify which system issues what and when, and how returns become correcting invoices.

Carriers. Parcel carriers and parcel locker networks exchange shipment requests, labels and tracking with the ERP or the webshop. I decide which system books the shipment and where tracking is stored, so customer service has one place to look.

Payroll. Payroll is often run by a provider or an accounting office, with social insurance filings handled there. What reaches the ERP is one monthly posting file split by account and cost center; finance signs off the element mapping, and a control check ties it to the provider's payroll totals.

The group. Subsidiaries and shared service centers exchange intercompany invoices and reporting data with a parent ERP abroad. The Polish entity's invoices still go through KSeF, so the design states which system issues them and how the group receives the data it needs. Ecommerce and manufacturing companies usually carry several of these flows at once.

Method, testing and keeping integrations alive

Every flow gets its own route decision, chosen among built-in ERP features, an extension from the publisher or a Polish specialist firm, a middleware platform, purpose-written code or plain file exchange. I score them on reliability, running cost drivers, who supports them and how quickly they follow rule changes. In Poland that last point carries extra weight, because KSeF and related requirements have changed more than once, and the contract should say who updates the connector and how fast.

Testing uses the KSeF test environment where the vendor supports it, plus Polish cases from your business: an invoice to a domestic buyer, a correcting invoice, a purchase invoice with no matching order, a payment run with a failed account check, a split payment, a foreign currency invoice using the correct rate, a marketplace refund and a payroll correction. Before approval, your accountant sets a trial JPK file against the ledger.

After go-live, named people are alerted when a submission fails, a permission is about to lapse or reconciliation totals drift apart, and written procedures describe safe resubmission. Engagements run remotely; on-site days happen only by arrangement. For the commercial end of these flows, see CRM consulting in Poland, and the full ERP picture under ERP consulting for Polish companies.