Features

The full list, with no plans in it.

Everything listed here exists in the product and is covered by automated tests. What does not exist yet is named at the bottom of the page rather than left out.

The action engine

Five built-in findings

Unpaid invoice, contract to decide, stalled deal, late delivery, unowned task.

Detection without a model

Each finding is a query you can check against your own data. No model is needed to notice.

Three levels per kind

Off, propose, or act alone. Set per kind of finding and per organization.

Undo

Anything done without you can be taken back, and the finding returns to being a proposal.

The reason, not a verdict

Every record carries the dates, amounts and rule that raised it.

Work

Tasks

Owner, due date, priority, and three views: everything, yours, and what nobody has taken.

Assigning is its own permission

Taking a task and handing one to somebody else are not the same right.

Requests

Equipment, a purchase, access. Everyone may ask; only a manager answers.

Approving creates the work

An approved request produces the task for it, in the same operation.

Deadlines

Nine modules on one screen, and the list names what your role did not let it see.

Approvals

Your rules decide what needs a person, and which one.

People

Staff directory

Job, department, contract type, start and end dates.

Pay is not the directory

Salary and identity numbers have their own permission and are encrypted.

Leave

Request, decision, and a balance counted from the leave actually taken.

Attendance

Present, absent, remote. The day carries no hours — that is not its job.

Working patterns

A weekly pattern per organization; expected hours stay absent until somebody sets one.

Timesheets

The hours, and what they went into, against a project.

Customers

Companies

Lead, prospect, customer, former: one axis, not a second table.

Contacts

With one primary contact per company, and only one.

Opportunities

Stages, amount, probability, and a weighted total per currency.

Quotes

The total is the sum of the lines; validity comes from the date, not a status.

Accepted quote, invoice issued

In one act, and never twice.

Activities

Calls, meetings, emails, notes: what a person did, as opposed to what the software observed.

Finance

Invoices

What is still owed is counted from the payments received, never written into a status.

Payments

Partial, multiple, and refunds as negatives.

Receivables

What is owed per currency, and how much of it is late.

Expenses and supplier bills

An unpaid expense with a due date is a bill. Not a second table.

Cash flow

Money in and money out, month by month.

Budgets

Spend is counted from the period's expenses, in the budget's own currency only.

Currencies

Every amount carries its own, and two currencies are never added together.

Electronic invoicing (DGI)

Compliance check

For each issued invoice, what would stop the DGI's platform validating it.

Company identity

ICE, IF, RC, professional tax and registered address — the article 145 mentions.

ICE check key

The fifteen digits and their modulo-97 key, verified on both sides of the invoice.

Lines and VAT per rate

Each line with its rate; VAT is totalled per rate, as a return declares it.

Rates in force on the date

Since 1 January 2026, 20% and 10%. A 2025 invoice keeps the rate it was issued at.

UBL 2.1 document

The standard XML file, downloadable invoice by invoice.

No submission

The platform's API is not published. Nothing is sent, and the screen says so.

Operations

Suppliers

A supplier is a company flagged as one: plenty of them are customers too.

Purchase orders

Lines, committed total, receipt, and a number unique per organization.

Contracts

Each with its own notice period, which is where the decision date comes from — not the end date.

Stock

The quantity is the sum of the movements; the reorder level raises a finding.

Fixed assets

Book value computed only where a useful life was stated; absent otherwise.

Projects

A project's cost is the sum of the expenses booked against it.

Documents

Upload and storage

The file's type is determined from its bytes, not from its name.

Reading, page by page

The PDF's own text where it exists, character recognition otherwise, with French and Arabic.

Recognising the document kind

Invoice, purchase order, contract, or one of the kinds you defined.

Capturing information

Amounts stay as printed, dates are normalised, what is absent stays empty.

Source page

Every value keeps the page it was taken from.

Corrections

What you correct is kept beside the original proposal, not in place of it.

Document centre

Kind, counterparty, amount, status and who uploaded it, with business-language filters.

Review screen

The document on one side, the captured information on the other, each marked captured, needs checking, or not found.

Information to capture

Three built-in kinds

Invoice, purchase order and contract work from the first upload.

