Groups and consortia
Several companies, each with its own account
Subsidiaries of a group or companies working on one project: the context of each request is preserved.
In Nereva, a company is an account: its users, roles, permissions, partners and prices. A group is a set of accounts; a consortium is a set of distinct companies working on a common project. In both cases, each transport request keeps its requester, its site, its company and its carrier.
15-day free trial · 2 licences included · No payment method required
Two situations
Group of companies or consortium?
Group of companies
- Several companies linked within the same organisation: subsidiaries, entities, depots.
- Each entity has its own Nereva account and runs its own operations: users, roles, sites, planning, partners.
- The same user can receive access in several accounts and switch between them.
Consortium or joint venture
- Several distinct companies working together on a given project, keeping their structures and their responsibilities.
- Each company keeps its account; it is the requests, missions and their evidence that keep the project context.
- Nereva does not allocate the consortium’s responsibilities and does not replace its agreement.
Each company keeps its account, its users and its relationships
There is no “group” account above the companies. Each company registers, sets up its users and roles, connects its partners and enters its prices. A person who works in several companies receives access in each one and chooses the active account at login.
- Users, roles and permissions specific to each account.
- Partnerships specific to each account: a carrier that is partner of one entity is not automatically partner of the others.
- Prices and framework agreements specific to each relationship.
- One licence per assigned role, in each account.
Scope
What exists, and what does not
What Nereva does
- One account per company, with its sites, requests, history and statements.
- Multi-account access for the same person, with an account selector.
- Structured requests that keep the requester, the site, the company and the carrier.
- Partnerships between accounts, accepted or refused by each company.
What Nereva does not do
- A consolidated dashboard or cross-company reporting at group level.
- Control of subsidiaries or unlimited access to other entities’ accounts.
- Financial consolidation or multi-company invoicing.
- A universal view: each user sees their account, within the limits of their role.
If a consolidation need exists, it is handled with the exports and statements of each account, or with the Nereva team on quotation. Nothing is promised beyond what exists.
On a common project
Who requested what, for which company, executed by whom
On a site where several companies intervene, each request keeps its context from start to finish.
Requester
The request carries the name of the person who created it, their company, their site, the time slot and the status.
Nereva Commandes · Construction back officeCarrier
The partner carrier receives the request with the context needed for its execution: site, address, time slot, type of skip or load, instructions.
Transport back officeExecution
The driver carries out the mission; the steps, photos and delivery note stay attached to the original request.
Nereva TransportsSupporting documents
When an inspection or an audit requires a supporting document, each company finds in its account the request, the mission, the delivery note, the photos and the history, when these elements exist in Nereva.
Back offices
Nereva keeps the operational context; it determines neither which company is responsible, nor who must provide which evidence.
Roll-out
Rolling out Nereva in a group, account by account
The roll-out follows the real structure: one registration per company, users and roles per account, partnerships between accounts.
One registration per company
Each company creates its account; its workspace is activated after validation by Nereva. 15-day free trial with 2 licences, no payment method required.
How to get startedPartnerships between accounts
An entity connects its carriers, inside or outside the group, through a partnership request that the other company accepts or refuses.
With your usual carrierMore than 40 licences
The public price applies from 1 to 40 licences; beyond that, the price is built on quotation, with the same product.
See pricingThe standard, without the intermediary
Your partners and your business relationships remain yours. Nereva synchronises operations without stepping into the commercial relationship.
Roles and profilesFrequently asked questions
Groups and consortia, in plain terms
Can we manage several entities or depots?
Yes, with one account per entity: each has its own users, roles, sites and partners. The same person can access several accounts.
Does group management see all the entities?
There is no consolidated dashboard. An executive who receives access in several accounts consults each account separately, within the limits of their role.
Can a group carrier serve several entities?
Yes, if it is a partner of each entity that sends it requests. It receives each entity’s requests in its Transport back office.
How do we integrate a subcontractor?
Either it has its own Nereva account and becomes your partner, or its drivers are created as Driver users of your account, with one licence per assigned role.
Can Nereva be used on a consortium site?
Yes. Each company keeps its account; requests and their history remain attached to their context: requester, site, company, carrier.
And beyond 40 licences?
The price is built on quotation with the team, according to your structure and your roll-out, with the same product.
How roles, environments and partnerships work is described on the dedicated pages.
Go furtherGroup or consortium: one account per company, and every request keeps its context.
15-day free trial with 2 licences. No payment method required. Monthly subscription afterwards, no long-term commitment.