api.suitsbooks.nlGuideReference

CoA providers

Chart of accounts providers

this is a concept design to solve the problem of a company’s CoA not being fixated / Locked to one signular framework like RGS 3.5 or RGS 3.7

coa_providers → registry of standard frameworks (RGS 3.7 NL, IFRS 2023 BE, etc)

company_coa_profiles → companies can link to one or many providers

each link is a “profile” (can be named)

Company can activate/deactivate profiles as needed

gl_accounts / gl_rules → always scoped to a company_id + coa_provider_id

Benefits of Profiles

  • company can run multiple charts in parallel:

    • RGS for local Dutch statutory reporting

    • IFRS for group consolidation

    • custom tax CoA for VAT filings

  • each profile has its own:

    • accounts (gl_accounts)

    • rules (gl_rules)

    • journals (linked via profile)

  • same transaction can be posted into multiple ledgers → each profile gets its own journal entry set

For each profile:

-1 looks up rules (gl_rules) scoped to that profile
-2 creates journal_entries + journal_lines linked to that profile
-3 Logs into gl_log



>1 profiles active, how does this bleed into our booking engine

When you post a transaction:

  • company has two profiles active (exp:

    • profile 1: RGS 3.7 NL

    • profile 2: IFRS 2023 BE
      ),
      then the transaction is posted twice:

  • once into the RGS ledger (journal_entries + journal_lines tied to company_coa_profile_id for RGS)

  • once into the IFRS ledger (journal_entries + journal_lines tied to company_coa_profile_id for IFRS)

Logs (gl_log) record the result per profile, so you can audit how each system interpreted the transaction