Chuyển đến nội dung
Peak Atlas

Peak Automations / Payment reminder template

Due means: someone knows.
In time, not afterwards.

Discount missed, supplier waiting, thanks forgotten: payments rarely fail on money, mostly on remembering. This template hooks into the receipts in Peak Finance: an invoice arrives, is approved or is paid, and the right person gets the next step.

For which occasion?

Change the trigger. The preview next to it reacts instantly.

Edit all texts and details ↗Test the automation locally ↗
Local demo with sample data
Automation · previewPreview reacts instantly
Peak AutomationsLocal demo with sample data

When an invoice from Example Ltd arrives in Peak Finance

read supplier, due date and invoice number with an AI step and tell the approver in the Inbox what to check.

Use sample data only.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Edit your draft in detailText, details & next action
01

Your sample automation

Make it yours.

Additional details

Name, e-mail and occasion are always part of the trigger as sample data in this demo.

JSON file for your local draft. Not an import into Peak Automations.

01 / Anatomy of the automation

Receipt, task,
due date.

The trigger is an event on the receipt. The steps turn it into a task with a due date or a note in the Inbox. Anything that goes outside waits for confirmation.

01 / The contextYour current draft

A beginning
that fits the flow.

Peak Automations · local preview
When an invoice from Example Ltd arrives in Peak Finance

read supplier, due date and invoice number with an AI step and tell the approver in the Inbox what to check.

Context → Details → Next action

The trigger says when the automation starts.

02 / The details
4visible details
01Tên02E-mail03Request04Company
03 / The next actionText preview

And then?
A clear next action.

Test run with a sample invoice. The extracted details are a suggestion the approver checks.

Test the flow in the preview directly above.

02 / Three moments

Arrival, approval,
paid.

Choose the moment in an invoice's life where things most often get stuck for you.

Another example replaces the current demo draft.

  • 01 / Invoice receivedSelected

    Read first, then approve.

    An AI step reads the key details.

    New incoming invoice

    „When an invoice from Example Ltd arrives in Peak Finance“

    4 details · Company
  • 02 / Invoice approvedSample draft

    Approved, so schedule it.

    The approval becomes a payment task.

    After approval

    „When an incoming invoice is approved“

    4 details · Timing
  • 03 / Invoice paidSample draft

    Paid and ticked off.

    For outgoing invoices that are paid.

    Close an incoming payment

    „When the invoice to Nordwind Studio GmbH (example) is marked as paid“

    4 details · Company

03 / Move on deliberately

No receipt without a next step.

In Peak Automations you describe the flow in one sentence or pick the template. Peak checks connections and permissions, shows the flow as boxes and arrows, and you start a test run. Only then do you activate it. Every change becomes a new version, and the run history explains in plain language what happened.

Your context, your details and your next action — as one connected draft.

Please fill in the draft texts before you take them along.

Stays in this browser. Nothing is sent, nothing is saved automatically.

Frequently asked questions

Does Peak dun customers automatically?

No. Peak does not chase anyone on its own. A reminder to a customer is a Gmail step with confirmation before every send.

Where do the invoices come from?

From the receipts in Peak Finance. The template reacts when an invoice arrives, is approved or is paid.

When does the template actually run?

Only once you have taken it over in Peak Automations, tested it with sample data and then activated it. No automation can be activated without a passed test of the current version.

More in Peak Automations