Skip to main content

Entities, holders, contacts and addresses

This page covers managing the data of an entity and of its associated elements: holders, contacts and addresses. To understand the concept of an entity and the roles it can take on, see Entities, holders and contacts.

An entity may be associated with several certificates and certification bodies. Before changing or removing shared data, confirm the impact. Entity sharing and shared contacts have their own rules.

Add entity

Creates a new entity in the system, identified by its tax number (NIPC or NIF), which is unique. If in doubt, consult the SICAE - Sistema de Informação da Classificação Portuguesa de Atividades Económicas (Portuguese Economic Activity Classification Information System).

The tax number (NIPC/NIF)

Forest HUB identifies each entity by the exact equality of its tax number, in the form, in the Excel file and in entity sharing. A number written with spaces does not match the same number written without them, and used to create a duplicate record without anyone noticing. That is why the NIPC/NIF field follows format rules, the same in the form and in Excel:

  • Only the number. No spaces, tabs or line breaks, before or after.
  • Allowed characters: digits, letters, dot and hyphen. Foreign formats such as CHE-100.963.407TVA or 39-3569149 remain valid. Lower case is converted to upper case.
  • A number with 9 digits only is treated as a Portuguese NIF/NIPC and the check digit is verified.
  • A foreign number with 9 digits must carry the country prefix, for example GB749933773 (UK VAT). Without a prefix, the application assumes it is a Portuguese NIF with a typo and rejects it.
  • In the form, spaces are removed automatically when leaving the field. In an existing record, the saved NIPC always passes, even if it does not follow the rules, so as not to block editing the other fields: the number is only validated when it is changed.

Messages of the NIPC/NIF field when a rule fails (shown in Portuguese by the application):

  • «O NIPC/NIF não pode conter espaços, tabs ou quebras de linha. Escreva só o número.» (The NIPC/NIF cannot contain spaces, tabs or line breaks. Write only the number.)
  • «O NIPC/NIF só pode conter dígitos, letras, ponto e hífen.» (The NIPC/NIF can only contain digits, letters, dot and hyphen.)
  • «O NIF 749933773 não é válido (dígito de controlo). Se for um número estrangeiro de 9 dígitos, acrescente o prefixo do país (ex.: GB749933773).» (The NIF 749933773 is not valid (check digit). If it is a foreign 9-digit number, add the country prefix, e.g. GB749933773.)

In the Excel file the same rules apply to the NIF/NIPC column of the Membros (Members) and Sites sheets: see Import data (Excel).

What is public

In the public certificate search, the Entidade Titular (Holder entity) block only shows the NIPC when the entity is a legal person: a Portuguese NIPC starting with 5 or 6, or a foreign number with letters (for example DE…, B15787963, GB…). For natural persons (NIF starting with 1, 2 or 3), undivided estates (7) and other cases, the field does not appear: the NIF of a natural person is never published. Members and sites never show the NIF/NIPC in the public search, only the name.

Edit entity

Changes the data of an existing entity (legal name, activity and the remaining fields).

Remove entity

Removes an entity from the system. This is not reversible and must only be used for entities created by mistake and without dependencies.

Merging duplicate records

Administration panel action, reserved for the PEFC team (users with permission to delete entities). It does not exist in the CB or Holder panels.

When to use it

When the same entity exists in two records, for example an old record with NIPC «FAKE…» and the real record, and the NIPC cannot be corrected because «Já existe uma entidade no sistema com este número fiscal» (an entity with this tax number already exists). The merge moves everything in the wrong record to the right one and deletes the wrong one.

Before merging, confirm that this is really the case: a simple «FAKE…» record, whose real NIPC does not yet exist in another record, is corrected in the record itself by changing the NIPC; a «FAKE…» record with nothing attached is deleted with Remover a entidade do sistema (Remove the entity from the system). Only duplicate records whose NIPC is already taken need a merge.

Where

In the entity list, through the icon of two converging arrows, Fundir com outra entidade (Merge with another entity), or through the button with the same name in the header of the entity page. The record where the action is opened is the source, the one that will disappear. The Sem NIPC/NIF (Without NIPC/NIF) filter of the list shows the records with NIPC «FAKE…».

Steps

  1. Open the action in the source record (the wrong one).
  2. In Ficha de destino (a que fica) (Destination record, the one that stays), search by name or NIPC and choose the right record, usually the one with the real NIPC.
  3. Read the preview. Nothing is changed at this step.
  4. Tick Revi a pré-visualização e confirmo a fusão. A ficha de origem será eliminada. (I have reviewed the preview and confirm the merge. The source record will be deleted.)
  5. Click Fundir (Merge). If the action was opened on the entity page, the application then opens the destination record.

What the preview shows

  • The two records: the source, which will be deleted, and the destination, which keeps its name and NIPC.
  • Everything that moves to the destination, by type: holder (with the certificates), certification body, sites and members (certificate, address, status, exit date), addresses (including those in the bin), licences, contacts and shares.
  • Contacts left out, with the reason: already associated with the destination; the destination already has a contact with the same e-mail (in that case, if the contact is left without any entity and is not a certificate manager, it is deleted; if it is a manager, it is kept); association already removed.
  • Shares that already exist in the destination (same requester for the same certificate) are deleted instead of duplicated.
  • If nothing is attached to the source, the merge simply deletes the record and logs the operation.

Warnings and blocks

The preview shows warnings in a yellow box: the merge is allowed, but you should know.

  • Both records are in the same certificate. After the merge that certificate has two records (two sites or two members) of the same entity; it is up to the user to decide afterwards whether one of them should be withdrawn.
  • The source has actions awaiting verification by the CB. As the record disappears, those actions no longer appear in the verification queue.

And blocks in a red box: the merge is not performed.

  • The source and the destination are the same record.
  • Both records are holders of certificates. An entity can only have one holder profile, and the application does not decide which one keeps the certificates.
  • Both records are certification bodies.

Result

  • The destination record keeps its name, NIPC and all its data. It gains a line in the notes: «[dd/mm/yyyy] Fundida com a ficha "Source name" (NIPC …); certificados: …» (Merged with record …; certificates: …).
  • The activity of each certificate touched records Entidade fundida com outra ficha (Entity merged with another record), with the deleted record, what moved and the certificates.
  • The public search of the certificates touched is updated with the name of the destination record.
  • No notice is sent to the certification bodies: a merge is not a change to the holder's data.
  • It is not reversible. The source record is deleted; its history is kept internally, but is no longer visible.

Holders

A Holder (Certified Entity) is the entity that holds a certificate. Holders can be created, changed and removed. Removing a holder is not reversible.

Contacts

Allows you to create, change and remove contacts associated with an entity. Pay attention to shared contacts between entities. Removing a contact is not reversible.

Addresses

Allows you to create, change and remove addresses associated with an entity.

The address description serves as a label and is used to distinguish between addresses of the same entity (for example, in multi-site certificates: head office, factory or warehouse). Assigning these descriptions also helps to distinguish sites for notification purposes (for more information, see the corresponding procedure Notification - PEFC Portugal). It is therefore essential that the address description makes clear what it represents and links clearly to what is shown on the certificate issued by the CBs (Certification Bodies), in compliance with definition 3.5 and requirement 7.7.1, including note 1, of the standard PEFC ST 2003:2020.

Removing an address is not reversible.