Draw request package for your lender

Build my draw request package for [PROJECT NAME OR LINK].

1. If I have not given you the cutoff date for my last draw, ask me for it and stop there. Do not pull anything until I answer. Nothing in FlipperForce stores that date, so guessing it will either overstate the request or leave money out.
2. Pull every expense line item on the project dated on or after that cutoff. Use the date filter on the line item endpoint rather than pulling everything and filtering yourself, and follow the pagination cursor to the end.
3. Use the totals the API returns for the full filtered set as the amount requested. Do not add up the page you happened to read. Check your own sum against those totals and tell me if the two disagree.
4. For each distinct transaction behind those line items, fetch the transaction itself to see whether a receipt is attached. The line item records do not carry receipt status, so this needs its own pass.
5. Pull the project photo log and keep the photos dated inside the same window. The photo log nests its results under photos by date rather than returning a flat list.
6. Download every receipt file attached to those transactions, and download every photo you are including. Check each downloaded receipt against the file size the API reports and tell me if any of them do not match.
7. Build the package as a single PDF in this order and no other: cover page, category breakdown, line item detail, progress photo gallery, then every supporting receipt appended in full at the end.
8. Put the amount requested on the cover as the largest element on the page, with the property address, the period start date, and the date prepared. Below it list the line item count, transaction count, vendor count, net of tax, sales tax, number of receipts appended, and number of photos.
9. Build the category breakdown with one row per expense category and these columns in this order: Category, Labor Total, Material Total, Labor and Material Total, Other Total, Tax, Gross. Class columns are net of tax. Every row must foot, meaning the class columns plus tax equals the gross for that row. Show a total row. Do not include a line count column and do not include a combined net column. Labor and Material is a real classification in FlipperForce, so give it its own column rather than folding it into Labor or Material.
10. Group the line item detail by transaction, not by category. Head each group with the vendor, invoice number, and date. For each line show the description, category, class, net, tax, and gross, with a subtotal per transaction and a grand total at the end.
11. Place the progress photos inline in the document as a visible gallery, three per row, in the order they appear in the photo log, labeled with their photo date. Do not list photo filenames or links in place of showing the images.
12. Append each receipt as the original file, unmodified. Do not re-render, screenshot, or summarize a receipt in place of the actual document. Bookmark each one by vendor and invoice number.
13. This document goes to a lender. Do not include an internal review section, a missing backup section, a receipt coverage count, a flag or exception list, or any annotation calling out a weakness in the data. Present what is there, cleanly.
14. Tell me in chat, separately from the PDF, the amount requested, the page count, how many receipts were merged, and how many photos were included. In that same chat message list every problem you found: any line item whose transaction has no receipt, any large amount sitting in a generic category, any line with no vendor attached, any two identical amounts on the same day, and anything you could not verify. That list is for me so I can fix it before I send the package. It does not go in the document.
15. Change nothing. This is read only. Do not create, edit, or delete any record, and do not alter a receipt file when you append it.

‍