Keep invoice follow-ups moving.

Start with the evidence

Connect the accounts that contain the relevant invoices, files and correspondence. Ask Ocur to identify the unpaid invoices from those sources and show the evidence for each one. Include the period, customer or folder when that helps narrow the task.

Make the source clear. An email saying a payment is expected is not the same as evidence that it arrived. The financial ledgers described on the homepage tie records to real activity; review the underlying information before approving a reminder.

Draft a reminder with context

Ask Ocur to consider the existing customer conversation before drafting a message. Specify the tone, the invoice details to include and whether a colleague must review it. A useful first task ends with drafts you can inspect.

Example: “Check these invoices against the customer threads. Draft a polite reminder for each unpaid item, include the invoice reference, and wait for my approval before sending.”

Make follow-up a recurring job

Once the first run works, a paid plan can run the job on a schedule. Define the connected sources, timing, approval boundary and where you want the report. Ocur tracks commitments and keeps the work on the record.

Set the rules for exceptions too: a disputed invoice, a promised payment date or an uncertain status can come back to you for a decision. Payment recovery depends on the customer and the evidence; a reminder is a workflow, not a guaranteed collection result.

Try it on a small set

Start with a few invoices and review the drafts. Expand the scope after you are comfortable with the connected sources and the results. See supported tools, plan details and where your data goes.