START WITH THE PRODUCT STEPS Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration. S24: Compare vendor invoices with approved quotes and ordered services Starter kit Status: Proposed / not tested PURPOSE Vendor invoice received → compare line items against approved quote/order/authorized amendments → arithmetic reconciliation and unapproved-or-unclear line-item review queue. PREREQUISITES 1. Sanitized vendor ID, event/order ID, quote/version, approved service codes, units/rates/currency/tax treatment, authorized amendments, invoice line IDs and approval references. Exclude bank/payment information. Staff must map vague service descriptions rather than allowing approximate joins to silently equate them. 2. Synthetic files first. Real use requires firm-approved access, privacy, processing terms, retention controls, export coverage and a named reviewer. 3. Prepare any required original files or rendered evidence separately. This kit does not configure accounts, connectors or live actions. FILES AND FORMATS approved-orders.csv: vendor_id, order_id, quote_version, service_code, approved_units, approved_unit_rate, currency, approved_tax_amount, approval_ref amendments.csv: vendor_id, order_id, amendment_id, service_code, approved_units, approved_unit_rate, currency, approved_tax_amount, approval_ref invoice-lines.csv: vendor_id, order_id, invoice_id, line_id, service_code, description, units, unit_rate, currency, tax_amount, line_total, source_ref scope.txt: approved service mappings and invoice coverage Files without .example are blank input worksheets; CSV templates contain headers only. .example files contain invented records for the dry run. Text input .txt files contain blank labeled fields. Use the original base filename when supplying an example to the prompt, or explicitly map the example filename to that input. CSV files are UTF-8 with comma delimiters, quoted fields where needed, and CRLF row endings. Preserve identifiers as text when importing into Excel. Blank means missing or unresolved, never a zero or a pass. Multi-value fields use a pipe only where the fixture scope says so. SETUP AND DRY RUN 1. Copy this kit to an approved working folder. Keep examples separate from any real exports. Do not upload client, privileged, personal, credential or financial-account data to an unapproved service. 2. Read the .example text policy/scope files and all .example.csv inputs together. They define this fixture only. For a real pilot, fill the blank templates from approved exports without changing headers and obtain approved policy values. 3. Use native read-only exports, exact joins and arithmetic for deterministic checks. This kit includes no executable automation, OAuth setup, live-action instructions or importable Make blueprint. 4. Give only the approved prepared inputs to a firm-approved text assistant and use the recipe prompt below. Keep source IDs, source row numbers and unresolved evidence visible. 5. Compare the proposed result with expected-fixture-result.txt. Verify every listed issue and that the prompt invents no missing evidence. The expected file describes assertions, not a performed workflow run. 6. Have the named reviewer check source evidence and record remaining questions before any separately authorized action. RECIPE PROMPT Compare these invoice rows with the matching approved quote, order and amendments using exact vendor and order IDs. Recalculate supplied quantities and rates, preserve currency and show unmatched descriptions, extra services, travel, duplicate lines and missing authorizations. Do not call a charge fraudulent, decide contractual liability, approve payment, post accounting entries or contact the vendor. Produce a factual comparison and questions for the purchasing owner. scope.txt must state whether line_total includes tax, the rounding policy, and whether each amendment replaces or adds to the base order. Missing or conflicting rules remain uncertain; do not infer them. INPUTS approved-orders.csv: vendor_id, order_id, quote_version, service_code, approved_units, approved_unit_rate, currency, approved_tax_amount, approval_ref amendments.csv: vendor_id, order_id, amendment_id, service_code, approved_units, approved_unit_rate, currency, approved_tax_amount, approval_ref invoice-lines.csv: vendor_id, order_id, invoice_id, line_id, service_code, description, units, unit_rate, currency, tax_amount, line_total, source_ref; scope.txt: approved service mappings, invoice coverage, tax inclusion, rounding policy, and amendment replacement/additive precedence OUTPUT invoice-review.csv: vendor_id, order_id, invoice_id, line_id, service_code, approval_ref, observed_units, approved_units, observed_unit_rate, approved_unit_rate, currency, recalculated_total, stated_total, difference, source_ref, issue, reviewer_question. Exact arithmetic and staff-approved mappings only. Use only these synthetic or firm-approved inputs and preserve source row/page IDs. Keep missing or conflicting evidence unresolved. Return a draft for the named reviewer. Do not send messages, connect accounts, change records or permissions, move money, or make legal decisions. Keep source files unchanged. List missing prerequisites before continuing. REVIEW CHECKLIST [ ] Headers match the exact input schema and the export covers the stated scope [ ] Synthetic example files were used alone for the first dry run [ ] Every output finding retains its original source ID/row/page reference [ ] Missing keys, contradictions, unavailable originals and ambiguous dates remain unresolved [ ] Every expected fixture finding is present; no live action or unsupported result is claimed [ ] Responsible reviewer checks the original records before a real deployment RECIPE-SPECIFIC REVIEW Purchasing owner/bookkeeper verifies scope and calculations, attorney resolves contractual issues. Test a legitimately approved rush amendment, a duplicate line and similar descriptions for different services. Distinct from A19 expense-entry preparation. VALIDATION Exact CSV header order, field counts, serialized round-trip values and fixture semantics were checked during kit preparation. This does not test OCR, a vendor integration, a model response or end-to-end reliability. All data and identifiers are synthetic. Dates are fixed fixture dates, not current monitoring results.