Skip to content

Finance and corporate operations

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Finance & Corporate Ops
Prototype reference Finance & Corporate Ops prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Procurement, expenses and approvals are spread across email and spreadsheets with no audit trail.

Product intent

Procurement, expenses, approvals and ledger integration with separation of duties built in.

What the Factory makes different here: approval chains from the approval-policy pattern (quorum, separation of duties, expiry).

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Integration Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration, security
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Integration Architect Agent, Backend Developer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: platform-cost-optimization-workflows.

Generated product shape

C4Context
    title Finance and corporate operations system context
    Person(user, "Users", "Finance & Corporate Ops users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Finance and corporate operations") {
        System(ctx_Procurement, "Procurement", "requests, vendors, orders")
        System(ctx_Expenses, "Expenses", "claims, policies, reimbursements")
        System(ctx_Ledger, "Ledger", "postings, periods, integration")
    }
    Rel(user, ctx_Procurement, "uses through the product gateway GW-07")
    Rel(factory, ctx_Procurement, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Procurement requests, vendors, orders OrderApproved
Expenses claims, policies, reimbursements ClaimApproved
Ledger postings, periods, integration PeriodClosed

Modules and templates

Module Template Notes
Microservice ×3 connectsoft-microservice
ERP connector client connectsoft-api-library
Shell connectsoft-blazor-saas-shell
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Finance & Corporate Ops prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed; ERP through a certified connector.