Kantora

01 / MOLDOVA · B2B FINTECH

Kantora

Banking, e-Factura and 1C in one place.
For SMEs and accounting firms in Moldova.

Kantora01 / 12

02 / PROBLEM

The bridge between three systems is a person.

ACCOUNTANT · RETYPE BY HANDBANKMONEYe-FacturaINVOICES1CBOOKSACCOUNTANT · RETYPE BY HANDBank, e-Factura and 1C remain separate, with the accountant bridging them manually.BANKe-Factura1CACCOUNTANT · RETYPE BY HAND

BANK

Money lives in MAIB.

FISCAL PORTAL

Invoices live in e-Factura.

LEDGER

Books live in 1C.

Accounting firms export an invoice from e-Factura and retype it into 1C. Every invoice. Every client. Every month.

Kantora02 / 12

03 / WHY NOW

The infrastructure is opening up.

20 MARCH 2026Moldova’s national Open Banking standard entered into force.
01 JANUARY 2021Electronic invoices required for taxable public-procurement supplies.

Structured invoices. Consent-based bank access. A foundation for connected accounting.

Kantora03 / 12

04 / SOLUTION

Company health. On your phone.

Our goal: understand your company’s financial health in 10 seconds.

One platform to synchronise banking, fiscal services and the accounting ledger.

e-Factura → 1C invoice syncIN BUILD
Bank sync & reconciliationNEXT
Cashflow dashboardNEXT
AI agent over the unified dataPLANNED
Kantora04 / 12

05 / HOW IT WORKS

Capture. Validate. Sync.

IN BUILD · INVOICE SYNC FIRSTe-FacturaCAPTUREKANTORAVALIDATE XML1CLOCAL AGENT · SYNCIN BUILD · INVOICE SYNC FIRSTPlanned invoice pipeline: e-Factura to Kantora for validation, then a local agent posts documents into 1C. Currently in build.TODAY: RETYPE BY HANDe-FacturaKANTORA1CINVOICE INVALIDATE XMLLOCAL AGENTIN BUILD · INVOICE SYNC COMES FIRST

1C is on-premise, so the sync runs as a local agent, and posts documents through the configuration’s own logic rather than writing to the database.

Kantora05 / 12

06 / DEFENSIBILITY

The hard leg is the moat.

The ledger is where the integration gets specific.

1C integration is per-install, not a clean public API. Kantora’s focus is the local agent and the configuration’s own posting logic.

Our defensibility thesis: build depth in the hardest connection.

Kantora06 / 12

07 / COMPETITION

Start where the ledger needs attention.

CapabilitySiriusKantora
Bank syncAdvertisedNext
DashboardAdvertisedNext
e-FacturaAdvertisedIn build
1C syncNot verifiedIn build
AI layerNot verifiedPlanned
Sirius public product page ↗ · Checked 15 September 2026.
“Not verified” does not mean absent. Kantora statuses describe work in progress.
Kantora07 / 12

08 / MARKET

From an internal tool to a national product.

Agency pilotAcross Moldova

Start with the agency’s clients. Learn from day-to-day accounting work. Then scale into a national product for SME owners and accounting agencies.

Planned rollout.

Kantora08 / 12

09 / GO-TO-MARKET

One agency. A direct route to the workflow.

Jizdan & Partner serves 400 companies.

We plan to ship internal tooling for the agency’s clients first, then expand after the pilot.

Client base of the accounting agency; pilot rollout planned.

Kantora09 / 12

10 / WHERE WE ARE

Pre-revenue. MVP in build.

  • Planned pilot · Internal tooling for Jizdan & Partner and its clients.
  • Integration research complete · MAIB API, e-Factura API and invoice XML schema specced.
  • 1C integration path chosen · Local agent; native document posting.
Kantora10 / 12

11 / PRODUCT SEQUENCE

Invoice sync first. Intelligence follows.

01 / IN BUILD

Invoice sync

e-Factura → 1C

02 / NEXT

Bank connection

Bank sync & reconciliation

03 / NEXT

Cashflow view

One dashboard over the data

04 / PLANNED

AI agent

Questions over unified data

Product sequence; no delivery dates committed.

Kantora11 / 12

12 / TEAM & CONTACT

Building in Chișinău.

Grecu Catalin

CTO. Technical developer at a game development company.

Andrei Jizdan

CEO, Jizdan & Partner. Accounting industry knowledge and mentorship to help ship Kantora.