---
title: "Switch a member to manual allowance management"
method: POST
path: "/members/{member_id}/manual-rule"
tags: ["Allowance Management"]
---

# Switch a member to manual allowance management

`POST /members/{member_id}/manual-rule`

Takes the member off automatic accrual for this allowance type from `valid_from` on. Nothing accrues afterwards, and the balance is whatever you set through adjustments. Pass the member's active assignment as `current_assignment_id` and it is ended on `valid_from` in the same transaction; without it, an assignment overlapping `valid_from` makes the call fail.

## Path parameters

- `member_id` string, uuid, required

## Request body

- object
  - `allowance_type_id` string, uuid, required
  - `valid_from` string, required — First day the member is managed manually (inclusive), in YYYY-MM-DD format.
  - `valid_until` string, nullable — Last day of manual management (inclusive), in YYYY-MM-DD format, or null for open-ended.
  - `current_assignment_id` integer, nullable — The assignment that is active today, from GET /members/{member_id}/rule-assignments. Send null when the member has none.
  - `reason` string, required — Why the member is managed manually — stored in the rule audit log.

## Response `200`

Successful response

- object
  - `success` boolean, required

## Other responses

- `400` — Invalid input data
- `401` — Authorization not provided
- `403` — Insufficient access
- `500` — Internal server error

---

[API](https://skmtc.net/absentify/apis/absentify-crud-api.md) · [All operations](https://skmtc.net/absentify/apis/absentify-crud-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/absentify/absentify-crud-api/revisions/ef777d51e6f2/schema)