TGH Tech
Case study · Workflow 20 of 20 · Money in and out · Designed

An overdue stage payment needs an owner, a next step and a date. The billing register is live. The follow-up is designed.

Viya Constructions bills homeowners stage by stage, and ProjectSignal already records those stage payments week by week: planned against actual completion, planned against actual collection, and the week's shortfall. What it does not do yet is age an overdue amount, name the person chasing it or record what was done. That layer is designed and not yet built.

Client
Viya Constructions
Department
Accounts, project managers, leadership
Starts from
Invoices, payments and stage dates already in ProjectSignal
Gives you
Every overdue amount by age, with an owner, a next action and a date
Connected to
ProjectSignal. Bleno chat, read-only, in the design
Status
Designed. The billing register is live. Aging, owners and next actions are designed, not built.

[01]What changesViya Constructions

Today the shortfall is a number. The design turns it into names and dates.

The first column is live in ProjectSignal. The second is the written design, not yet built.

Before

A weekly shortfall, reviewed by leadership.

  • Stage payments planned and tracked week by week
  • One headline figure: collection short of plan
  • Overdue amounts raised in the review, then left for the next
  • No record of who is chasing, or what was done
As designed

A list where every overdue rupee has a name.

  • Each unpaid invoice in one of four age bands
  • An owner, a next action and a date on each amount
  • Stages finished but not invoiced, listed on their own
  • A Monday review that opens on actions past their date
  • 7
    statuses a stage payment can hold in the live register
  • 24
    weeks of plan, collection and shortfall in the weekly summary
  • 13
    weeks in the ranking of sites by shortfall and delay
  • 4
    age bands in the design, from 0 to 30 days up to over 90

The first three are live. The fourth is the design. Nothing on this page is a measured result.

A home builder is funded by its customers' stage payments. Working capital, not demand, limits how much it can build, and collections are the cash that pays every contractor and supplier on more than 40 sites. Labor contractors are paid every week, so a stage that is finished and unpaid is work the builder has already funded. When that payment slips two weeks, the builder has lent the customer two weeks of working capital, and nobody decided to.

Of the 131 workflow proposals we scored for Viya in November 2026, this one ranked first: top of the scale for impact, urgency and reach. It answers a requirement Viya wrote into its own plan for the platform. It has no prerequisites: it runs on records Viya already keeps.

[02]Why this is hardViya Constructions

The stage is built. The money has not come in. Four reasons it stays that way.

  1. 01

    A finished stage is money already spent

    Labor contractors are paid every week while a roof slab is built. The customer's stage payment comes after the stage is done. Every day that payment waits, the builder carries the house.

  2. 02

    A total has no owner

    A weekly shortfall says how much is short, not which customer, for how long, or who is calling them. So it is discussed and waits another week.

  3. 03

    The ask comes late, and in passing

    Homeowners are usually asked for a stage payment after the stage is done, often by the project manager in the middle of a site conversation. The money then takes days to arrange.

  4. 04

    A dispute is not a slow payer

    One customer is arranging funds. Another is unhappy with progress and holding payment because of it. Chase both the same way and the second relationship gets worse.

[03]Live todayViya Constructions

The billing register already does the arithmetic. Stage by stage, week by week.

This part is live in ProjectSignal, the platform we rebuilt for Viya. It is the record the design reads.

Each calendar week, leadership plans which stage payments will complete and be billed. The plan can be copied forward from the week before. At the week's end, actual completion dates and cash received are entered against it. From those rows ProjectSignal raises the stage invoice, records payments and issues receipts. Both print in a formal layout with the amount in words, and can be shared with the homeowner on WhatsApp.

Seven statuses. Late and short are worked out, never typed.

Nobody marks a stage payment late or short. ProjectSignal works it out from dates and cash, and the first rule that matches wins.

  • Date is judged before cash: a stage finished late stays delayed, even once paid
  • Complete only when collection reaches the planned invoice amount. Part payment shows as partial, with the amount still short
