Codex repeats photography invoices from client rules

Photographer Yoshi Okada describes moving from an initial Codex experiment to repeated invoice preparation. Much of the job follows client-specific conditions: the project fee, transport and parking expenses, and, where agreed, a distance-based charge for vehicle travel.

Okada has those conditions written down as reusable rules instead of relying on a request to remember them. With the current job details and expenses available, Codex can revisit the rules and prepare an invoice. The author reports that automatic or partly automatic creation has worked in repeated operations and reduced repeated transcription and calculation.

Exceptions still need attention. Extra shooting, a changed fee or a job whose price now includes travel cannot simply inherit the previous terms. Preparation and delivery are separate: Okada checks the invoice contents, recipient and attachment before sending.

The same article discusses receipt collection, but automatic monthly collection schedules and fully unattended login are ambitions still being refined. They are not counted as completed invoice outcomes here. Additional authentication may require the owner, and regular execution depends on the computer being running and connected.

The reusable detail is a stored client contract rule set plus current-job inputs and an exception checkpoint. No invoice amount, client identity, exact accounting application, independent error rate or time study is provided. The demonstrated result is repeated invoice preparation in the photographer’s own operation, with human review retained at delivery.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Blog · Yoshi Okada (yoshi okada｜フォトグラファー×Codex)