Dashboard
What are we owed, what is in the bank, and can we make payroll this month?
From the muster roll to the balance sheet, one month at a time. One month of attendance produces the payroll, the client’s invoice, the VAT challan and a double-entry ledger: nothing typed twice, and every change can be reversed.
Security, cleaning and facility services · Bangladesh VAT and AIT built in
Companies that post staff at client sites (security, cleaning, facility services) and bill per person, per day worked.
Clients and their rates, the roster, and each month’s attendance. Typed in, or uploaded from a spreadsheet row by row.
Payslips, bank letters, invoices, the VAT challan and six financial reports, all from the one attendance figure.
Your own machine or server, with no outside service needed to close a month, and a backup taken before every risky step.
Each month moves left to right through four steps. The attendance typed at step one is the same figure every document downstream is built from, so changing it once changes everything that depended on it.
Days worked, leave, absence and overtime for every person on every project: the only figure anyone types.
Pay is worked out from the rules, checked, then locked once approved. Nothing is re-entered to produce it.
The client is charged for the days each post was covered, at the rate their contract actually says.
Payments are recorded against invoices, and the ageing updates itself rather than being maintained.
Overview, the monthly cycle, the reports, the records behind them, and the setup that makes all of it correct for your contracts rather than generically correct.
What are we owed, what is in the bank, and can we make payroll this month?
What is still missing, and what each project needs before the month can close.
Who worked which days this month: the single entry everything downstream is built from.
What everyone takes home, how it is paid, and every document that says so.
What the client owes for the month, at the contracted rate per post.
Who has paid, who has not, and for how long, with the ageing maintained automatically.
Profit and loss, balance sheet, cash flow, trial balance, ledger and profit by project.
What went through the cash tin, with the proof attached to each line.
Who changed what, and whether it can be put back, because sometimes it has to be.
Who is billed, how they are taxed, and what each post costs on their rate card.
The roster, how each person is paid, and what the posts are called in English and Bengali.
Spreadsheets in row by row, the pay rules, and who is allowed to change them.
Attendance is the input. Everything after it (gross, deductions, net, the bank list, the invoice line, the VAT on it) is derived, so there is no second place for the numbers to disagree.
What are we owed, what is in the bank, and can we make payroll? Receivables are grouped by the month the bill is for, not the month somebody chased it.
Days worked, leave, absence and overtime, per person, per project: typed in or uploaded from the sheet the site supervisor already keeps.
Pay worked out from the rules, checked, then locked once approved. Basic, gross, present days, deductions and overtime resolve to a net payable and the method it is paid by.
The client is charged for the days each post was actually covered, at the rate their own contract specifies, with the tax treatment that client carries stated on the bill.
The attendance figure entered at step one is the same figure the payslip, the bank letter, the invoice and the VAT challan are built from. Change it once and every document that depends on it changes.
Pay is worked out from the rules, checked, then locked. After that it takes an explicit, recorded action to move it, not a stray edit in a cell nobody was looking at.
The client is charged for the days each post was actually covered, at the rate their own contract specifies, so a gap in cover is a smaller invoice rather than an argument next month.
Payments are recorded against invoices and the receivables ageing follows. Nobody rebuilds a spreadsheet of who owes what, because nobody has to.
Because every step posts to the same double-entry ledger, the financial statements are a view of it rather than a monthly reconstruction. Any figure drills to the lines behind it.
Every figure on this screen is the ledger's own balance, carried under its account code. Nothing is typed here: it is a view of what the month already posted.
Every step posts to the same ledger, and so do petty cash and bank balances. The reports are not assembled from the operational screens. They are read straight off the books.
Profit and loss, balance sheet, cash flow, trial balance, general ledger and profit by project. Any figure drills to the ledger lines behind it.
A contract-services business lives or dies on which sites earn their keep. Profit by project puts each one’s revenue against the cost of covering it.
History records who changed what and when, and the change can be put back. Your data is backed up before every risky step, not on a schedule that missed the one that mattered.
Each one is generated from the attendance and the rate card rather than typed. The Bengali payslips and the VAT challan are produced from the same figures as the invoice, so they can never fall out of step with it.
Installed on hardware you control and backed up before every risky step. Nothing about closing a month depends on a connection to somebody else’s service.
Bring one client, one site and one month of attendance. We will produce the payslips, the bank letter, the invoice, the challan and the resulting statements in front of you.