Hermes checks invoice references before CRM updates

Uygar Duzgun runs invoice processing through a dedicated Hermes profile, separate from unrelated assistant work. It examines a bounded recent IMAP window, checks local deduplication state and live Perfex CRM records, then verifies the actual invoice PDF before creating or updating an expense.

The source describes a real correction: sender and supplier clues initially directed a consultant invoice toward the wrong party, while the invoice's reference field identified the correct consultant. Duzgun changes the workflow so explicit reference data outranks a remembered supplier pattern. Existing consultant costs should be updated or receive the attachment when appropriate, rather than duplicated as new expenses.

The verification is concrete. Downloads must contain real PDF bytes rather than a login page or HTML response; amounts, references and identity must reconcile. Unclear or conflicting evidence stops the workflow for review. Sanitised memory stores recurring patterns, but cannot override live invoice evidence or a duplicate check. The account does not provide an independently audited error rate or establish that all financial decisions are unattended. The useful lesson is the precedence rule: verify the document and reference, check the live target, and treat memory as supporting context rather than authority.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Blog · Uygar Duzgun