Getting paid isn't usually the problem. Getting paid on time, in the right amounts, at the right stages of the job - that's where installation businesses lose control as they grow.
When you're doing five installs a month, someone in the office remembers to send the deposit invoice after the proposal is accepted and chases payment before the install date. At 20 or 30 installs, that person is juggling too many jobs to keep track. Deposit invoices go out late. Install dates pass without payment being confirmed. Cash flow suffers because the system depends on someone remembering to do something at the right time.
Payaca's automations and payment schedules fix this by triggering the right action at the right stage, every time.
What this covers
How to set up automatic deposit invoices when a proposal is accepted
Configuring payment schedules across project stages
Using pipeline automations to enforce payment before work starts
Connecting to Stripe for instant payment collection
Before automating payments, your pipeline needs to reflect how your jobs actually move through your business. A typical clean tech installer pipeline looks something like this:
Lead - enquiry received
Survey booked - site visit scheduled
Quoted - proposal sent to customer
Accepted - customer signed the proposal
Deposit paid - payment confirmed
Scheduled - install date booked
Installing - work in progress
Commissioning - DNO/MCS paperwork
Complete - job done, final invoice paid
The key stages for payment automation are Accepted and Deposit paid. The transition between these two is where most businesses lose time.
In Payaca, go to Pipeline Settings and set up an automation on the Accepted stage. When a project enters this stage (meaning the customer has signed the proposal), trigger an automatic deposit invoice.
You configure the deposit amount in your proposal template - typically a percentage of the total. When the automation fires, Payaca generates the invoice and sends it to the customer with a payment link. No one in your office needs to do anything.
If you're connected to Stripe, the customer clicks the link, pays by card or direct debit, and the payment is reconciled automatically. The project moves to the next stage.
Here's where it gets powerful. Set a pipeline guard on the stage after "Deposit paid" - in this example, "Scheduled". The guard prevents a project from moving into the scheduling stage until the deposit invoice is marked as paid.
This means your scheduling team physically can't book an install date for a job where the deposit hasn't been collected. No more turning up to a site and discovering the customer hasn't paid. No more awkward conversations on the day of the install.
For larger installations - especially heat pumps and multi-technology projects - you might want to split payments across multiple stages. A common structure:
30% deposit on acceptance
50% on installation day (before work starts)
20% on completion (after commissioning)
Payment schedules let you define these splits at the proposal level. Each stage triggers its own invoice at the right time, with its own payment link.
Payment schedules work with change proposals too. If a customer adds optional items after accepting the original proposal, the schedule adjusts to reflect the new total.
Deposit sent - when the deposit invoice is created
Deposit paid - when payment is confirmed
Final invoice sent - when the completion invoice goes out
These tags give your office team a dashboard-level view of where every project sits financially. No one needs to open individual projects to check payment status - they can filter by tag and see every job that's waiting on a deposit at a glance.
A customer accepts your solar proposal on Monday morning. Within seconds, they receive a deposit invoice with a Stripe payment link. They pay that afternoon. The project automatically moves to the scheduling stage, and your install coordinator books them in for the following week.
On install day, the second payment invoice is sent before the team arrives on site. On completion, the final invoice goes out with the commissioning confirmation.
Your office team didn't send a single manual invoice. They didn't chase a single payment. The cash came in at the right time because the system enforced it.
If you're already using Payaca's pipeline, this is a configuration exercise, not a rebuild. Start with your most common project type, set up the automations on the acceptance stage, add the stage guard, and connect Stripe if you haven't already. Most businesses have this running within an hour.
If you're not sure which stages to use or how to structure your payment splits, ask Dave in the help chat. Dave can walk you through the setup for your specific workflow.
Ready to streamline your operations?
See how Payaca helps clean tech installers save time and grow their business.
Vague payment terms are why installers wait 60 days for money they earned in a day. Here's how to set terms that hold up, what you can charge for late payment, and how to make getting paid the default.
Taking a deposit at the kitchen table is normal. Doing it without handling the customer's cancellation rights is how installers end up unable to enforce payment. Here's what to get right.
Connect your AI assistant straight to your Payaca account and ask it to do real work: pull stuck jobs, bulk-update projects, draft follow-ups, build reports. Here's why we built it and the practical things install teams use it for.