CONTRACTS AND USAGE

What you contracted, and what is left.

Contracts, lines, hour banks, rates and usage in one place. Nexo checks the contract before opening or resolving a ticket.

Service linesShared hour banksReal usageContract blocking

The contract is in a PDF and usage is in a spreadsheet.

Nobody knows what is left until the client asks.

01

Hours without control

Banks are consumed without a shared record between support and projects.

02

Scattered rates

Everyone applies their own criterion because there is no single rate.

03

Late blocking

Service stops after the team has already worked too much.

What it solves

The contract stops being a document and becomes a system rule.

01

Service lines

Support, projects, consulting and other services with their limits.

02

Shared banks

Hours split across lines without losing the total.

03

Rates

Global, per company or per person; euros per hour or per ticket.

04

Usage

Hours and tickets recorded from Nexo and Projects.

05

Blocking

Per line, with alerts to the client and the team.

06

Nexo integration

The agent knows whether they can open, resolve or escalate.

How it works

01

Define the contract

Company, term, lines and limits.

02

Split the banks

Hours shared across services and people.

03

Record usage

Nexo and Projects send hours and tickets to the contract.

04

Block in time

When a line runs out, the system warns and stops.

Inside the product

Contract, lines and usage, together.

panel.l6ecosystem.comdemo

Product view

Contract summary

Term, lines and status in one view.

What it connects to

Contracts is a satellite of Nexo and operations.

01

Adder IdP

Companies, users and roles.

Explore
02

L6 Nexo

Blocking and usage in the support flow.

Explore
03

Billing

Usage is recorded in Contracts; billing remains in the client ERP.

WHO IT IS FOR

For those who bill by service and do not want surprises.

Support providers, consultancies and internal departments splitting hours across teams. The contract becomes a visible rule, not an argument.

What buyers ask first

Does it replace our ERP?

No. Contracts controls contract, usage and blocking; billing stays in the accounting system.

How is usage recorded?

Nexo and Projects send hours and tickets; the contract accumulates them per line.

Can a single line be blocked?

Yes. Blocking is per service line, not per entire contract.

Who can see the contract?

Authorised people in the company and the support team with permission.

Next step

Your company already has an identity. Now let the applications work.

Tell us what you need and we will propose the smallest module that already delivers value. No endless rollouts.