File receipts, reconcile card bills and build a checked payment list

Shahram Pourmakhdomi, who runs the one-person consultancy Poush Digital in Sweden, replaced his monthly evening of renaming receipts with three Claude skills, a set of OneDrive folders and one Microsoft Dataverse table as the expense register. The intake skill reads every PDF, screenshot and photo in an inbox folder, pulls out supplier, date, total, VAT and currency, decides whether it is a receipt or an unpaid invoice, renames and logs it, and moves it into the folder that marks its state. A reconcile skill reads each credit card bill and lists purchases with no receipt in the register. A payment-list skill reads unpaid invoices and builds a worklist by due date. Python scripts do the matching, sums and check digits. Intake runs as a scheduled task at 07:00 every weekday through the Microsoft 365 connector; the first version ran on his Mac against an Excel register. A small Power Automate flow, not the agent, emails filed documents to his accounting system.

He reports that every incoming receipt and invoice is now read, classified and filed without him, card bills are checked for missing receipts automatically, and he only gets a notification when something was processed. The register also feeds a read-only dashboard he built as a Claude artifact. Payments stay manual: he pays in his bank, then tells Claude which invoice he paid and the skill moves the file and records the date. Unclear documents go to a review folder for him. He gives no figures for time saved or error rates.

The hard part was the receipt-or-invoice call: Swedish firms print bank details on every document, so he wrote ordered rules (already paid beats everything, direct debits never go on the payment list). The extracted card-bill lines must add up to the bill's printed total, and a valid check digit only proves a number is consistent, not that it belongs to the supplier. The author sells AI agent consulting.