Cadense posts tagged "Banking" — AP automation notes, reconciliation guides, and agent operations patterns.
3 published posts
Why a single $50k legal invoice in your baseline can blind a classical z-score, how robust statistics fix it, and the five signals Cadense uses to flag spend spikes without drowning AP teams in noise.
A worked example of how Cadense matches bank transactions to invoices and payments using five independent signals — amount, date, identity, history, and topology — with weekend-aware tolerance, a rules layer, and a 15-category exception taxonomy.
A real walkthrough of the five-stage cascade Cadense uses to suggest GL codes — deterministic rules first, embeddings as a fallback, abstention when nothing fits — and the trade-offs we made along the way.