synkriaops

Tag: syscohada

  • 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.

  • Best accounting software in Cameroon (2026): how to choose

    The best accounting software in Cameroon in 2026 is the one that is natively SYSCOHADA revised 2019, that handles Mobile Money (MTN MoMo, Orange Money), that generates the FEC and the statutory tax package, and that works in CFA francs (XAF) — not a French or Anglo-Saxon tool retrofitted after the fact. Below are the 8 concrete selection criteria, what separates a real OHADA tool from an imported one, and where SynkriaOps stands in this landscape.

    Why the question deserves real framing

    A Cameroonian SME looking for accounting software quickly runs into two families of tools, neither of which fits as-is:

    • French or Anglo-Saxon suites (designed for the French chart of accounts, 20% VAT, the euro, the SIRET). They are mature but structurally foreign to the SYSCOHADA framework.
    • Excel spreadsheets and standalone invoicing tools, which handle sales but not the standardized accounting required by the tax authority.

    Choosing therefore means first verifying deep compatibility with the OHADA standard — not a list of attractive features. Here is the grid.

    The 8 selection criteria

    1. Native SYSCOHADA revised 2019 framework

    This is the disqualifying criterion. The chart of accounts must be the OHADA one (classes 1 to 8, 411 client accounts, 401 suppliers, 422 payroll, VAT in 443/445), not a “translated” French chart. Verify that the software ships a ready-to-use SYSCOHADA chart the moment you open a file, not an empty chart to rebuild by hand.

    2. XAF currency and CFA-franc presentation

    Amounts must be natively in XAF, with no parasitic euro conversion, and statements presented in CFA francs. Software showing euro cents on a Cameroonian balance sheet betrays a superficial adaptation.

    3. Mobile Money collection

    In Cameroon, MTN MoMo and Orange Money weigh heavily in an SME’s cash flow. Good software must not only book these flows cleanly (581 transit account, never the 512 bank account) but ideally collect directly via Mobile Money with a payment QR code. This is the number-one differentiator of the French-speaking African market. At SynkriaOps, Mobile Money collection is currently being brought into service: the secure infrastructure is built, the connection with the operators (MTN, Orange) is not yet active.

    4. Statutory FEC export

    The Fichier des Écritures Comptables (FEC) is the standardized format the tax authority may request during an audit. The software must generate it for each closed fiscal year, in the revised SYSCOHADA format, not in a proprietary export the inspector cannot read.

    5. Complete financial statements and tax package

    Balance sheet, income statement, cash flow statement (TFT), statement of changes in equity (TVCP), and above all the notes 1 to 47 of revised SYSCOHADA. This is the most time-consuming part of a closing: software that generates them automatically saves you weeks of accounting-firm work.

    6. CEMAC VAT and local taxation

    Cameroonian VAT is 19.25% (a rate many imported tools reject because they are calibrated to 20% or 19%). The software must handle this rate, the VAT return, the deduction proration, and local specifics such as withholding at source (tax advance).

    7. Compliance and immutability

    The tax authority expects immutable accounting. Look for: non-reusable sequential numbering, immutability of validated entries (no retroactive edit possible), traceability (audit trail). These are audit guarantees, not marketing.

    8. Collaboration and firm mode

    If you work with an accountant, the software must let the business record and the accountant validate and review — in real time, on the same file, without emailing Excel files back and forth. For an accounting firm, multi-file management with strict data isolation is essential.

    Comparison of tool families

    CriterionImported suiteExcel / invoicingNative OHADA tool
    SYSCOHADA revised 2019AdaptedNoNative
    Native XAF currencyPartialManualYes
    Mobile Money importNoNoYes
    Mobile Money collectionNoNoIn progress
    FEC exportOther formatNoYes
    Tax package + 47 notesNoNoYes
    VAT 19.25% / CEMACRareManualYes
    Provable immutabilityVariableNoYes

    Pitfalls to avoid

    • “OHADA-compatible” on the brochure, but a French chart in reality. Ask for a demo and check the 411 account and the 19.25% VAT.
    • Invoicing without accounting. Issuing an invoice is not keeping accounts. You need the general ledger, the trial balance, reconciliation.
    • No FEC. Without a FEC, you are exposed on audit day.
    • No mobile strategy. Your field teams must be able to capture an invoice from a phone, not re-enter it at the office in the evening.

    Where SynkriaOps stands

    SynkriaOps is an accounting and management SaaS designed from the ground up for CEMAC and OHADA — the stated positioning is that of a “SYSCOHADA Pennylane”. In practice, it ticks the 8 criteria above:

    • SYSCOHADA revised 2019 chart of accounts, bilingual FR/EN, delivered turnkey per file.
    • Mobile Money collection for MTN MoMo and Orange Money — currently being brought into service: the secure infrastructure (HMAC-SHA256 webhook, AES-256-GCM encryption, payment QR code) is built, the connection with the operators is not yet active.
    • Statutory FEC generated per fiscal year, complete tax package with the 47 notes, balance sheet, income statement, TFT and TVCP.
    • CEMAC VAT across 6 countries (Cameroon, Gabon, Congo, Chad, CAR, Equatorial Guinea) with return, proration and PDF/CSV/XLSX exports; configurable withholding at source.
    • Immutability via chained SHA-256 hash and immutability of validated entries.
    • Collaborative and multi-file firm mode with strict per-file data isolation.
    • Field mobile app (photo capture, banking, stock, barcode scan) — currently in internal pilot distribution.

    We stay honest about the limits: 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 published on the stores. The accounting core, however, is complete.

    In summary

    The right software is not the best-known one: it is the one that natively speaks SYSCOHADA, CFA francs, Mobile Money and FEC. Run every candidate through the 8 criteria above, demand a demo on your real documents (an invoice with a NIU and 19.25% VAT), and watch the closing: that is where the difference plays out between an attractive tool and one that saves you weeks.

    To check these criteria on your own documents, start free on SynkriaOps and open a test file in minutes.

  • 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.

  • Managing multi-warehouse stock with accounting valuation (weighted average cost) in SYSCOHADA

    Managing multi-warehouse stock with accounting valuation means tracking quantities per warehouse while computing, at each movement, the stock value at weighted average cost (WAC) — so that your inventory value on the balance sheet (class 3 accounts) always reflects physical reality. This is what separates simple “quantity tracking” from real commercial management integrated with accounting. Here is the mechanic, and how mobile scanning and accounting hold together.

    WAC: the right valuation method

    When you buy the same item at different prices over time, at what value does it leave stock on a sale? SYSCOHADA favors the weighted average cost (WAC): at each inbound movement, a new average unit cost is recomputed.

    WAC formula after an inbound movement:

    WAC = (value of existing stock + value of the inbound)
      ÷ (existing quantity + inbound quantity)

    Example:

    • Opening stock: 100 units at 1,000 XAF → value 100,000 XAF.
    • Inbound: 50 units at 1,300 XAF → value 65,000 XAF.
    • New stock: 150 units, value 165,000 XAF → WAC = 1,100 XAF/unit.
    • An outbound of 30 units is valued at 30 × 1,100 = 33,000 XAF.

    WAC smooths purchase-price variations and gives a stable and defensible valuation in an audit — unlike an approximate “latest price” valuation.

    Multi-warehouse: quantities per site, consistent value

    A trading SME often has several storage points: central warehouse, shop, secondary depot. The challenge is to track where each unit is, without losing overall accounting consistency.

    The necessary building blocks:

    • Identified warehouses (name, code, address, main warehouse, responsible keeper), enable/disable.
    • Stock per warehouse: quantities and valuation split by site.
    • Typed movements: inbound, outbound, adjustment, inventory — each attached to a warehouse and, ideally, to an accounting document/entry.
    • Per-item thresholds (minimum, reorder point, maximum) to steer replenishment and detect stockouts.

    Inter-warehouse transfers

    Moving stock from one warehouse to another must never be a manual double entry “out here / in there”: that is the door to variances.

    A clean transfer is a single operation with:

    • A source warehouse and a destination warehouse.
    • One or more lines of items with quantities.
    • A workflow (draft → validated), validation by the keeper, a possible return, a cancellation.
    • A transfer note (PDF) for physical traceability.

    Valuation follows the goods: value leaves the source warehouse and arrives at the destination at the same WAC, with no creation or destruction of value.

    Inventory and valued variances

    Periodically, you physically count the stock and compare it to the theoretical stock. The variance must be:

    • Valued in XAF (variance quantity × WAC), not just in units.
    • Booked via an inventory-variance entry (adjustment of the balance sheet stock value and recognition of the corresponding expense/income).

    Without this step, the stock value on the balance sheet diverges from reality — and the inspector notices. Multi-product inventory campaigns (with line-by-line entry and validation) make the exercise manageable even on wide catalogues.

    The bridge with SYSCOHADA accounting

    Stock is not just a quantity table: it is an asset on the balance sheet (class 3). Each physical flow must find its accounting counterpart:

    • Stock inbound → class 3 movement, linked to the purchase (class 6 / supplier 401).
    • Outbound on sale → recognition of the cost of goods sold.
    • Inventory variance → valued adjustment entry.

    It is this stock ↔ accounting integration that distinguishes serious commercial-management software from a mere product-sheet manager.

    Mobile scanning: stock in the field

    The most rigorous valuation is worthless if field entry is painful. Hence the value of barcode scanning (EAN-13, EAN-8, Code 128) on mobile:

    • Scan an item to find or update it instantly.
    • Run a mass inventory by scan during a campaign.
    • Mass-create catalogue products by scanning a list of items.
    • Correct the warehouse of an item from its sheet (traced transfer), manage expiry and thresholds.

    The field scans, the accounting stays correct.

    How SynkriaOps does it

    SynkriaOps embeds ERP-grade multi-warehouse stock management, tied to SYSCOHADA accounting:

    • Warehouses and stock per warehouse (quantities + valuation split), warehouse optional or mandatory depending on your configuration.
    • WAC valuation recomputed at each movement, with total valuation and a stock dashboard (dormant, stockouts, below-minimum).
    • Inter-warehouse transfers with workflow, keeper validation, return and a PDF transfer note.
    • Inventory sessions and campaigns with variance valued in XAF and variance-entry generation.
    • Mobile app: barcode scan, quantity capture, default VAT by regime, mass inventory by scan, transfer from the sheet — currently in internal pilot distribution.
    • Accounting integration: stock movements feed class 3 accounts and link to documents.

    Stock steering indicators

    A correct valuation also serves to steer. A few indicators to track:

    • Value tied up at WAC — how much cash “sleeps” in stock.
    • Dormant items — references with no movement for a long time, candidates for impairment or clearance.
    • Stockouts and below-minimum — items under their threshold, to replenish.
    • Turnover rate — how fast stock moves: a low rate signals overstock, a high rate a stockout risk.
    • Expiry — for dated products, expired or soon-to-expire lots, which weigh on real value.

    These indicators link operational management (what to order, what to clear) to accounting reality (the value on the balance sheet). Without a reliable valuation, they mislead; with WAC recomputed at each movement, they become decision levers.

    In summary

    Well-kept multi-warehouse stock is three things together: quantities per warehouse, a WAC valuation recomputed at each movement, and an accounting bridge to class 3 accounts. Add mobile scanning for field entry, and you get commercial management that never drifts from the accounting.

    To manage your multi-warehouse stock with integrated accounting valuation, start free on SynkriaOps.