> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cadanapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Reimbursement

> Create a reimbursement for a worker in your business. The reimbursement is created in a pending status and must be reviewed (via [`POST /v1/reimbursements/{reimbursementId}/review`](#tag/reimbursements/post/v1/reimbursements/{reimbursementId}/review)) before it is paid out. Each entry may optionally reference one or more `fileIds` of previously uploaded files to attach proof (e.g. receipts).



## OpenAPI

````yaml /openapi/workforce-management.yaml post /v1/reimbursements
openapi: 3.0.0
info:
  description: APIs for interacting with Cadana Payroll Platform
  version: 1.0.0
  title: Business Workforce Management
  termsOfService: https://cadanapay.com/terms-and-conditions
  contact:
    email: api@cadanapay.com
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
servers:
  - url: https://api.cadanapay.com
    description: Prod Server
  - url: https://dev-api.cadanapay.com
    description: Dev Server
security:
  - Authorization: []
tags:
  - name: Custom Auth
    description: APIs for interacting with Custom Authentication
  - name: Persons
    description: APIs for interacting with the HR module
  - name: Instant Pay
    description: APIs for interacting with Instant Pay functionality
  - name: Users
    description: APIs for interacting with employee/contractor Cadana accounts
  - name: Files
    description: APIs for interacting with file uploads
  - name: Payrolls
    description: APIs for interacting with Payroll
  - name: Platform
    description: Platform APIs for interacting with businesses
  - name: Businesses
    description: APIs for interacting with Business
  - name: Contracts
    description: APIs for interacting with contracts
  - name: Sandbox
    description: APIs for relevant sandbox simulations
  - name: Invoices
    description: APIs for interacting with invoices
  - name: Reimbursements
    description: APIs for interacting with reimbursements
  - name: Entities
    description: >-
      APIs for managing legal sub-entities (subsidiaries, branches) under a
      parent business
paths:
  /v1/reimbursements:
    post:
      tags:
        - Reimbursements
      summary: Create Reimbursement
      description: >-
        Create a reimbursement for a worker in your business. The reimbursement
        is created in a pending status and must be reviewed (via [`POST
        /v1/reimbursements/{reimbursementId}/review`](#tag/reimbursements/post/v1/reimbursements/{reimbursementId}/review))
        before it is paid out. Each entry may optionally reference one or more
        `fileIds` of previously uploaded files to attach proof (e.g. receipts).
      operationId: createReimbursement
      parameters:
        - $ref: '#/components/parameters/XMultiTenantKey'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateReimbursementRequest'
      responses:
        '200':
          description: The created reimbursement's id
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: string
                    format: uuid
              example:
                id: d1e2f3a4-5678-9012-cdef-345678901234
        '400':
          $ref: '#/components/responses/BadRequestError'
        5XX:
          $ref: '#/components/responses/InternalError'
      security:
        - Authorization: []
components:
  parameters:
    XMultiTenantKey:
      name: X-MultiTenantKey
      in: header
      required: false
      schema:
        type: string
      description: >-
        Required when using a Platform API token. The tenant key identifying
        which business to operate on.
  schemas:
    CreateReimbursementRequest:
      description: >-
        Create reimbursement request payload. Identify the worker with exactly
        one of `userId` or `personId`.
      type: object
      required:
        - title
        - currency
        - destinationCurrency
        - entries
      properties:
        userId:
          type: string
          format: uuid
          description: >-
            The worker the reimbursement is for. Provide either `userId` or
            `personId`.
          example: a3b4c5d6-e7f8-9012-abcd-ef3456789012
        personId:
          type: string
          format: uuid
          description: >-
            The worker the reimbursement is for, identified by their personId
            within the tenant. Provide either `userId` or `personId`.
          example: c5d6e7f8-9012-3456-cdef-789012345678
        title:
          type: string
          description: A short title describing the reimbursement.
          example: Client dinner
        currency:
          type: string
          description: The currency the entry amounts are denominated in.
          example: USD
        destinationCurrency:
          type: string
          description: The currency the worker is reimbursed in.
          example: USD
        entries:
          type: array
          description: The individual line items that make up the reimbursement.
          items:
            $ref: '#/components/schemas/ReimbursementEntryRequest'
    ReimbursementEntryRequest:
      description: A single reimbursement line item
      type: object
      required:
        - description
        - amount
      properties:
        description:
          type: string
          example: Dinner with client
        amount:
          type: object
          properties:
            currency:
              type: string
              example: USD
            value:
              type: string
              example: '1000.00'
        category:
          type: string
          example: Meals
        date:
          type: string
          description: The date the expense was incurred (YYYY-MM-DD).
          example: '2025-11-28'
        fileIds:
          type: array
          description: >-
            IDs of previously uploaded files to attach as proof for this entry
            (e.g. receipts). Optional.
          items:
            type: string
          example:
            - f1e2d3c4-5678-9012-cdef-345678901234
    BadRequestError:
      description: Bad input provided by client
      allOf:
        - $ref: '#/components/schemas/Error'
        - type: object
          properties:
            params:
              description: A map for meta data around the error that occurred
              type: object
      example:
        code: invalid_request_body
        message: The request body provided is not valid
        params:
          field: Value is invalid.
    InternalError:
      description: Internal server error
      allOf:
        - $ref: '#/components/schemas/Error'
      example:
        code: internal_error
        message: An unexpected error occurred. Please try again later.
    Error:
      type: object
      properties:
        code:
          description: A machine parsable error code
          type: string
          enum:
            - invalid_request_body
            - resource_not_found
            - forbidden
            - internal_error
        message:
          description: A human readable message describing the error
          type: string
  responses:
    BadRequestError:
      description: Bad input provided by client
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/BadRequestError'
    InternalError:
      description: Internal error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/InternalError'
  securitySchemes:
    Authorization:
      type: http
      scheme: bearer
      bearerFormat: API_SECRET_KEY

````