# T044 - ASP Purchase-Order Dates vs Later Fiscal Signatures At least two produced purchase orders carry handwritten purchasing-officer dates later than their printed order and delivery dates. The documents do not define whether the handwriting records original approval, later certification, correction, scanning, payment review, or another fiscal step, so the signature dates cannot safely be used as procurement-effective dates. ## Statement A - PO `4502204877` is printed `"Date 03/06/2024"`, `"Delivery Date: 04/30/2024"`, and states that it is subject to cancellation if not delivered and invoiced by June 14, 2024 (`raw/arkansas-state-police/2026-07-31-motorola-watchguard-fiscal/4502204877.pdf`, p. 1). - PO `4502304706` is printed `"Date 10/08/2025"` and `"Delivery Date: 10/31/2025"` (`raw/arkansas-state-police/2026-07-31-motorola-watchguard-fiscal/4502304706.pdf`, p. 1). ## Statement B - The purchasing-officer line on `4502204877.pdf` is handwritten `3/24/25` (p. 1). - The purchasing-officer line on `4502304706.pdf` is handwritten `12/4/25` (p. 1). Both handwritten dates postdate the corresponding printed delivery date; the first also postdates the stated fiscal-year cancellation deadline. ## Why it matters The lifecycle synthesis depends on the printed PO dates to sequence the 4RE baseline and cloud-replacement orders. Without the fiscal workflow or acceptance records, the later handwritten dates cannot establish when the state became bound, when the goods were received, when services began, or whether an order was retroactively certified. ## Resolution status **Bracketed.** The on-face chronology is clear, but its meaning is not. Resolution requires AASIS workflow history, approval/certification records, delivery and acceptance records, invoices, or an ASP Fiscal explanation of the signature field. ## Discovery The March 2024 / March 2025 sequence was identified during visual review on 2026-08-01. Review of the cloud-subscription order then identified the second printed-delivery/handwritten-signature sequence. ## Notes This page does not allege backdating or invalidity. It preserves the record's dates and the missing explanation.