Name changes in monitoring: why there is no “edit” function

Marriage, rebranding, a change of legal form: a business partner’s name changes and your monitoring list still shows the old one. There is deliberately no function to overwrite a record. Instead you add the new name alongside the old one and let the old one keep running for a while. This article explains why that is not a detour but the safer route – and what to do in practice.

Why can’t I simply overwrite a name?

Because an overwritten name would never have been screened in full – and nobody would notice. There are three reasons; the first is the decisive one:

1. A renamed record would never see the existing list content

Here is how monitoring works: every record is screened once against the entire list content when it is created – against everything on the lists at that moment. From then on it takes part in the ongoing comparison and, at each screening run, is only compared against entries that have been added since its last check. That is the only reason many thousands of records can be compared daily against lists holding millions of entries.

Exception: very short names of one or two characters may be skipped by the automatic screening – the record then counts as screened even though no comparison took place. So always enter business partners with their full name: Li Trading Ltd. rather than Li.

A renamed record would keep its screening timestamp. The new name would therefore never be screened against the existing content – from that point on it would only ride along in the delta.

Example. In 2024 you add Meier Handels GmbH. The initial screening runs against the entire list content: no hit. In 2026 the company is renamed Nordstern Trading GmbH. A Nordstern Trading Ltd. has been on the sanctions list since 2021.

• If you overwrote the record, that 2021 list entry would be older than the record’s last check – it would never come up for comparison again. The hit would never appear. And it would go unnoticed: in the overview the record would look exactly like any other screened record.
• If you create a new record, the new name starts with an initial screening against the entire list content – and the 2021 entry is found.

This is the real reason. It is not about a missing convenience feature, but about the fact that renaming would create a silent screening gap.

2. The old name is your second chance at a hit

Sanctions lists carry every person and every organisation with all known name variants: aliases, former company names, alternative spellings, transliterations from other scripts. easycompliance screens your records against all of these variants, not just the primary name.

The reverse case is the interesting one: when an authority newly lists someone, it uses the name it can substantiate – not necessarily the one currently in the commercial register or in the passport. Months or years often pass between the conduct being sanctioned and its publication.

That last case is the best evidence that this is not a theoretical risk: easycompliance additionally screens vessels by their IMO number, because it does not change over a ship’s lifetime – whereas the name does, and not by accident. Changing names is a well-known way of evading screening. Anyone who deletes the old name immediately loses precisely the trace that, in such a case, is the only one that matches.

Sanctions apply to the person or organisation, not to a string of characters. Two names for the same entity are therefore not an error in your list but two ways of reaching the same target.

3. Assessments belong to the record – and the record belongs to the name

A hit is stored with the name under which it arose: together with the time, the list entry that matched, and your assessment including its comment. That is exactly what makes it evidence years later.

Overwriting would silently transfer that assessment to a different name. A record you rated “False Positive” in 2024 would carry a different name in 2026 – and that other name would count as already screened and assessed, although it never was. In an audit you would have to explain why your documentation shows an assessment for a name that was not being monitored at the time. There is no way to make that explanation work.

Deleting the record does not destroy your hit history. Hits already recorded are retained – with the hit result, your assessment and your comment – and remain visible in the hits overview even once the name is no longer in monitoring. Adding and removing records is additionally recorded in the event log.

If you need evidence about the record itself, create it before deleting. Export the hit list as a CSV file and, if you want to evidence the population you were monitoring, the CSV status report of your monitoring list as well. Those files are then in your own hands and do not depend on what remains traceable inside the system – that is the most robust evidence you can hold.

Deleting and re-creating is therefore the audit-proof route; overwriting would not be.

Step by step: what to do when a name changes

1. Add the new name alongside the old one. Open “Automated Screening (Monitoring)” → “View/Edit List” and enter it under “Add a single name” in the “Name / Company name” field. For several changes use “Bulk add” or the “Import Data” menu item.
2. Use the same reference as the old record if you work with references – that keeps the two entries visibly related in your exports. If your account detects duplicates by reference, the form will otherwise report “Reference already exists.”; in that case switch “Detect duplicates by” to “Name”, or clear the “Skip duplicates (recommended)” checkbox for this one entry.
3. Wait for the initial screening. After adding, the message “The name was added successfully and is being checked in the background.” appears. Screening does not run immediately but with the next automatic run – and then against the entire list content.
4. Leave the old name in place for now. For how long is your decision – there is no fixed requirement, and easycompliance does not impose one. Base it on your own risk assessment and on the retention and due-diligence obligations that apply to your business. Put the period and your reasoning in writing – that is the decision an audit will ask about.
5. Remove the old name deliberately, later. Individually via the Delete action in the table, several at once via “Bulk delete”, or – for larger volumes – via the “Delete Data (via Import)” menu item using a deletion list. Beforehand: if you need to document the operation, export the hits and the list status as CSV files (see Good to know).
6. Fix the source. Change the name in your ERP, CRM or merchandise management system as well. Otherwise the next import brings the old name back and you end up with a permanent duplicate.

