TGH Tech
Case study · Workflow 18 of 20 · Money in and out · In build

The weekly payment sheet goes in as it is. In build: each vendor's due, paid and balance, with a payment calendar.

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.

Client
Viya Constructions
Department
Purchase and accounts
Starts from
The weekly payment sheet, Excel or Google Sheet link
Gives you
As designed: vendor ledger, all-vendors summary, payment calendar, upload history
Connected to
ProjectSignal vendor register. Purchase and work orders once built
Status
In build. Requested by Viya on 1 November 2026. Not live. No run on real sheets is on record yet.

[01]What changesViya Constructions

What each vendor is owed, the week the sheet is made. Not when the books catch up.

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.

Before

Ask accounts, or wait for the books.

  • The payment sheet is the only record of the week's vendor dues, and it reaches no system
  • When accounts pays a vendor, only accounts knows
  • What a vendor is owed is a call to accounts
  • Critical payments come from memory, or from a supplier who has stopped delivering
As designed

Upload the sheet. Mark each payment as it goes out.

  • Each current-week row becomes a ledger line, posted as not paid
  • Paid or part-paid is marked in ProjectSignal with date, mode and reference
  • Due, paid and balance per vendor, with every line behind the total
  • A Monday list of open lines, with vendors supplying active work marked critical
  • 2
    things a row needs to post: vendor name and amount
  • 3
    states for a line: not paid, part-paid, paid
  • 0
    payments made by the system. It records what accounts paid

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

The week's dues live in one file. Four things make a vendor balance hard to trust.

  1. 01

    The dues are written once, in a spreadsheet

    Purchase prepares the sheet in its own format. Nothing else records what is due until the accounting package is updated.

  2. 02

    There is no clean vendor list

    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.

  3. 03

    Part payments blur the balance

    A vendor is paid part of what is due, then another part. After a few weeks the balance is unclear.

  4. 04

    Paying in the wrong order stops work

    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

Read the sheet, check it, post it. Then mark each payment when it goes out.

The design in build. The steps are Viya's written flow, plus one of ours: the preview in step five.

  1. 01Purchase or accounts

    Upload the week's sheet

    An Excel file or a Google Sheet link goes into Bleno in purchase's own format. Nobody retypes it.

  2. 02The workflow

    Read the layout

    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.

  3. 03Fixed logic

    Keep this week's rows

    Only rows dated in the current week are taken. Older rows are skipped and listed back.

  4. 04The workflow

    Link or create each vendor

    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.

  5. 05Uploader confirms

    Review the preview

    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.

  6. 06The workflow

    Post as not paid

    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.

  7. 07Accounts or purchase

    Mark the payment when it goes out

    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.

Payment sheet for this week
Rows read46, on this week's worksheet
To post as not paid38 rowsReady
New vendors3, codes given on postingNew
Possible duplicateTwo spellings that look like one vendorMerge list
Skipped5 dated last week, 2 total rowsListed
Held for review1 row with no amountCheck
Column F has no headingIs it the site?Asked once
Illustrative. Made-up counts. Nothing is posted yet.

Four views, built from the same lines.

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.

Vendor ledger · Material supplier V-0311
Site B · sandDue 86,000 · paid 86,000Paid
Site C · blocksDue 124,500 · paid 60,000 · balance 64,500Part-paid
No site · cementDue 48,200 · balance 48,200Not paid
Vendor totalDue 258,700 · paid 146,000 · balance 112,700
Illustrative. Made-up vendor, sites and amounts.

[04]Connected to ProjectSignalViya Constructions

The ledger is being built inside ProjectSignal, where the vendor register already sits. Nothing is written there today.

  1. Reads

    From ProjectSignal

    • Vendor profiles: code, tax number, phone, spellings
    • Ledger lines from earlier sheets
    • Open requests, orders and deliveries, for the Monday list
  2. Does

    What happens in between

    • Reads the sheet
    • Links or creates each vendor
    • Previews what would post
    • Waits for the uploader to confirm
  3. Writes

    To ProjectSignal

    • New vendor profiles, each with a code
    • Ledger lines, posted as not paid
    • One upload history entry per sheet

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.

