Which e-signature provider does Lexnus use?

Scrive. By default your team signs through the Lexnus Scrive account, with no setup. An Admin can connect your organisation's own Scrive account instead.

Can a contract be signed before it is approved?

No. Sending for signature checks the latest version first: it must be analysed, every required approval in place, and no finding left unresolved. There is no Admin override.

What if we sign outside Lexnus?

Use "Skip signing, finalize" to mark the contract executed after the same checks. A contract that is already signed when you upload it is filed as active and still checked against your playbook.

Can a signed contract still be changed?

No. Once a contract is active it is locked: no new versions, and the data captured from it cannot be edited.

How are obligations found?

Lexnus reads the signed contract and proposes the obligations it finds, with who owes each one and when. A person reviews them. Nothing is tracked until it is accepted.

Who gets renewal reminders?

The contract's owner and watchers, at 90, 60 and 30 days by default, counted back from the notice deadline, or from the expiry date if the contract does not renew automatically. Each workspace can change the timing. A reminder nobody acknowledges escalates to your Admins.

Features

Signing and Obligations

A contract is not done when it is approved. Lexnus sends it for e-signature, files the signed copy, and then keeps what the contract promises in front of the people who own it — renewal dates, notice deadlines, and the obligations on each side.

From approved to signed

Checked before it goes out

Sending for signature checks the latest version against its playbook first. It has to be analysed, every required approval in place, no unresolved findings, and no rule broken that cannot be approved. If something is missing, Lexnus says what and what to do next.

Send for signature

Signing runs through Scrive. Your team uses the Lexnus Scrive account by default, or an Admin connects your own. Add each party, choose how they sign and, if it matters, the order they sign in. Parties with the same number are invited together.

The copy that goes out is a clean PDF with your appendices. Tracked changes are accepted and comments removed in that copy only. The saved version keeps them.

Follow it to the last signature

The contract shows each party's progress: delivered, viewed, signed. Send a reminder to everyone who has not signed yet, or withdraw the request. If a party declines, or the request expires, the contract goes back to where it was.

Signed, filed and locked

When the last party signs, Lexnus stores the signed PDF and the contract becomes active. An active contract is locked: no new versions, and its captured data cannot be edited. The people you name — finance for customer agreements, say — are told it is signed, by email or in a Slack channel.

Signing outside Lexnus? "Skip signing, finalize" marks a contract executed after the same checks. A contract that arrives already signed is filed as active, and still checked against your policy.

After the signature

Dates read from the contract

Lexnus reads the term from the signed contract: effective date, expiry, renewal, whether it renews automatically, and the notice period. From those it works out the notice deadline. If someone corrects a date by hand, Lexnus never overwrites it.

Obligations, proposed for review

Lexnus finds what each side has promised — payments, deliveries, notices, reporting — and who owes it. These are proposals. Nothing is tracked until a person accepts it. Accept, edit or discard each one. Discarded ones stay discarded when the contract is read again.

Reminders that reach the owner

Renewal reminders go to the contract's owner and watchers at 90, 60 and 30 days by default, counted back from the notice deadline — or from the expiry date, if the contract does not renew by itself. Obligation reminders go to the contract owner. A reminder nobody acknowledges escalates to your Admins. Each workspace sets its own timing, and each person chooses whether reminders reach them in the application, by email or in Slack.

One list of what is waiting

The To do page holds every task and obligation waiting on you, across every workspace. Filter to what is overdue or due in the next seven days. In the repository, filter contracts by renewal date, notice deadline, or the obligations they carry, and save the filter for your whole team.

What you get

E-signature through Scrive — Email link, SMS PIN, Swedish and Norwegian BankID, Danish MitID, Finnish Tupas, Smart-ID and Verimi, plus qualified electronic signatures.
A gate before signing — The same checks guard sending for signature and marking a contract executed. There is no override.
A clean signing copy — Tracked changes and comments stay in your version, not in what the other side signs.
Signed-contract notices — Tell finance, a team channel or an outside address when a contract is signed, per workspace or per playbook.
Renewal and notice dates — Read from the contract, corrected by a person when needed, and never overwritten after that.
Obligations you approve — Proposed by Lexnus, tracked only once a person accepts them. Recurring obligations roll forward on their own.
Automations on the playbook — Raise a task for the contract owner a set number of days before expiry, when a contract is signed, or when an obligation falls due.
Export — The repository table exports to Excel with the columns you chose.