Milestone collection · this week
Planned invoice total₹58.0 lakh · 10 stage payments, 8 sites
Actual collection₹39.5 lakh · 6 stage payments in full
Shortfall₹18.5 lakh · 4 stage payments shortShort
Paperwork due3 invoices to raise, 2 receipts to issueDue
Site C · Roof slabDone 4 days late, part paidDelayed
Illustrative. Made-up sites and figures, laid out like the live weekly view. One lakh is 100,000 rupees.

No netting.

The week's shortfall is the sum of each stage's own shortfall. Extra collected on one stage never cancels what is short on another. Netting hides the stage that is in trouble.

The register also lists paperwork due: an invoice the moment a milestone carries a planned amount, a receipt once money has landed. A planned amount with no invoice is a demand nobody has made yet.

[04]How it worksViya Constructions

The design reads the register and adds the follow-up. Only one step asks a person to enter anything new.

This is the design, described as it is meant to run. It reads the register above and needs no new data source.

  1. 01Fixed logic

    Work out what is owed

    Every invoice sent or partly collected counts. What is owed is the invoice amount less payments recorded, recalculated daily.

  2. 02Fixed logic

    Age each balance

    From the invoice's due date, each balance falls into one of four bands, per site and per customer. A part-paid invoice ages on what is still owed.

  3. 03Fixed logic

    Name the owner

    The site's project manager by default, or the holder of that customer's relationship. ProjectSignal already keeps one holder per customer: never blank, never two people.

  4. 04The owner records

    Record the next action and its date

    Call, visit, statement sent or dispute, with a date. A customer's promise goes into the commitments register that is already live, so kept and broken promises are counted.

  5. 05Fixed logic

    List what was never billed

    A stage with an actual completion date and no invoice after three working days goes on its own list, with invoices approved but not sent. The three-day threshold is a proposal.

  6. 06Fixed logic

    Show what has gone quiet

    An overdue amount with no future-dated next action shows red, to its owner and in the review.

  7. 07Accounts and directors

    Review on Monday

    Accounts and directors take the list at 10:00 every Monday: actions past their date first, shown by owner, then the largest and oldest amounts.

Collections · Monday review
Site A · Roof slab · 47 days₹4,60,000 · Project manager · Visit was due WednesdayAction late
Site F · Lintel · 64 days₹3,10,000 · Project manager · No next actionNo action
Site K · Plastering · 33 days₹2,25,000 · Relationship holder · Customer promised FridayPromise
Site D · Plinth · 12 days₹1,80,000 · Project manager · Call done, amount disputedDispute
Site M · Brickwork · not invoiced₹2,90,000 · Accounts · Stage completed 6 days agoRaise invoice
Illustrative. Made-up sites, amounts and dates, laid out as the design describes.

[05]Connected to ProjectSignalViya Constructions

This one belongs inside ProjectSignal. The design gives Bleno a read-only window.

Most workflows in this set are Bleno jobs a person starts in chat. This one is a ProjectSignal build, set beside the invoices it describes.

  1. Reads

    From ProjectSignal

    • Invoices, with due date and status
    • Payments against each invoice
    • Billing milestones and completion dates
    • Project manager and relationship holder
  2. Does

    What the design does in between

    • Ages every unpaid balance
    • Assigns the default owner
    • Lists finished stages with no invoice
    • Shows red where no dated action exists
  3. Writes

    To ProjectSignal

    • Next action, date and outcome on each amount
    • Customer promises, into the commitments register
    • A weekly snapshot, so the trend can be read

What it reads exists today. The rest is the design.

Writes follow the rules ProjectSignal already has. The owner records the next action in ProjectSignal itself, not in chat. The list needs no approval. Any change to an invoice still goes through the register's own rules: approval, a version check and a kept snapshot once a payment lands.

