Skip to main content

Set up a payment schedule

Many suppliers don't take one payment 30 days after the invoice. They want a deposit when you place the order and the rest when the goods ship or arrive. A payment schedule on a payment term writes that deal down as milestones. SKU.io then works out what's due and when on every purchase order that uses the term: deposits become vendor deposits, the balance is forecast against the supplier's bill, and the whole plan shows on the cash-flow schedule.

Before you begin​

  • Payment schedules are for purchasing only. Turning one on sets the term's Applies to to Purchasing, and it stops appearing on customers and sales orders.
  • You need permission to manage payment terms.
  • For plain terms such as Net 30, you don't need a schedule. See Set up payment terms.

Build the schedule​

This example sets up 40% deposit on approval, 60% as each shipment leaves.

  1. Go to Settings → General → Payment Terms.

  2. Click Create Payment Term, or open an existing purchasing term.

  3. Enter a Name, such as 40% Deposit, 60% on Shipment, and a Description.

  4. Under Invoice Payment Terms, set the Due Date Type and Net Days for the supplier's bill as usual.

  5. In the Payment Schedule section, click Add Milestone.

  6. Describe the first milestone:

    • Label: Deposit.
    • Percentage: 40. Switch the % toggle to $ for a fixed amount instead.
    • Trigger Event: On PO Approval, with Offset Days 0 for payment the same day.
    • Settlement Type: Vendor Deposit, so this milestone raises a vendor deposit.

    Milestone 1, a 40% vendor deposit due when the purchase order is approved

  7. Click Add Milestone again, and describe the balance:

    • Label: Balance on shipment.
    • Percentage: 60.
    • Trigger Event: On Each Shipment (prorated), so each shipment releases its share, dated by the Date Basis you choose (here, Dispatched).
    • Settlement Type: Final Goods Invoice. This milestone is paid through the supplier's bill, and no vendor deposit is created.
  8. Check the panel at the bottom. What this schedule does works the plan through on a sample purchase order, and Schedule Total must reach 100%.

    The balance milestone, a worked example on a $10,000 PO, and a 100% schedule total

  9. Click Save. The Payment Schedule column on the terms list sums the schedule up in one line.

If the save button stays disabled, hover over it: the reason points at the Schedule Total banner, which says what's missing.

Choosing triggers​

The list of triggers depends on the Settlement Type.

Trigger EventOffered onThe milestone falls due…
On PO ApprovalVendor depositsWhen the purchase order is approved.
On First Shipment (once) / On First Receipt (once)Vendor depositsOnce, when the first shipment leaves or the first goods arrive. Later shipments and receipts release nothing more.
On Each Shipment (prorated) / On Each Receipt (prorated)BothOnce per shipment, for that shipment's share, from its dispatch or receipt.
On Full Shipment / On Full ReceiptBothWhen everything has shipped, or everything has arrived.
On Logistics MilestoneBothWhen a tracking date you choose, such as Customs Cleared, is recorded.
On Bill DateFinal goods invoicesOn each supplier bill's own date. Each bill is due its bill date plus the Offset Days, so it doesn't need a linked shipment.
ManualBothOnly when someone marks it due. Offset Days doesn't apply.

The Payment Schedule column on the terms list uses the same names, for example "40% Vendor Deposit on PO Approval".

The trigger list on a Final Goods Invoice milestone, including On Bill Date

Offset Days pushes the due date back from the trigger, for example 30 days after receipt.

On a Vendor Deposit milestone, the per-shipment triggers, On Each Shipment (prorated) and On Each Receipt (prorated), split the deposit so each shipment releases its share. On a Final Goods Invoice milestone, they date each bill from the shipment it's linked to. SKU.io links a bill to its shipment for you when their lines match, and you can link one yourself (see Link a shipment to a bill). Until a bill has a shipment, its due date is projected from the order's estimates. When your supplier dates payment from the invoice itself, On Bill Date avoids that wait: a supplier on "net 30 from invoice" is a Final Goods Invoice milestone on On Bill Date with Offset Days 30.

Other options on a milestone​

  • Legal ownership of goods transfers at this milestone — tick this on the one milestone where the goods become yours. From that point, the paid deposit balance counts as goods you've bought rather than money held by the supplier.
  • More than one Final Goods Invoice milestone — the supplier's bill is split into installments, each with its own due date.

Change a schedule later​

Every saved change to the schedule creates a new revision. A Revision chip at the top of the Payment Schedule section shows the current number; click it to see the Schedule revision history, with who changed it and when.

The schedule revision history listing revisions 1 to 3

Vendor deposits remember the revision they were created under, so changing a term doesn't rewrite deposits you've already recorded. If purchase orders already have deposits under the old schedule, SKU.io shows you the effect on each one before it saves, and asks for a Reason for change that goes into the revision history.

Next steps​

Last verified: