SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-032'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-032'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-032' AND decision_code='REPORT_LIVE_CUSTOMER_BALANCE'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-032' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-032 completed — REPORT_LIVE_CUSTOMER_BALANCE' AND body LIKE '%REPORT_LIVE_CUSTOMER_BALANCE%'

financebenchmark:erp_qa/Customer Balance (user-brief example rephrased onto in-world entity)

Prompt:
**Casey Morgan · AR & Collections · Teams 09:14**

Tell Collections exactly what Fourth Coffee East owes now and what records make up the balance.

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. Carry the decision through the governed case record and leave Controls a reproducible completion message.

SELECT ROUND(SUM(amount-settled),2) FROM erp_cust_trans WHERE account='SYNCUS-0069' AND txn_type='Invoice' AND closed=0

SELECT COUNT(*) FROM erp_cust_trans WHERE account='SYNCUS-0069' AND txn_type='Invoice' AND closed=0

Question: finance case work item

Question: finance case work item

FINCASE-032 completed — REPORT_LIVE_CUSTOMER_BALANCE

Question: finance case work item

Resolve immutable work item FINCASE-032 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Resolve the customer master and aggregate only its live open transactions net of settlement.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-032 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-032"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-032 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-032"}) + successful_required_calls + reads_before_write

Check metadata for lgr-032-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-032-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-032-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-032-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-032-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-032-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-032-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-032-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-032 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-032"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-032-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-032-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-032-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-032-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-032-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-032-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-032-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-032-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-032 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-032"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-032-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-032-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-032-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-032-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-032-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-032-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-032-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-032-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The customer-specific open remainder, not invoice face value or an aging snapshot, is the carrying balance.

Reject the unsupported branch: Use the first name match or sum closed transactions.

Select `REPORT_LIVE_CUSTOMER_BALANCE` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `customer_account` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `outstanding_balance` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `open_invoice_count` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-032 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use the first name match or sum closed transactions.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-033'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-033'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-033' AND decision_code='CERTIFY_BALANCE_WITH_SNAPSHOT_EXCEPTION'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-033' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-033 completed — CERTIFY_BALANCE_WITH_SNAPSHOT_EXCEPTION' AND body LIKE '%CERTIFY_BALANCE_WITH_SNAPSHOT_EXCEPTION%'

escalated variant of erp_qa/ar-balance-fourthcoffee-east via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: financebenchmark:erp_qa/Customer Balance (user-brief example rephrased onto in-world entity)

Prompt:
**Casey Morgan · AR & Collections · Teams 09:14**

Can Fourth Coffee East's balance be released to the customer after controls review?

Treat this as a live control decision rather than a lookup. Reconcile the relevant systems at their effective dates, call out any unresolved evidence gap, and do not make the numbers agree by changing unrelated records. Record the supported disposition on the open finance case and send Controls a concise completion note.

Question: finance case work item

Question: finance case work item

FINCASE-033 completed — CERTIFY_BALANCE_WITH_SNAPSHOT_EXCEPTION

Question: finance case work item

Resolve immutable work item FINCASE-033 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Reconcile live transactions to the effective customer-balance policy and explain any difference from cached aging.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-033 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-033"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-033 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-033"}) + successful_required_calls + reads_before_write

Check metadata for lgr-033-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-033-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-033-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-033-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-033-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-033-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-033-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-033-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-033 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-033"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-033-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-033-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-033-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-033-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-033-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-033-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-033-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-033-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-033 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-033"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-033-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-033-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-033-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-033-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-033-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-033-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-033-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-033-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The communicated balance must come from current open remainders and retain a control note for stale snapshots.

Reject the unsupported branch: Send the cached aging total without testing its refresh date.

Select `CERTIFY_BALANCE_WITH_SNAPSHOT_EXCEPTION` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `customer_account` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `outstanding_balance` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `open_invoice_count` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-033 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use only when the required evidence intersection is incomplete or conflicting.

Send the cached aging total without testing its refresh date.

verifiers/vcode.py (binary reward; all checks must pass)

answer_checks: submitted fields graded by type with tolerances

trace_checks: required servers visited, reads precede submission

state_checks: writes_only anti-hack veto plus SQL over the world left behind


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-034'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-034'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-034' AND decision_code='CAPTURE_ELIGIBLE_DISCOUNT'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-034' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-034 completed — CAPTURE_ELIGIBLE_DISCOUNT' AND body LIKE '%CAPTURE_ELIGIBLE_DISCOUNT%'

