Find work waiting to become an invoice.
The project is complete, but Finance still cannot invoice. Someone has to find the acceptance record, check the purchase-order reference and keep asking until the gap is resolved.
Discuss this workflowKeep completed work moving toward finance review.
Harmony is a private AI operating model. Assign this work with approved context and authority, and an agent can pursue the next useful step between conversations.
Work completed.
Acceptance record missing.
Authority in this example: request the record internally, send one reminder, then escalate once. Checkpoint timing is set by the team.
An unanswered request stays owned.
- 01Internal request sent
The agent sends request REQ-042 to Alex Kim for the missing acceptance record and attaches it to BIL-042. This action is delegated in the example.
- 02Checkpoint 1 · No reply
Check the sources again and send the one reminder allowed by the assignment.
- 03Checkpoint 2 · Still unresolved
Escalate the missing record and request history to Taylor Morgan, the finance owner.
- 04Escalation unanswered
Pause further requests. Keep the case unresolved and assigned to Taylor; do not mark it ready or keep messaging indefinitely.
Not complete. The missing acceptance evidence is still a blocker.
A matching record or an authorized owner instruction resumes this same case. A revised follow-up limit needs the owner’s decision.
A reply changes the next step—not the standard of evidence.
- 01A response arrives
Alex supplies acceptance record AC-041. The agent reopens billing case BIL-042.
- 02Check the record
AC-041 refers to PROJECT-041. This case concerns PROJECT-042. The prerequisite is still missing.
- 03Revise the question
Attach the mismatch and request the record for PROJECT-042 within the existing internal-request authority.
- 04Retain the checkpoint
Wait for the corrected evidence. The request history and the owner stay attached to BIL-042.
Not complete. Receiving a document is not the same as receiving the right evidence.
Recheck the project reference when a corrected record arrives. If the next checkpoint passes, use the assignment’s escalation limit.
Close the gap with a record Finance can inspect.
- 01The missing evidence arrives
Acceptance record AC-042 identifies PROJECT-042 and its approved completion record.
- 02Check the prerequisites
Match completion CMP-042, purchase-order reference PO-772 and acceptance AC-042 against the example billing requirements.
- 03Prepare the finance handoff
Attach the source references, what was checked and the resolved exception for Taylor Morgan.
- Close this readiness case
The evidence gap is resolved. Finance still decides whether to issue an invoice; the standing responsibility remains assigned.
The readiness task is complete. No invoice has been posted and no payment is assumed.
The ongoing responsibility can pick up the next completed project. Reopen this case if its supporting evidence changes.
Read the assignment and its decision boundary
Keep completed work moving toward finance review.
A project is marked complete, but the acceptance evidence required for billing is missing.
- 01
Compare the completed work with the contract’s billing prerequisites.
- 02
Identify the missing acceptance record and the internal person responsible for supplying it.
- 03
Prepare the request and supporting finance handoff; send an internal request only where that action has been delegated.
Recheck when the acceptance record arrives or the agreed checkpoint is reached. If the missing item is still unresolved, bring its owner a focused escalation with the history attached.
Finance decides whether the item is ready to invoice. Posting an invoice, writing off a balance or changing terms remains outside this assignment.
Finance gets a review-ready handoff with the missing prerequisites pursued, rather than another report listing what is missing.
How you know the job is done
The required evidence is complete and Finance has a reviewable record. Invoice issuance and payment are separate states.
Discuss this workflowThe same signal can mean
something different in your business.
Your priorities, contract terms, customer preferences and available capacity shape the right response. Start with representative examples, including the exceptions your team encounters.
Source access, action authority and model-processing permissions are configured separately. Financial or restricted context can narrow where a task is allowed to run.
What would you
stop chasing?
Bring one recurring process. We’ll map what an agent can carry forward,
the decisions your team keeps and how to evaluate the result.