Why should you care?

Finance teams distrust black-box postings; AI must explain and draft while humans approve journal entries.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Erp/ErpExplainController.cs
[ApiController]
[Route("api/erp/gl")]
public sealed class ErpExplainController(VarianceReasoner reasoner) : ControllerBase
{
    [HttpGet("variance/{accountCode}")]
    public async Task<ActionResult<VarianceAnalysis>> Explain(
        string accountCode, [FromQuery] decimal delta, CancellationToken ct) =>
        Ok(await reasoner.AnalyzeAsync(accountCode, delta, ct));
}

What happened?

• ErpExplainController exposes structured variance analysis for finance UI embedded in ERP screens.
• Follow the steps below — typing the code yourself is the fastest way to learn.

Practice next

1. Connect GlPlugin to read-only replica of ledger DB.
2. Map ErpExplainController routes in ERP Blazor host.
3. Require FinanceRead policy on GET variance.
4. Add drill-down links from analysis steps to transaction IDs.
5. Compare reasoner output to rule-based baseline in eval tests.

Remember

ERP AI focuses on explain and draft, not silent posting. GlPlugin reads authoritative ledger data. Expose structured VarianceAnalysis to finance UI.

Controller variance review

Finance controller clicks Explain on travel expense spike.

Outcome: VarianceReasoner returns ranked causes tied to fetch_balance tool output.