Compliance and KYC
Changes that matter for compliance, each with a date and full context.
Verification is not a photograph. It is a film.
The procedure usually ends with a printout: we checked the counterparty, there is a file, there is a date. A month later the company changes its name and legal form, six months later its registered office – and the file still describes last year.
Under inspection or audit the problem is rarely that you did not know something. The problem is that you cannot show when you found out – and whether anything happened between two checks that should have raised a flag.
Entiway gives you continuity instead of points in time: every registry change arrives as its own event, with the old value, the new value and the entry date.
Four things for a compliance team.
Verification before onboarding
You look a counterparty up by tax or registry number and get their registry state: name, legal form, registered office, status, business activity, identifiers.
Continuous monitoring instead of reviews
Rather than periodically refreshing your whole counterparty base, you watch it continuously. The periodic review stops being an exercise and becomes a look at what the system already caught.
A time trail for audit
Every event carries the registry entry date and the day of detection. That lets you reconstruct what was known and when, without rebuilding it from emails.
Thresholds by severity
Events carry a class and a severity, so your procedure can tell routine from a signal that needs a decision – a new fax number and a new tax identifier are not the same thing.
Changes that matter for compliance.
All of them arrive in the same shape: event type, old value, new value, entry date and severity.
Identity of the entity
A change of name, of legal form, a transformation and above all a change of registration identifiers – that event carries the highest severity, because it means the identifier in your database no longer points where it used to.
Registered office and branches
Changes of registered address, branches opened and closed. Relevant wherever your procedure depends on jurisdiction, competent authority or service of documents.
Proceedings and status
Bankruptcy, restructuring, liquidation, suspended activity, removal from the registry. Each a separate dated event rather than a lumped "status change".
Business activity
Activity codes added, removed and changed, with a change of the principal activity called out separately. A counterparty that changes its profile is often one you need to assess again.
What you will not find here.
This matters especially for KYC, because some of what people expect from such tools simply is not in business registries:
- No ultimate beneficial owners. The UBO register is a separate registry and is not one of our sources.
- No sanctions or PEP lists. We neither maintain nor resell such lists.
- 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. If a complete picture of individuals is your primary use case, tell us – it changes our order of work.
- We do not assess compliance. We deliver registry facts and their chronology; the decision and its documentation stay with you.
Before you ask.
Are the events usable as audit evidence?
They carry what you need to reconstruct a chronology: the type of change, the value before and after, the registry entry date and the day of detection. The registry remains the source of law – we show what changed in it and when.
How far back does the history go?
Events carry a registry date that can reach back years, plus the day we detected them. Read those two axes separately: the first says when the change happened, the second when it appeared in our data.
Is personal data in the stream?
Events describe businesses, not people. The layer covering individuals connected to companies is kept separately and does not enter the event stream today.
Try it on your own counterparty base.
Take a dozen counterparties you verified last year and see what has changed since. The starting credits cover a review like that.