Remittance Split
A remittance workflow where one payment has to be mapped across multiple final invoices while ignoring drafts and a proforma.
Transparency boundary
This page shows the files the model can inspect. It does not show the hidden oracle solution.
Excluded: ground_truth.json, expected_artifacts.json, human_reading.md, and calibration_results.md.
What This Tests
- single payment split
- draft bank export
- proforma distractor
- active remittance batch
Files Shown
4 generated image files and 7 text/CSV/task files.
All files are synthetic benchmark material.
Generated Images
Scans and visual attachments visible to the model.




Task And Source Files
No oracle solution files.
incoming/README_TASK.md
# Paperwork Workflow Case 06: Remittance Split
Audit this synthetic intake folder. This is benchmark bookkeeping, not financial or tax advice.
You must not modify anything under incoming/.
Case ID for audit_result.json: P3-WORK-06
Steps:
1. Identify active source files and ignore drafts, old exports, and non-invoice distractors.
2. Use the remittance advice to map the single bank payment to the final invoices.
3. Create work/attachment_index.json.
4. Create work/final_document_set.json.
5. Create normalized invoice text files under work/normalized/.
6. Create audit_result.json.
7. Create proof.txt containing only the final proof_code.
Required audit_result.json keys:
case_id, approved_invoice_ids, review_invoice_ids, reject_invoice_ids,
ignored_document_ids, total_approved_gross_cents, warnings_by_invoice,
evidence, proof_code
Required audit_result.json values and formats:
- case_id must be "P3-WORK-06"
- ignored_document_ids must be ["PRO-3303"]
- warnings_by_invoice must use short warning codes only, not prose sentences
- evidence must be an array of source path strings, not a nested object
Proof code formula:
total_approved_gross_cents
+ numeric parts of approved/review/reject invoice IDs
+ numeric part of the active remittance batch
+ 97 * total warning count
Use invoice IDs only for approved/review/reject invoice IDs. Do not include proforma or remittance document IDs in the invoice-ID sum.
Required work/attachment_index.json shape:
{"attachments":[{"attachment_path":"...","document_id":"...","document_type":"...","use":"..."}]}
Required work/final_document_set.json shape:
{
"active_bank_export": "...",
"active_remittance_batch": "...",
"final_invoice_ids": [...],
"ignored_document_ids": [...],
"ignored_source_files": [...],
"payment_allocations": [{"invoice_id":"...","gross_total_cents":123}]
}
incoming/ap_notes.txt
AP intake note, May batch:
- Use bank_export_final.csv, not bank_export_draft.csv.
- Vendor Bright Coast Office Supplies is active.
- Remittance advice RA-771 explains payment BATCH-771.
- The proforma is a quote-style document and should not be treated as an invoice.
incoming/bank_export_draft.csv
date,description,amount_cents
2026-05-07,DRAFT BATCH 771 DO NOT USE,30000
incoming/bank_export_final.csv
date,description,amount_cents
2026-05-11,BATCH-771 BRIGHT COAST REMITTANCE,29730
incoming/purchase_orders.csv
po_id,vendor_id,status,approved_invoice_id
PO-9001,V-BRIGHT,approved,INV-3301
PO-9002,V-BRIGHT,approved,INV-3302
PO-9003,V-BRIGHT,draft,PRO-3303
incoming/vendor_master.csv
vendor_id,vendor_name,status
V-BRIGHT,Bright Coast Office Supplies,active
V-FAKE,Fake Sample Vendor,inactive
model_prompt.md
Audit the synthetic remittance split intake folder in `incoming/`.
Write these files:
- `work/attachment_index.json`
- `work/final_document_set.json`
- `work/normalized/INV-3301.txt`
- `work/normalized/INV-3302.txt`
- `audit_result.json`
- `proof.txt`
Use `incoming/README_TASK.md` as the full task specification. Use the generated image attachments, the AP note, bank exports, vendor master, and purchase orders.
Important:
- Identify the active bank export and ignore the draft export.
- Use remittance advice RA-771 to split the single bank payment across two final invoices.
- Do not treat the proforma estimate as an invoice.
- Do not modify anything under `incoming/`.
- This is benchmark bookkeeping, not financial, tax, or legal advice.
- `proof.txt` must contain only the numeric proof code.