Bleno cannot read billing data today. The design adds one read-only tool, so the same list can be asked for in chat. Bleno chat answers as the signed-in person and shows nothing that person could not already see in ProjectSignal.

ProductIts part in collectionsStatus
ProjectSignalHolds stage payments, invoices and receipts. Works out status and shortfall.Live
ProjectSignalAging, owners, next actions, the not-invoiced list, the Monday review.Designed
Bleno workflowIssues a customer receipt from a payment screenshot, after review. The payment is still entered in the register by a person.Live
Bleno chatAnswers what is overdue, read-only, as the signed-in person.Designed
AI colleagueNone in this design. AI colleagues work inside site groups. Asking a customer for money stays with a named person.Not used

Which product does which part.

  1. Milestone readiness
  2. Stage invoice
  3. Payment receipt
  4. Collections follow-up

[06]Who decides whatViya Constructions

Fixed logic ages the invoice. A person makes the call. In this design, no AI asks a customer for money.

StepDone byStatus
Planning the week, entering actuals, approving invoicesLeadership, the customer relations role and financeLive
Stage status, shortfall, invoice stateFixed logic in ProjectSignalLive
Balance owed, days overdue, age bandFixed logicDesigned
Who owns an overdue amountA fixed rule: project manager or relationship holderDesigned
The next action, its date, and whether an amount is disputedThe ownerDesigned
Where the week's attention goesAccounts and directors, on MondayDesigned

Usually the AI reads, fixed logic calculates, a person confirms. Here there is no document to read, so the AI reads nothing.

[07]More detailViya Constructions

The rules it follows

What the register enforces now, and what the design adds.

For the accounts head who asks how a status or an age is decided.

Live: how a stage payment gets its status

StatusWhen it applies
SkippedMarked as not to be considered
PendingPlanned completion date has passed, stage not complete
PlannedNot complete, planned date still ahead
DelayedCompleted later than planned, whatever the cash position
Awaiting cashCompleted on time, nothing collected
CompletedCollection has reached the planned invoice amount. Shown as on time
PartialSome cash in, shown with the amount still short

Checked in this order. The first match wins. The weekly summary counts delayed, partial and awaiting cash together as deviated.

Live: invoices and receipts

RuleWhat it does
Invoice numbersOne invoice per stage payment. A person types a site's first invoice number. Later ones count up from it
Version checkApproving or marking sent fails if the invoice changed since it was opened
Locked on paymentA payment locks the invoice and keeps a snapshot of that version
No deleting paperworkA milestone with an invoice or receipt cannot be removed
Receipt numbersHighest existing number plus one, never a count of rows
Sending is a choiceGenerating the invoice when a stage completes is on by default. Emailing it to the customer is off by default
Amounts in wordsPrinted on invoices and receipts in the Indian system: thousand, lakh, crore

Designed: the follow-up layer

RuleWhat it does
AgingFrom the invoice's due date. A part-paid invoice ages on the balance
No silent itemsAn overdue amount with no future-dated next action shows red
Three working days to billAfter that, a completed stage with no invoice is listed. The threshold is a proposal
Promises are countedA customer's promise becomes a commitment in the existing register
Disputes are markedA disputed amount is flagged and linked to the customer escalation record
One portfolio figureDays sales outstanding: what is owed, divided by the last 90 days of collections, times 90
Is this your problem too?

Four signs, and what we would need to start.

  • Your weekly review names a shortfall, and the same customers come up again next week
  • Nobody can say, without phoning around, who last spoke to a customer about an overdue stage
  • Stages are finished on site days before anyone raises the invoice
  • A disputed amount and a slow payer sit in the same column

To start we would need your billing register as it stands, one owner in accounts, and thirty minutes a week to review the list. A spreadsheet is fine. If you keep no register of stage payments yet, that is the first job, and ProjectSignal already does it.

Who in your company owns each overdue stage payment this week?

Send us your billing register as it stands, even a spreadsheet. We will show you how it would age and who would own what. Start with one workflow. You only pay if it works.