financebenchmark:erp_qa/Cash Discount + domain-workflows discount-capture runbook

Prompt:
**Priya Shah · AP Manager · Teams 08:20**

Should AP accelerate the Fourth Coffee East payment today, and how much is still capturable?

The earlier working paper is not a conclusion. Please determine what the current records actually support, including the viable option and any hold, then leave enough provenance for an independent reviewer to reproduce it. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

Question: finance case work item

Question: finance case work item

FINCASE-034 completed — CAPTURE_ELIGIBLE_DISCOUNT

Question: finance case work item

Resolve immutable work item FINCASE-034 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join vendor identity, invoice date, open amount, discount code chain, and today's eligibility window.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-034 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-034"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-034 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-034"}) + successful_required_calls + reads_before_write

Check metadata for lgr-034-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-034-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-034-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-034-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-034-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-034-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-034-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-034-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-034 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-034"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-034-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-034-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-034-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-034-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-034-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-034-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-034-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-034-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-034 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-034"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-034-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-034-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-034-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-034-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-034-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-034-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-034-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-034-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

An acceleration is supported only for open invoices still inside the effective discount window.

Reject the unsupported branch: Apply the headline discount to every open invoice from the vendor.

Select `CAPTURE_ELIGIBLE_DISCOUNT` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `has_active_discount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `qualifying_invoices` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `potential_discount_usd` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-034 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Apply the headline discount to every open invoice from the vendor.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-035'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-035'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-035' AND decision_code='CERTIFY_CURRENT_DISCOUNT'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-035' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-035 completed — CERTIFY_CURRENT_DISCOUNT' AND body LIKE '%CERTIFY_CURRENT_DISCOUNT%'

escalated variant of erp_qa/cash-disc-fourthcoffee-east via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: financebenchmark:erp_qa/Cash Discount + domain-workflows discount-capture runbook

Prompt:
**Priya Shah · AP Manager · Teams 08:20**

Can the proposed early-payment saving be approved after review?

I need the answer and the operational consequence, not a list of screens visited. Resolve conflicting versions and identities, use the effective rule, and make the smallest supported change without disturbing neighboring work. Update only the scoped finance case, verify what persisted, and close the loop with Controls.

Question: finance case work item

Question: finance case work item

FINCASE-035 completed — CERTIFY_CURRENT_DISCOUNT

Question: finance case work item

Resolve immutable work item FINCASE-035 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Recalculate eligibility under the effective discount policy and verify payment timing, open amount, and any next-code rule.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-035 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-035"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-035 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-035"}) + successful_required_calls + reads_before_write

Check metadata for lgr-035-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-035-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-035-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-035-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-035-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-035-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-035-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-035-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-035 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-035"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-035-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-035-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-035-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-035-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-035-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-035-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-035-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-035-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-035 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-035"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-035-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-035-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-035-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-035-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-035-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-035-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-035-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-035-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Only currently exercisable discounts may be certified; expired or chained terms remain excluded.

Reject the unsupported branch: Use the vendor master discount code without testing invoice dates.

Select `CERTIFY_CURRENT_DISCOUNT` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `has_active_discount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `qualifying_invoices` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `potential_discount_usd` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-035 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use the vendor master discount code without testing invoice dates.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-036'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-036'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-036' AND decision_code='REPORT_SPARROW_COLLECTIONS_POSITION'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-036' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-036 completed — REPORT_SPARROW_COLLECTIONS_POSITION' AND body LIKE '%REPORT_SPARROW_COLLECTIONS_POSITION%'

financebenchmark:erp_qa/Collection Letters + Payment History; customer injected by task seed (Contoso demo US-008)

Prompt:
**Casey Morgan · AR & Collections · Teams 16:40**

Give the collections meeting Sparrow's live balance, current dunning position, and recent payment behavior.

I need a decision the team can use today, with the amounts, dates, and immutable record identifiers that support it. Some surrounding records came from an older review, so establish what is current before relying on them. Carry the decision through the governed case record and leave Controls a reproducible completion message.

Question: finance case work item

Question: finance case work item

FINCASE-036 completed — REPORT_SPARROW_COLLECTIONS_POSITION

Question: finance case work item

Resolve immutable work item FINCASE-036 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Join customer identity, open transactions, settlements, and collection-letter history as of the same date.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-036 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-036"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-036 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-036"}) + successful_required_calls + reads_before_write

