Skip to main content
Collections campaigns are what we mean by automated collections: the automated sequence of emails that chases customers for unpaid invoices, on the schedule you set. This is what we mean whenever we say campaign on its own. Elsewhere in the industry this is called dunning. Same thing.
The workflow is the editor you build a collections campaign in, and the shape of the campaign itself. You’ll find the campaign listed under Collections but edit it in the workflow builder. Campaign and workflow refer to the same thing from different angles.
One email in a collections campaign, with its own timing, wording and recipients. A campaign is a series of steps.
A procedure Ari runs whenever a trigger fires, separate from collections campaigns, and used for everything else you want handled automatically.
Automations were previously called Ari tasks, and you’ll still see both names in places. They’re the same thing.
The pieces an automation is built from, arranged left to right.
Two meanings, depending on where you are. In an automation, the trigger is the event that starts a run, an invoice paid, an email received. In a collections campaign, the equivalent is a step’s overdue condition.
The AI agent inside LedgerUp. Ari works in the web app and in your shared Slack channel, and does the work you grant it permission to do.
The badge on an invoice where a customer has told you payment is on its way. Behind it sits a payment remittance record, which is what you create and remove.
The accounts receivable view that groups unpaid invoices by how long they’ve been outstanding.