> 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/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual.md). # Attendance & Payments User Manual Step-by-step guide for Campaign Managers, Proximity Supervisors, Bill Generators, Payment Editors, Payment Reviewers, and Payment Approvers ## Overview HCM Attendance and Payments is the module that tracks field worker attendance during a campaign and turns approved attendance into worker payments. It covers the full chain, from setting up who is tracked and where, through daily attendance capture on the APK, supervisor approval, and role-based bill review through to bank payment advisory generation. This manual is organised by role. Each section walks through exactly what a person in that role sees on screen and what they need to do. Read only the section relevant to your role. You do not need to read the entire document. Each role section follows this structure: what this role does, where to log in, a step-by-step flow matching the demo video, screenshots taken from the product, and tips or error notes for common mistakes. ## Key Features * Cross-campaign worker registry: one record per worker (name, ID, signature, photo, payee details) reused across campaigns instead of re-entered each time * Excel-based attendance register creation and worker mapping via HCM Console, at any chosen boundary level * Proximity Supervisor review and approval of attendance registers, with per-worker day-count edits before approval * Signature-based attendance verification on the APK, checking the captured signature against a stored baseline * Role-based payment workflow: Bill Generator, Payment Editor, Payment Reviewer, Payment Approver * Excel-based bulk editing of bills for wage rates, allowances, and attendance corrections * Automated email notifications to Payment Reviewers and Approvers when bills need their attention * Bank payment advisory generation for final disbursement ## User Roles The rest of this manual is organised by role. Find your role below and go directly to that section.

User Role	Scope of Action
All roles	Overview: how attendance and payments connect
All roles	Role reference
Campaign Manager	Setting up attendance: creating registers, mapping workers
Proximity Supervisor	Approving attendance registers
Campaign Supervisor (Bill Generator)	Generating bills
Payment Editor	Verifying worker payment details
Payment Reviewer	Reviewing and editing bills
Payment Approver	Approving and downloading payment advisory
All roles	Excel template field reference
All roles	Access URLs and credentials

#### Overview: how attendance and payments connect Attendance and payments are two connected modules in HCM. Attendance is captured in the field. Payments flow out of what is approved in attendance. Understanding the handoff between the two is important before using either module.

Attendance module	Payments module
Campaign Manager sets up registers before the campaign. Team Supervisors mark attendance daily on the APK, capturing signatures. Proximity Supervisor reviews, edits, and approves each register at the end of the billing period.	Campaign Supervisor, acting as Bill Generator, selects approved registers and generates a bill. Payment Editor verifies and corrects worker payee details. Payment Reviewer edits wage rates and bill data, then sends for approval. Payment Approver approves and downloads the bank payment advisory for disbursement.

Attendance module

Payments module

Campaign Manager sets up registers before the campaign.

Team Supervisors mark attendance daily on the APK, capturing signatures.

Proximity Supervisor reviews, edits, and approves each register at the end of the billing period.

Campaign Supervisor, acting as Bill Generator, selects approved registers and generates a bill.

Payment Editor verifies and corrects worker payee details.

Payment Reviewer edits wage rates and bill data, then sends for approval.

Payment Approver approves and downloads the bank payment advisory for disbursement.

{% hint style="info" %} **Key dependency:** A bill cannot be generated until the Proximity Supervisor has approved the attendance register for that billing period. If a register is still in Pending or Approved state, the Bill Generator will see it in their inbox but will not be able to generate a bill until it is approved. {% endhint %} #### Role reference

Role	Scope of action	Role description
Campaign Manager	Attendance	Creates registers and maps workers from HCM Console before the campaign begins.
Proximity Supervisor	Attendance	Reviews and approves attendance registers at the end of each billing period. Can also add, remap, or disable workers in registers.
Campaign Supervisor (Bill Generator, BG)	Payments	Generates the payment bill by selecting approved attendance registers. This is the same person who manages the campaign.
Payment Editor (PE)	Payments	Verifies worker payee details (payee name, bank account, bank code, beneficiary code) and individually approves each worker's record.
Payment Reviewer (PR)	Payments	Reviews the fully verified bill, edits wage rates via Excel if needed, adds comments, and sends the bill for final approval.
Payment Approver (PA)	Payments	Approves the reviewed bill and downloads the bank payment advisory Excel for disbursement.

--- # 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/access/public-health-product-suite/health-campaign-management-hcm/attendance-and-payments-user-manual.md?ask=&goal= ``` `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.