Building in public — shipping new features daily

Accounting & Treasury Management System — built in public.

Liquanta is a modern workspace for accounting and treasury management, with cash visibility, statement processing (EBS), payment execution controls — with audit trails and many more features. Also, there is org-level data isolation from day one.

For: Treasury Ops, Treasury Analysts, Controllers and CFOs managing multiple entities, banks and currencies.

Treasury OpsTreasury AnalystController / CFOFinance Systems

After you sign in:

1) Create your organization (≈ 30 seconds)
2) Land in the app (your command center)
3) Start testing the newest screens and features + leave feedback

Command Center

Cash, coverage, exceptions — one place

Preview

Total available (base)As-of 09:12

€ 12,480,320

Coverage: 34/36 accounts (2 stale)

Approvals pending

maker-checker

EBS runs

Healthy

Last: 08:55

Why this number is trustworthy

Lineage: run → artifact → mapping → output
Stale accounts are excluded or flagged (your choice)
Sensitive actions are permissioned and logged

This is the UI vibe you’ll see inside the app.

Cash: As-of + coverage
Statements: EBS + lineage
Payments: Maker-checker
Forecast: 13-week plan

What you can try today

Liquanta is built screen-by-screen. These are the parts that are usable right now (and what’s next).

Live now

Google sign-in + redirect to the app
Organization onboarding (one org per person for now)
Org-scoped pages (everything belongs to your workspace)
Early Treasury screens (bank accounts / balances / EBS runs)
Feedback loop on shipped screens (fast iteration)

Coming next

Payments execution controls (BCM-style approvals)
Payment status & investigations (returns/recalls evidence)
Cash position “as-of” with strict vs carry-forward totals
Accounting foundations (journals + audit trail) — staged

You influence this by testing pages and leaving feedback.

Tip: share direct links to the app. If someone isn’t signed in, they’ll be prompted.

How it works

A simple, explainable pipeline. When someone asks “why?”, the product answers with lineage.

1
Connect banks (API/SFTP/SWIFT/EBICS) with monitoring and retries.
2
Process statements (EBS) into canonical balances + bank transactions.
3
See cash as-of with coverage rules that keep totals honest.
4
Control payments with maker-checker release and status tracking.
5
Forecast and fund with scenarios and headroom alerts.

Build in public

Every shipped screen is testable. Every screen has a feedback box.

Changelog Sign in

Latest shipped

EBS: Statement versioning

Superseded statements preserved with lineage.

Today

Try it in the app → Treasury → EBS

What’s next

Payments: investigations

Return reasons, recall flow, and audit-ready evidence.

Target: this week

Your clicks shape what ships next. Try the latest screen and leave feedback.

Trust & data safety

Built for finance teams: explainable numbers, controlled actions, and workspace isolation.

Your data is scoped to your organization. You only see your workspace. Sensitive actions (like approvals/exports) are permissioned and logged.

Lineage by default

Each balance can be traced back to the statement version and mapping rules used.

Coverage is explicit

Totals show how many accounts are included and which are stale or missing.

Maker-checker controls

Release procedures and approvals designed for treasury execution.

Audit-ready exports

Exports include as-of mode, FX source, coverage summary, and lineage identifiers.

FAQ

The questions people ask right before they try it.