Skip to content
Skip to content
Build n Bloom
← All workflow paths

C3 · DEL.6 → FIN.2 · Example design

See why accepted work is still unpaid

Delivery acceptance, an invoice and a payment answer different questions. Match all three in a fictional engagement to expose an unsupported charge and show exactly what remains outstanding.

01 / HANDOFF DESIGN

What goes in. What comes out. Who decides.

Select a stage to inspect the records it needs, the work it prepares and the person who accepts or returns it. Follow a role link to try its own fictional example.

C3 · DEL.6 → FIN.2EXAMPLE DESIGN · HUMAN REVIEW AT EACH STEP

Choose a step to see the input, prepared output and person who decides. The complete sequence remains available below.

Accepted milestone → collected cashFive steps show what moves to the next owner. A returned decision goes from step 3 to step 2. Inputs, outputs and reviewers are written below.Acceptance receiptMatched invoice packetInvoice ID and receivableCollection or dispute receiptAmount mismatch / invoice hold01 · DEL.6Accepted workEngagement lead02 · FIN.2Invoice basisFinance owner03 · FIN.2Invoice decisionFinance owner04 · FIN.2 / REL.2Collect / resolveFinance + account par…05 · FIN.2Cash recordFinance owner
Selected handoff / 01

Accepted work

Engagement lead owns this step.

What goes in
Issued deliverable and contract condition
What comes out
Acceptance or exception record
Try a supporting role
Case coordinator
Allowed sources and actions
Current signed milestone boundary
Who decides
Client / lead confirms acceptance
Other stop and return routes
  • A client dispute at collection returns to the account partner (REL.2), engagement lead (DEL.6) and finance owner to reconcile acceptance, scope and signed payment terms before any action.
  • A partial payment remains an open receivable until finance records the remaining balance or an authorised resolution; invoice issue alone is not cash.
Read the full handoff and exception sequence
  1. Accepted work (DEL.6) — Engagement lead receives issued deliverable and contract condition and produces acceptance or exception record. The handoff is acceptance receipt. Client / lead confirms acceptance.
  2. Invoice basis (FIN.2) — Finance owner receives acceptance, terms and time/fee and produces reconciled invoice evidence. The handoff is matched invoice packet. Finance resolves mismatch.
  3. Invoice decision (FIN.2) — Finance owner receives matched packet and produces approved invoice or hold. The handoff is invoice id and receivable. Finance approves issue.
  4. Collect / resolve (FIN.2 / REL.2) — Finance + account partner receives receivable and client response and produces cash, dispute or write-off route. The handoff is collection or dispute receipt. Finance approves collection action.
  5. Cash record (FIN.2) — Finance owner receives bank/ledger event or approved resolution and produces collected contribution or explicit open balance. This is the recorded outcome. Finance signs reconciliation.

Return path: Amount mismatch / invoice hold sends work from Invoice decision to Invoice basis.

A client dispute at collection returns to the account partner (REL.2), engagement lead (DEL.6) and finance owner to reconcile acceptance, scope and signed payment terms before any action.

A partial payment remains an open receivable until finance records the remaining balance or an authorised resolution; invoice issue alone is not cash.

02 / WHY ASSESS IT

What would make this worth changing?

Fewer missing invoice prerequisites and avoidable delays may improve collected contribution; an invoice is not cash.

MEASUREMENT BASIS

Records to inspect

Signed payment term, authorised milestone, acceptance evidence, invoice and bank/ledger receipt.

STOP / RETURN

Where it can fail

Missing acceptance, amount mismatch, duplicate attempt or dispute blocks issue and returns to delivery, relationship or finance.

DESIGN ACCEPTANCE

Cases to test

Test accepted/unaccepted milestones, changed terms, duplicate retry, dispute and partial payment; reconcile IDs and cash.

03 / SPECIALIST ROLES

Give each supporting role a clear job.

These candidate roles prepare specific parts of the work. Inspect the output and the reviewer before deciding whether a person, existing software, a rule or AI role is appropriate.

COORD

Case coordinator

Show who needs to act, what is overdue and which earlier decision is holding up the case.

Human review: The operations or account owner approves commitments and resolves missing cover. This example sends no reminders or reassignments.

Try this role’s example ↗
COMMERCIAL

Commercial analyst

Check scope and cost for sales, or reconcile milestone, invoice and payment for finance.

Human review: The partner and finance owner approve fees, terms, invoices and collection decisions. Sales and finance keep separate source access.

Try this role’s example ↗
CHECK

Quality checker

Compare the proposed output with the original evidence and explain each discrepancy.

Human review: The named reviewer decides whether to correct or issue the work. A clean check is not professional sign-off.

Try this role’s example ↗

Find out whether this could improve your firm’s capacity

Start with a no-fee Firm Capacity Fit Call about a constraint on client work. If the paid Blueprint is the right next step, it measures one important revenue path, fully designs three connected improvements and ranks the first installation. A simpler process or no installation may be the right answer. Installation is separately scoped; pricing is quote-specific.

Book a free Fit Call ↗

How a Blueprint is scoped →