Riseworth Fund treasury analysis dashboard displayed on screen

Features

Every function built around idle capital, measured and accounted for

Below is a complete breakdown of how Riseworth Fund identifies, allocates, and monitors uncommitted business funds — from first data sync to ongoing reporting.

Core capabilities

What Riseworth Fund actually does

Each feature below addresses a specific stage of treasury oversight — detection, allocation, monitoring, and reporting — so idle balances don't sit unexamined between finance cycles.

Idle balance detection

Connected accounts are scanned on a set schedule to flag cash sitting above operational thresholds you define. Detection logic runs continuously in the background rather than relying on manual quarterly reviews.

Threshold logic: min_operating_buffer

Predictive data analysis

Historical cash flow patterns are analysed to estimate near-term liquidity needs, reducing the chance that funds are allocated away from balances a business will need within the coming weeks.

Model input: rolling_90d_flow

Allocation routing

Once surplus is identified, it is routed according to the allocation profile selected by the business — ranging from conservative to growth-oriented — without requiring a manual transfer each time.

Profiles: conservative / balanced / growth

Configurable risk bands

Businesses set upper and lower bounds for how much exposure any single allocation can carry. These bands are enforced automatically and can be adjusted as circumstances change.

Bound type: exposure_ceiling

Reduced manual oversight

Once configured, the system requires periodic review rather than daily attention. Alerts are raised only when a decision genuinely needs a human, not for routine activity.

Review cadence: configurable

Reporting and audit trail

Every allocation decision is logged with the data inputs that informed it, giving finance teams a record they can reference during internal reviews or external audits.

Export format: CSV / PDF

In depth

How each stage works together

Switch between the tabs below for a closer look at detection, allocation, and monitoring — the three stages Riseworth Fund runs continuously once connected.

Detection Allocation Monitoring

Detection: finding capital that isn't working

Riseworth Fund connects to business accounts and continuously compares current balances against a configured operating buffer. Any balance held beyond what day-to-day operations require is flagged for review before an allocation decision is made.

Benefit: idle funds are identified on a rolling basis instead of being discovered during a manual end-of-quarter review.

Allocation: putting flagged capital to work

Once a surplus is confirmed, it is routed according to the allocation profile and risk bands the business has set. No allocation occurs outside the bounds configured by the account holder.

Benefit: allocation decisions follow a documented, repeatable process rather than ad hoc judgement calls.

Monitoring: keeping allocations accountable

Allocated positions are tracked against the original risk bands. If conditions move outside the configured tolerance, the business is notified and can choose to adjust the allocation profile.

Benefit: oversight continues after the initial allocation rather than stopping once funds are placed.

Riseworth Fund data analysis workspace used for treasury configuration

Configuration stays in your hands

Every feature described on this page operates within limits the business itself sets. Riseworth Fund does not make allocation decisions outside the risk bands and buffer thresholds configured by the account holder.

Settings can be revised at any time, and a full history of past decisions remains available for reference — so adjustments are informed rather than reactive.

Review configuration options

Built-in controls

Features that exist to limit exposure

Allocation tools are only useful if exposure stays within bounds a business can tolerate. These controls apply automatically across every allocation profile.

What's enforced automatically

Risk bands, operating buffers, and allocation ceilings are checked before any transfer is executed. If a configured limit would be breached, the transfer does not proceed until the business reviews it.

Operating bufferMinimum balance that is never flagged for allocation.
Exposure ceilingMaximum share of surplus that can be allocated at once.
Alert triggersNotification sent when an allocation nears a configured bound.