Who this connection is for
inFakt runs in the browser and combines an invoicing tool with accounting services. It is mostly used by companies that do not run a full ERP system but still want online sales to land in their books without anyone touching them. If your accountant works in an inFakt account, the integration removes one task from their list: retyping invoices from the shop.
The flow goes one way. The platform is the source of the sales document and inFakt is its recipient. Data travels directly through the inFakt API, with no file export and no manual import.
An invoice’s path, step by step
- The order is confirmed. The invoice is created on the platform: automatically at the order status set in the configuration, or manually when an administrator issues it.
- The platform hands the document over to inFakt with the full dataset: the buyer and the line items.
- Every handover leaves a trace on the deliveries list in the sales section of the admin panel. That is where you check which invoices have reached the accounting system.
- If routing is set that way, inFakt performs the submission to KSeF, Poland’s national e-invoicing system.
Along the way the platform keeps its own mapping of customers and documents, so it knows which customer and which invoice on its side corresponds to which record at the vendor.
Two decisions you make at rollout
The connection is configured once, in the admin panel. Apart from the link to the inFakt account itself, there are two things to set. Both have accounting consequences, which is why changing them requires confirmation.
| Setting | Platform-side option | inFakt-side option |
|---|---|---|
| Invoice numbering | Endora Commerce assigns the number using its own numbering pattern | inFakt assigns the number |
| KSeF submission | The native KSeF integration built into the platform | inFakt performs the submission |
In practice it is worth agreeing this with your accountant before go-live. If you also issue invoices in inFakt outside the shop, a single numbering sequence on the inFakt side avoids two parallel series. If the shop is your only source of sales, platform numbering gives you full control over the number pattern.
What to prepare on the inFakt side
- An inFakt account and an API key. The inFakt API is REST with JSON payloads, and access is authorised with a key generated in the user account. Details are in the inFakt API documentation.
- A test environment. inFakt provides a sandbox with separate limits, so the first documents can be checked without any risk to real accounting data. Information for integrators is on the developers page.
- KSeF authorisation in inFakt. This applies to the option where inFakt submits the e-invoices. Linking the account to KSeF is confirmed on the inFakt side, among other ways with a Trusted Profile (Profil Zaufany). It is a step outside the platform and has to be done before the first invoice.
Limits worth knowing about
- One accounting system at a time. The platform allows only one invoicing vendor to be active. inFakt will not run in parallel with wFirma or Subiekt 123.
- Switching it off does not erase history. When you disable the connection, its tab disappears from the panel, but the list of delivered documents stays.
- It is not a stock integration. inFakt receives invoices. Stock levels, price lists and product records are not driven by it.
inFakt or something else
Choose inFakt if your company or your accounting office already works in it and you want to keep a single source of truth for the books. The same holds for the other systems in this group: what decides is where your accountant has an account, because the way the connection works is shared.
Consider another route in two situations. First, when invoices are issued by your ERP system, for example Comarch ERP Optima or Subiekt GT: a second invoicing system would then only duplicate documents. Second, when you do not need an external invoicing tool and it is enough for the platform to issue the document itself and send it to KSeF.
