Skip to content

Expense Policies — Proposed Guide

Planned API — Reference Only

Expense Policies: Policies define permitted spending and required evidence for a particular population and period. An expense should reference the policy…

Overview

Policies define permitted spending and required evidence for a particular population and period. An expense should reference the policy version used for its evaluation.

Key concepts

Separate eligibility, monetary limits and evidence requirements. A policy can apply by category, entity or employee group.

Implementation considerations

Avoid evaluating an old expense against a newly edited policy without an explicit re-evaluation decision.

Proposed API behavior

GET /v1/expense-policies is an illustrative design for this topic. Path and field names may change before implementation. Access would require an authorized organization context and operation-specific permission; no public API or authorization grant is available here.

No additional request fields are illustrated; this is not a finalized contract.

Static example requests

Proposed, non-executing request examples
# Proposed request text only; this reserved host is not a live API.
curl -X GET 'https://api.remizen.example/v1/expense-policies' \
  -H 'Authorization: Bearer YOUR_API_KEY'

Fictional response example

200 (proposed example)Static response fixture

Fictional documentation data only. No request was sent, record created, review performed, payment initiated or provider connection activated.

JSON
{
  "data": [
    {
      "policy_id": "policy_example_123",
      "version": 1,
      "effective_on": "2026-01-15",
      "category_id": "category_example_123",
      "id": "expense_policies_example_123",
      "organization_id": "org_example_123"
    }
  ],
  "pagination": {
    "has_more": false,
    "next_cursor": null
  },
  "meta": {
    "request_id": "req_example_123",
    "reference_only": true
  }
}

Illustrative error case

Review this failure case in context: Avoid evaluating an old expense against a newly edited policy without an explicit re-evaluation decision.

422 (illustrative; final error contracts are undecided)Proposed error fixture

Synthetic diagnostic example. Human-readable messages must not be used as stable programmatic contracts.

JSON
{
  "error": {
    "code": "validation_error",
    "message": "The proposed expense policies operation requires review of its input or authorization.",
    "request_id": "req_example_123"
  }
}

Proposed data types

Illustrative field dictionary
NameTypeDescription
policy_idstringStable fictional policy reference; not a secret and not evidence that a resource exists.
versionintegerIllustrative resource revision for detecting stale updates; no live concurrency contract is published.
effective_onstring (date)Synthetic calendar date in YYYY-MM-DD form; period inclusivity must be defined by the future contract.
category_idstringStable fictional category reference; not a secret and not evidence that a resource exists.