Good to know

• Secure whatever you need to document before deleting. The deleted record itself is gone afterwards. Two exports are enough: Exporting hits as a CSV file and Exporting a CSV status report.
• A typo is not a name change. If a name was simply captured incorrectly (“Musterr GmbH”), there is no reason to keep it: the wrong name identifies nobody. Delete it and create it correctly. The waiting period from step 4 applies only to names that were genuinely valid at some point.
• Both entries count as records. An old and a new name are two entries in monitoring and count towards your record total accordingly. What that means for your account depends on your billing model – see Billing models: transaction- vs. record-based.
• Expect a hit notification for the new name. If the old name once produced a hit that you assessed, that does not automatically carry over: as far as the system is concerned the new name is a new record and is screened and assessed in its own right. This is intentional – an assessment should deliberately attach to a name rather than be inherited.
• “Reset” is not “rename”. The Reset action keeps the name and returns the record to “not yet screened”: at the next run it is screened against the entire list content again (“Record was reset. It will be checked again during the next screening.”). Your existing hits and their assessment are retained and stay visible in the hits overview; if the renewed screening produces a hit again, an additional entry is added. Reset is the right tool when a record should be screened in full once more – but it is no substitute for a new name.
• This applies in every module – sanctions lists, PEP and Dow Jones behave identically.
• Never delete before updating. That rule is unaffected: to update your list, simply upload a new file; existing records are skipped as duplicates. Details: Deleting or resetting records.

Frequently asked questions

Why can’t I edit a business partner in monitoring? Because an overwritten name would never be screened against the existing list content. Every record is screened in full once when it is created, and after that only against newly added list entries. A renamed record would keep that screening state – an existing listing under the new name would go undetected permanently, without anyone noticing. On top of that, your hit assessments belong to the record and would transfer to a name that was never screened under that assessment.

A business partner got married / the company was renamed. What do I do? Add the new name alongside the old one and leave the old one in monitoring for now. Delete the old name only after a period you define and document yourself. Also change the name in your source system so the next import does not bring the old name back.

How long should I keep the old name in monitoring? There is no fixed requirement, and easycompliance deliberately does not name a period – it depends on your risk assessment and your own due-diligence obligations. The decisive consideration: a considerable time often passes between sanctionable conduct and its publication, and during that window a listing may still carry the former name. The higher the risk – sanctions exposure in the surrounding network, vessels, high-risk countries – the more that argues for keeping the old name running permanently. Set the period in your compliance rules and document the reasoning.

Isn’t this a purely theoretical risk? No. Sanctions lists explicitly carry aliases and former company names as separate name entries, and listings regularly use names that are already out of date when published. Deliberate name changes are also a well-known evasion pattern – which is why vessels are additionally screened by their unchanging IMO number.

It was just a typo – do I have to keep the wrong name as well? No. A misspelling identifies nobody. Delete the faulty record and create it correctly. Also fix the error in your source system.

Does deleting destroy the evidence that the old name was screened? Not your hit history: hits already recorded remain in the hits overview with their hit result, assessment and comment, even after the record has been removed. The record itself is gone once deleted. If you must evidence that a particular name was in monitoring at a particular time, export the hits and the list status as CSV files before deleting.

Do I have to assess the hit for the new name again if I already rated it “False Positive” for the old one? Yes. The new name is a record in its own right and is screened and assessed independently. Assessments are deliberately not transferred – otherwise a name that was never screened would count as cleared.

Can I remove many old names at once? Yes. Under “Bulk delete” you enter one name per line; for larger volumes use the “Delete Data (via Import)” menu item with a file. Both are irreversible; hits already recorded are retained either way. Secure whatever you need to document beforehand.

Requirements

• An account with permission to edit lists. Without it you will not see the functions for adding and deleting; attempting to use them shows “You do not have permission to edit lists.”
• The relevant module must be enabled for your account.

Related articles

• Deleting or resetting records
• Adding names to your monitoring list
• Deleting records via file import
• Rating a hit as false positive or positive
• Exporting hits as a CSV file

Last reviewed: 2026-08-07