> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/release-notes/stock-attendance-payments-and-facial-recognition.md).

# Stock, Attendance, Payments & Facial Recognition

## Summary

This release strengthens two areas of HCM: the Stock module and the Attendance, Payments, and Facial Recognition workflows.

Stock Management v2.1 addresses operational gaps observed across field deployments in campaigns such as ITN, SMC, and co-delivery, improving data accuracy, accountability, and real-time visibility across the health commodity supply chain, from national warehouses down to last-mile distributors. Key improvements include bulk stock dispatch via console upload, reliable data persistence across devices and sessions, real-time stock dashboards, live stock balance visibility on the mobile app, manual downsync, push notifications, offline QR-based issue and acceptance at the last mile, and a new web-based Commodity Management module.

Attendance, Payments and Facial Recognition covers the initial build for attendance register setup and worker management from Console, Proximity Supervisor register approval and editing, signature-based attendance marking on the APK, a face recognition-based proof-of-work pilot, and a role-based payment workflow for bill generation through to disbursement.

### At a Glance

<table data-header-hidden><thead><tr><th width="139.3515625"></th><th width="293.3828125"></th><th></th></tr></thead><tbody><tr><td><br></td><td><strong>Stock</strong></td><td><strong>Attendance, Payments and Facial Recognition</strong></td></tr><tr><td><strong>Upgrade path</strong></td><td>v2.0 to v2.1. Existing facility stock balances are not modified; balances are derived from transaction history on the next sync.</td><td>Initial build. No upgrade from a prior version of these workflows.</td></tr><tr><td><strong>New services</strong></td><td>Commodity Management web module for transaction tracking and warehouse stock overview.</td><td>Face ID Attendance (Proof of Work via Facial Recognition): biometric-verified, timestamped, GPS-tagged check-in.</td></tr><tr><td><strong>Major feature</strong></td><td>Bulk stock dispatch via console upload and facility-owned, persistent, real-time stock balances.</td><td>Role-based payment workflow (Bill Generator, Payment Editor, Payment Reviewer, Payment Approver) with bank payment advisory generation.</td></tr></tbody></table>

### What You Need to Do

**Stock**

* Console and campaign admins: Assign the Bulk Upload and Commodity Management module roles (National Warehouse Manager, State Warehouse Manager, Campaign Admin, role-configurable) before campaign start.
* Supervisors: No setup needed. The Stock KPI dashboard is available automatically once role permissions are assigned.
* Field teams: No action needed. Existing balances rebuild automatically from transaction history on first login or sync after upgrade.
* Last-mile Warehouse Managers and Distributors: Update the APK to the latest version to get QR-based offline issue and acceptance.

**Attendance, Payments and Facial Recognition**

* Campaign Managers: Create the cross-campaign worker registry and attendance registers via Console Excel upload before the campaign starts.
* Proximity Supervisors: Confirm register-approval access and assigned registers before the first billing period closes.
* Payment role holders (BG, PE, PR, PA): Confirm role assignment. Payment Editors should confirm payment-provider fields have been configured on the backend, since the Console UI for this is not yet available.
* Sites piloting Face ID Attendance: Plan face enrollment sessions (3 to 5 angle captures) before go-live. Note that iOS is not supported in this release.

## Highlights

* **Stock Management v2.1** — bulk stock dispatch via console upload, real-time facility-owned stock balances, and offline QR-based issue/acceptance at the last mile
* **Attendance, Payments & Facial Recognition** — new cross-campaign worker registry, signature and face-recognition-based attendance marking, and a role-based payment workflow through to bank disbursement

## New Services

Stock, Commodity Management Module (Web): A new web-based module provides a centralised view of all commodity transactions and warehouse stock across the supply chain hierarchy. It has two tabs: Transaction Overview (metric cards and the full transaction list) and Warehouse Stock Overview (drillable by boundary, with bulk template download and upload, and a Commodity Shipment modal for initiating transactions directly from the web).

Attendance and Facial Recognition, Face ID Attendance (Proof of Work via Facial Recognition): Validates face recognition as a mechanism for worker attendance check-in, replacing manual attendance with biometric-verified, timestamped, and GPS-tagged events for the pilot scope. Covers enrollment, login, re-verification, offline sync, and helper enrollment flows.

## New Features

**Stock**

* Bulk Stock Upload (via Console): Campaign managers can dispatch stock to multiple facilities in a single Excel or CSV upload instead of recording transactions one at a time, with pre-submission row-level validation and a Valid, Warning, or Error preview.
* Stock Data Sync and Persistence: Stock balances and transaction states persist across logout, device change, app restart, and intermittent connectivity. The facility, not the device, is the authoritative owner of stock.
* Stock KPI Dashboard: Real-time dashboard for supervisors with summary indicators, a drillable stock position table, and automatic risk and exception flagging. Loads within 5 seconds for up to 10,000 facilities.
* Available Stock Visibility on Mobile App: Field users see real-time, colour-coded stock balances on the app, updated immediately after every transaction.
* Manual Downsync from Home Screen: Users can trigger a data download on demand, without logging out and back in.
* Push Notifications for Stock Transactions: Automatic notifications for stock issued, received, discrepancies, return initiated, accepted, or rejected, and sync reminders.

