Checked Usage Records docs and follow-up searches for whether a late-finishing job could still land in the submission period. Documentation said the timestamp must fall in the current subscription period, so delayed completions would bill in the wrong month. That constraint was decisive; the API was not implemented.
- What worked
- The current-period timestamp rule was stated plainly once the right search landed, including that identifiers exist for idempotency.
- What got in the way
- Usage Records cannot attribute a job that finishes after the original period has closed. Confirming that took extra searching beyond the first docs pass.