BotCurrent↗
← Back to examples

User report · Research across apps

Draft invoices from completed work for manual sending

Source-backed example. Practical decision guidance is proposed and untested; this is not a full implementation guide.

The problem

Completed work is spread across task and time records, leaving billing staff to reconstruct what belongs on each client invoice.

Agent job

Review ClickUp and Harvest status, history and completed work, then prepare invoice drafts and a client work summary.

Expected output

Invoice drafts and client work summaries for human review and manual sending.

Where this framing comes from
  • Core problem: Editorial purpose framing
  • Agent job: Editorial purpose framing
  • Expected output: Editorial purpose framing
  • Relevant job roles: Editorial purpose framing
  • Benefit type: Editorial purpose framing
Editorial framing and outcome limits

Describes the task’s purpose and intended output; measured benefit, safe unsupervised operation and successful delivery are not established by this framing.

Editorial synthesis based on the linked source. This framing does not add evidence of successful delivery or results.

Case-specific decision guidance · untested

Case-specific decision guidance and first checks are original proposals. The linked source supports the attributed task; this added guidance has not been executed.

Read the attributed source evidence and original caveats below ↓

Why use this

  1. Billing preparation becomes difficult when completion status, time entries and task descriptions live in different systems. A task marked done may already have been billed, while a recorded hour may belong to a fixed-fee milestone or a different client.

  2. This job could assemble a traceable billing draft and plain-language work summary from the same evidence. Reviewing both together helps the billing owner notice charges that lack support and summaries that disclose more internal detail than the client needs.

Why an agent / simpler alternative

Useful judgment

Reconcile inconsistent task descriptions and translate completed work into reviewable invoice lines.

Simpler alternative

Use native invoicing rules when time records already map cleanly to billing codes.

Unsuitable when

Billing terms or approved rates are missing, disputed or require contractual interpretation.

Proposed inputs

  1. Name

    Completion and time exports

    Owner

    Delivery manager

    Minimum scope

    Selected client, billing period, task IDs and time-entry IDs

    Quality check

    Exclude drafts, nonbillable work and entries outside the period.

  2. Name

    Billing rules and prior invoices

    Owner

    Billing owner

    Minimum scope

    Approved rates, fixed-fee terms, taxes and previously billed references

    Quality check

    Confirm currency and identify duplicate billing risks.

Access and setup — proposed or unknown

Proposed minimum
  1. Read scoped exports and produce local drafts; preserve the source’s human review and manual-send boundary.

Compatibility unknowns
  1. Unknown: current ClickUp/Harvest access, invoice formats and rate-field availability.

External actions requiring approval
  1. Creating records in billing systems, altering time entries or sending invoices.

Expected deliverable and review checks

Proposed artifact

Invoice draft and client summary with line-level links to supporting work and explicit unresolved charges.

Critical checks
  1. Quantities, rates, currency and totals reconcile.

  2. Previously invoiced work is excluded and internal comments are not copied into client prose.

Missing output evidence

This overlay adds no new output inspection or execution validation. Preserve the canonical implementation evidence and its outcome limits.

Failure signals and proposed responses

  1. Signal

    A task appears in both a milestone fee and hourly entries.

    Why it matters

    The same work may be billed twice.

    Proposed response

    Hold the overlapping lines and ask the billing owner which contractual treatment applies.

  2. Signal

    A completed task has an unapproved rate.

    Why it matters

    A correct quantity can still produce an incorrect charge.

    Proposed response

    Leave the amount unresolved and request the authorized rate rather than borrowing a similar client’s rate.

Effort and cost — unknown

Setup work
  1. Define client mappings, billing rules and duplicate identifiers.

Ongoing review
  1. Review exceptions and reconcile late time-entry changes.

Unknowns
  1. Unknown: platform fees, export limits and reconciliation effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional client export includes three completed tasks, one previously billed item and one milestone with overlapping time.

Acceptance checks
  1. Only supported nonduplicated lines become billable proposals.

  2. The overlap is held and the work summary excludes internal comments.

Stop conditions
  1. A rate must be invented or an invoice would be sent automatically.

Limits

  1. Drafts depend on approved commercial terms and remain unsent pending owner review.

Tasks: Money & accountingWriting & content

Useful for: Finance professionalService business owner

Editorial relevance from the title and source-supported actions; not evidence of the operator’s occupation.
Hermes AgentIndependent testing: No

Editorial candidate. This is source-backed reporting or a documented workflow. BotCurrent has not independently tested this task. A proposed Canadian adaptation is not evidence of a Canadian deployment or compliance certification.

Original source

https://x.com/corxntyn/status/2082888133105070106 ↗

Attributed to: Corentin (@corxntyn)

User report
Original action type
cross_app_investigation
What the source supports
Hermes reviews task status, history and completed work in ClickUp and Harvest, creates invoice drafts and generates a client work summary.
Source outcome limits
Actions and outcomes are attributed user reports, not an independent reproduction or an execution guarantee.
Evidence attribution caveat
Actions and outcomes are attributed user reports, not an independent reproduction or an execution guarantee.
Source approval description
Every invoice is reviewed by a human and sent manually; agent never sends invoices itself.
Named tools
Hermes, Harvest, ClickUp
Model or version
Unknown
Publication date
2026-07-30
Source last checked
2026-10-14
Demonstrated in Canada
Unknown
Canadian availability
Unknown
Proposed Canadian adaptation
Proposed only: configure CAD, correct tax treatment and authorized client records with accountant review.
Recommended approval boundaries
Review rates, billable scope, taxes and recipient before manual sending.

More examples of this task

Source-backed approaches using this or another agent. Not independently tested.

dots

Recover a missed invoice and prepare approved delivery

An early tester’s dot found uninvoiced work, prepared the invoice and sent it after approval.

Vendor report · Published 2026-09-29 · Independently tested: No

https://openai.com/index/introducing-dots/ ↗

Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.

Source facts, caveats and approval gates
Source attribution
OpenAI
Source publication date
2026-09-29
Source checked
2026-10-14
Model or version
Unknown
Named tools
Dot; invoice; messaging
Source approval description
Sending required the tester’s approval.
Evidence attribution caveat
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Source outcome limits
Actions and outcomes are attributed vendor claims, not an independent reproduction or an execution guarantee.
Recommended approval gates
Approve amount, tax treatment, recipient and send.
Canadian availability
Canada fits published regional eligibility; plan, age and gradual rollout restrictions apply.
Demonstrated in Canada
Unknown
Proposed Canadian adaptation
Check Canadian invoice details, CAD amounts and applicable tax treatment with the owner.