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.
[01]What changedViya Constructions
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
Most of a receipt never changes. The few lines that do are where it goes wrong.
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.
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.
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.
The customer holds it. A second receipt for one transfer, or one in the wrong name, cannot be recalled.
[03]How it worksViya Constructions
One card carries the whole batch.
Accounts types "/", picks Payment receipts and attaches one screenshot or a batch. The review card opens at once, one row per payment.
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.
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.
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.
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.
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.
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 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.
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.
[04]Connected to ProjectSignalViya Constructions
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.
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.
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
[06]More detailViya Constructions
For the accounts head who will ask what it refuses.
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.
Every field is checked on the card and again before the PDF is produced.
The name comes from your client register, the wording from your approved template, and accounts is copied on every email.
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.
Each screenshot is fingerprinted. Issuing needs the exact preview that was checked and repeats the duplicate check. 53 automated tests cover it.
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.
[07]Where this fitsViya Constructions
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.