Vendor Memory Around Invoice Decisions: Treating Agent Memory as Evidence, Not Authority
AdPlenty2373 · reddit · 2026-09-30
The author built an AI agent for invoice/PO exception handling, using Hindsight as the long-term memory layer.
Workflow: Invoice + PO → detect mismatch → recall similar past decisions → explain context → human decision → store as memory.
Key design choice: memory is treated as evidence, not authority. If a previous Nova Equipment invoice with a quantity mismatch was approved, the next similar invoice isn't auto-approved — the system retrieves the prior case, shows the reviewer the context and reasoning, and lets the human choose Approve, Reject, or Request Review. Only then is the decision retained.
The application database and memory layer stay separate: the database remains the source of truth, while Hindsight handles cross-case contextual retrieval.
The most interesting part is the feedback loop: Retain → Recall → Reason → Human Decision → Retain — a more useful way to think about agent memory than just making an LLM remember conversations.
Related event: Developers Share Long-Term Memory Designs for AP Invoice Agents(5 posts)→
More from coding & agent
- Google Research open-sources PaperOrchestra, a multi-agent framework for writing AI papers — google-research · 2026-11-16
- ffmpeg-skill gives coding agents local video editing via 42 FFmpeg tools and MCP — kajisho5 · 2026-11-16
- Agents Now Reply to Slack Messages on Their Own, Resolving a Prod Incident Ghost-to-Ghost — iamrobotbear · 2026-11-16
- Engineer's Interview Prep Method: Use Claude to Find Which Answers Undersell Your AI Work — brandon_galang · 2026-11-16
- DeepSeek open-sources its app frontend "chat-demo", already at 3.9k stars — NielsRogge · 2026-11-16
- lemire: AI's real impact on coding is expanding the engineer's 'cognitive radius', not speed — lemire · 2026-11-16