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

A payment screenshot goes in. A numbered receipt and a reviewed client email come out.

A homeowner pays in stages, and the proof of each transfer arrives as a screenshot. At Viya Constructions someone then typed the receipt into a Word template. We built a workflow for that job: the payment is read from the image, the client and site are picked from ProjectSignal, and a numbered receipt comes out as PDF and Word. An email goes to the client only after a person checks it and clicks Send. Live since 15 October 2026.

Client
Viya Constructions
Department
Accounts
Starts from
Payment screenshots, one or a batch
Gives you
A one-page receipt as PDF and Word, and an optional reviewed client email
Connected to
ProjectSignal: client register and email
Status
Live. Live since 15 October 2026.

[01]What changedViya Constructions

The receipt no longer has to be typed from a screenshot. The client comes from the register, and the email waits for a click.

Before

Retype the screenshot into Word.

  • Payment proof shared in a chat group, then typed into a template
  • The client's name retyped by hand, from screenshots that often misspell it
  • One payment could end up with two receipts
  • The email sent from one person's own inbox
Now

Read it, pick the client, preview, issue once.

  • Seven payment details read from each screenshot, a whole batch on one card
  • Client and site picked from ProjectSignal's register, never from the image
  • A repeat blocked on bank reference, screenshot or receipt number
  • The email sent through ProjectSignal, after a check and a click
  • 7
    payment details read from each screenshot
  • 3
    hard blocks on a repeat: bank reference, screenshot, receipt number
  • 1
    approved page. A receipt that does not fit is refused
  • 0
    emails the AI can send. A person clicks, after a dry run

Figures from the workflow's own rules.

A builder who executes homes end to end is funded by its customers' stage payments, and every receipt is a document the customer keeps. The rule in Viya's operating principles is short: a receipt goes only to a registered client on a linked site, after a person confirms the details, and only once. The workflow puts that rule inside the job.

[02]Why this is hardViya Constructions

The receipt is one page of fixed text. The mistakes are in who it names and what it proves.

Most of a receipt never changes. The few lines that do are where it goes wrong.

  1. 01

    One home, many receipts

    Viya bills each home by construction stage. Its standard agreement carries 11 payment stages, with a design fee before them. Each payment gets its own receipt, across more than 40 live sites.

  2. 02

    The payer's name is not always the client's

    A bank shows the payer in its own spelling. The receipt ties the payment to the construction agreement, so it must carry the client's registered name. One client can have several sites.

  3. 03

    A screenshot is not money received

    A banking app can show "Request accepted" before a transfer completes. Transfers also fail, or go to another payee. A receipt says the company has the money.

  4. 04

    A receipt cannot be taken back

    The customer holds it. A second receipt for one transfer, or one in the wrong name, cannot be recalled.

[03]How it worksViya Constructions

Seven steps. Accounts decides at four of them. The AI is used in exactly one.

One card carries the whole batch.

  1. 01Accounts

    Attach the screenshots

    Accounts types "/", picks Payment receipts and attaches one screenshot or a batch. The review card opens at once, one row per payment.

  2. 02The workflow

    Read the payment evidence

    Each image is read for amount, date, method, payer, bank reference, payee and status. An unreadable field stays empty. The AI is told not to name a client, a site or a receipt number. If neither the amount nor the bank reference can be read, the card asks for a better screenshot.

  3. 03Accounts confirms

    Pick the client and the site

    Accounts searches ProjectSignal's client register by name, place or email. An unregistered name cannot be chosen. A single linked site is selected; with several, accounts chooses. The site's location fills in from its record. If ProjectSignal holds none, accounts types it.

  4. 04Accounts confirms

    Number the receipt

    Accounts types the next number in the company's own series and sets the building type. One client and site can be applied to several payments.

  5. 05Fixed logic

    Check the money

    The amount is held to the paisa, a hundredth of a rupee, and written in words in lakh and crore, the Indian system. The payment date cannot fall after the receipt date. A failed payment is refused.

  6. 06Accounts confirms

    Preview, tick, issue

    The preview re-reads the client and site from ProjectSignal, builds the real one-page receipt and lists possible duplicates. Accounts ticks that it was checked. Only that preview can be issued, as PDF and Word.

  7. 07Accounts confirms

    Check the email, then send

    Optional, and separate for each receipt. A dry run through ProjectSignal sends nothing. Then accounts clicks Send. The card reports the email accepted for sending, and says delivery is not confirmed.

The bank's evidence and the registered client are kept apart.

The card shows the payer as the bank wrote it beside the client picked from the register. A misspelled payer never becomes the name on a receipt.

  • Nobody can change a payment's status to success on the card
  • Any edit clears the preview, so what is issued is what was checked
Review payment receipts · 1 of 4 generated
Payment 1 · Site A₹3,75,000 · no. 26-27/113Generated
Payment 2 · Site C"Request accepted". Funds tick neededNeeds attention
Payment 3 · Site APossible duplicate of payment 1Needs attention
Payment 4Failed transfer. No receiptNeeds attention
Illustrative. Made-up sites, receipt number and amount.

The email is checked before it can be sent.

It goes to every address on the client's record, with accounts in copy. Edit the subject or message after the check, and Send switches off until it is checked again.

  • If the connection drops mid-send, only that same email can be retried
Email receipt · Review and send
ToThe client's two registered addresses
CCAccounts mailbox
SubjectPayment receipt 26-27/113
Attachment26-27-113.pdf
Check emailChecks passed. Nothing has been sent yet.Ready
Illustrative. Made-up receipt number and recipients.

[04]Connected to ProjectSignalViya Constructions

