Peak Automations / Invoice reminders
The receipt has arrived.And then it sits there.
Receipts arrive in Peak Finance by e-mail, as an upload or by hand. After that someone has to check, approve and pay. You describe in one sentence who is up when. Peak turns it into an automation with the triggers “receipt received”, “receipt approved” and “receipt paid”, creates tasks with a due date and lets people know. It is switched on only after a passed test run.
Put the goal into words. Add perspectives and timing right below.
Try it with a sample receipt. Nothing is created.
Sample receipt / fictional data
Three moments, three steps.
- Receipt received
- Task “check receipt” for accounting, due in three days.
- Receipt approved
- Task “transfer the payment” for the person who pays.
- Receipt paid
- A note in the Inbox to owners and admins.
Your receipt path in three answers
Who is up when?
Fill in the example with a made-up flow. You see which details Peak needs for the automation. Nothing is saved, connected or switched on.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A reminder that lands.
Draft · not yet put together
- The trigger
- Still open
- The people in charge
- Still open
- The close
- Still open
From a sentence to a running reminder
Describe. Test. Only then let it run.
The order makes sure no reminder goes to the wrong person and nothing is created twice.
- 01Describe
Say the receipt path in one sentence.
Receipt receivedTask “check receipt” for accounting, due in three days.
Typed or dictated. If something is unclear, such as who pays, Peak asks instead of guessing.
Sentence → typed automation - 02Test
Run it with a sample receipt.
Receipt approvedTask “transfer the payment” for the person who pays.
The test run shows which task would be created for whom, without creating anything. Only then can the version be switched on.
Test run → passed - 03Run
Every run can be traced.
Receipt paidA note in the Inbox to owners and admins.
The history says in plain language what happened and why a run stopped. Every change becomes a new version.
Sample artifact → run log
The next proof is the product
Describe your receipt path in Peak.
In Peak Automations you say the flow in one sentence, check it in the simple view and the flow view, and switch it on after the test run. Tasks land in Peak Task, notes in the Inbox.
Start with Peak AutomationsPeak Automations / Your next step
Every receipt has a next person.
Try the example with the receipt that has been waiting the longest.
See the receipt example
No receipt gets left lying around.
A note in the Inbox to owners and admins.
Frequently asked questions
Which triggers exist for receipts?
Receipt received, receipt approved, receipt rejected and receipt paid, each from Peak Finance.
Does Peak remind customers about overdue invoices?
No. Overdue invoices are not a trigger today, and Peak sends no dunning letters on its own. An e-mail through Gmail waits for confirmation.
Does Peak pay the receipts?
No. Peak creates tasks and lets people know; a person pays through your bank.