Skip to Content
Docs

How Tosven works

One database, shared records, and one order followed from the deal to the journal entry.

Tosven keeps every module on one database. This page explains what that means in daily work, then follows a single order through the system. The example uses the demo company Kaarna Group and its customer Nordlys AB.

One database

In a setup with separate tools, each tool has its own copy of the customer, its own users and its own log. Integrations move data between the copies, and someone explains the differences at month end.

Tosven has one set of records. Three things follow from that.

  • One customer. The company in the sales pipeline is the counterparty on the invoice. Its name and identifiers are stored once.
  • One set of permissions. A right is granted once, per company, and applies in every module.
  • One audit trail. A change is recorded where it happens, whichever screen it was made from.

Shared records, not integrations

Modules do not send data to each other. They read the same record.

You are inYou seeIt is read from
CustomersOpen receivables on the deal screenLedger, at that moment
ChannelsAn invoice card with its current statusThe invoice record itself
KnowledgeA customer balance inside a pageLedger, for each reader
CommandToday's net salesThe same entries as the income statement

There is no sync job that can fall behind. What you may see is decided when you read it, under your own rights. A reader without ledger rights sees no access in place of a figure.

The order chain, end to end

The demo shows one order moving through the chain. Select a step to see which record it creates.

Try itOne sale, one chain of records
OPP-2026-0412Antti KorhonenDeal with Nordlys AB moves to Proposal
QUO-2026-0142Antti KorhonenQuote version 3 sent by link · 48.000,00 €
QUO-2026-0142Sanna Lind · Nordlys ABAccepts the quote on the link
INV-2026-0418Sara NyströmDraft invoice created from the accepted quote, approved and sent
PAY-2026-0391Bank statementPayment matched to the invoice
JRN-2026-01284LedgerEntries posted. Every figure opens back to this voucher
Each step is a record linked to the one before it. Nothing is copied between modules. · Sample data

The same story in steps, on 14.10.2026:

Deal

Antti Korhonen works deal OPP-2026-0412 for Nordlys AB in Customers. The deal carries its stage, amount and contacts.

Quote

At 09:12 he sends quote QUO-2026-0142, version 3, to Sanna Lind. A sent version is frozen. Any change is a new version.

Acceptance

At 11:40 Sanna Lind opens the link, types her name, confirms her authority and accepts. Antti moves the deal to Won.

Invoice

At 13:05 Sara Nyström converts the accepted version into draft invoice INV-2026-0418 for 48.000,00 €. Each invoice line points to its quote line.

Journal entry

At 13:20 she posts the invoice. Journal entry JRN-2026-01284 is written in the same step, with a gapless number. Nordlys AB changes from prospect to customer.

Payment

The bank statement is imported. The payment carries a valid reference number, so it settles the invoice in full as PAY-2026-0391. The bank line is itself a ledger entry.

Nobody retyped anything between these steps. The invoice lines came from the quote lines, and the receivable everyone sees closed when the payment was matched.

On the way

A separate sales order record, with delivery state, is planned. In the pilot an accepted quote plays the role of the order and converts straight into a draft invoice. Stock, purchasing and delivery are also on the way.

Follow the chain backwards

The chain works in both directions. From a figure on a board you can open the accounts behind it, then the lines, then the voucher, then the source document. From the invoice you can go back to the quote and the deal.

Permission is checked again at every step. A step you may not open shows no access. It does not reveal a name or an amount.

Where agents fit

Agents work on the same records, inside the same permissions.

  • The Ledger agent proposes the coding of purchase invoices and matches for bank lines. Live in the pilot
  • The Collections agent proposes payment reminders for overdue invoices. Live in the pilot
  • A Sales agent that raises follow-up cards from deal signals is designed. On the way

Each proposal arrives as a decision card with a reason, evidence and a confidence level. A person signs it. Before the work runs, Tosven checks that the records and the signer's rights are still what they were. If not, nothing runs.

Next steps

  • Core concepts: the vocabulary used on this page.
  • Record numbers: what the prefixes mean and how records link to each other.
  • Ledger: what happens when an invoice is posted.

On this page