B
Brian Rand
Current behavior:
When a customer accepts an estimate over the configured deposit threshold, Homeworks correctly requires the customer to pay a deposit.
However, once the deposit is collected, the payment is added to the customer's account as a general credit. It is not tied to the estimate the customer accepted or to the jobs created from that estimate.
This creates several problems:
1.) The deposit can accidentally be applied to an unrelated invoice, such as recurring mowing.
2.) The deposit can remain unused on the account when the project is completed.
3.) If the full project amount is charged at completion without manually accounting for the deposit, the customer can effectively be charged 150% of the project price.
4.) Owners and office teams have to manually track what the credit was originally intended for.
5.) We've had to create additional workflows around deposits simply to prevent the payment from being lost or misapplied.
Requested behavior
When a customer pays a deposit while accepting an estimate, that payment should remain linked to that specific estimate/project.
Ideally:
  1. The deposit is clearly shown on the estimate as Deposit Paid.
  2. The deposit cannot automatically be applied to unrelated invoices or services.
  3. When the estimate converts into jobs/invoices, the deposit follows those jobs.
  4. When the final project invoice is created, the deposit is automatically deducted from the remaining balance.
Example
Customer accepts a $2,000 project and pays a required $1,000 deposit.
Instead of placing $1,000 into the customer's general credit balance, Homeworks should associate that $1,000 with the $2,000 estimate.
When the project is completed, the system should recognize:
Project Total: $2,000
Deposit Paid: $1,000
Remaining Balance: $1,000
The customer should then be charged only the remaining $1,000.
Why this matters
The current deposit feature successfully collects the money, but it doesn't preserve what that money was collected for. Tying the deposit to the estimate would remove several manual steps, reduce billing errors, and make the deposit workflow much safer for both the business and the customer.
Always Giving 150%,
Brian Rand