InnerWeb
Skip to main content

Contractor firm in the portal: linking by tax ID

A portal organisation is linked to a firm in the plant only after the first manual approval by the operator, and only when the tax ID (NIP) of the firm matches the NIP of the organisation. The NIP entered in the portal is not verified there, so it does not grant access on its own. This scenario shows how to use it safely.

1
manual approval needed to link a firm
Source: card

Situation: a contractor with several organisations in the portal

In this scenario a large service company has been serving the plant for several years. Its employees created profiles in the contractor portal and assigned themselves to organisations, some of them to more than one, because the company has branches and sister companies. Access requests started arriving from different organisations, and the coordinator for external firms had to answer which of them should be treated as the firm the plant already knows.

An important limitation: the NIP of an organisation is not verified in the portal. Someone may enter another company's NIP, so a match of numbers alone must not open the door. For this reason the plant treats the NIP match as a condition, not as proof.

Rule: the first approval is always manual

A link between an organisation and a firm in the plant is created only after the first manual approval by the operator, and only if the NIP of the firm in the plant matches the NIP of the organisation in the portal. The operator therefore assesses the request with their own eyes: who is applying, for what purpose, and whether the plant has actually ordered work from this firm.

After the approval, further requests from the same organisation are recognised as belonging to a known firm. This reduces the number of questions, but it does not remove control. Authorisations from a request are created with a status pending verification, so even a request from a known firm does not mean confirmed qualifications.

Operator decisions for the same firm (example)

Operator decisions for the same firm (example)For five further requests from a known firm with new e-mail addresses, manual decisions fall from five to zero after automation is switched on.012345decisionsWithout a firm link: Next 5 requests: 5 decisions5Without a firm linkAfter linking and automation: Next 5 requests: 0 decisions0After linking and automation
Source: Sample calculation: 5 requests from a known firm, new e-mail addresses, automation switched on

Automatic acceptance: an option, not a default setting

The plant may go one step further and enable automatic acceptance of requests from a linked firm. The feature is disabled by default, is switched on with a configuration variable of the installation, and works only when the e-mail address in the request does not yet have an account. Removing the variable restores full manual approval, so the decision can be reversed in one move by an administrator.

Recommendation for the coordinator: switch on automation only after several successful manual approvals with this firm, and only for contractors with stable, verified cooperation. For one-off firms keep manual approval.

  • The first approval is always manual.
  • The NIP in the plant must match the NIP of the organisation.
  • Automation works only for new e-mail addresses.
  • Switching automation off means removing the configuration variable.

When a firm has several organisations in the portal

When one group has several organisations, each of them is a separate entity with its own NIP. The coordinator approves them one by one, and only then is each linked to the right firm in the plant. If the NIP of an organisation does not correspond to any firm in the plant, the request is not assigned automatically and requires a human decision, including a possible creation of the firm after checking the registers.

Practical tip: before you switch on automation, tidy up the register of firms in the plant. Duplicate firms with the same NIP and typing errors in numbers are the most common causes of mismatches, which later create unnecessary requests for manual review.

Result and conclusions

The result is fewer repeated decisions while keeping control over the first contact. The coordinator does not keep answering the same question about the identity of a firm, and the plant does not hand over the decision on entry to the site to the portal.

Conclusions: treat the NIP from the portal as a hint, not as proof. Leave the first approval to a person. Switch on automation gradually, with the option to switch it off quickly. Keep only correct, verified NIP numbers in the register of firms.

Checklist

Video

Frequently asked questions

Is a matching NIP enough to admit a contractor?

No. The NIP in the portal is not verified, so it is only a condition for linking. The decision on access still belongs to the plant.

How do I switch off automatic acceptance?

Remove the configuration variable of the installation. The system then returns to full manual approval.

Will automation accept a request with an address that already has an account?

No. Automation works only when the e-mail address does not yet have an account in the plant.

Let's talk about the contractor portal at your plant

We will show you on a live example how a contractor's request reaches the operator and how the plant keeps full control over entry to the site.

Let's talk