What connects to the ledgerHowStatus
The weekly payment sheetCurrent-week rows post as not paid. Past bills, payments and opening balances are typed, pasted from Excel or read from an old register, and marked Manual.In build
Purchase ordersThe order's vendor is picked from this vendor database. An open order or a delivery due marks that vendor critical on the Monday list.Requested, not live
Work ordersThe subcontractor is picked by vendor code from the same vendor database. The work order's value enters that subcontractor's ledger for the site, and weekly payments are recorded against it the same way. A payment taking the total above that value is flagged.Requested, not live
Supplier invoicesA later proposal. The invoice is matched to the purchase order and delivery receipts, and differences go to the purchase manager. A matched, approved invoice enters the cost ledger, of which this ledger is the first part.Designed, not built
  1. Purchase request
  2. Purchase order
  3. Payment sheet
  4. Vendor ledger
  5. Payments due this week

[05]The Monday listViya Constructions

Payments due this week become a list. Planned next: read from the ledger, not from memory.

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.

Vendor payments due this week
ProjectSignal

From the vendor ledger, as of Monday 08:00. Open lines with 27 vendors. Part-paid lines: 9. Paid last week: 19 vendors.

ProjectSignal

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.

Illustrative. Made-up sites and counts.

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

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

StepDone by
Finding the header row, columns and payment rowsThe AI. It asks once when a column is unclear
Suggesting that two spellings are one vendorThe AI suggests. Purchase merges
Current-week filter, duplicate check, totals, balancesFixed logic
Posting the rowsThe uploader, after the preview
Marking Paid or Part-paidPurchase or accounts, once the money has gone out
Deciding what to pay this weekDirectors and accounts
Making the paymentAccounts, through its own banking. The system never makes one

As designed. Nothing here approves or makes a payment.

[07]More detailViya Constructions

The rules it follows

Every rule, written down.

Viya's own rules from its request, plus two design defaults of ours: the week and the source label.

RuleWhat it does
No fixed formatA row needs only a vendor name and an amount. Without either, it is held for review.
No date, site or bill numberThe sheet's week or upload date is used. The line posts untagged, to be tagged later. The duplicate check falls back to vendor, amount and date.
Matching a vendorBy tax registration number, phone or name, ignoring case, spaces, punctuation and words such as M/s, Pvt Ltd and & Co. With neither number on the sheet, by name only.
Look-alike vendorsNever blocked. Listed for purchase to merge, and the merged spelling is remembered.
One profile per tax numberA merge moves every line and purchase order to the profile kept.
Vendor profileCode, other spellings, contacts, tax numbers, sites, ledger and purchase orders. Missing details show as pending. A code already used in the books can be entered instead.
The same sheet, uploaded againUpdates existing lines and creates none. It never changes a payment status.
A changed amount, or a removed rowFlagged for review. Never overwritten, never deleted.
Paying above the due, or undoing a paymentAllowed only with a remark.
DatesNo payment can be dated in the future. A week runs Monday to Sunday, by each row's date.
Manual entriesBill, payment, bill with payment or opening balance, on any past date. An opening balance sets the start as on a date. They never overwrite sheet lines, and a match shows a warning.
Bank detailsVisible to accounts only.
Source labelScreens say the figures come from payment sheets. The accounting package stays the book of record, with a monthly reconciliation proposed.
What it means for you

Three readers, three answers.

  1. For owners

    Know what is open before a supplier calls

    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.

  2. For purchase heads

    Keep your sheet

    No fixed format, no vendor setup first. A vendor gets a code the first time it appears. Your weekly job is the merge list.

  3. For accounts

    Your books stay the book of record

    Opening balances go in as you hold them, with an as-on date. Marking a payment takes amount, date, mode and reference.

Is this your problem too?

Three signs, and what we would need to start.

  • The week's vendor dues exist only in a spreadsheet purchase sends to accounts
  • You learn a payment was critical when the deliveries stop
  • One supplier is spelled three ways across your sheets

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.

Who in your company can say, today, what each vendor is owed?

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.