feat(cashier): add end-of-day report, my work, and cashier updates
This commit is contained in:
@@ -9,11 +9,10 @@
|
||||
<div class="pg">
|
||||
<header class="pg-head">
|
||||
<div>
|
||||
<div class="pg-eyebrow">CASHIER · DAY BOOK</div>
|
||||
<h1 class="pg-title">Day Book</h1>
|
||||
<h1 class="pg-title">{{ title }}</h1>
|
||||
<p class="pg-sub">
|
||||
Every voucher raised on the selected date — cash deposits, withdrawals, disbursements, collections and bank
|
||||
transfers, with credit and debit totals.
|
||||
Every voucher raised on the selected date — cash deposits, withdrawals, disbursements, collections, interest and
|
||||
journals, with each person's own credit, debit and net.
|
||||
</p>
|
||||
</div>
|
||||
<div class="pg-toolbar">
|
||||
@@ -103,11 +102,90 @@
|
||||
Totals count approved vouchers only — pending and rejected rows are listed but never move the money.
|
||||
</p>
|
||||
|
||||
<!-- The day per person, for the officer who signs the book off. The sections below trace one
|
||||
voucher at a time; this is the other reading a branch needs — what each member of staff
|
||||
handled, and whether their column adds up. Built from whoever appears in the day's rows, so
|
||||
one person working alone gets one line and five people get five. -->
|
||||
@if (byUser.length > 0) {
|
||||
<div class="pg-card db-section db-byuser">
|
||||
<div class="db-section__head">
|
||||
<strong>Officer Verification Sheet</strong>
|
||||
<span class="db-muted">Each person's own credit, debit and net for the day</span>
|
||||
<span class="db-section__count"> {{ byUser.length }} {{ byUser.length === 1 ? 'person' : 'people' }} </span>
|
||||
</div>
|
||||
<div class="pg-table-wrap">
|
||||
<table class="pg-table db-table">
|
||||
<thead>
|
||||
<tr>
|
||||
<th>Handled by</th>
|
||||
<th class="num">Items</th>
|
||||
<th class="num">Credit (CR)</th>
|
||||
<th class="num">Debit (DR)</th>
|
||||
<th class="num">Net</th>
|
||||
<th class="num">Pending</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@for (u of byUser; track u.name) {
|
||||
<tr>
|
||||
<td class="db-byuser__name">{{ u.name }}</td>
|
||||
<td class="num">{{ u.items }}</td>
|
||||
<td class="num db-byuser__cr">₹{{ u.credit | number: '1.2-2' }}</td>
|
||||
<td class="num db-byuser__dr">₹{{ u.debit | number: '1.2-2' }}</td>
|
||||
<td
|
||||
class="num db-byuser__net"
|
||||
[class.db-byuser__net--pos]="u.net >= 0"
|
||||
[class.db-byuser__net--neg]="u.net < 0"
|
||||
>
|
||||
₹{{ u.net | number: '1.2-2' }}
|
||||
</td>
|
||||
<td class="num">
|
||||
@if (u.pending > 0) {
|
||||
<span class="db-badge db-badge--pending">{{ u.pending }}</span>
|
||||
} @else {
|
||||
—
|
||||
}
|
||||
</td>
|
||||
</tr>
|
||||
}
|
||||
</tbody>
|
||||
<!-- The sheet's own total, which must equal the day's totals above. That equality is
|
||||
what makes the sheet verifiable rather than just informative. -->
|
||||
<tfoot>
|
||||
<tr class="db-byuser__total">
|
||||
<td>All staff</td>
|
||||
<td class="num">{{ byUserTotals.items }}</td>
|
||||
<td class="num db-byuser__cr">₹{{ byUserTotals.credit | number: '1.2-2' }}</td>
|
||||
<td class="num db-byuser__dr">₹{{ byUserTotals.debit | number: '1.2-2' }}</td>
|
||||
<td
|
||||
class="num db-byuser__net"
|
||||
[class.db-byuser__net--pos]="byUserTotals.net >= 0"
|
||||
[class.db-byuser__net--neg]="byUserTotals.net < 0"
|
||||
>
|
||||
₹{{ byUserTotals.net | number: '1.2-2' }}
|
||||
</td>
|
||||
<td class="num">
|
||||
@if (byUserTotals.pending > 0) {
|
||||
{{ byUserTotals.pending }}
|
||||
} @else {
|
||||
—
|
||||
}
|
||||
</td>
|
||||
</tr>
|
||||
</tfoot>
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
}
|
||||
|
||||
<!-- One table per source register rather than one long list. The two read differently: the
|
||||
cashier's rows are cash that actually crossed the counter, the clerk's are requests nobody
|
||||
has actioned yet. Mixed together they invited the wrong sum. -->
|
||||
@for (s of sections; track s.key) {
|
||||
<div class="pg-card db-section">
|
||||
<!-- The section's own colour on the left edge: cash that actually crossed the counter, work
|
||||
still waiting to be actioned, and postings the system made are three different things to
|
||||
a person closing the day. -->
|
||||
<div [class]="'pg-card db-section db-section--' + s.key">
|
||||
<div class="db-section__head">
|
||||
<strong>{{ s.label }}</strong>
|
||||
<span class="db-muted">{{ s.hint }}</span>
|
||||
|
||||
Reference in New Issue
Block a user