Features

Financial approval workflow for income and expense requests

Create income and expense requests, control who can approve or reject them, record decisions, and connect approved one-time requests to bookkeeping.

What this feature brings together

Lyniti Financial Approvals gives teams a focused request-and-decision workflow inside finance workspace. Requesters add operational context, authorized members approve or reject, and one-time approved items can continue into bookkeeping without suggesting a configurable multi-stage approval chain.

Best for

  • Teams that need a clear approval step before income or expense activity reaches bookkeeping.
  • Requests that need operation name, category, amount, description, project context, and recurring settings.
  • Workspace roles where approval authority must remain separate from general finance access.

Capability overview

CapabilityDetails
Income and expense request formsCreate request with operation, category, amount, type, description, project context, and optional recurring frequency.
Permission-controlled decisionsApproval and rejection use finance approval permission so decision access can be assigned through workspace roles.
Pending, approved, and declined statusRequest views show current status, requester context, decision maker, decision date, and rejection reason when provided.
One-time bookkeeping handoffApproved non-recurring requests create bookkeeping transaction context with pending-review status, keeping final accounting review separate.
Recurring request visibilityApproved recurring requests remain visible in finance cash-flow context instead of becoming a one-time bookkeeping entry.

Frequently asked questions

Who can approve a financial request?

Approval or rejection requires finance approval permission in workspace role.

What happens after a one-time request is approved?

Approved non-recurring request creates bookkeeping transaction context with pending-review status for later accounting review.

Does Lyniti support multi-step approval chains?

No multi-step or configurable approval-chain capability is claimed. Current workflow supports one permission-controlled approve or reject decision.

Related features

Solutions for