Skip to content

uid: I-042 title: A receipt dated two years in the future was accepted, and created a 2028 folder in Drive status: open area: receipts created: 2026-09-14 owner: girafeev1 related: T-209, T-207

I-042 β€” A misread receipt date reached the books unchallenged

What happened, plainly

A receipt from benefit for HK$230 was uploaded on 22 July 2026. The AI read its date as 8 July 2028 β€” two years in the future, and almost two years after the upload. Nobody corrected it (the original parse and the stored value are identical, so it was never hand-edited), and it was confirmed into the books carrying that date.

The app then did exactly what it is built to do: expense receipts are filed in Drive under a folder for their year, created on demand, so it created 14. Expenses Records / 2028 / 14a. Expense Receipts to put it in.

So the mysterious 2028 folder the Drive audit flagged was not created by a person. Timestamps confirm it to the second:
Drive folder 2028 created 2026-07-22T06:31:45.586Z
Receipt record written 2026-07-22T06:31:56Z

Receipt id e15365d9-2bd9-401b-9d59-6dad9053faac; Drive folder id 1npLDM_dtLL7HT4kFVYa-HL7HeZNZUbuy.

Why it matters more than one stray folder

The folder is cosmetic. The date is not. A receipt's date decides which accounting period the expense falls into, so a confirmed receipt dated 2028 sits outside every period the company will report on for the next two years. This one is small (HK$230, category "other", never settled, no payment confirmation attached), so the exposure is trivial β€” but nothing stopped it, and nothing would stop a larger one.

There is no sanity check on a parsed receipt date. A date years in the future, or before the company was incorporated (3 September 2024), is accepted silently. The only reason this surfaced at all is that it happened to create a folder someone later noticed in an unrelated audit.

Suggested fix (not built)

  1. Flag a parsed date that is in the future, or earlier than incorporation, at the review step β€” the submitter is looking at the receipt and can fix it in seconds.
  2. Refuse to lazily create an expense-year folder for a year outside a sane window; that folder is the symptom that made this visible, and it should have been the thing that refused.
  3. Decide what to do with this one receipt: correct the date (the Drive file stays in 2028 unless moved) or leave it. Owner's call β€” not actioned.

Found while investigating the Drive audit's "what created the 2028 folder?" question (owner, 2026-09-14). Source: Records (Infrastructure) Β· https://claude.ai/code/session_018RDB37kCqfouHdygVXTAtD