synkriaops

Tag: ohada

  • Closing a SYSCOHADA fiscal year: the 5 most expensive pitfalls

    Closing a SYSCOHADA fiscal year is rarely the most relaxing moment for an SME. Here are five errors that consistently appear in the Cameroonian SMEs we support, ranked by correction cost.

    1. Mis-generated carry-forward entries

    The first pitfall — and the most painful — is switching to a new fiscal year without generating the carry-forward journal (« à-nouveaux »).

    The carry-forward is the pseudo-entry that re-injects on day one of fiscal N+1 the balance sheet balances (classes 1 to 5) from fiscal N. Without this journal, your opening balance is empty. Your 411 client accounts appear at zero, your 401 supplier accounts too, your cash too. Your accountant gets nervous. So do you.

    How to detect:

    • N+1 opening balance = empty balance or N-1 columns at zero
    • General ledger of a regular client’s 411 account: 0 movement before the first N+1 receipt

    How to fix:

    • Re-generate the carry-forward from the final balance of fiscal N
    • Verify that debit sum = credit sum on the carry-forward journal
    • Spot-check a few known accounts to validate the extrapolation

    In SynkriaOps, carry-forward regeneration is automatic upon re-closing fiscal N (see LOT-RECLOTURE-AUTO-AN, PR #279). Which reduces this pitfall to zero occurrences for users after the first closing.

    2. Wrong result allocation

    Second pitfall: confusing the P&L statement (the calculation) with the balance sheet allocation account (12).

    The fiscal year result is computed from class 6 (charges) and class 7 (revenues). Once computed, it is allocated to a liability account:

    • 1301 — Net result: profit
    • 1309 — Net result: loss

    The account 12 is an aggregation account, not a destination account for allocation. If your software sends the result to account 12, the balance sheet rebalances visually but the next step (reserve allocation, dividend distribution) will be off.

    3. The FEC export forgotten until the audit

    The « Fichier des Écritures Comptables » (FEC) is a normalized format allowing tax authorities to audit your accounting. It is not optional when an audit triggers — and it must be generated in the revised SYSCOHADA format, not in a proprietary format.

    What many forget: the FEC must be generated for each closed fiscal year, not just “if we get audited”. Generating it on the day of the audit notice is technically possible but stresses the team and increases the chance of omissions (unreconciled social charges, missing adjustments).

    Best practice: generate the FEC at closing, archive it outside your ERP (immutable cloud, physical media) and forget it exists until the next audit.

    4. Unbalanced class 6 and 7 accounts at year-end

    Before computing the result, charge and revenue accounts (classes 6 and 7) must be balanced. This is the automatic mechanism that flips them to account 12 then to 1301/1309.

    The pitfall: some software lets regularization entries dated after the closing date linger on 6/7 accounts — typically supplier invoices received in January N+1 but relating to fiscal year N.

    How to avoid: a clean cut-off. If a charge belongs to N, it goes to invoices to receive (4081) or prepaid expenses (4886) depending on case, with a counterpart on class 6 in fiscal N.

    5. Unreconciled entries on auxiliary accounts

    Reconciliation (« lettrage ») is the mechanism for matching Debit↔Credit entries on the same third-party account. A properly-reconciled client account (411######) clearly shows which invoices have been paid and which are outstanding.

    An unreconciled client account shows a mass of entries that may or may not offset. At closing, it is technically valid (the balance correctly adds to the balance sheet) but it pollutes client reminders and aging analysis.

    Recommendation: reconcile continuously during the fiscal year, not in a marathon at closing time. SynkriaOps automatically reconciles matching receipts detected via bank reconciliation.

    Going deeper

    • The SynkriaOps immutability trigger prevents any modification of a validated accounting document — see apps/api/src/migrations/1782100000000-TightenPiecesValideeImmutability.ts.
    • The chained SHA-256 hash on validated documents detects any retroactive alteration — see apps/api/src/modules/pieces-comptables/services/piece-hash.service.ts.
    • The SYSCOHADA FEC is automatically generated by apps/api/src/modules/exercice-fiscal/fec-generator.service.ts.

    These three mechanisms do not replace the rigor of accounting practices, but they guarantee that history is reliable when the auditor walks in.

  • SynkriaOps vs Sage, Odoo and Excel for an OHADA SME: which tool to choose?

    For an SME in the OHADA zone, the right choice hinges on one decisive criterion: is the accounting natively SYSCOHADA, in CFA francs, with Mobile Money, FEC and tax package? On that ground, Sage and Odoo are solid tools but designed elsewhere, Excel does not hold up on compliance, and SynkriaOps is built from the ground up for CEMAC. Here is a factual, non-disparaging comparison to help you choose with full knowledge.

    The criteria that truly matter in OHADA

    Before comparing brands, let us set the grid — the one that really weighs on a Cameroonian or CEMAC SME:

    1. Native SYSCOHADA revised 2019 (chart of accounts, statements, notes).
    2. XAF currency and CFA-franc presentation.
    3. Mobile Money (booking today; collection to come).
    4. Statutory FEC export for the tax audit.
    5. Tax package + 47 notes generated.
    6. CEMAC VAT (including Cameroon’s 19.25%) and withholding at source.
    7. Provable compliance (immutability, hash, locked numbering).
    8. Business ↔ accountant collaboration and firm mode.
    9. Field mobility (capture, scan, banking).

    Excel: the starting point, not the destination

    Excel (or an equivalent spreadsheet) remains the starting tool for many SMEs. Its strengths are real: total flexibility, zero cost, immediate familiarity.

    But to keep OHADA accounting, its limits are structural:

    • No built-in standard: the SYSCOHADA chart, the statements, the notes must be rebuilt by hand.
    • No FEC usable by the tax authority.
    • No immutability: a cell is edited without a trace — the opposite of what an inspector expects.
    • No reliable real-time collaboration or rights management.
    • Silent formula errors that propagate.

    Excel is fine for tracking, not for standardized, auditable accounting.

    Sage: a robust standard, but a different native framework

    Sage is a historic, robust, well-established vendor. Many firms know it. Its strengths: functional maturity, ecosystem, reliability.

    For an OHADA SME, the points of attention:

    • Sage is primarily designed for other frameworks (the French chart of accounts notably); SYSCOHADA fit depends on the edition and configuration.
    • The very local building blocks — native Mobile Money collection (being brought into service), turnkey 19.25% VAT, CEMAC withholding at source — are not the historical core target.
    • Depending on the editions, the experience can be closer to installed software than to real-time collaborative SaaS.

    Sage remains a serious choice; you simply need to verify edition by edition the fit with the CEMAC criteria above.

    Odoo: a complete ERP, generalist by nature

    Odoo is a powerful modular ERP: sales, purchases, stock, accounting, CRM. Its strength is functional breadth and modularity.

    The flip side for an OHADA SME:

    • Odoo is generalist and international: SYSCOHADA compliance goes through localization modules and configuration, whose depth (tax package, 47 notes, statutory FEC) varies.
    • The power comes with an implementation cost: an ERP is configured, often with an integrator.
    • The Mobile Money and CEMAC tax specifics are not native and require adaptation.

    Odoo shines when you want a full ERP; for an SME that first wants impeccable OHADA accounting quickly, it is sometimes oversized.

    SynkriaOps: built for CEMAC from the start

    SynkriaOps embraces a precise positioning: the “Pennylane” of CEMAC/OHADA. The product is not adapted from a foreign framework — it is built on SYSCOHADA revised 2019. Concretely:

    • SYSCOHADA chart of accounts, bilingual FR/EN, turnkey; native XAF currency.
    • Mobile Money MTN MoMo and Orange Money: clean booking (581 transit); secure collection infrastructure (QR, webhook) ready, service launch to come.
    • Statutory FEC per fiscal year, complete tax package with the 47 notes, balance sheet, income statement, TFT, TVCP.
    • CEMAC VAT across 6 countries (including Cameroon’s 19.25%) + withholding at source.
    • Provable compliance: immutability of validated entries, chained SHA-256 hash, locked numbering.
    • Real-time collaboration business ↔ accountant, multi-file firm mode with isolation.
    • Field mobile app (capture, barcode scan, banking, stock) — in internal pilot distribution.

    Honesty: Mobile Money collection (MTN and Orange Cameroon) is currently being brought into service — the secure infrastructure is built, the connection with the operators is not yet active; the mobile app is in pilot access (APK), not yet on the stores. The accounting core is complete.

    Summary table

    CriterionExcelSageOdooSynkriaOps
    SYSCOHADA revised 2019NoBy editionLocalizationNative
    Native XAF currencyManualBy editionConfigYes
    Mobile Money (collection)NoNot nativeAdaptationIn progress
    Statutory FEC exportNoBy editionVariableYes
    Tax package + 47 notesNoBy editionVariableYes
    VAT 19.25% / CEMACManualConfigLocalizationNative
    Provable immutabilityNoYesYesYes
    Real-time collaborationNoBy editionYesYes
    Field mobile (scan)NoVariableVariableYes (pilot)

    “By edition” = depends on the edition/version and configuration; “Localization” = via a localization module to configure.

    How to decide

    • You are starting and want light tracking → Excel may do for a while, but plan the switch before the first audit or serious closing.
    • You want a complete ERP and can afford to integrate it → Odoo is a candidate, provided you validate the SYSCOHADA/FEC depth.
    • Your firm is already standardized on Sage → check the edition and the CEMAC fit (Mobile Money, 19.25%, withholding at source).
    • You want impeccable, local, collaborative OHADA accounting with no integration project → SynkriaOps is made exactly for this need.

    In summary

    The right tool is not a matter of fame but of fit with the OHADA field. Excel starts but does not hold compliance; Sage and Odoo are solid but designed elsewhere and to be adapted; SynkriaOps is CEMAC-native. Run every candidate through the 9 criteria, test on your real documents, and look at the closing and the FEC — that is where everything is decided.

    To compare on your own entries, start free on SynkriaOps.

  • Financial statements and tax package under SYSCOHADA revised 2019: balance sheet, income statement, cash flow and the 47 notes

    The SYSCOHADA revised 2019 tax package is the set of summary financial statements an OHADA company must produce at closing: the balance sheet, the income statement, the cash flow statement (TFT), the statement of changes in equity (TVCP), and the 47 notes that explain each line. It is the deliverable that stands as evidence before the tax authority and third parties. Here is its detailed composition, why it costs weeks of manual work, and how to generate it automatically from your trial balance.

    What the SYSCOHADA package contains

    The revised SYSCOHADA framework (in force since 2018) requires, for the normal system, a package structured into five blocks:

    1. The balance sheet

    A snapshot of net worth at the closing date. It sets assets (fixed assets, inventory, receivables, cash) against liabilities and equity (equity, financial debt, operating payables). The SYSCOHADA balance sheet presents assets in GROSS, DEPRECIATION/IMPAIRMENT and NET — a forgotten depreciation column skews the entire fixed-asset section.

    2. The income statement

    It explains the formation of the result for the year from revenues (class 7) and expenses (class 6), organized by nature and by intermediate balances (value added, gross operating surplus, operating result, financial result, net result).

    3. The cash flow statement (TFT)

    The TFT (sometimes called TAFIRE in the old system) traces where cash comes from and where it goes: operating flows, investing flows, financing flows. It links the accounting result to the actual change in cash — a formidable consistency check.

    4. The statement of changes in equity (TVCP)

    It explains how equity evolved between opening and closing: contributions, result for the year, distributions, reserves.

    5. The 47 notes

    This is the explanatory heart of the package. Notes 1 to 47 detail each line: fixed assets and depreciation, inventory, receivables and payables by maturity, capital, provisions, off-balance-sheet commitments, headcount, and so on. Each note must be consistent with the balance sheet and income statement — for example, the total of a fixed-asset note must equal the corresponding balance sheet line.

    Why it is the most time-consuming part

    Producing this package by hand (or in a spreadsheet) is a marathon:

    • Each note is reassembled from account balances — a line-by-line reconciliation job.
    • The smallest last-minute entry breaks consistency: you must redo the balance sheet, the note concerned, sometimes the TFT.
    • The balancing controls (note total = balance sheet line, Σ maturities = balance, note closing = opening + increases − decreases) must be redone at each iteration.

    Result: in many SMEs, the package ties up the accounting firm for several weeks at year-end, with error risk proportional to the number of manual redos.

    The accounting invariants to respect

    A correct package always satisfies these controls:

    • Assets = Liabilities + Equity (the balance sheet balances).
    • Total of a note = the balance sheet line it details.
    • Σ of maturities in a schedule note = balance of the account.
    • Closing of a movement table = Opening + Increases − Decreases (fixed assets, depreciation, provisions).
    • Net cash in the TFT = the actual change in cash on the balance sheet.

    If even one of these controls fails, the package is wrong — even if each statement “looks fine” in isolation.

    How SynkriaOps generates the package

    SynkriaOps produces the SYSCOHADA revised 2019 financial statements from your trial balance, with no re-keying:

    • Balance sheet, income statement, TFT and TVCP generated automatically, with the correct GROSS/DEPR/NET presentation on assets.
    • Notes 1 to 47 driven by a data engine (each note reads the right accounts), with the ability to apply cell overrides, manual lines and editable bilingual note texts (FR/EN).
    • Import of the previous year’s texts so you do not start from scratch each year.
    • Drill-down line → detail: click a balance sheet amount to see the entries that compose it.
    • Versioned generation with history, and exports for filing.

    Because the notes are recomputed from the entries, a last-minute entry updates the whole package — the balance sheet, the affected note and the TFT stay consistent automatically. The year-end marathon becomes a few-minute review.

    Normal system and minimal cash-basis system

    Revised SYSCOHADA does not require the same package from every company. It mainly distinguishes two systems by size:

    • The normal system — the complete package described in this article: balance sheet, income statement, cash flow statement and the notes. It applies to companies above the thresholds of the minimal system.
    • The minimal cash-basis system (SMT) — a lightened arrangement reserved for very small entities whose turnover stays below a threshold set by the framework. Accounting there is kept essentially on a receipts-and-payments basis, with simplified statements.

    The practical point: a company that grows may switch from the SMT to the normal system. It is better to use a tool that produces the full normal-system package from the start, so you do not end up rebuilding the entire history the day the threshold is crossed.

    In summary

    The SYSCOHADA revised 2019 package (balance sheet, income statement, TFT, TVCP and 47 notes) is the summary deliverable that stands as evidence — and the most costly to produce by hand because of the dozens of consistency controls to maintain. Generated from the trial balance, with notes that recompute themselves, it goes from several weeks to one click.

    To generate your package and your 47 notes from your entries, start free on SynkriaOps.