Settled late

Settled after the T+n window (open), ₹84,886.67. Rule stage4.settlement_window; 18 record(s).

₹84,886.67Awaiting settlementopen15 Oct 2026settlement setl_qkwQpGptCQDU81

Explanation

Generated from the read-only evidence below. It never changes a match or a record.

LLM · openai/gpt-oss-120b

The settlement was posted after the allowed T+2 business‑day window for card payments.

Seventeen card payments were due by 2026-10-13 but the settlement batch was recorded on 2026-10-15, which is two business days late. This exceeds the stage4.settlement_window rule that permits a maximum of 2 business days delay. The engine flags this as a TIMING_WINDOW_EXCEEDED exception.

Recommended action

Escalate to the gateway provider to investigate the delay and ensure future settlements meet the T+2 SLA.

No review requiredConfidence 99%· Cites 2 evidence ids, all verified to be in the bundle

Evidence records

Read-only source records involved in this exception.

Settlementsetl_qkwQpGptCQDU81

utr: HDFCN26288967029
amount: ₹84,886.67
settled at: 2026-10-15
created at: 2026-10-15T09:00:00+05:30
item count: 17
fee total: ₹1,738.78
gst total: ₹313.00

Paymentpay_XQIqaV0BOCvsNE

order id: order_eNDMZn8hdd2gU5
amount: ₹79.34
method: card
status: captured
captured at: 2026-10-09T07:02:50+05:30

Paymentpay_OZV0QErH1ZnPeq

order id: order_GN3RDrGumRDoEV
amount: ₹199.00
method: card
status: captured
captured at: 2026-10-09T07:06:42+05:30

Paymentpay_U8Pir81Llfc4MQ

order id: order_eFdeoMBe3eDIm0
amount: ₹25,150.00
method: card
status: captured
captured at: 2026-10-09T08:08:29+05:30

Paymentpay_SPpJP3rCTZXsBH

order id: order_9nb3L8QoNnwwpz
amount: ₹576.89
method: card
status: captured
captured at: 2026-10-09T08:56:12+05:30

Paymentpay_X1fJhrLB2y3H3C

order id: order_7SH5NnPjmbPEmD
amount: ₹290.36
method: card
status: captured
captured at: 2026-10-09T08:57:49+05:30

Paymentpay_iIk0VzRCLSK45w

order id: order_Egmvkej8bLoXkO
amount: ₹240.05
method: card
status: captured
captured at: 2026-10-09T09:12:46+05:30

Paymentpay_ejAE1FnTGMmAe4

order id: order_GuTDnUuisDZiAU
amount: ₹199.00
method: card
status: captured
captured at: 2026-10-09T09:35:03+05:30

Paymentpay_BiGd4ffNPZsvww

order id: order_phQsAKa2w9Q4TG
amount: ₹31,595.00
method: card
status: captured
captured at: 2026-10-09T09:48:21+05:30

Paymentpay_PfEf64usQsR5fp

order id: order_kZ7nrhlGNPyU5C
amount: ₹1,499.00
method: card
status: captured
captured at: 2026-10-09T10:17:26+05:30

Paymentpay_cVzj7XSUYGmYcy

order id: order_HCw5ltRenpedk0
amount: ₹90.03
method: card
status: captured
captured at: 2026-10-09T10:28:59+05:30

Paymentpay_YyGRRk5a0hYSKQ

order id: order_AsIy0Klyv3DBWl
amount: ₹11,210.00
method: card
status: captured
captured at: 2026-10-09T10:37:12+05:30

Paymentpay_uSpHvBnSUrt0RB

order id: order_lrnmam49FGHA9v
amount: ₹272.00
method: card
status: captured
captured at: 2026-10-09T11:20:31+05:30

Paymentpay_aP6nbhrxdsSzKq

order id: order_88yyzd0v0X48xU
amount: ₹199.00
method: card
status: captured
captured at: 2026-10-09T11:51:01+05:30

Paymentpay_Mcwf9DLNxOGwLi

order id: order_lvx34vrGhcGjl0
amount: ₹11,945.00
method: card
status: captured
captured at: 2026-10-09T12:03:38+05:30

Paymentpay_cDSM9rrmqycu4H

order id: order_lCO6vU8DpuRB7W
amount: ₹2,688.78
method: card
status: captured
captured at: 2026-10-09T12:45:51+05:30

Paymentpay_WLWQhKWnj162SF

order id: order_4TI5wrPXhBNw2i
amount: ₹652.00
method: card
status: captured
captured at: 2026-10-09T12:56:25+05:30

Paymentpay_QkzDJyUvDrRTDG

order id: order_LzYWgB0DvesoOo
amount: ₹53.00
method: card
status: captured
captured at: 2026-10-09T15:09:47+05:30

Rule trace

The deterministic rule that fired and what it saw.

{
  "rule": "stage4.settlement_window",
  "windows_business_days": {
    "card": 2
  },
  "earliest_due_date": "2026-10-13",
  "settled_at": "2026-10-15",
  "max_business_days_late": 2,
  "late_payments": 17
}

Audit history

Append-only. Actor: system, llm or human.

llminvestigation2026-11-03 10:27:52 UTC
source=llm · model=openai/gpt-oss-120b · review_policy_applied=false
systemjournal draft2026-11-03 10:28:12 UTC
applicable=false · reason=TIMING_WINDOW_EXCEEDED needs a matching decision, not a journal entry