Leasing and factoring
Portfolio monitoring and risk control for the life of the contract.
Checked at signing, then silence for three years.
A client goes through analysis before the contract. You check them thoroughly, because at that moment you have the time and the budget for it. Then the contract runs for thirty-six months, and you come back to that company only when the first instalment goes unpaid.
Risk does not follow that rhythm. A company that was fine in January can have an arrears entry in July, change owner in September and move its registered office across the country in November. Each of those is public on the day it is filed – nobody reads them, because the book runs to hundreds of contracts.
Monitoring flips the proportions: the analysis at signing stays a one-off, while the watching becomes continuous and takes nobody's time.
A portfolio that speaks up.
The whole book under watch
Leasing clients or factoring debtors go onto the list once, by tax or registry number. Checks run daily, no matter how many contracts you carry.
A signal before the first missed payment
An entry about arrears to the State, or about ineffective enforcement, usually comes before the client stops paying you. That is your window to make contact before the case turns into collections.
Assignments and reorganisations
Mergers, demergers and changes of legal form bear directly on the contract. The event tells you the counterparty changed shape before the paperwork reaches you.
Review at renewal
Before extending a contract or raising a limit you have the client's whole registry history in one place, with dates – instead of a single snapshot from the day of analysis.
What shows up while the contract runs.
The same events that are evidence in collections are a warning in leasing and factoring – because they arrive while you can still act.
Public-law arrears
Tax, customs and social-security arrears in Section 4 of the KRS. For a leasing book this is the earliest hard signal the registry offers – it appears before the problem reaches your own account.
Enforcement and security over assets
Enforcement discontinued as ineffective, court-ordered security over assets, a bankruptcy petition dismissed for lack of funds. With the leased asset in the client's hands, that is notice you will have to fight for it.
Proceedings and liquidation
Bankruptcy or restructuring opened, liquidation started, an administrator appointed. The entry date decides whether you still make the deadline to file your claim and recover the asset.
Capital and structure
A reduction of share capital, a merger, a demerger, a change of legal form. In a long-term book these change who your counterparty is and what they answer for.
Suspension and change of address
Suspended activity is often the first symptom, and a change of address is a practical problem for service of documents and asset recovery. Both are separate event types.
What you will not find here.
Entiway reads state registries – GUS and full KRS extracts. This is not a scoring system and it does not replace credit analysis:
- No financial statements and no ratios. We will not compute liquidity or leverage – we deliver registry facts and the moment they changed.
- No credit-bureau data (KRD, BIG, ERIF) and nothing from banking registers.
- The event stream carries no changes of people. Individuals connected to companies are in the data – public from GUS, masked from KRS but with the role they hold – they simply feed a separate historical layer that is not yet exposed as events. One exception: a change of partner in a civil or general partnership, and a change of owner of a sole trader business, do come through, because GUS carries them.
- Section 4 covers registered companies. For sole traders the signal is their GUS status: suspension, resumption, removal.
Before you ask.
Can I monitor several hundred clients at once?
Yes – the cost is linear and predictable: 2 credits per company per day. Five hundred clients for a month is 30,000 credits. Above the self-serve ceiling we move to a conversation about individual terms.
Will I get a signal before the client stops paying?
Sometimes yes, sometimes no – and we will not claim otherwise. An entry about public-law arrears or ineffective enforcement usually precedes trouble with instalments. But a company can stop paying without any registry entry, and the registry does not know about your contract.
How do I wire this into a decisioning system?
Through the API – you pull the event stream into your own system and set the thresholds there. Reading events costs no credits, so how often you poll does not affect the bill.
Try it on your own book.
Put a dozen clients from live contracts under watch and see how many events show up in the first month. The starting credits cover a test like that.