Automation
Receipts filed automatically
The system collects the receipts for the month itself: it reads the mailbox, checks the sender and files the receipt.
| Kind | Automation |
|---|---|
| Start | |
| Technology | Python |
| Third-party dependencies | 0 |
| In service | 1monthrunning |
In detail
What breaks automations like this is rarely the filing. It is the forged invoice that looks like the real one. So this system verifies the sender’s DKIM signature per RFC 6376 in its own code, and checks attachment filenames and actual file types as well.
Dry run is the default: nothing is written without explicit approval, and every decision it made is in the log afterwards. The code that reads the mailbox is entirely ours and manages without third-party libraries.
The log for this system.
- Build
Built the receipt pipeline, implementing RFC 6376 DKIM verification ourselves rather than trusting a library to get exactly that right.
Next step
We will tell you up front where the time will go.
Describe your plan in a few sentences. We will name the two or three places where a system of this kind turns expensive.