Browse help topics

Invoices and operations

Create and track a deposit or progress payment request

Request funds against the correct project/invoice context and track funding without treating the request itself as payment. Follow the current customer-facing workflow and verify access, status, and resulting records before continuing.

6 min read Updated Accounting Admin, company admin

Before you begin

  • Audience: Accounting Admin, company admin.
  • Accounting/company-admin permission
  • project/customer
  • amount and intended allocation
  • customer contact if sending.

Project → Payments (#/sites/:id/payments) or Sales → Payments (#/payments); related invoice/estimate schedule

Create and track a deposit or progress payment request

  1. Open the workspace

    In JobBuddy, go to Project → Payments (#/sites/:id/payments) or Sales → Payments (#/payments); related invoice/estimate schedule.

  2. Confirm access and starting state

    Accounting/company-admin permission; project/customer; amount and intended allocation; customer contact if sending.

  3. Complete the main setup

    Define request type DEPOSIT versus DRAW, status lifecycle, draft/send/cancel, partial funding, link to estimate schedule or invoice, and why a funded request is evidence of applied receipts—not a second charge.

  4. Verify the result

    Request funds against the correct project/invoice context and track funding without treating the request itself as payment.

    Expected result: Request funds against the correct project/invoice context and track funding without treating the request itself as payment.

Troubleshooting

The page, control, or action is unavailable.

Confirm the required access and starting state: Accounting/company-admin permission; project/customer; amount and intended allocation; customer contact if sending.

The result is incomplete or unexpected.

Deposit and draw requests have their own DRAFT/SENT/PARTIALLY FUNDED/FUNDED/CANCELLED lifecycle; allocations, invoice linkage, and actual receipts determine funding.

The issue remains after checking the record.

Capture the exact visible error, record status, approximate time, and intended result. Give support only the minimum customer-safe evidence needed to trace the problem.

What happens next

  • Request funds against the correct project/invoice context and track funding without treating the request itself as payment.
  • Review the resulting record, status, notifications, and related history before continuing downstream work.
  • Use the related guide when the next action belongs to another JobBuddy workflow.
Open JobBuddy