Viridem icon

Viridem

Interact's with Viridem

Actions77

Expenses → Lock Expense

AI-generated

Overview

This node operation locks one or multiple expenses in the Viridem system. It is useful in scenarios where you want to prevent further modifications to expense records after they have been reviewed or approved. For example, a finance team might use this operation to lock expenses at the end of a reporting period to ensure data integrity.

Use Case Examples

  1. Lock a single expense by providing its ID and company ID.
  2. Lock multiple expenses by providing an array of expense IDs and the company ID.

Properties

Name Meaning
Company Id The identifier of the company to which the expense(s) belong. This is required to specify the context for the expense locking operation.
Id The ID of a single expense to lock. Used when locking one expense at a time.
Ids A JSON array of expense IDs to lock. Used when locking multiple expenses in a batch.
Request Options Additional options to control the request behavior, such as batching, SSL certificate validation, proxy settings, and timeout duration.

Output

JSON

  • id - The ID of the locked expense(s).
  • status - The status of the lock operation, indicating success or failure.

Dependencies

  • Requires an API key credential for Viridem OAuth2 API authentication.

Troubleshooting

  • Ensure the company ID and expense IDs are valid and exist in the Viridem system to avoid errors.
  • If batching is enabled, verify batch size and interval settings to prevent request throttling issues.
  • Check proxy and SSL settings if network connectivity issues occur.
  • Timeout errors may occur if the server is slow to respond; increase the timeout setting if needed.

Discussion