Plan a $3,000 project in three payments
For example, agree 900 before work starts, 1,200 at a milestone and 900 on completion. Enter the amounts and dates that match the agreement. The schedule totals 3,000 and gives the client a clear payment plan.
Agree a payment schedule for a larger job, or let a client pay part of an invoice. Keep the amount received and the remaining balance on the same record, using a supported payment method.
What is inside
Choose split payments when you agree the amounts and dates in advance. Choose partial payments when the client can decide how much to pay, subject to the configured minimum and remaining balance. Check payment-method support before sending.
You set the schedule
For example, agree 900 before work starts, 1,200 at a milestone and 900 on completion. Enter the amounts and dates that match the agreement. The schedule totals 3,000 and gives the client a clear payment plan.
Use dates the client has agreed to. A due date records when payment is expected; it does not authorize an automatic debit or guarantee collection. Review the payment settings and reminders before sending.
How reminders workThe client sets the amount
For a supported partial-payment flow, set the smallest amount the client can submit. This gives you a way to request a minimum contribution while leaving the rest of the invoice balance open.
For example, a client may pay 800 toward a 2,000 invoice when the configured minimum is 500. After the successful payment is recorded, 1,200 remains due. Confirm the exact options in the client preview.
The invoice does the bookkeeping
Recorded payments reduce the invoice balance. Check the payment status before treating an amount as collected, especially when a provider processes payments asynchronously.
Before sending, preview the document and check the amounts, dates and available payment methods. Use the configured reminder workflow to follow up on outstanding amounts.
What the client seesAlso included
Use the invoice, customer record and payment history together when following up or checking a balance.
Keep the original amount, recorded payments and remaining balance together.
Availability depends on the provider, currency and invoice settings. A connected gateway does not automatically support every split or partial flow.
Give clients a place to review their documents and available payment options.
Convert an approved estimate into an invoice, then configure the supported payment terms.
Review invoices and payment history when reconciling what is paid and what remains due.
Compare a reusable payment link with the payment route on an existing invoice.
Questions
Split payments use agreed amounts and dates. Partial payments allow an amount toward the balance, subject to the configured minimum and the payment flow available on the invoice.
Yes, where the invoice and selected payment method support the requested collection. Agree what the deposit covers and how the rest will be paid, then preview the invoice before sending it.
A schedule alone does not authorize an automatic charge. Automatic collection requires a separately supported and configured payment arrangement with the necessary customer authorization.
No. Support varies by provider and payment flow. Check the options available for the invoice currency and settings, and resolve any payment-capability warning before sending.
Once the payment is successfully recorded against the invoice, its outstanding balance is reduced by that amount. Check pending provider payments separately from completed payments.
No. Instalments settle an existing invoice over time. Recurring invoices create invoices on a repeating schedule. Choose the workflow that matches the agreement with the client.
Create the invoice, choose supported payment settings and check the client preview before you send it.