Skip to content
Build n Bloom
Menu
WorkflowsRolesSystem BlueprintResourcesEvidenceExisting-client NDISInstallation
Request a Fit Call
← All workflow paths

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

Make accepted work collectible

Keep accepted work, agreed payment terms, invoice authority and actual collection in one auditable path.

Request a Workflow Fit Call ↗How a Blueprint is scoped
TRIGGER → ACCEPTED OUTPUTAccepted milestone → collected cash

Typical sponsor: Finance owner and managing partner. This is an illustrative route. It is not an installed workflow or a promise that this path is one of your three Blueprint designs.

01 / HANDOFF DESIGN

The object, the owner, the decision.

Select any stage to inspect what it receives and produces, which specialist role might assist, what it may access, and who makes the human decision.

C3 · DEL.6 → FIN.2REFERENCE DESIGN · NOT AN INSTALLED SYSTEM

Scroll the diagram horizontally, or use the stage buttons below.

Accepted milestone → collected cashFive stages linked by named handoff objects. A rejected decision returns from stage 3 to stage 2. The full sequence and ownership 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.

Receives
Issued deliverable and contract condition
Produces
Acceptance or exception record
Possible agent roles
Case coordinator
Permission boundary
Current signed milestone boundary
Human decision
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

Value is a hypothesis until measured.

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

Possible assistance, bounded by authority.

These roles are candidate responsibilities in the reference architecture. They are not prebuilt products or active agents in your systems.

COORD

Case coordinator

Show the next owner, dependency or proposed follow-up.

Boundary: One current case state; routine effects require separate delegation and receipt.

COMMERCIAL

Commercial analyst

Reconcile scope and cost, or signed milestone and invoice evidence.

Boundary: Sales and finance have separate identities, corpora and minimal authorised fields.

CHECK

Quality checker

Compare a draft with the original permitted evidence and exact request.

Boundary: Read-only comparison; a discrepancy report is never professional sign-off.

All ten roles ↗

From reference to a firm-specific decision

A Blueprint starts with a service the firm already sells, examines permitted records and measures the constrained work. It selects three connected boundaries, designs each to the same depth and ranks the first installation. A reference path may change, narrow or be rejected when the evidence is different.

Inspect the System Blueprint ↗