Skip to content
Skip to content
Build n Bloom
Menu
WorkflowsRolesDemosSystem BlueprintResourcesEvidenceExisting-client NDISInstallation
Request a Fit Call
← All working demos

Example design · fictional finance ledger

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.

Interactive browser demonstration · Fictional data · No live AI or client results

Acceptance, ledger and cash receiptAn acceptance receipt supports invoice evidence. Finance matches cash to a bank entry; partial payment stays an open balance. Example design using fictional work records.Accepted milestone → collected cash
WHAT GOES IN

Signed milestone terms, acceptance evidence, an invoice draft and a payment record.

WHAT COMES OUT

A reconciliation showing the supported amount, allocated payment and open balance.

WHO DECIDES

The named reviewer approves, returns or stops each step.

01 / TAKE THE REVIEWER’S SEAT

Change the input.
Check what changes.

Change the payment amount. Follow the remaining balance, compare the draft with the signed terms and see why a mismatch goes back to finance. Choose the situation, set the input and select “Run this case”. You make each fictional review decision; nothing is sent or applied outside the demo.

Choose the situation
4500 USD
012000

Changing the input or situation starts a fresh example.

Accepted milestone → collected cashRevision 1 · Not started
Accepted milestone → collected cash: Ready to runFive handoffs: Accepted work, Invoice basis, Invoice decision, Collect / resolve, Cash record. Blue marks the current step. A person reviews each output before work moves on.01Accepted workEngagement lead02Invoice basisFinance owner03Invoice decisionFinance owner04Collect / resolveFinance + account partner05Cash recordFinance owner
  1. 01
    Accepted workEngagement lead
  2. 02
    Invoice basisFinance owner
  3. 03
    Invoice decisionFinance owner
  4. 04
    Collect / resolveFinance + account partner
  5. 05
    Cash recordFinance owner
Ready to run

Set the situation and input, then select “Run this case” to prepare the first output.

THE BRIEF

A partial payment leaves a real balance in the example

A fictional advisory engagement has a USD 12,000 milestone. Change the payment in its made-up ledger and follow acceptance, invoice evidence, issue review, collection and the remaining balance. The amount is illustrative and is not a Build n Bloom fee.

Acceptance, invoice issue and cash collection are separate records. A partial payment leaves an open receivable; a mismatch returns to finance instead of becoming a larger invoice.

Source excerpts and the complete design remain readable below.

02 / OPEN THE SOURCE PACK

Read the records behind the result.

Use these fictional originals to check the number, period, version and permission behind each output. Missing or conflicting evidence remains visible. These are teaching records, not client results.

CASH-SCOPE1

Fictional milestone and signed terms

Synthetic source. Case F-01 has one milestone M-01 for an invented advisory engagement: a findings report and handover. The signed-term specimen sets USD 12,000, payable after acceptance. There is no tax, fee, credit, interest or write-off in this example. Selected ledger payment P is from USD 0 to USD 12,000, rounded to cents; scenario balance = 12,000 − P. These are not Build n Bloom fees.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-ACCEPTANCE1

Synthetic acceptance specimen

Synthetic source. Specimen SIM-ACCEPT-01 records both report and handover for F-01/M-01 as accepted within the fiction. Both are prerequisites for this milestone. It is made-up evidence for the demonstration, not a client acceptance receipt.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-INVOICE1

Matched invoice specimen

Synthetic source. Specimen SIM-INV-01 references F-01, M-01 and SIM-ACCEPT-01 for USD 12,000. The amount matches the signed terms. Amount variance = draft amount − 12,000 = 0. This record is synthetic; finance still reviews the demo's invoice decision.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-INVOICE-OLD0

Amount-mismatch draft — exception

Synthetic source. The draft for the same F-01/M-01 and specimen SIM-INV-01 says USD 13,200. Signed terms still say USD 12,000. Variance = 13,200 − 12,000 = USD 1,200. There is no signed change, extra milestone or extra tax supporting the difference. Hold the draft.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-INVOICE-REPAIR2

Corrected invoice basis — repair evidence

Synthetic source. Replace the mismatched amount with USD 12,000 for the existing F-01/M-01 and SIM-INV-01. Preserve the same acceptance reference and original draft for comparison. This supplies a corrected draft, not a newly issued invoice, payment, collection authorisation or write-off.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-LEDGER1

Original fictional allocation ledger

Synthetic source. SIM-INV-01 has face value USD 12,000. For the selected P, a made-up allocation SIM-PAY-01 records exactly P against it when P > 0; P = 0 means no payment entry. Collected in this fixture = P. Open balance = 12,000 − P, rounded to cents. For 0 < P < 12,000 it remains partial; only P = 12,000 leaves zero balance. There are no unallocated receipts, refunds or currency changes.

Use boundary: Synthetic finance-scoped ledger; no bank, accounting provider or sales-corpus access.

CASH-COLLECTION1

Collection and reconciliation rule

Synthetic source. An open balance remains visible. Missing acceptance, mismatched amount or dispute returns to finance and the account partner. A reminder is only a proposal; recipient, timing and consent must be checked by the finance owner. Do not infer a write-off, chase, payment instruction or external effect from the calculation.

Use boundary: Synthetic fixture; private review within this fictional case only.

CASH-RECOVERY1

Ledger-read interruption fixture

Synthetic source. At Collect / resolve, the fictional ledger connection times out. Retain the allocation specimen and last known invoice ID. Diagnose whether the same read can be checked again; do not retry invoice issue, collection messages or a payment. Technology and finance/risk owners decide any resumption separately.

Use boundary: Synthetic fixture; private review within this fictional case only.

Read the complete workflow design
  1. Accepted work

    Engagement lead receives issued deliverable and contract condition and prepares acceptance or exception record.

    Decision: Client / lead confirms acceptance. Permission: Current signed milestone boundary.

  2. Invoice basis

    Finance owner receives acceptance, terms and time/fee and prepares reconciled invoice evidence.

    Decision: Finance resolves mismatch. Permission: Finance-scoped ledger and agreement.

  3. Invoice decision

    Finance owner receives matched packet and prepares approved invoice or hold.

    Decision: Finance approves issue. Permission: Invoice issue is human-authorised.

  4. Collect / resolve

    Finance + account partner receives receivable and client response and prepares cash, dispute or write-off route.

    Decision: Finance approves collection action. Permission: Reminders require consent and delegation.

  5. Cash record

    Finance owner receives bank/ledger event or approved resolution and prepares collected contribution or explicit open balance.

    Decision: Finance signs reconciliation. Permission: Actual bank/ledger receipt.

Return route: Amount mismatch / invoice hold. Missing acceptance, amount mismatch, duplicate attempt or dispute blocks issue and returns to delivery, relationship or finance.

See the workflow’s inputs and owners ↗
FROM AN EXAMPLE TO YOUR SERVICE

Does this job slow down your service?

Use the no-fee Workflow Fit Call to discuss where your cases get held up. If there is a fit, a paid System Blueprint measures one service line and fully designs three connected workflows, with a ranked installation roadmap. Installation is separately scoped; pricing is quote-specific.