We need answer JSON only. Need process payroll. Need parse rules.

We have record gross 3357.30, payroll_month 2026-01, allowed_deduction 393.61. Source contract gross same 3357.30, so no conflict. Authoritative case reference schedule overrides defaults for case. Need select first-half for 2026-01. Values: rate 0.08, cap 4500.00, deduction cap 400.00, tax-free 1200.00, upper begins 3300.00, middle 0.14, upper 0.24.

Need calculate:
gross_pay = 3357.30
employee_contribution = rate * min(gross, cap) = 0.08 * 3357.30 = 268.584. Round half-up two decimals = 268.58? Let's compute: 3357.30*8% = 3357.30*0.08 = 268.584. Third decimal 4, so 268.58. If using round half-up yes 268.58.

allowed_deduction = 393.61. Must not exceed selected deduction cap 400.00 and gross minus rounded employee contribution = 3357.30 - 268.58 = 3088.72. 393.61 <= 400 and <= 3088.72. OK.

taxable_pay = gross - employee_contribution - allowed_deduction = 3357.30 - 268.58 - 393.61 = 2695.11? Compute: 3357.30 - 268.58 = 3088.72; -393.61 = 2695.11. Yes.

Income tax progressive with tax-free amount 1200.00, upper bracket begins 3300.00, middle rate 0.14, upper 0.24. Taxable pay 2695.11. It is above free 1200 but below upper 3300. So middle portion = 2695.11 - 1200 = 1495.11. Tax = 1495.11 * 0.14 = 209.3154. Round half-up to two decimals: 209.32? Let's compute precisely: 1495.11 * 14 = 20931.54 /100 = 209.3154. Third decimal is 5? 209.3154: decimals .3154. Hundredths digit 1? Wait 209.3154: digits after decimal: 3 tenths, 1 hundredths, 5 thousandths, 4 ten-thousandths. To round to two decimals, look at thousandths digit = 5. Round half up, hundredths 1 becomes 2: 209.32. Yes.

Net pay = gross - employee_contribution - allowed_deduction - income_tax = 3357.30 - 268.58 - 393.61 - 209.32. Compute: 3357.30 - 268.58 = 3088.72. -393.61 = 2695.11. -209.32 = 2485.79. Alternatively taxable - tax = 2695.11 - 209.32 = 2485.79.

Need return JSON with decision calculate, currency LCR, fields strings. Clauses supporting calculation. Need cite R1-R6, and R9 only if amendment needed. No amendment needed. Since source contract same gross, no R9 conflict. The authoritative case reference schedule? It's under R1. Clauses maybe ["R1","R2","R3","R4","R5","R6"]. Need exactly required answer fields: calculate uses decision, currency, gross_pay, employee_contribution, allowed_deduction, taxable_pay, income_tax, net_pay, clauses. Explanation optional. We can include no explanation or short? The instructions: Return one JSON object without Markdown. Allowed answer fields. Optional explanation permitted. We can include explanation maybe not necessary. Need only clauses that directly govern answer. Could include R1,R2,R3,R4,R5,R6. Yes.

Need check if any subtle issue: Authoritative case reference schedule: first-half rate 0.08, cap 4500.00, deduction 400.00. It says "schedule must include rate, cap, deduction, free, upper, middle_rate, upper_rate in each row." The keys match. We replace defaults. Good.

Potential issue: allowed_deduction is 393.61, deduction cap 400.00. OK.

Potential issue: "employee contribution is selected contribution rate multiplied by smaller of monthly gross pay and selected wage cap. Round contribution under R2." We did.

Potential issue: "Do not round intermediate bracket products separately before summing income tax." We only one product. Round total.

Potential issue: "When month or applicable row absent, accept structurally valid deductions up to 350.00 for task validation, but do not calculate..." Not applicable.

Potential issue: Source documents include contract with gross_pay "3357.30" same. So no conflict. Good.

Potential issue: Retrieval? No, calculate.

Need ensure money strings with two decimals. All fields:
"gross_pay":"3357.30"
"employee_contribution":"268.58"
"allowed_deduction":"393.61"
"taxable_pay":"2695.11"
"income_tax":"209.32"
"net_pay":"2485.79"
"currency":"LCR"
"decision":"calculate"
"clauses":["R1","R2","R3","R4","R5","R6"]

Should we include R9? No. "Calculated answers cite R1 through R6, and also R9 only when an amendment is needed to resolve a conflict." Not needed. The source contract same, no amendment. Good.

Need final JSON only. Ensure no markdown.

