Life ConnectLife Connect
Wiki index
Architecture
Services
Concepts
Runbooks
Infra
Swagger Docs
GitHub
Wiki index
Architecture
Services
Concepts
Runbooks
Infra
Swagger Docs
GitHub
  • Cross-cutting concepts

    • EventBridge fanout
    • Atlas Triggers
    • ECS Fargate deploy lifecycle
    • Keycloak hosting
    • Cloudflare Pages auto-deploy
    • Bitbucket Pipelines (legacy)
    • Terraform-managed envs (legacy)
  • Accounting model

    • Accounting model
    • Events catalog
    • Accounting journals
    • Plan of accounts (PCG)
    • Auxiliary accounts
    • FEC fields (Fichier des Écritures Comptables)
    • pieceReference numbering
    • Tenant matrix (payable / receivable)
    • Owner matrix (payable / receivable)
    • Take-over UI display rules
Last updated 2026-05-04

Take-over UI display rules

AI-generated content

This document was generated by an AI assistant from the 'Event Matrix Accounting' Google Sheet. Verify accuracy before relying on the details.

When the user opens the take-over screen and selects either a tenant or an owner, the UI only displays the take-over events relevant to that side. The direction (RECEIVABLE / PAYABLE) is also constrained per event. This page mirrors the sheet's "Take-over UI rules" tab.

At a glance

EventDisplay when tenant selectedDisplay when owner selectedRECEIVABLE allowedPAYABLE allowed
ACCOUNTING_TAKEOVER_TENANT_BALANCE_DEBITORyesnoYESNO
ACCOUNTING_TAKEOVER_TENANT_BALANCE_CREDITOR_CASHyesnoNOYES
ACCOUNTING_TAKEOVER_TENANT_BALANCE_CREDITOR_NOT_CASHyesnoNOYES
ACCOUNTING_TAKEOVER_TENANT_DEPOSITyesnoNOYES
ACCOUNTING_TAKEOVER_OWNER_BALANCE_CREDITORnoyesNOYES

Why this matters

The tenant variants split into three sub-natures (rent only, rental charges only, generic misc) which all share the same display rules above; only the credit account differs (467200 / 467210 / 467220). See:

  • ACCOUNTING_TAKEOVER_TENANT_BALANCE_DEBITOR
  • ACCOUNTING_TAKEOVER_TENANT_BALANCE_DEBITOR_RENT
  • ACCOUNTING_TAKEOVER_TENANT_BALANCE_DEBITOR_RENTAL_CHARGES
  • ACCOUNTING_TAKEOVER_TENANT_BALANCE_CREDITOR_CASH
  • ACCOUNTING_TAKEOVER_TENANT_BALANCE_CREDITOR_NOT_CASH
  • ACCOUNTING_TAKEOVER_TENANT_DEPOSIT
  • ACCOUNTING_TAKEOVER_OWNER_BALANCE_CREDITOR

Open questions

  • Whether the UI enforces these rules client-side or whether the back end also validates the (event × direction) combination on persist. Worth checking before exposing the take-over flow to a new client.
Edit this page
Last Updated:
Contributors: Yevhenii Khudolii
Prev
Owner matrix (payable / receivable)