Your own kinds

Describe in plain language what you want captured, field by field.

Six field types

Text, number, money, date, yes/no and list.

Fields a person must check

Mark a field as one that has to be checked by a person before any approval.

Protected deletion

A kind used by past documents cannot be deleted; it can be disabled.

Automations and approvals

Rules in business language

When, if, then, otherwise — read back as a sentence before being saved.

Templates

Four templates build a working rule from two questions.

Shadowed rules flagged

A rule another will always beat to the match is pointed out to you.

Approvals inbox

Grouped in three: for you, for someone else, already decided.

Findings in the open

A possible duplicate appears on the decision card, not in a log.

Decisions on the record

Approve or decline with a note; the author and the date are kept.

What follows a decision

Notify another system, or record an internal event.

Knowledge and assistants

Questions about your documents

Streamed answers, with the sources shown before the first word.

Refusing to guess

With no relevant document, no model is called and the absence is stated.

Permissions inside the search

Permissions filter the search itself, never its results after the fact.

Citations you can open

An extract does not cross a page, so every citation leads somewhere you can look.

Knowledge base

Notes you type or documents already processed, with access by role.

AI Assistants

Standing instructions, with capabilities chosen from a list of what can actually be carried out.

Real trial run

A trial against the real model, from the configuration screen.

Runs recorded

Duration and estimated cost of every run; a failure is a failure, never a substitute answer.

AI quality

Test case sets

A fixed set of cases, run against one pinned model, so a score belongs to that model.

Two kinds of case

A free-text answer, or capturing information from text the case carries itself.

Three ways to grade

Exact match, contains, or judged by a model.

Errors count as failures

A case that errors is not skipped: it is graded as failed.

Team, access and languages

Seven roles

Each described from the permission table, including where the answer is uncomfortable.

Invitations

A public page to join the organization; revoke, change role, remove.

Two-factor authentication

TOTP, with single-use recovery codes.

Sessions

The list of your open sessions, revocable immediately on the server.

Three languages

French, English and Arabic, with a full right-to-left layout.

Light and dark

Verified against WCAG 2.1 AA in all three languages and both themes.

Tracking, reports and cost

Reports

Documents processed, approvals requested and decided, average time, over 7, 30 or 90 days.

A shareable window

The period lives in the address, so a figure can be passed on as it is.

AI usage

What the AI cost, per day and per use, computed from the provider's published rates.

A cost stated as an estimate

Never presented as an invoice, because it is not one.

Notifications

In the application, with preferences per kind of event.

Background watching

Stuck work, a provider failing repeatedly, a budget approached, a broken integration.

Outbound connections

A signed message

After a decision, Intelliflow notifies a web address you provide.

Signed over the bytes sent

HMAC-SHA256 over the exact message, with the timestamp inside what is signed.

Protection against internal addresses

Every resolved address is checked, IP literals included.

Delivery history

Response status, latency and errors, all kept.

Security and traceability

Isolation by the database

Every customer-data table carries a policy enforced even against the owner of the table.

Audit trail

Update and delete rights are withdrawn from the application account.

Secrets out of the browser

AI provider keys never leave the server.

Encryption at rest

Sensitive stored values are encrypted with a key derived per use.

Rate limiting

On sensitive routes, against repeated attempts.

What does not exist yet

We would rather you read it here than discover it later. Submitting invoices to the DGI is not possible: the platform's API is not published, and nobody can submit to it today. The electronic signature and the PDF/A-3 pairing are not implemented either. There is no general accounting or tax filing, no CNSS payroll, no bank connection, no mobile application, no single sign-on, and no connector to any named software. No certification either: not SOC 2, not ISO 27001.

  • No connector to any named accounting package, CRM or storage service.
  • No public API and no API keys for customers.
  • No email sending configured: an invitation produces a link you share yourself.
  • No mobile app. The web application works on a phone.
  • No single sign-on (SSO, SAML, OIDC).
  • No visual drag-and-drop workflow builder.
  • No folders or tags on documents.
  • No online billing: no payment provider is connected.

The simplest way is still to try it on your own documents.

Create an organization