Let's verify arithmetic with high precision:
Gross 3357.30
Contribution = min(3357.30, 4500.00)=3357.30 *0.08=268.584 -> round half up 268.58 (since 268.584, thousandths=4? Wait careful: 268.584. Decimal digits: 268 . 5 8 4. Hundredths digit is 8. Thousandths digit is 4. So round down? Actually 268.584 to two decimals: look at third decimal = 4, so 268.58. Yes. I previously said third decimal 4. Correct. 268.58.

Taxable = 3357.30 -268.58 -393.61 = 2695.11. Compute: 3357.30 - 268.58 = 3088.72. 3088.72 - 393.61 = 2695.11. Yes.

Income tax: 2695.11 - 1200.00 = 1495.11. 1495.11 * 0.14 = 209.3154. Round half up: hundredths: 1? 209.3154: digits 209 . 3 1 5 4. To two decimals, look at third decimal 5 -> round up second decimal from 1 to 2. So 209.32. Yes.

Net = 3357.30 - 268.58 - 393.61 - 209.32 = 
3357.30 - 268.58 = 3088.72
3088.72 - 393.61 = 2695.11
2695.11 - 209.32 = 2485.79. Yes.

Return.

We need answer JSON only. Need process. Need be careful. We have payroll record gross_pay 3357.30, payroll_month 2026-01, allowed_deduction 393.61. Contract gross_pay 3357.30 matches, no conflict. Authoritative case reference schedule first-half applies. Values replace defaults: rate 0.08, cap 4500.00, deduction cap 400.00, free 1200.00, upper 3300.00, middle 0.14, upper 0.24.

Need calculate.

Check R4 allowed_deduction defaults 0 if omitted. Must not exceed deduction cap or gross_pay minus rounded employee contribution. Gross 3357.30. Contribution rate 0.08 * min(gross, wage cap 4500)=3357.30*0.08=268.584 -> round half-up two decimals = 268.58? 268.584: third decimal 4? Let's see 268.584, hundredths = 8? Actually 268.584: digits after decimal 584. To two decimals: 268.58 because third decimal 4 (<5). Wait 268.584: hundredths digit is 8? 268.58 4. Yes round down to 268.58.

Allowed deduction 393.61. Check <= deduction cap 400.00 yes. Check <= gross - employee contribution = 3357.30 - 268.58 = 3088.72 yes. So allowed deduction 393.61.

Taxable pay = gross - employee contribution - allowed deduction = 3357.30 - 268.58 - 393.61 = ? 3357.30 - 268.58 = 3088.72. -393.61 = 2695.11. Yes.

Income tax progressive:
taxable 2695.11. Tax-free 1200. Upper bracket begins 3300. Since taxable below upper (2695.11 < 3300). Portion above free up to upper = 2695.11 - 1200 = 1495.11. Middle rate 0.14. Tax = 1495.11 * 0.14 = 209.3154. Round half-up to two decimals = 209.32? 209.3154: hundredths 1? Let's calculate: 1495.11*14/100 = 20931.54/100 = 209.3154. To 2 decimals: third decimal 5, but need round half-up. 209.3154 -> 209.32 because 0.0054 above .315. Yes 209.32. Upper tax 0. Total 209.32.

Net pay = gross - contribution - allowed deduction - income tax = 3357.30 - 268.58 - 393.61 - 209.32. First 3357.30 -268.58 = 3088.72. -393.61 = 2695.11. -209.32 = 2485.79. Or taxable - tax = 2695.11 - 209.32 = 2485.79.

Need return decision calculate, currency LCR, fields strings two decimals, clauses. Need citation requirements. Calculated answers cite R1 through R6, and R9 only when amendment needed. No amendment needed because contract matches gross. But there is contract source? It says source documents include contract gross_pay equal to payroll. R9 matching contract values require no amendment. So cite R1-R6 maybe. Need clauses array? Allowed answer fields include clauses. Use exactly required fields. For calculate uses decision, currency, gross_pay, employee_contribution, allowed_deduction, taxable_pay, income_tax, net_pay, clauses. Optional explanation permitted but not necessary. Need maybe clause references supporting calculation. We should include ["R1","R2","R3","R4","R5","R6"]? The instruction: "Calculated answers cite R1 through R6, and also R9 only when an amendment is needed to resolve a conflict." So yes R1-R6. But maybe R4 allowed deduction? Yes.

Need ensure no input-only fields like payroll_month. So JSON with decision, currency etc.

Double-check contribution rounding: 3357.30 * 0.08 = 268.584. Round half-up to 2 decimals: 268.58? Wait 268.584: to two decimal places, 268.58 if the third decimal is 4. Let's explicitly: 268.584, decimals: 5 tenths, 8 hundredths, 4 thousandths. Yes 268.58. But if amount string exactly 3357.30 * 0.08 could be 268.5840. Third decimal 4. So 268.58. Good.

Tax: 1495.11 * 0.14. Let's recalc decimal: 1495.11 * 14 = 20931.54, /100 = 209.3154. Round half-up: hundredths 1, thousandths 5, ten-thousandths 4. If exactly 209.315, round half-up to 209.32. Here 209.3154, yes 209.32. Wait hundredths digit of 209.3154: 209.31, next digit 5, so round up to 209.32. Correct.

Net: 3357.30 - 268.58 = 3088.72. -393.61 = 2695.11. -209.32 = 2485.79.

Need maybe check R4: allowed deduction must not exceed gross pay minus rounded employee contribution. 3357.30 - 268.58 = 3088.72. 393.61 OK. Also deduction cap 400. OK.

Need final JSON only, no markdown. Ensure money strings with two decimals. For fields: gross_pay "3357.30", employee_contribution "268.58", allowed_deduction "393.61", taxable_pay "2695.11", income_tax "209.32", net_pay "2485.79". Clauses array.

Need include currency "LCR". decision "calculate".

Let's produce.

We need answer JSON only. Need compute. Need parse. We have payroll record gross_pay 3357.30, payroll_month 2026-01, allowed_deduction 393.61. Contract gross_pay 3357.30 same as gross, no conflict. Authoritative schedule first-half applies for 2026-01. Values replace defaults: rate 0.08, cap 4500.00, deduction cap 400.00, free 1200.00, upper 3300.00, middle_rate 0.14, upper_rate 0.24.

Need check allowed_deduction valid? R4: must not exceed selected deduction cap or gross pay minus rounded employee contribution. Deduction cap 400.00. Allowed 393.61 <=400. Also available pay check: gross - employee contribution. Compute employee contribution = rate * min(gross, wage cap) = 0.08 * min(3357.30, 4500.00)=0.08*3357.30 = 268.584. Round half-up to two decimals = 268.58? Let's calculate: 3357.30*8/100 = 268.584. Decimal third digit 4? 268.584: hundredths = 8? Actually 268.584: digits 268 . 5 8 4. thousandth digit 4 <5, so round down 268.58. Yes.

Available gross - contribution = 3357.30 - 268.58 = 3088.72. Allowed 393.61 <= 3088.72. OK.

Taxable pay = gross - employee contribution - allowed_deduction = 3357.30 - 268.58 - 393.61 = 2695.11? Let's compute: 3357.30 - 268.58 = 3088.72. -393.61 = 2695.11. Yes.

Income tax progressive with free 1200.00, upper begins 3300.00, middle rate .14, upper .24. Taxable pay 2695.11. Since above free but below upper. Taxable portion above free = 2695.11 - 1200.00 = 1495.11. Middle rate 0.14 = 209.3154? Compute 1495.11*0.14 = 209.3154. Round half-up to 209.32 (since 209.3154 -> hundredths: 209.31? Wait 209.3154: hundredths digit 1, thousandths digit 5, so round up to 209.32. Yes). No upper portion. Income tax = 209.32.

Net pay = gross - employee_contribution - allowed_deduction - income_tax = 3357.30 - 268.58 - 393.61 - 209.32 = 2485.79? Let's compute: 3357.30 - 268.58 = 3088.72; -393.61 = 2695.11; -209.32 = 2485.79. Yes.

Need return JSON with decision calculate, currency LCR, fields strings two decimals, clauses. Need cite R1 through R6, no R9 because amendment not needed. Clauses maybe ["R1","R2","R3","R4","R5","R6"]. Need exactly required answer fields and only clauses that directly govern. The instruction: "Use exactly the required answer fields and only the clauses that directly govern the answer." For calculate required: decision, currency, gross_pay, employee_contribution, allowed_deduction, taxable_pay, income_tax, net_pay, clauses. Optional explanation permitted but likely not needed. Need no markdown fences. Money strings two decimal places. Ensure allowed_deduction string "393.61". gross_pay "3357.30". employee_contribution "268.58". taxable_pay "2695.11". income_tax "209.32". net_pay "2485.79".

Need verify if authoritative schedule replaces defaults. Yes.

Potential issue: deduction cap in schedule is "deduction": "400.00". Allowed deduction 393.61 <=400. OK.

Potential issue: R4 says allowed deduction must not exceed selected deduction cap or gross pay minus rounded employee contribution. OK.

Potential issue: contract gross same, no conflict. No amendment needed.

Potential issue: retrieval? No.

Need output exactly JSON object. Include clauses as array of strings. Maybe clause references supporting calculation: R1 selects row, R2 rounding, R3 contribution, R4 deduction/taxable, R5 tax, R6 net/calculation. That seems right.

Need maybe cite R1 through R6 only. "Calculated answers cite R1 through R6" exactly. So clauses ["R1","R2","R3","R4","R5","R6"]. Good.

Let's ensure no extra explanation. Final only JSON.