The Blueprint for a Global AI Finance Hub: My "North Star" Structure

Even before the meetings happen, preparation is everything.

I’ve been brainstorming how to take the principles we learn here and scale them for a global corporation (14,000 employees, 72 countries).

This is the "North Star" for my journey toward becoming an AI Finance Manager. It’s a technical skeleton that ensures security, scalability, and—most importantly—the K.I.S.S. (Keep It Simple Stupid) model for the end-user.

The Infrastructure (The Engine Room)

Using the folder structure we’ve mastered, I’ve mapped out how a global hub would actually look "under the hood":Plaintext/

├── CLAUDE.md # The Master Router (Direct OData Logic)

├── /identity # ACCESS CONTROL GATE

│ ├── global_admins.md # Full access (Admin level)

│ ├── DK.md # Validated users for Denmark

│ └── [70+ countries].md # Global validation files

├── /library # THE COMMAND CATALOG

│ ├── /global # Standard tools (e.g., /extract_ledger)

│ └── /local # Country-specific tools (e.g., /dk_vat_report)

├── /core-logic # THE ENGINE ROOM

│ ├── date_parser.md # Translates "MMYY" into OData parameters

│ └── odata_templates.md # Master OData entity mapping

├── /countries # LOCAL CONTEXT & AUDIT

│ └── /DK

│ ├── audit-log.md # Record: Date | User | Command | Status

│ └── local_settings.md # Local Legal Entity IDs / Currencies

├── /technical # SYSTEM RELIABILITY

│ ├── mcp_config.md # OData read-only parameters

│ └── health_check.md # System status triggers

└── /schemas # EXCEL TEMPLATES

└── ledger_standard.xlsx # Raw data structure

The User Journey: From Teams to "Done"

I want a user (let’s call him Lars) to get what he needs in under 60 seconds without ever touching a complex ERP menu.

The Request: Lars types /dk_vat_report 0126 in Microsoft Teams.
The Gatekeeper: The system checks /identity/DK.md. Lars is validated.
The Health Check: The system pings the MCP (Model Context Protocol). Connection is green.
The Data Pull: The AI uses the date_parser to see that 0126 means January 2026. It reaches directly into D365 via OData.
Delivery: The AI maps the data into a clean Excel template and uploads it to the chat.
Audit: The system silently logs the action for compliance.

The Outcome: Lars spends 0 minutes navigating menus and 100% of his time analyzing the figures for month-end closing.

The Execution Pipeline (The "Rules of the Road")

I’ve defined strict Strategic Guardrails:

Rule - Description

No Persistence - The bot starts fresh every time. It never "remembers" sensitive data between users.

Read-Only - The system is strictly prohibited from writing or deleting data. Only GET (Read) is permitted.

Local Priority - If a /local command exists, it always overrides a /global command for that specific country.

Logic over UI - We pull data through OData templates to ensure accuracy, bypassing front-end bugs.

Why this matters

This isn't just a hobby project. By thinking in this structure before the first "dry run," I can show the Head of AI and the Head of Finance exactly how we manage security and global scalability.

We aren't just automating; we are building a Global AI Infrastructure.

Getting closer to that AI Finance Manager title every day!

10 comments