**Attendance and Payments**

* Cross-Campaign Worker Registry: A central registry stores worker details across all campaigns using a unique User ID, instead of per-campaign records.
* Register Generation via Console: Attendance registers are generated at any chosen hierarchy level via Excel-based upload.
* User Creation and Mapping to Register: Users are created and mapped to registers via Console Excel upload, capturing payment-related user fields at creation time.
* Updating users before campaign begins: Campaign Managers can update user details and register mappings any time before the campaign starts.
* Attendance Register Approval: Proximity Supervisor reviews performance and attendance days, edits days per worker, and approves the register.
* Proximity Supervisor Updating Attendance Register: Add, remap, disable, or upload users into their own registers via Excel.
* Extension of Campaign Dates: Date extensions automatically flow into bill creation, carrying the prior rate card forward.
* Selecting Payment Provider and Bank Account: Campaign Manager selects payment providers and bank accounts per campaign from Console.
* Role-Wise Payment Workflow: Bill Generator, Payment Editor, Payment Reviewer, and Payment Approver, ending in a bank payment advisory.
* Email Notifications for Payment Roles: Payment Reviewer and Approver are emailed automatically when bills need attention.
* Signature Capture on APK: Workers sign on the Attendance Marker's device. The signature is compared against a stored baseline. Works fully offline.

**Facial Recognition**

* Face Profile Setup, Login, PIN Fallback, Helper Enrollment, Re-verification Ticker, Offline Sync, Supervisor Anomaly Review: Enrol with 3 to 5 angle captures and liveness detection. Morning face-scan login with timestamp, GPS, and confidence score. PIN or HCM-credential fallback after 3 failed attempts. Up to 2 helpers per device. Non-blocking re-verification ticker. Full offline operation with auto-sync. Supervisor visibility into missed re-verification windows.

## Changed

#### Stock

<table><thead><tr><th width="146.0390625">Function</th><th width="247.421875">Old version</th><th>This release</th></tr></thead><tbody><tr><td>Recording stock</td><td>One transaction at a time on mobile (receipt, issue, return, damage, loss, each its own form)</td><td>Same individual entry still exists, plus bulk dispatch to multiple facilities in one action via Console Excel upload</td></tr><tr><td>Where balances live</td><td>On the device, re-entered or rebuilt per session</td><td>On the server, per facility. Device downloads it on login or device change</td></tr><tr><td>Reconciliation</td><td>Transaction-based balance checked against a manual physical count, with an override reason if mismatched</td><td>Same transaction-based balance report, but no manual physical-count entry required</td></tr><tr><td>Viewing stock status</td><td>Static tabular reports, viewed one at a time, after the fact</td><td>Real-time KPI dashboard plus live color-coded balances and transaction status</td></tr><tr><td>Alerting</td><td>None</td><td>Push notifications for every stock event</td></tr><tr><td>Low-connectivity handling</td><td>Implicit, no manual refresh option</td><td>Explicit manual downsync button on the home screen</td></tr><tr><td>Admin and dispatch interface</td><td>Mobile app only</td><td>New web-based Commodity Management module</td></tr><tr><td>Last-mile stock acceptance (Distributor)</td><td>Required an internet connection to accept incoming stock</td><td>Distributor can now accept stock fully offline by scanning the incoming transaction's QR code via Scan Stock Receipt. Issuing stock has never required internet; this removes the internet requirement from the distributor's acceptance step too. The last-level Warehouse Manager's own acceptance step still requires internet and is unchanged.</td></tr></tbody></table>

#### Attendance, Payments & Facial Recognition

<table><thead><tr><th width="139.90234375">Function</th><th width="200.82421875">Before this release</th><th>This release</th></tr></thead><tbody><tr><td>Attendance marking</td><td>Manual attendance, no identity check</td><td>Signature capture verified against a stored baseline. Face ID Attendance available as a biometric alternative where piloted</td></tr><tr><td>Worker records</td><td>Per-campaign, re-entered each time</td><td>Central cross-campaign registry keyed on a unique User ID</td></tr><tr><td>Payment processing</td><td>No structured role workflow</td><td>Role-based workflow (BG, PE, PR, PA) with email notifications and a bank payment advisory as the disbursement path</td></tr></tbody></table>

## Related Docs

{% content-ref url="/pages/AP1Iyu3AgORLAGaLhtp9" %}
[Attendance & Payments User Manual](/health/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual.md)
{% endcontent-ref %}

{% content-ref url="/pages/MQ7FDifWN0OAQQefp1Fx" %}
[Facial Recognition](/health/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/health/release-notes/stock-attendance-payments-and-facial-recognition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.