A Payment Schedule Must Survive the Ledger
TL;DR for operators Financial AI becomes consequential when it recommends which invoices to pay, how much cash to retain, or which collections to prioritize. Access to ERP records does not automatically make those recommendations correct. Architectural contribution: A proposed three-engine system assigns financial records and relationships to a knowledge graph, constrained calculations to an optimization engine, and request interpretation and explanation to specialized LLM agents. Operational mechanism: Context engineering selects the relevant entities, historical states, permissions, business constraints, computational steps, and validation checks for each financial question. A separate validation process checks generated claims against structured evidence and solver outputs. Production observations: Across 15 selected deployments, the authors report approximately 7–9% unsupported recommendations in early single-agent reviews versus roughly 1% in later graph-backed production reviews. Deployment duration also declined from approximately six to two weeks. Evidence boundary: These are uncontrolled observational comparisons, not estimates of the architecture’s independent causal effect. The paper does not establish financial returns or universal reliability. Implementation priority: For decision-bearing financial workflows, invest in source normalization, temporal validity, explicit optimization constraints, claim-level verification, and reproducible audit trails before expanding agent autonomy. A plausible payment schedule can still be wrong A finance manager asks an AI assistant which supplier invoices should be paid this week while preserving enough cash for payroll and other commitments. ...