Check metadata for lgr-036-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-036-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-036-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-036-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-036-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-036-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-036-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-036-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-036 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-036"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-036-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-036-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-036-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-036-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-036-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-036-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-036-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-036-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-036 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-036"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-036-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-036-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-036-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-036-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-036-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-036-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-036-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-036-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The meeting position must separate current exposure, last payment, and the highest valid dunning step.

Reject the unsupported branch: Use the aged snapshot alone or infer payment behavior from letter status.

Select `REPORT_SPARROW_COLLECTIONS_POSITION` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `collection_letter_level` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `last_payment_date` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `last_payment_amount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `open_balance` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-036 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use the aged snapshot alone or infer payment behavior from letter status.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-037'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-037'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-037' AND decision_code='CERTIFY_DUNNING_POSITION'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-037' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-037 completed — CERTIFY_DUNNING_POSITION' AND body LIKE '%CERTIFY_DUNNING_POSITION%'

escalated variant of erp_qa/collections-sparrow via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: financebenchmark:erp_qa/Collection Letters + Payment History; customer injected by task seed (Contoso demo US-008)

Prompt:
**Casey Morgan · AR & Collections · Teams 16:40**

Can Sparrow's collections status be certified under the current runbook?

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. Record the supported disposition on the open finance case and send Controls a concise completion note.

Question: finance case work item

Question: finance case work item

FINCASE-037 completed — CERTIFY_DUNNING_POSITION

Question: finance case work item

Resolve immutable work item FINCASE-037 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Reperform live balance and payment checks, then apply the effective dunning timing rule to the letter history.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-037 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-037"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-037 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-037"}) + successful_required_calls + reads_before_write

Check metadata for lgr-037-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-037-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-037-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-037-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-037-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-037-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-037-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-037-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-037 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-037"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-037-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-037-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-037-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-037-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-037-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-037-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-037-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-037-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-037 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-037"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-037-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-037-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-037-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-037-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-037-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-037-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-037-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-037-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Certification depends on exact sequence and elapsed time, not merely the highest letter code present.

Reject the unsupported branch: Approve escalation from a stale summary or skip the elapsed-time test.

Select `CERTIFY_DUNNING_POSITION` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `collection_letter_level` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

File the task-specific `last_payment_date` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `last_payment_amount` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `open_balance` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-037 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Approve escalation from a stale summary or skip the elapsed-time test.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-038'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-038'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-038' AND decision_code='DECIDE_ORDER_CREDIT_RELEASE'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-038' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-038 completed — DECIDE_ORDER_CREDIT_RELEASE' AND body LIKE '%DECIDE_ORDER_CREDIT_RELEASE%'

financebenchmark:erp_qa/Credit Limit (query verbatim; GT recomputed in-world)

Prompt:
**Dana Kim · Credit Manager · Teams 10:02**

Can Sales release the SYNCUS-0001 order within the customer's current credit authority?

Treat this as a live control decision rather than a lookup. Reconcile the relevant systems at their effective dates, call out any unresolved evidence gap, and do not make the numbers agree by changing unrelated records. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

Question: finance case work item

Question: finance case work item

FINCASE-038 completed — DECIDE_ORDER_CREDIT_RELEASE

Question: finance case work item

Resolve immutable work item FINCASE-038 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Resolve exact customer identity, credit limit, hold status, and live exposure before comparing the proposed order.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-038 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-038"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-038 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-038"}) + successful_required_calls + reads_before_write

Check metadata for lgr-038-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-038-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-038-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-038-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-038-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-038-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-038-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-038-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-038 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-038"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-038-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-038-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-038-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-038-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-038-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-038-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-038-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-038-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-038 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-038"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-038-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-038-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-038-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-038-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-038-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-038-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-038-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-038-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Release depends on remaining credit and hold status for the exact account, not the customer name alone.

Reject the unsupported branch: Quote the credit-limit field without considering exposure or holds.

Select `DECIDE_ORDER_CREDIT_RELEASE` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `credit_limit` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `customer_name` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-038 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Quote the credit-limit field without considering exposure or holds.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-039'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-039'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-039' AND decision_code='CERTIFY_CREDIT_DECISION'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-039' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-039 completed — CERTIFY_CREDIT_DECISION' AND body LIKE '%CERTIFY_CREDIT_DECISION%'

escalated variant of erp_qa/credit-limit-adatum via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: financebenchmark:erp_qa/Credit Limit (query verbatim; GT recomputed in-world)

Prompt:
**Dana Kim · Credit Manager · Teams 10:02**

Can the Adatum order decision survive the controls review?

The earlier working paper is not a conclusion. Please determine what the current records actually support, including the viable option and any hold, then leave enough provenance for an independent reviewer to reproduce it. Update only the scoped finance case, verify what persisted, and close the loop with Controls.

Question: finance case work item

Question: finance case work item

FINCASE-039 completed — CERTIFY_CREDIT_DECISION

Question: finance case work item

Resolve immutable work item FINCASE-039 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Apply the effective credit policy to exact-account limit, exposure, holds, and any approved exception.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-039 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-039"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-039 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-039"}) + successful_required_calls + reads_before_write

Check metadata for lgr-039-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-039-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-039-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-039-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-039-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-039-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-039-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-039-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-039 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-039"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-039-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-039-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-039-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-039-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-039-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-039-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-039-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-039-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-039 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-039"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-039-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-039-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-039-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-039-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-039-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-039-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-039-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-039-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The decision is certifiable only if the operative rule and current account state support it.

Reject the unsupported branch: Use the superseded policy or a similarly named account.

Select `CERTIFY_CREDIT_DECISION` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `credit_limit` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `customer_name` conclusion in the discovered reporting schema using its declared type and scale.

deterministic answer check: contains_all

Use the Dynamics generic action surface to move only FINCASE-039 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use the superseded policy or a similarly named account.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-040'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-040'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-040' AND decision_code='BUILD_NEXT_WEEK_CALL_LIST'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-040' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-040 completed — BUILD_NEXT_WEEK_CALL_LIST' AND body LIKE '%BUILD_NEXT_WEEK_CALL_LIST%'

financebenchmark pattern: deliberately-empty ground truths (hallucination traps)

Prompt:
**Casey Morgan · AR & Collections · Teams 09:30**

Which Adventure Works Cycles receivables belong on next week's call list?

I need the answer and the operational consequence, not a list of screens visited. Resolve conflicting versions and identities, use the effective rule, and make the smallest supported change without disturbing neighboring work. Carry the decision through the governed case record and leave Controls a reproducible completion message.

SELECT COUNT(*) FROM erp_cust_trans WHERE account='SYNCUS-0002' AND txn_type='Invoice' AND closed=0 AND due_date>'2026-03-02' AND due_date<='2026-03-09'

Question: finance case work item

Question: finance case work item

FINCASE-040 completed — BUILD_NEXT_WEEK_CALL_LIST

Question: finance case work item

Resolve immutable work item FINCASE-040 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Resolve the exact account, live open remainder, and due dates within the seven-day business window.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-040 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-040"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-040 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-040"}) + successful_required_calls + reads_before_write

Check metadata for lgr-040-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-040-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-040-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-040-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-040-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-040-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-040-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-040-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-040 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-040"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-040-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-040-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-040-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-040-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-040-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-040-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-040-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-040-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-040 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-040"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-040-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-040-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-040-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-040-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-040-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-040-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-040-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-040-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Only open customer invoices falling inside the stated window belong on the call list.

Reject the unsupported branch: Include all open invoices or calculate from the report date rather than the world date.

Select `BUILD_NEXT_WEEK_CALL_LIST` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `invoice_count` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `invoice_numbers` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-040 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-041'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-041'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-041' AND decision_code='CERTIFY_CALL_LIST'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-041' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-041 completed — CERTIFY_CALL_LIST' AND body LIKE '%CERTIFY_CALL_LIST%'

escalated variant of erp_qa/due-next-week-adventure via sim/grow_tasks.py (buried_docs: governing policy hidden in the adjacent-policy library; quiet_prompt: explicit policy pointers removed from the ask); ground truth unchanged. Base: financebenchmark pattern: deliberately-empty ground truths (hallucination traps)

Prompt:
**Casey Morgan · AR & Collections · Teams 09:30**

Is the Adventure Works call list ready to publish after control review?

I need a decision the team can use today, with the amounts, dates, and immutable record identifiers that support it. Some surrounding records came from an older review, so establish what is current before relying on them. Record the supported disposition on the open finance case and send Controls a concise completion note.

Question: finance case work item

Question: finance case work item

FINCASE-041 completed — CERTIFY_CALL_LIST

Question: finance case work item

Resolve immutable work item FINCASE-041 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Rebuild the date window under the effective collections calendar and verify each invoice remains open for the exact account.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-041 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-041"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-041 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-041"}) + successful_required_calls + reads_before_write

Check metadata for lgr-041-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-041-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-041-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-041-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-041-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-041-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-041-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-041-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-041 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-041"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-041-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-041-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-041-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-041-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-041-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-041-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-041-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-041-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-041 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-041"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-041-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-041-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-041-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-041-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-041-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-041-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-041-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-041-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

Publication excludes settled items and dates outside the governed window even if they appeared on the old list.

Reject the unsupported branch: Carry forward the preparer's list without rechecking settlement and calendar rules.

Select `CERTIFY_CALL_LIST` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `invoice_count` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `invoice_numbers` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-041 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use only when the required evidence intersection is incomplete or conflicting.


SELECT status FROM erp_finance_cases WHERE case_id='FINCASE-042'

SELECT decision_code FROM erp_finance_cases WHERE case_id='FINCASE-042'

SELECT evidence_refs FROM erp_finance_cases WHERE case_id='FINCASE-042' AND decision_code='REPORT_PORTFOLIO_AGING'

SELECT COUNT(*) FROM erp_audit_trail WHERE entity_type='FinanceCase' AND entity_id='FINCASE-042' AND action='decide'

SELECT COUNT(*) FROM email_messages WHERE folder='sent' AND subject='FINCASE-042 completed — REPORT_PORTFOLIO_AGING' AND body LIKE '%REPORT_PORTFOLIO_AGING%'

clone of microsoft/FinanceBenchmark erp_qa (AR / Aged Balance); question verbatim, ground truth recomputed in-world (docs/AUDIT.md A3)

Prompt:
**Casey Morgan · AR & Collections · Teams**

Give Collections the USMF aging total by bucket and identify the bucket driving the risk.

This is blocking today's operating review. The obvious screen may be stale and similarly named records exist, so give me the current supported position, the realistic alternatives, and the source identities behind it. Leave the open finance case in the exact supported state and give Controls an audit-ready handoff.

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) <= 0

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 0 AND julianday('2026-03-02') - julianday(due_date) <= 30

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 30 AND julianday('2026-03-02') - julianday(due_date) <= 60

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 60 AND julianday('2026-03-02') - julianday(due_date) <= 90

SELECT ROUND(COALESCE(SUM(amount-settled),0),2) FROM erp_cust_trans WHERE txn_type='Invoice' AND closed=0 AND julianday('2026-03-02') - julianday(due_date) > 90

Question: finance case work item

Question: finance case work item

FINCASE-042 completed — REPORT_PORTFOLIO_AGING

Question: finance case work item

Resolve immutable work item FINCASE-042 and its scoped subject before combining records.

Identify FIN-CONTROL-2026.03 as operative and treat FIN-CONTROL-2025.11 as historical evidence only.

exact policy metadata and full-document reads

Recompute the population from live transactions at the requested date and reconcile it to the batch aging snapshot.

source-system reads before the governed write

Open the independent scope approval; it authorizes the work but does not supply the outcome.

exact Gmail message and attachment reads

Compare the current evidence register with the retained prior tracker instead of trusting either display in isolation.

Discover the ERP entity that owns finance work items before assuming which table or record shape contains the case.

required_calls exact erp.data_find_entity_type({"query": "finance case work item"}) + successful_required_calls + reads_before_write

Inspect the FinanceCases metadata so status, decision, evidence-reference, and ownership fields are interpreted from the live schema.

required_calls exact erp.data_get_entity_metadata({"entity": "FinanceCases"}) + successful_required_calls + reads_before_write

Read the exact immutable case row for FINCASE-042 and use its current subject and status as the scope anchor.

required_calls exact erp.data_find_entities({"entity": "FinanceCases", "filters": {"case_id": "FINCASE-042"}}) + successful_required_calls + reads_before_write

Search governed documents by FINCASE-042 so the decision begins from task-linked controls rather than a familiar policy title.

required_calls exact docs.search_documents({"query": "FINCASE-042"}) + successful_required_calls + reads_before_write

Check metadata for lgr-042-control-current to establish its effective date and FIN-CONTROL-2026.03 revision before applying it.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-042-control-current"}) + successful_required_calls + reads_before_write

Read the full body of lgr-042-control-current and apply its decision rule to this case, not merely its search snippet or title.

required_calls exact docs.get_document({"doc_id": "lgr-042-control-current"}) + successful_required_calls + reads_before_write

Inspect metadata for lgr-042-control-prior and disqualify FIN-CONTROL-2025.11 before comparing operational facts.

required_calls exact docs.get_document_metadata({"doc_id": "lgr-042-control-prior"}) + successful_required_calls + reads_before_write

Use lgr-042-evidence-map to correlate authority, approval, operations, and case identity by immutable reference rather than display name.

required_calls exact docs.get_document({"doc_id": "lgr-042-evidence-map"}) + successful_required_calls + reads_before_write

Search the inbox for FINCASE-042 to identify the contemporaneous approval, operations, challenge, and stale threads.

required_calls exact email.messages_list({"label": "INBOX", "q": "FINCASE-042"}) + successful_required_calls + reads_before_write

Open approval message em-lgr-042-approval and confirm the reviewer, timestamp, and approved scope.

required_calls exact email.messages_get({"id": "em-lgr-042-approval"}) + successful_required_calls + reads_before_write

Read the attachment on em-lgr-042-approval to distinguish authorization to investigate from authorization of a predetermined outcome.

required_calls exact email.attachments_get({"message_id": "em-lgr-042-approval"}) + successful_required_calls + reads_before_write

Open current operations message em-lgr-042-operations and use it to locate the task-native system records needed by the finance analysis.

required_calls exact email.messages_get({"id": "em-lgr-042-operations"}) + successful_required_calls + reads_before_write

Open retained draft em-lgr-042-prior and reject its shortcut because its date and governing revision are stale.

required_calls exact email.messages_get({"id": "em-lgr-042-prior"}) + successful_required_calls + reads_before_write

Search Drive for FINCASE-042 to find both the current evidence register and the retained prior tracker.

required_calls exact sheets.drive_search({"q": "FINCASE-042"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-042-control-pack.xlsx and establish its owner and modification time before trusting its rows.

required_calls exact sheets.get_drive_item({"item": "fincase-042-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F5 from fincase-042-control-pack.xlsx and reconcile the current identity, authority, operations, and approval references.

required_calls exact sheets.workbook_range({"address": "A1:F5", "item": "fincase-042-control-pack.xlsx"}) + successful_required_calls + reads_before_write

Inspect Drive metadata for fincase-042-prior-tracker.xlsx so its former owner and older modification time remain visible in the comparison.

required_calls exact sheets.get_drive_item({"item": "fincase-042-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Read A1:F3 from fincase-042-prior-tracker.xlsx and reject rows tied to FIN-CONTROL-2025.11 instead of silently merging them into the current register.

required_calls exact sheets.workbook_range({"address": "A1:F3", "item": "fincase-042-prior-tracker.xlsx"}) + successful_required_calls + reads_before_write

Use the task-scoped Internal governed policy and SOP library evidence needed for this case.

Use the task-scoped Gmail v1 users.messages, users.threads, labels, attachments, and send resources evidence needed for this case.

Use the task-scoped Microsoft Dynamics 365 Finance MCP generic data, form, and ICustomAPI action tools evidence needed for this case.

Use the task-scoped Microsoft Graph Drive and workbook resources evidence needed for this case.

The reported buckets must cover the whole scoped population without pagination loss or closed items.

Reject the unsupported branch: Use the first page or report only the snapshot grand total.

Select `REPORT_PORTFOLIO_AGING` only after the evidence intersection supports it.

Keep evidence-insufficient or conflicting alternatives visible rather than forcing a clean answer.

File the task-specific `current_not_due` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `days_1_30` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `days_31_60` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `days_61_90` conclusion in the discovered reporting schema using its declared type and scale.

File the task-specific `days_over_90` conclusion in the discovered reporting schema using its declared type and scale.

Use the Dynamics generic action surface to move only FINCASE-042 from open to decided.

Persist the exact four independently sourced immutable references with the case decision.

exact serialized evidence_refs assertion

Produce exactly one Dynamics audit event for the case transition.

Send exactly one scoped Controls handoff naming the case and supported decision.

Complete all required context reads before recording the case decision.

Read the exact FinanceCases record after the decision action.

Reopen the exact completion thread after sending it.

Required evidence calls must succeed; failed lookups do not count as investigation.

Preserve every table outside the source task's authorized mutations, the finance case, its audit row, the completion email, and the reporting row.

Use the first page or report only the snapshot grand total.