Let me start by listing documents.

Let me read the document.

The payroll month is 2025-11. R1 says only 2026 is covered. Dates outside 2026 require clarification under R7. The month2025-11 is not covered by any reference row. R7 item 3: "A month without a reference row: return decision clarify, reason_code NO_APPLICABLE_REFERENCE, citing R1 and R7. Do not extrapolate an old row."

But also R1 says "Dates outside 2026 require clarification under R7." So it's out of range. Which reason code? The month 2025-11 has no reference row, so NO_APPLICABLE_REFERENCE applies. But R1 says dates outside 2026 require clarification under R7. The ordering in R7: 1. missing gross_pay, 2. missing payroll_month, 3. month without reference row, 4. conflict. Since gross_pay and payroll_month are present, we hit #3: NO_APPLICABLE_REFERENCE, citing R1 and R7.

Should I still check lookup_reference? The task says reference rows available only through lookup_reference. But2025-11 is outside 2026; there's no row for it. I could verify by looking up both references, but it's not strictly necessary. However, to be careful and demonstrate, I could do the lookups. The month2025-11 falls in the "first half" (Jan-Jun) conceptually? Actually first-half/second-half refer to the effective months of reference rows within 2026. 2025-11 is outside 2026 entirely. No row applies.

Also R4: "When the month or applicable row is absent, accept structurally valid deductions up to the largest reference deduction cap for task validation, but do not calculate a payslip." That's for validation of deductions; here we don't calculate anyway.

Answer: clarify, reason_code NO_APPLICABLE_REFERENCE, clauses ["R1", "R7"].

Maybe do lookup to confirm no row applies. Let me just quickly do the lookup for completeness — but "only the clauses that directly govern the answer". The answer is fine without lookup. But being careful: the case might supply a reference_tables schedule where effective months differ. The rules say "A case may include an authoritative reference_tables schedule for first-half and second-half. When supplied, its numeric values replace the defaults." Let me check lookup_reference for both to see the effective months. If the schedule shows effective months within 2026, then 2025-11 has no row.

Let me do both lookups in parallel.

Reference rows cover 2026-01 to 2026-06 and 2026-07 to 2026-12. The payroll month 2025-11 is outside both ranges and outside 2026. So NO_APPLICABLE_REFERENCE under R7 item 3, citing R1 and R7.

Gross pay present (3876.02), payroll month present. So no missing fields. Return clarify with reason NO_APPLICABLE_REFERENCE.

No monetary fields. Explanation: payroll month 2025-11 is not covered by any reference row (only 2026 is covered); request a valid 2026 payroll month.

Let me list documents first.

Read the payroll document.

Payroll month 2025-11 is outside 2026. R1: "Only 2026 is covered. Dates outside 2026 require clarification under R7." R7 order: 1. missing gross_pay - no. 2. missing payroll_month - no. 3. A month without a reference row: NO_APPLICABLE_REFERENCE. 2025-11 has no reference row (only 2026 covered). So clarify with NO_APPLICABLE_REFERENCE, citing R1 and R7.

Hmm, but "Missing or out-of-range dates cite R1 and R7." That fits too. The reason code for out-of-range date... R7 item 3 is "A month without a reference row" → NO_APPLICABLE_REFERENCE. Since 2025-11 has no reference row, that's the code. Cite R1 and R7.

Should I lookup_reference? Not needed - the month is outside 2026 regardless. But to be thorough, maybe check? Not necessary. The answer: clarify.

No monetary fields.

Let me list documents.

Read the document.

Payroll month 2025-11 is outside 2026. R1: only 2026 is covered. Dates outside 2026 require clarification under R7. Reason code: NO_APPLICABLE_REFERENCE (month without a reference row). Cite R1 and R7.

Order of checks: gross_pay present, payroll_month present, then month without reference row → NO_APPLICABLE_REFERENCE.

The payroll month 2025-11 is outside 2026; no reference row covers it. Clarify with NO_APPLICABLE_REFERENCE, citing R1 and R7.