Advance payments
Take money before you ship, and never lose track of whose it is.
The problem
A customer pays 30% upfront. The money lands in the bank but sits as unexplained receipt for weeks. When the invoice is finally raised, nobody links the two, and the customer gets a past-due reminder for money they already paid.
The flow, step by step
1. Request the advance. From the sales order, Sundial creates a payment request for the agreed amount and emails it to the customer.
2. Record the receipt. When the money arrives, a payment entry is made against the sales order. It shows as an advance on the customer's account, not as revenue.
3. Fulfill the order. The order moves through delivery as normal. The advance stays visible on the order.
4. Invoice and allocate. When the sales invoice is created, the advance is pulled into it and allocated. The invoice shows the amount already received and the balance due.
5. Reconcile leftovers. Where advances and invoices were recorded separately, the payment reconciliation tool matches them in bulk.
6. Same for suppliers. Advances paid to suppliers work the same way against purchase orders and purchase invoices.
What the team sees
On every sales order: advance received, invoiced amount and balance. In the receivables report: advances shown against the customer, so the balance owed is the real one.
Finance can choose where advances sit in the ledger, so customer advances appear as a liability until they are earned.
In the Kestrel Workspace sample, a $63,000 advance by ACH on a $210,000 office build-out order is allocated to the final invoice, which then shows $147,000 due.
With AI (coming to Sundial)
On the Sundial roadmap: an agent that spots bank receipts matching an open payment request and proposes the payment entry for a person to confirm. Not shipped yet.

