Payment plans list with active status and last update

Payment Plans

Build clear installment journeys connected to units, contracts, due dates, collections, customer communication, and exceptions.

Why the installment matters

Create payment plan form and plan details

An installment journey stays on one plan with its unit, its contract, and its due dates. Collection and customer communication stay there, and an exception stays with that plan.

Connected view

Keep the unit, the contract, and the due dates on one installment plan.

Right context

Show the active status and the last update before the next installment is due.

Workflow data

Read the collection already recorded to see what the plan still needs.

Shared pipelines

Hand an exception on with the due date and the customer communication still attached.

Exceptions

Keep an exception on the plan, so it can be read back to the due date and the installment it changed.

Related Features

Each plan keeps its unit and its due dates together, so collection is not opened on a different contract.

Create payment plan form and plan details

Confirm the unit, the contract, and the due dates before the plan is saved.

Payment plans list with active status and last update

Why Amarnex?

Amarnex

Limits

The plan holds the unit, the contract, the due dates, the collection, and the exception. The invoice stays outside it.

Handoffs

A due installment goes into collection, and an exception returns with the customer communication still attached.

Confirm first

Confirm the unit, the contract, and the due dates before the plan is created.

Limits

The plan holds the unit, the contract, the due dates, the collection, and the exception. The invoice stays outside it.

Handoffs

A due installment goes into collection, and an exception returns with the customer communication still attached.

Confirm first

Confirm the unit, the contract, and the due dates before the plan is created.