Skip to main content

Manage Zero-Accrual Policies With Manually Added Balances and Custom Expiration

  • Apr 27, 2026 11:19 AM UTC
  • 0 replies
  • 61 views
  • Translate All

Use this approach to grant leave manually while still controlling when the balance expires—even outside the policy cycle.

 

Some companies need a policy that doesn’t accrue leave automatically but still allows HR to grant balances when needed. In these cases, you can use the policy as a framework to manage expiration, even if the entitlement itself is fully manual.

 

This works well when you want full control over when balances are granted and how long they remain available.

 

When this setup makes sense

-The policy should not grant any automatic entitlement

-HR adds balances only when employees become eligible

-The granted balance should expire after a limited time

-Expiration timing shouldn’t depend on the standard policy cycle

 

Common examples include one-off entitlements, temporary leave balances, or special cases that shouldn’t follow a recurring accrual model.

 

How it works in Bob

The policy is configured with a 0 allowance, so no balance is accrued automatically.

 

When needed:

-Assign the employee to the policy

-Manually add the balance

 

From that point, the policy settings control how long the balance remains available.

 

To support expiration that doesn’t rely on annual logic, structure the policy with:

-A short cycle (for example, monthly)

-A defined carryover limit

-A defined carryover expiration period

 

This allows the balance to expire after a set time, even though it wasn’t generated by the policy itself.

 

Recommended setup

-Allowance entitlement: 0

-Cycle: Monthly

-Carryover limit: Set to the maximum balance you plan to grant

-Carryover expiration: Set to how long the balance should remain valid (in months)

 

Then:

-Add employees to the policy

-Grant balances manually

-Let the carryover expiration handle validity

 

Why this works

This setup separates the key needs:

-No automatic accrual

-Full control over manual balance grants

-A built-in way to enforce expiration

 

It’s a practical workaround when you need more flexibility than a standard accrual policy allows.

 

Important limitation

Bob doesn’t currently support expiration based on the exact date a manual balance is granted.

 

This means:

-Expiration is still tied to policy logic (like cycle and carryover rules)

-It won’t track each grant independently

 

So while this setup helps approximate custom expiration, it isn’t fully dynamic per grant.

 

Best fit

This approach is most useful when you need:

-No automatic accrals

-Manual balance control

-A defined (but approximate) expiration window

-A structured alternative to fully manual tracking