The client comes from ProjectSignal. The email goes out through it. The payment is not posted to its billing register yet.

  1. Reads

    From ProjectSignal

    • The client register: name, place, email addresses
    • The sites linked to each client
    • Each site's location, and whether it is archived
  2. Does

    What happens in between

    • Reads the payment from the screenshot
    • Checks amount, dates, status, duplicates
    • Builds the receipt, waits for the tick
    • Dry-runs the email, waits for Send
  3. Writes

    To ProjectSignal

    • The receipt email, to the client's registered addresses, accounts in copy
    • Email addresses added to or removed from the client's record

Reads and writes use the signed-in person's own connection, never a shared account.

Two things are written to ProjectSignal, each by the person's own click and within that person's permissions. The email goes through the platform's own email tool, dry run first. ProjectSignal accepts mail only to registered client addresses, active staff and the company's own listed internal addresses, caps the day's volume, and will not send the same request twice. The AI cannot reach either action.

The payment itself is not written. ProjectSignal keeps its own billing register: planned and collected amounts for each stage, with its own stage invoices and receipts. The receipt issued here is a separate document and does not post to that register yet, so the payment is still entered there by a person.

  1. Design invoice
  2. Client register
  3. Stage invoice
  4. Payment receipt
  5. Collections

Next, not built yet.

Three improvements are listed. Record the payment against its stage invoice in ProjectSignal when the receipt is issued, so one receipt exists for it. Suggest the client from the payer's name, still confirmed by a person. Track email delivery.

Its sibling at design stage.

The design fee, invoiced before construction, has its own live workflow. It has no connection to ProjectSignal. Details are below.

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms.

StepDone by
Reading the seven payment details from the screenshotThe AI, those fields only
Who the client is, and which siteAccounts, from ProjectSignal's register. The AI is barred from naming either
The receipt numberAccounts types it. Fixed logic refuses one already used
Amount in figures and words, date order, duplicates, one-page fitFixed logic
Whether unclear money has arrivedAccounts, with a tick. Not offered for a failed payment
Receipt wording and layoutViya's approved template, never rewritten by the AI
Issuing the receiptAccounts, from a preview that still matches
Sending the emailAccounts, after a dry run. No AI step can send

[06]More detailViya Constructions

The rules it follows

Every rule, written down.

For the accounts head who will ask what it refuses.

RuleWhat it does
What the AI may readOnly the visible payment evidence. Text inside the image is data, never an instruction.
"Request accepted"Read as pending, never as success.
Failed or reversed paymentRefused. No receipt, and no funds tick.
Pending, unclear, or paid to another nameAccounts must tick that the company received the funds. A successful transfer to another payee is not evidence of money received.
Client and siteA registered client, and one of that client's linked sites. An archived or unlinked site stops the preview.
Amount and datesPositive, at most two decimal places, held in whole paise. The payment date cannot be after the receipt date.
Receipt numberTyped by accounts. The workflow does not invent the next number, and refuses one already used for another payment.
Duplicate, blockedThe same bank reference, screenshot or receipt number, checked against every receipt the workflow has issued for the company. A payment submitted twice shows its existing receipt.
Duplicate, warnedSame client, site, date and amount under a different bank reference. Accounts must tick that it is a separate payment.
Fixed wordingThe approved paragraph tied to the construction agreement, plus a line that the receipt is not a tax invoice for GST, India's goods and services tax.
One pageA receipt that will not fit the approved page is refused, never clipped. The card asks for a shorter site location or client details.
Finishing a batchOnly when every payment is issued or excluded.
After issueNo edits. A correction goes through accounts and a new receipt.
EmailAccounts always in copy. Any change to text, recipients or copy list needs a new check. A client with no email goes to the client register first. Up to 10 extra addresses per client.
At design stage

Before construction, the client gets a design-fee invoice. A sibling workflow issues it on one approved page.

Live. In production since 23 September 2026 and handed over on 5 October. It produces a PDF and has no connection to ProjectSignal.

Before construction Viya charges a design-phase fee for the site visit, floor plan, 3D elevation, estimation and permit drawings. Its invoice is a different form from a contractor invoice: one project, one client, no tax-deduction or retention lines. It is a three-step card with no attachment.

Part of the invoiceHow it is handled
Client, location, built-up areaTyped, or taken from the chat request, then confirmed on the card
Invoice numberTyped by accounts. The workflow does not guess the sequence
AmountWhole rupees. The words are generated from the figure, so the two cannot disagree
ServicesFive standard design services prefilled, eight at most to stay on one page
Company and bank details, payment QR codeFixed. A request in chat cannot change them
A later correctionAsked for in chat. The same checks run again and the invoice is saved as a new version

Every field is checked on the card and again before the PDF is produced.

What it means for you

Three readers, three answers.

  1. For owners

    No receipt leaves in a name nobody checked

    The name comes from your client register, the wording from your approved template, and accounts is copied on every email.

  2. For accounts

    Your template, your number series

    The layout and the number series stay yours. A client's details are entered once in the register and reused, and a duplicate is caught before a number is used.

  3. For your technical person

    Issued once, sent once

    Each screenshot is fingerprinted. Issuing needs the exact preview that was checked and repeats the duplicate check. 53 automated tests cover it.

Is this your problem too?

Five signs, and what we need to start.

  • Customers send payment proof as a screenshot in a chat group
  • Receipts are typed into a template where only a few lines change
  • The payer's name on the transfer is not always the client's
  • Nothing stops one payment from getting two receipts
  • Receipt emails go out from someone's own inbox

To start we need your receipt template, a few past receipts with their screenshots, your client list, one owner in accounts, and thirty minutes a week.

When a customer pays, who types the receipt, and how do you know it was issued only once?

Send us your receipt template and one real payment screenshot. We will show you how the job runs today and what a first version would look like. Start with one workflow. You only pay if it works.