This use case is an illustrative scenario: it describes how the product actually works, applied to the typical week of a CEMAC accounting firm. SynkriaOps is pre-launch — when real pilot firms share their experience, their stories will be published here, under their name or anonymised at their request.

The firm’s problem

An accounting firm that manages several dozen SMEs faces a singular operational problem: keeping data strictly separated between clients while letting the internal team move from one file to another in a few clicks.

Traditional solutions impose either one instance per client (cost and maintenance) or fragile application-level partitioning (risk of cross-client leaks).

The SynkriaOps model

SynkriaOps uses a strongly isolated multi-tenant architecture: a single PostgreSQL schema, but every row carries a client-file identifier and PostgreSQL Row Level Security filters access at the database engine level itself.

In practice, this means:

  • A firm collaborator has a single SynkriaOps user account.
  • They are individually attached to each client file they work on.
  • When they switch files, the session switches context at the database engine level; any query outside that context returns 0 rows — a fail-safe, not a best effort.

The visible effect: the internal team changes client in two clicks, but no data leak is physically possible server-side, even in the event of an application bug. Files marked confidential are only visible to the file manager and the signing partner — filtering happens server-side, not in the interface.

A typical week at the firm

  1. Monday morning — reviewing client entries. SME clients enter data as they go; the internal team scans the portfolio dashboard and spots the files that need attention (imbalances, pending documents, closing delays).
  2. Tuesday to Thursday — accounting production. Complementary entries, matching, bank reconciliation, adjustment entries for files in monthly close. In the field, a collaborator captures documents from the mobile app — the permanent “Client file” banner guarantees they are working in the right file.
  3. Friday morning — exports and delivery. Generating PDFs (balance sheet, income statement, general ledger, trial balances) for ongoing closings, tracking time spent and preparing fees.

Honest limits today

  • No client portal yet for SMEs to consult their documents on the firm’s side (in development).
  • No integrated payroll — payslips and social declarations stay in a third-party tool, re-imported as monthly adjustment entries.

FEC export, complete SYSCOHADA financial statements (balance sheet, income statement, cash-flow statement, notes) and VAT returns are, on the other hand, operational today.