City Misses Deadline on 3PI General-Ledger Records Request

The City of Phoenix did not produce 3PI general-ledger data in native, structured format by the deadline GOOD|GOAT set in its April 30, 2026 Notice of Intent to Treat as Denial. As of May 2, 2026, Public Records Request R031544-021226 stands as constructively denied.

The request, submitted February 12, 2026, sought line-item detail for Funds 1022 and 1437 (FY 2025 and January 2026) — the General Ledger and Funds Management data that lives in the City’s SAP environment. The City responded with four PDF reports. Arizona’s Public Records Law requires production in the format records are maintained in. SAP data is maintained in structured tables that export natively to Excel and CSV. PDF reports strip the underlying technical metadata — user name, entry date, document header text, offsetting account — that makes a ledger searchable, joinable, and analyzable.

GOOD|GOAT’s Notice named the exact SAP transaction codes and source tables required to fulfill the request: standard G/L line-item reports (FAGLL03 / FAGLL03H), Funds Management postings (RFFMEP1AX), Budget Control System reports (FMBLL03), and the underlying tables BKPF, BSEG, ACDOCA, FMIFIIT, FMIOI, and FMBDP. Format is not a preference. It is what the statute requires.

This matter is tagged to the broader 3PI Compliance work but is procedurally distinct — a public-records enforcement action under A.R.S. § 39-121 et seq., separate from the substantive 2008-ballot-compliance hold letter served February 10, 2026. Filings, the City’s PDF productions, and the demand letter are linked from the 3PI Compliance case page at /cases/3pi-compliance.