01 / OPERATING CONTEXT
Finance requests that require coordinated execution.
A request about billing, cash or the close rarely stops at a single number. Someone has to collect the right records, apply the appropriate checks, explain the exceptions and prepare an output another person can review or act on.
The Finance Agent Orchestration architecture puts a Teams-facing orchestration agent in front of specialized finance agents. The request starts in an existing work environment; the orchestrator coordinates the relevant agent capabilities and supporting business services.
Each specialist has a defined responsibility. Shared services supply calculations and evidence, while the agent layer coordinates the work and prepares the explanation. Review and approval remain part of the process.
02 / IMPLEMENTATION SCOPE
Application and service capabilities.
Billing and reporting
Review recurring billing, identify changes and exceptions, check reporting completeness and prepare explanations tied to the source evidence.
Expense completeness and close
Identify missing expense patterns, prepare accrual recommendations and coordinate close checks, missing artifacts and unresolved exceptions.
Cash and collections
Prepare cash outlooks using receivables, payables and timing drivers. Prioritize collection follow-up using aging, disputes and customer context.
Vendor spend
Examine spend patterns, invoice and contract consistency, unusual changes and concentration to identify items that need finance review.
03 / ARCHITECTURE & TOOLS
System boundaries and the stack behind them.
Teams is the access point to an Azure-based multi-agent architecture. A shared orchestration agent coordinates specialists, with reusable identity, business services and evidence standards underneath.
Teams and orchestration
The Teams application passes the user's request into an Azure-hosted orchestration layer. Entra ID supplies identity context. An agent registry and domain metadata define each specialist's responsibilities, dependencies and available capabilities.
Specialized finance agents
Billing, Reporting, Expense Completeness, Month-End Close, Cash Forecast, Collections and Vendor Spend agents each have bounded responsibilities and review or escalation rules.
Shared business services
A business API layer connects PSA, GL Accounting software and Microsoft services through API or MCP integrations. Deterministic services own calculations, source evidence and structured report contracts.
Tools, frameworks and their roles
- Microsoft Teams · Microsoft Entra ID
- The user entry point and enterprise identity context for finance requests.
- Microsoft Azure · Azure Key Vault
- Hosting and secret-management architecture for the assistant and supporting services.
- TypeScript · Node.js · Fastify
- The orchestration and domain contracts, runtime and business API supporting finance-agent execution.
- PSA · GL Accounting software · Microsoft Graph · MCP
- Connected operational, accounting and Microsoft services accessed through defined API and tool contracts.
- Vitest · tsx
- Deterministic finance-service tests and TypeScript runtime tooling.
Domain logic, controls & engineering decisions
- Specialist agents share orchestration and identity while retaining their own domain responsibilities.
- Calculations and accounting checks remain in testable business services, separate from AI explanation.
- Billing review compares preview records with customer, contract and historical context to identify missing or new customers, price and quantity changes, duplicates and recurring-invoice gaps.
- Structured report contracts carry findings, severity, source evidence and recommended action from the business API through the agent layer to Teams.
- Accrual recommendations, accounting judgments and external actions follow review and approval rules.
- Shared report and evidence standards give each agent a consistent way to return usable work.
04 / WORKFLOW WALKTHROUGH
From a Teams request to a billing review.
Billing review shows the division of work between the entry point, orchestration, specialist agents and business services.
- 01
Ask through Teams
A user requests a review of a billing period. The request enters the shared assistant with the context needed to identify the finance task.
OUTPUTA scoped finance request - 02
Coordinate the specialist
The orchestration agent routes the work to the Billing Review Agent and its defined business-service dependencies.
OUTPUTThe right agent and source context - 03
Check and explain
Business services check customer changes, prices, quantities, recurring invoices and duplicates. The agent organizes the findings and supporting evidence for review.
OUTPUTPrioritized, evidence-backed findings - 04
Return work ready for review
A Teams response and structured review output bring the findings back to the user, with recommended actions and the context for an approval or escalation.
OUTPUTA review report and clear next steps
05 / SYSTEM OUTPUTS
What the system produces.
Finance capabilities become accessible through the environment people already use. The architecture carries a request into coordinated specialist work and returns an output that a finance operator or business leader can evaluate and act on.
- Billing review findings with source evidence
- Reporting explanations and accrual recommendations
- Close checks and cash outlooks
- Prioritized collection and vendor follow-up