Every week, purchase at Viya Constructions prepares a payment sheet and sends it to accounts. It is the only place the week's material vendor dues are written down, so a balance means a call to accounts or a wait for the accounting package. Viya asked for the sheet itself to build the ledger: uploaded as it is, each of the week's rows posted as not paid, each payment marked when it goes out. This is in build, not live.
[01]What changesViya Constructions
Viya asked for this in writing on 1 November 2026, first on its list of eight. The right-hand column is the design, not a live system.
From the rules as designed.
What exists today. Our contractor invoices workflow already reads Viya's weekly labor contractor payment workbook in production, and ProjectSignal has a vendor register, mostly labor contractors, with vendor codes and tax numbers. The ledger half is new. When the request arrived, ProjectSignal had no ledger line, no vendor payment record, no payment calendar and no upload history, and purchase's material payment sheet had not been read. All of that is in build.
Where the build stands. The plan starts with a reader run on real sheets that writes nothing. It passes when three sheets are read and their totals match purchase's own. No result is on record yet.
Why it matters. The order the week's cash goes out in decides which deliveries arrive and which crews stay on site.
[02]Why this is hardViya Constructions
Purchase prepares the sheet in its own format. Nothing else records what is due until the accounting package is updated.
Material vendors had no master to start from, and building one first would delay the ledger by weeks. The same trader can be Sree on one sheet and Sri on the next.
A vendor is paid part of what is due, then another part. After a few weeks the balance is unclear.
Cash each week is limited across more than 40 sites. Pay the wrong supplier first and a supply stops. Pay the wrong labor contractor first and the crew needed for next week's critical work walks off, while one whose work is finished is paid early.
[03]How it worksViya Constructions
The design in build. The steps are Viya's written flow, plus one of ours: the preview in step five.
An Excel file or a Google Sheet link goes into Bleno in purchase's own format. Nobody retypes it.
It finds the header row, columns and payment rows, and skips totals and blanks. Unsure what a column holds, it asks once and remembers the answer for that layout.
Only rows dated in the current week are taken. Older rows are skipped and listed back.
Each name is matched to a ProjectSignal vendor profile by tax registration number (GSTIN), phone or name. A first-time vendor is queued as a new profile. Look-alike spellings are listed for purchase to merge.
A card shows the rows to post, new vendors, skipped rows and any row held for having no vendor name or no amount. Nothing is posted yet.
Each confirmed row becomes a ledger line with its amount due, and each new vendor gets a profile and a vendor code. The reply counts rows posted, vendors created and rows skipped or held.
In ProjectSignal the line is marked Paid in full, or Part-paid with the amount actually paid, plus date, mode (bank transfer, UPI, check or cash) and reference. Who marked it is stored. A part-paid line stays open for further payments. Balances, totals and the payment calendar update at once.
Each vendor's ledger shows due, paid and balance, then every line with its site and status. Around it sit an all-vendors summary with grand totals, a calendar of what was paid to whom each day, in week and month views, and an upload history: rows read, posted, updated and skipped for every sheet.
[04]Connected to ProjectSignalViya Constructions
In build, as designed. Payment status is set in ProjectSignal's own screens, never from the sheet.
As designed, each write runs first as a preview inside ProjectSignal. It is saved only after the person confirms, as that signed-in person, within their permissions and through the platform's own validation. Every change is logged with who, when, the old value and the new value.
[05]The Monday listViya Constructions
Planned to follow the ledger. Not built. Each Monday at 08:00 the directors get a five-line summary on Telegram with a link to the list: open lines by vendor, with amount, site and days since the sheet date.
From the vendor ledger, as of Monday 08:00. Open lines with 27 vendors. Part-paid lines: 9. Paid last week: 19 vendors.
Critical: 5 vendors. Block yard, deliveries due at Site A and Site C. Steel supplier, Site F slab next week. Lines without a site: 6.
In the rule's first version, a vendor is critical when it has an open purchase request, purchase order or delivery due in the next 14 days on an active site, or when a line with such a vendor has stayed part-paid for more than 14 days. The list ranks critical lines first, then by days since the sheet date, then by balance. Every figure shows the time it was read.
Lines without a site are listed separately for purchase to tag, and last week's payments sit beside the list. It is a report: it schedules, approves and pays nothing.
[06]Who decides whatViya Constructions
As designed. Nothing here approves or makes a payment.
[07]More detailViya Constructions
Viya's own rules from its request, plus two design defaults of ours: the week and the source label.
The design gives you a Monday view of what you owe each vendor, what went out last week and which vendors supply active work. You still decide who is paid.
No fixed format, no vendor setup first. A vendor gets a code the first time it appears. Your weekly job is the merge list.
Opening balances go in as you hold them, with an as-on date. Marking a payment takes amount, date, mode and reference.
To start we would need your last four weekly payment sheets, one owner, a rule for who may mark a payment as paid, and thirty minutes a week.
[08]Where this fitsViya Constructions
Send us four recent payment sheets as purchase sends them to accounts. We will show you how they read and what a first ledger would look like. Start with one workflow. You only pay if it works.