LexOne

Legal Finance & Operations Platform

Modules and their real status

Each module below is labelled with its status today. Modules that require a provider agreement do not work until that agreement is in place.

How the modules connect. Illustration — not a product screenshot.

Finance and bookkeeping

  • Receivable ageing, collection rate, lockup and WIP indicators
  • Income, cost and profitability by matter and client
  • Disbursement entry, category management, matter allocation
  • Instalment fee tracking and overdue analysis
  • finans.kpiWorking
  • muhasebe.on_muhasebeWorking
  • muhasebe.masrafWorking
  • muhasebe.yevmiyeIn development

Clients, matters and documents

  • Client and matter records, statements, balances
  • Document store: type validation, size limits, tenant scoping
  • Linking a document to a transaction
  • Field extraction from documents (OCR) — requires a provider agreement
  • muvekkil.yonetimWorking
  • dosya.yonetimWorking
  • belge.depoWorking
  • belge.ocrRequires a provider agreement

Banking and e-documents

Bank transactions are read through a licensed aggregator. LexOne is not itself a payment service provider, and payment initiation is deliberately absent.

  • banka.okumaRequires a provider agreement
  • banka.mutabakat_otomatikIn development
  • ebelge.esmmRequires a provider agreement
  • imza.eimzaRequires a provider agreement

Administration and audit

  • Role-based permissions, office scope, per-user exceptions
  • Multi-stage approval workflows
  • Immutable audit trail
  • Subscription, quota and usage metering
  • guvenlik.rbacWorking
  • onay.akisiWorking
  • guvenlik.denetim_iziWorking
  • abonelik.kotaWorking

Manage finance, accounting and operations on a single AI-assisted platform.

Explore the demo → Request a demo

Every capability on this page is labelled with its real status. Features that require an external provider do not work without an agreement, and are not presented here as if they did.