Use this queue to find unfinished work quickly and jump straight to the desk that clears it.

Enter the tender opportunity first. This stage captures the authority, district, fund, dates, and tender notice before any bid decision is made.

Use this only for projects that are already awarded and need to enter the live project list directly. It records the entity and contract details, then activates the project immediately.

Use this desk to keep project milestone, completion percentage, and weekly Monday update status current. The demand and authorization modules will use these controls later.

Enter the project budget and BOQ by payment category so proceedings and authorization can see exposure against approved limits.

Use this only when you need to add an already-awarded active project directly. Normal flow should start from Interested Projects in the Projects tab.

This is the first workflow backbone for the coming commercial control app. Create a demand here, then move it through proceedings and authorization.

Demands returned from proceedings or authorization appear here. Open one, edit it in Demand Desk, add explanation, and resubmit.

Executed payments that still need retroactive proceedings and authorization stay here until they are formally cleared.

Choose a date, then tick the employees who are present. Unchecked employees are saved as absent for that date. This works for office/shared staff, single-project staff, and multi-project supervisors, drivers, and operators.

Attendance is entered in the Attendance tab first. Select one or more saved attendance sheets and push them into the Demand Desk or direct batch creation as one demand per selected sheet.

Enter attendance in the Attendance tab first. Review, approve, return, and close salary sheets here in Workforce before loading them into the Demand Desk.

Use this tab to register the named accounts and role permissions that will be used as the app moves into the secured multi-user build.

Only admin should change which primary tabs and desk sections are open for each app role. The saved matrix stays in the database, and the workbook is only kept as a protected synced export.

These rows were found in the status file but could not be matched back to an exported payment row.

Select one or more statement files from the statement folders, then run reconciliation for the period you want to verify. Mixed weekly or monthly statement downloads are supported.

Shows the last date up to which each account has been fully reconciled. Future runs will only process transactions after this date per account.

Each row shows your payment record alongside the matched bank statement line. Tick to confirm reconciliation. Unmatched items require justification.

Enter inward bills received from departments or clients, split the bill into work, taxes, deposits, and deductions, then use reconciliation to link bank credits back to these bills.

Credits from reconciliation stay here until you classify them as bill receipts, cash deposits, internal transfers, other income, or leave them pending.

Use these books for live vendor, project, expense head, particular, account, organisation, and initiator visibility. The rows update from demands, authorizations, bills, credits, payments, and the latest reconciliation run.

See all organisation bank accounts with their entered opening balance, latest statement balance, and reconciliation position in one place.

Configured bank adapters and sample-driven banks available to the payment flow.

Organisation bank accounts maintained in the account workbook and used in banking, reconciliation, and books.

Cash treasury accounts used for petty cash, site cash, receipts, CS payments, and cash books.

Saved bank-account vendors used across quotations, bills, rate work, attendance, and direct banking.

UPI payees maintained separately for direct UPI execution and lookup.

Project master entries currently available for demand, commercial, workforce, and books.

Interested project intake entries with entity, department, district, fund, and tender-stage details.

Salary master entries used for attendance, advances, monthly sheets, and payroll settlement.

Business-origin people used as payment raisers across source desks, books, reports, and Telegram mapping.

Registered expense types maintained in Masters and reused across heads, particulars, books, and reports.

Saved expense heads used in demands, attendance extras, books, and reporting.

Direct-demand quotation, bill, and voucher identities linked to demands and later settled by bank, UPI, or instrument payments.

Recorded canonical particulars used to keep materials, rate-work items, wages, emergencies, and voucher descriptions under one matched name.

Signed-in app operators and their current assigned roles.

Organisation names, account types, vendor types, UPI vendor types, and other shared list dimensions used across the app.

Suggested assigned-role combinations for the current package, based on how the workflow, books, and treasury controls work now.

Acknowledge compared batches here after you verify the status report result. Pending, mixed, and failure batches stay here until they are marked as reviewed.

Payments that were made directly (e.g., bulk or UPI file simulated for testing) without a corresponding demand. Use Create Demand to retroactively link each payment into the workflow for post-authorization audit.

Physically completed projects stay highlighted here until their unpaid approvals, credit carry-forward, and open workflow rows are fully cleared.