Applications — three things a month

Open this screen in Saral/projects/subcontractors/applications

The first tab of Payments, and the one a QS opens every month. One row per package, three cells per month — application in, valuation out, invoice in — the APP-VAL tracker kept by hand before. Click a cell to open that month: the date chain, their figures, our valuation and the notice.

You enter

Each month: whether the application came in (received / not applying / no response), their figures and ours
A reason for every line where our figure differs from theirs

Saral fills in

The date chain for every package-month — application due, valuation date, payment-notice and pay-less dates — from the package's terms
The tracker codes per cell (✔ R NA NR PL PL 0 !) and what is due this month
Our contract works back-to-back from CSA progress, and their claim read off the application they emailed or uploaded
The valuation ladder (gross, retention, previously certified, due) from the engine the server runs

It produces

The APP-VAL tracker as Excel (12 months) and a PDF on the company letterhead (6 months)
The interim valuation PDF, filed in the project file
The received claim the CVR and the Payment Schedule read

The monthly cycle

Every package in the cycle owes three things a month: their application in, our valuation and notice out, their invoice in. Applications shows all three for every package across six months, with the code that says where each stands. Click a cell to open that month: the date chain, their figures, our valuation on the interim-valuation ladder, the notice and the invoice. Save the month and the tracker updates; the notice is issued on Notices.

Dates are computed, never typed

Each package carries payment terms — days from the valuation date to the due date, the payment-notice and pay-less windows. Saral works every month's dates from those terms, so a late application or a missed pay-less date shows as “!” without anyone keeping a diary. Change the terms on the package and every future month moves.

What Saral reads for you

A subcontractor's application emailed to the project or dropped in a watched folder is read into the month as their claim (gross, works, variations, materials) — and line by line into the build-up on “Fill their lines”. Our contract works is drafted back-to-back from our own CSA progress on the lines the package delivers. A figure a person typed is never changed; a differing claim stays visible.

Issued outside Saral

A month whose valuation went out from another system is marked as such and shown dotted in the tracker. The panel links the original, the autopilot leaves its figures alone, and Saral never issues a second notice for it. Clear the flag if it was wrong and the month becomes a Saral month again.

Contra charges

Contras live with the package's final settlement — the Final settlement button in the month's panel opens the statement and its contra register (proposed, notified, agreed, disputed). A contra notified or agreed by the valuation date is deducted on the ladder; a disputed one is listed and not deducted. The pay-less notice names every deduction with its reason.

Next screen: /projects/payment-schedule

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.