TimeModified is local wall-clock time with the standard-time offset all year (-08:00 in Pacific daylight time), and a modified-date filter reads an offset the same way, so a TimeModified sent back as FromModifiedDate finds its own record

Observed 2026-10-11 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.

QuickBooks writes TimeModified as the local wall-clock time with the standard-time offset all year. On a machine in Pacific time, during daylight time, it labels the local time -08:00 instead of -07:00, which puts the stamp an hour after the real moment. A FromModifiedDate filter reads its offset with the same fixed -08:00, so a TimeModified sent back exactly as written finds its own record.

A customer updated at 05:12:45 UTC came back with:

qbXML
<TimeModified>2026-10-09T22:12:46-08:00</TimeModified>

Every one of the file's 33 customer stamps carried -08:00, summer dates included. Four CustomerQueryRqs with ActiveStatus All then filtered on that customer's time:

qbXML
<CustomerQueryRq>
  <ActiveStatus>All</ActiveStatus>
  <FromModifiedDate>2026-10-09T22:12:46-08:00</FromModifiedDate>
</CustomerQueryRq>

The time as written found the customer (status 0). One second later, 2026-10-09T22:12:47-08:00, answered status 1, "A query request did not find a matching object in QuickBooks". The time without an offset, 2026-10-09T22:12:46, found it. So did 2026-10-10T06:12:46+00:00, an hour after the update really happened: QuickBooks converted it with its own -08:00 to 22:12:46 local.

So the bound is inclusive, and a time without an offset is the file's local time. A true UTC time sent during daylight time is read an hour early.

What to do

Keep TimeModified exactly as QuickBooks wrote it and send it back unchanged as FromModifiedDate, expecting the record itself again because the bound is inclusive. Do not convert QuickBooks' stamps to UTC and compare them with your own clock as instants. If you send a true UTC time as FromModifiedDate during daylight time, expect up to an hour of records to repeat; none are missed.

Not observed

  • Stamps written in winter, when -08:00 would be correct.
  • Other time zones, and where QuickBooks takes the offset from.
  • ToModifiedDate, a date alone, and ModifiedDateRangeFilter on transactions.
  • Edits in the hour that repeats when the clocks go back.

QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.