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

The weekly payment sheet goes in. Numbered contractor invoices come out. Each one reconciles to the paisa.

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.

Client
Viya Constructions
Department
Accounts
Starts from
The weekly payment workbook, as accounts keeps it
Gives you
A PDF with a page per invoice, an Excel file with a tab per invoice
Connected to
Nothing yet. Ledgers in ProjectSignal are in build
Status
Live. Production runs recorded 22 to 24 October 2026. Documents only. Ledgers in build.

[01]What changedViya Constructions

Accounts keeps its sheet. The retyping stops. The backward sum is done the same way every week.

Before

Retype the sheet. Work each bill back by hand.

  • Every paid row typed again into the invoice layout
  • Stage amount, tax and retention worked back by hand
  • Tax numbers kept in a separate labor master sheet
  • Staff and contractors on one sheet, deductions due on only one
Now

Attach the sheet. Check one card. Get the batch.

  • The workbook read as it is. The card names the week and date used
  • Fixed logic works back in whole paise, so every invoice reconciles
  • Tax numbers looked up fresh. A missing one prints blank
  • Staff rows recognized by labor code, deductions off
  • 1
    review card between the sheet and the invoices
  • 0
    amounts worked out by the AI
  • About 48
    tabs in the real workbook, read without cleanup
  • 40
    automated tests on reading, numbering and arithmetic

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 shows the payout. The invoice has to start higher and land on it exactly.

  1. 01

    The sum runs backward

    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.

  2. 02

    A paisa is easy to lose

    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.

  3. 03

    The workbook is not one tidy sheet

    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).

  4. 04

    The tax number is somewhere else

    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.

How the workflow closes the gap.

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

One review card between the sheet and the invoices.

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.

  1. 01Accounts

    Attach the workbook

    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.

  2. 02Fixed logic

    Find the week, read the rows

    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.

  3. 03Accounts confirms

    Check the review card

    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.

  4. 04Fixed logic

    Read the file again

    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.

  5. 05Fixed logic

    Look up, number, calculate

    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.

  6. 06The workflow

    One PDF, one Excel file

    A page per invoice and a tab per invoice, drawn from one layout grid so they cannot disagree.

You see what will be billed before it is billed.

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.

Check the invoices before they are generated
Worksheet, dateW 45 · 7 Nov 20269 rows read
First invoice numberINV-0412, then counts upTyped
3 · ShutteringBill yes · Deductions yesContractor
4 · Site staffBill no · Deductions noStaff
6 · PlasteringAmount unreadableType amount
Illustrative. A made-up week, payees and numbers.
After the batch is made
Bleno

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.

Accounts

Tax number for L-218 is ABCDE1234F.

Bleno

INV-0417: tax number blank, now ABCDE1234F. Both files saved as a new version. No amount changed.

Illustrative. Made-up numbers, labor code and tax number.

[04]Connected to ProjectSignalViya Constructions

Today it produces documents. The ledgers that give payments a place in ProjectSignal are in build.

  1. Reads

    From accounts' own files

    • The weekly payment workbook
    • The labor master, for tax numbers
    • Nothing from ProjectSignal today
  2. Does

    What happens in between

    • Finds the week and the payment block
    • Reads the rows, flags staff
    • Waits for accounts to confirm
    • Works out every amount in whole paise
    • Builds both files from one layout
  3. Writes

    To ProjectSignal

    • Nothing today. The PDF and the Excel file are kept in Bleno, with their versions

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.

  1. Contractor work order
  2. Weekly payment sheet
  3. Contractor invoices
  4. Ledgers in ProjectSignal, in build

[05]Who decides whatViya Constructions

The AI reads. Fixed logic calculates. A person confirms. Here the AI does the least of the three.

StepDone by
Passing on the week you typed, writing the closing noteThe AI. It may not calculate or restate a figure
Finding the worksheet, the payment block and the rowsFixed logic, from the original file
Stage amount, tax, retention and amount dueFixed logic, in whole paise
Invoice numbers after the firstFixed logic, counting up
First invoice number, invoice date, which rows to bill, whether deductions apply, any amount the sheet does not state readablyAccounts, on the review card
The contractor's tax numberThe labor master. If missing there, the field stays blank
Paying the contractorAccounts, through its own banking. The workflow never moves money

The same split holds in every Bleno workflow at Viya.

[06]More detailViya Constructions

The rules it follows

Every rule, written down.

For the accounts head who will ask how it decides.

RuleWhat it does
Working backThe amount due always equals the sheet amount. Stage amount is worked back from it and rounded once. Tax is taken on the stage amount and rounded once. Retention is what remains. Every figure is a whole number of paise, and a test holds the three lines to the payout.
No deductionsStage amount equals amount due. Tax and retention cells print blank, not 0.00.
Staff and contractorsStaff are recognized by labor code, or a Contractor column reading Employee: deductions start at no. Contractors start at yes, and a contractor row with no decision is refused.
Reading the sheetLabor code and amount columns must be present, found by their headers. Total rows are skipped. A week tab ignores blocks titled for another week. An empty payee cell falls back to the contractor column, then the labor code.
Source lockIf the card no longer matches where its rows came from: "The worksheet or payment date changed. Read the rows again before generating."
AmountsCurrency signs, commas and bracketed notes are removed: 12000(cash) reads as 12,000. A sum such as =3000+250 is added up. Cell references and functions are never evaluated: that amount stays on the card for the reviewer to type. Zero or negative is rejected.
NumberingTrailing digits count up, keeping prefix and leading zeros. A first number not ending in digits is refused.
Tax numberRead fresh on every run, matched on labor code in its long or short form. Never guessed. If the labor master cannot be reached, nothing is generated.
After generationOnly a tax number (five letters, four digits, a letter) or a contact number (10 to 13 digits) can be added. Both files get a new version. Amounts cannot be edited: create the invoices again.
On each invoiceBusiness name, labor code, contact number, tax number, invoice number and date, site name and address, work type, stage completed, stage amount, tax, retention, net amount, amount due.
What it is notA GST (goods and services tax) invoice or a tax return. These are contractor payment invoices in the company's own layout.
What goes in, what comes out

One workbook in. Two files and a note out.

ItemIn or outFormat
Weekly payment workbookInExcel or CSV, attached in the chat
Review card choicesInFirst invoice number, invoice date, yes or no per row
Labor masterInRead by the workflow for tax numbers. Nobody attaches it
Invoice PDFOutA4, a page per invoice
Invoice workbookOutExcel, a tab per invoice named for the payee, same layout as the PDF
Closing noteOutEach invoice listed from the calculated values
What it means for you

Three readers, three answers.

  1. For owners

    Paperwork that matches the payment

    Each invoice ends on the amount paid, with deductions shown the same way every week.

  2. For accounts

    Keep the sheet you already keep

    No new format and no cleanup. Total rows, several payment dates and amounts typed as sums are read as they are.

  3. For your technical person

    Whole numbers, rules under test

    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.

Is this your problem too?

Four signs, and what we would need to start.

  • Accounts retypes a payment sheet into invoices or bills every week
  • The sheet shows what was paid. The document must show the amount before deductions
  • Tax numbers or vendor details live in a different file
  • Staff and contractors are paid from one sheet, with different deductions

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.

What does your accounts team retype every week?

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.