Viya Constructions pays its labor contractors weekly from a payment workbook. Each payment needs a numbered invoice showing tax deducted at source and retention, and accounts typed those by hand. Now accounts attaches the workbook, checks one review card, and gets the batch as PDF and Excel. Documents only today: nothing is written to ProjectSignal. The vendor and subcontractor ledgers that come next are in build.
[01]What changedViya Constructions
From the workflow's rules, its tests and the real workbook.
A contractor invoice is a document the contractor keeps. A wrong payee, a wrong tax number or a missed deduction goes straight onto it, and one wrong row can start a dispute. With more than 40 live sites, a week's sheet runs to dozens of contractor rows.
Where it stands. Live. Production runs are on record for 22 to 24 October 2026, the only Bleno workflow at Viya with runs on record.
[02]Why this is hardViya Constructions
The sheet amount is what the contractor receives. The invoice must open with a larger stage amount, take off tax deducted at source (TDS) and retention, the share held back from each bill, and end on exactly the sheet figure.
Add the deductions on top of the payout and every stage amount is wrong. Work back correctly but round each line on its own, and the three can miss the payout by a paisa, a hundredth of a rupee.
About 48 tabs, one a week, with last year's final weeks at the end. A sheet can hold several dated payment blocks, total rows, and amounts typed as a sum, =3000+250, or with a note, 12000(cash).
Staff and contractors share the sheet, and deductions apply to contractors only. The contractor's PAN, the Indian tax ID each invoice carries, sits in a separate labor master sheet, keyed by labor code.
One fixed order. Stage amount first, worked back from the payout. Tax on the stage amount. Retention is whatever is left, so rounding has one known home. Viya's deduction rates are set in the workflow and are not published here.
[03]How it worksViya Constructions
This job has almost nothing for the AI to read. The workbook has structure, so fixed logic reads it. The AI passes on the week you typed and writes the closing note.
Accounts attaches the week's payment workbook, Excel or CSV, and types the command for Create invoices. A week or a payment date can be named.
A named week is matched loosely: W 41, week 41 and 41 find the same tab. A named date is read day first. With nothing named, the newest dated payment block that has rows is used. Staff rows are flagged.
Accounts types the first invoice number, checks the invoice date, which starts as the payment date, and sets each row to yes or no for billing and for tax and retention. Changing the worksheet or the date reads the rows again and clears those choices.
On confirm, the original file is read again. The card's choices carry over. Its figures do not, except an amount accounts had to type.
Tax numbers are looked up fresh in the labor master. Invoice numbers count up from the first. Stage amount, tax, retention and amount due are worked out in whole paise.
A page per invoice and a tab per invoice, drawn from one layout grid so they cannot disagree.
The card shows where the rows came from, every row with its payee, labor code and amount, and a total. Worksheet and date are picked from the file, not typed. Amounts are locked unless the sheet's figure could not be read. Staff rows arrive with deductions off. Billing them is the reviewer's yes or no.
8 invoices created from W 45, payment date 7 Nov 2026: INV-0412 to INV-0419. The labor master has no tax number for labor code L-218, so INV-0417 shows it blank. You can give it here.
Tax number for L-218 is ABCDE1234F.
INV-0417: tax number blank, now ABCDE1234F. Both files saved as a new version. No amount changed.
[04]Connected to ProjectSignalViya Constructions
As of late October 2026. No send step, no payment step.
Nothing is written to ProjectSignal. Workflows that do write, such as the milestone plan import, write as the signed-in person, through the platform's own validation, after a preview.
What is in build. On 1 November 2026 Viya asked for the next step: a vendor ledger in ProjectSignal. Purchase uploads the payment sheet it prepares each week for material vendors. Each row is posted as not paid, then marked paid or part-paid once the money has gone out. It reuses the sheet reading built here, not the invoices. It is in build, not live.
For labor contractors, the same request ties payments to the work order: its value enters the subcontractor's ledger for the site, and accounts records each weekly payment against it. That is also in build. The weekly invoice step stays.
[05]Who decides whatViya Constructions
The same split holds in every Bleno workflow at Viya.
[06]More detailViya Constructions
For the accounts head who will ask how it decides.
Each invoice ends on the amount paid, with deductions shown the same way every week.
No new format and no cleanup. Total rows, several payment dates and amounts typed as sums are read as they are.
No AI in the calculation path. Generation reads the source file again instead of trusting the screen. Automated tests hold the parsing, numbering and arithmetic.
To start we need two or three real weeks of your payment workbook, a few invoices made from them by hand, your deduction rules, one owner in accounts, and thirty minutes a week. The first test is reproducing your past invoices to the paisa.
[07]Where this fitsViya Constructions
Send us one real payment sheet and the invoices made from it. 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.