Please sweep the receipts out of [DRIVE FOLDER NAME, or GMAIL LABEL] and file them into FlipperForce.
1. List the receipt images and PDFs you find, with filenames and dates. Do not upload anything yet.
2. Pull my project list so you have the names and addresses to match against.
3. Read each receipt and work out the vendor, date, total, and which project it belongs to. Use the property address if the receipt shows one, otherwise the folder or subject line, otherwise tell me you cannot tell.
4. Show me a table before you upload anything: filename, vendor, date, total, and the project you plan to file it under. Mark your confidence on each row.
5. Wait for my confirmation. Upload only the rows I approve. Leave anything you were unsure about in the folder and tell me why, because a receipt on the wrong project is worse than one still sitting in the folder.
6. When the uploads are done, confirm what was filed on which project and list anything that failed.
7. Then ask me separately whether I want these converted into expense transactions. Do not create any transaction until I say yes, and if I do, show me the line items and the totals before saving and stop if a total does not match the receipt.
Do not delete or move anything in Drive or my inbox.
Your assistant needs access to wherever the receipts live as well as to FlipperForce, so this runs in a client that can reach both, such as Claude with a Google Drive or Gmail connection turned on plus code execution.
Uploading a file to FlipperForce is a three step process. The API issues an upload intent, the file bytes go to a signed URL with exact headers and a checksum, then the receipt record is created. Your assistant handles all three, but it means this automation needs code execution rather than plain REST calls.
One receipt links to one expense transaction. If a single image covers purchases for two properties, split it by hand before running this.
Receipts arrive as email attachments and phone photos dumped into a Drive folder. They sit there because filing them means opening each one, working out which property it belongs to, and uploading it by hand.
Then the folder has ninety receipts in it, your books are missing spend you definitely incurred, and your lender asks for backup on a draw you cannot fully support.
Your assistant reads the receipt images out of the folder or label you point it at, reads each one to work out the vendor, date, total and which property it belongs to, and shows you the routing plan as a table before anything is uploaded.
Once you approve, it uploads each file and creates the receipt on the right project. Anything it could not confidently assign to a project stays in the folder with a reason, because the wrong project is worse than an unfiled receipt.
What it will not do: it does not delete or move anything in your Drive or inbox, does not upload a receipt to a project you did not approve, does not create an expense transaction unless you ask for that second step, and does not invent a total it could not read off the image. Unreadable receipts get listed for you to handle by hand.
This prompt requires a connection to the FlipperForce Public API. Once your AI agent is connected to your account, you can run any prompt in the library.
Learn how to connect your AI agent to the FlipperForce Public API
Before you run this, check:
Start with ten receipts rather than two hundred. Check where the first batch landed, then turn it loose on the backlog.