System map
We list what runs in the business, such as ERP, shop, CRM, WMS, Microsoft 365 and sector software, along with everything that is currently typed in two or three places.
Almost anything can be connected technically. The hard part is agreeing internally where the authoritative version of each customer, item, price list and document lives.
We list what runs in the business, such as ERP, shop, CRM, WMS, Microsoft 365 and sector software, along with everything that is currently typed in two or three places.
Direction and frequency of every exchange, plus the owning system for contractors, items, stock, price lists and orders. The result is one diagram that the board can follow too.
Sending invoices from your system to the National e-Invoicing System, fetching purchase invoices and handling UPO receipts. PEF for public sector buyers as well.
For public offices and local authorities: taking in letters from ePUAP and e-Doręczenia into the case system or EZD RP and sending replies back without copy and paste.
Queues, retries, duplicate guards and a notification to a named person when a document needs a human decision rather than another attempt.
We watch every run. If an integration stays quiet longer than usual, the person responsible is alerted before a customer notices anything.
A simple link between two systems with ready APIs is a much shorter job than several systems sharing master data. We give a schedule once the data has been reviewed.
We review the data on both sides. Duplicate contractors and mismatched records almost always turn up and need sorting out before go-live.
Flows, precedence rules, conflict handling and VAT Act requirements wherever invoices are involved.
On the KSeF test environment and on copies of your data with personal details removed, never on made-up samples.
For a short while both the old manual routine and the integration run in parallel; then the copy-typing ends and monitoring takes over.
Most sync clashes start when one field can be changed in two places. Sales update a client's address in the CRM, accounts fix it separately in the ERP, and the next sync wipes out one of the edits. We therefore name an owning system for each kind of record before go-live and make that field read-only in the rest.
Options still exist: CSV or XML drops, direct database reads or vendor mechanisms such as Sfera in Subiekt nexo. None is as robust as a supported API and each needs attention whenever the software is updated, but they generally get the job done. Sometimes upgrading the ERP turns out cheaper.
Many popular accounting packages have their own KSeF support, so check what your vendor offers first. We write an integration when invoices are generated in a line-of-business system, a web shop or your own application, or when purchase invoices must be matched to orders automatically.
Seldom. The majority of processes are fine on syncs every few minutes, and that setup copes better with outages. Real time makes sense for shop stock levels, where every unit sold counts.
Our support contract defines reaction times and who owns what. Most failures are caused on the other side, by a supplier changing its API or a certificate expiring, so we monitor external system responses as well as our own code.
List the applications between which data is still copied by hand. You will get an estimate and a note on any clean-up needed first.
Your enquiry has reached us
You will hear back within one working day, and if you have reported an outage that is holding up work, it goes to the front of the queue.
No match for that name. Try a different spelling or pick a bigger town nearby - all our support is delivered online, so your choice has no effect on the service.