KolayBi Integration

You will not find the second field in the panel

The KolayBi setup has two required fields, and they come from different places. You generate the API key yourself under settings → profile account → API keys. The channel value you cannot generate — it has to be requested from KolayBi support. Scanning the panel end to end without finding this field is normal; its absence is by design.

Sending that request up front speeds things up when planning the setup, because the waiting time is not under your control. If you will work against the test environment, factor in that its credentials are separate from production.

What month-end looks like once the connection is in place

The real effect of the KolayBi connection shows up at month-end. Without it you download each sales channel's report separately and merge them by hand, and that work multiplies as channels are added. With the connection in place the sales document moves to the accounting side the moment it exists; month-end turns from a collection task into a review task.

The waiting in the setup comes from having to request the channel value from support. Putting that at the front of your plan brings every remaining step down to a few minutes.

Withholding yes, cancellation no: which work does it suit?

The KolayBi connection issues e-Invoices and e-Archive documents and supports withholding. Withholding support can be decisive for sellers issuing service invoices or working in goods categories subject to it — on a connection without that item you would end up issuing those invoices by hand.

Two items sit outside its scope: you cannot cancel an issued document through this connection, and you cannot book deductions such as commission as expense invoices. Both run from the KolayBi panel.

In practice that means automating the issuing and keeping corrections and expenses manual. As order volume grows it is the issuing step that creates the real load; cancellations and expenses happen a few times a month.