Module

Automations and Workflows

The month does not wait for somebody to remember. Fifteen jobs run on their own — statements, late fees, renewals, closings, report packages — and the checklists your company runs are yours to define.

Book a walkthrough All features

What runs on its own

Statements on a schedule

Set the day and who gets them. A late notice schedule can assess late fees first, so the notice that goes out already reflects them.

Late fees

Assessed by collections step or ahead of a late notice, on your rules rather than whenever somebody gets to it.

Collections

Steps by days past due. Each step can send a document, assess a fee, or open a task for a person — and stops when the balance clears.

Month-end close

The close runs to your calendar, with the checks it depends on made first rather than assumed.

Report packages, sent

The monthly package owners expect, assembled and delivered without anybody exporting a thing.

Renewals

Expirations found before they surprise you, with the offer raised and tracked to an answer.

Move-outs

The deposit accounting and the steps around a departure, on the clock your state gives you.

Preventive maintenance

A due schedule creates the work order, assigned, rather than a reminder somebody has to notice.

Percentage rent

Chases the sales figures a retail tenant owes, then bills the rent those figures produce — or proposes it for review.

Insurance and compliance

Tenant policies and vendor certificates watched for expiry, so a lapse is a notice rather than a discovery.

Approval digests

A single mail listing what is waiting on someone, instead of one per bill.

Lease reading in batches

A folder of leases read through overnight, with a list to review in the morning.

Workflows you build yourself

Your checklists, not ours

Name a workflow, give it ordered steps, and choose the page its Start button appears on. Two ship for onboarding; the rest are yours.

Against a real record

A run is about something — a lease, a property, a vendor, an owner — and shows on that record as well as in the list across all of them.

Steps become tasks

Each step lands in somebody's queue with an owner, so a checklist is work assigned rather than a document nobody opens.

One queue per person

Tasks belong to whoever is signed in, fed by every workflow and automation at once, filtered to one person when a hundred is too many.

Nothing bills itself by surprise

Review before charge, by default

Where an automation produces money owed, proposing it for a person to approve is the default and billing outright is the opt-in.

Every run leaves a record

What ran, when, and what it did — so a month nobody watched is still a month you can account for.

Off is a setting

Each automation is switched on per company, with its own timing and its own thresholds. None of it is mandatory.

A month nobody looks at is a month of rent nobody bills

Every one of these was a report somebody had to open and act on. The report still exists — what changed is that the work no longer waits for a person to remember it is due.

Related

Accounts Receivable Community Associations Reporting