Payment terms on a supplier

Every supplier page has a Customer payment policy panel, and it works the same way as the one on a product.

As the panel puts it: when set, sourced bookings against this supplier inherit these terms instead of the operator default. Leave it inheriting to fall back to the deployment-wide policy.

Where this sits in the chain

Voyant looks for payment terms in order, taking the first it finds.

1. The booking itself, if somebody set an override there.
2. The product, if it has its own policy.
3. The category.
4. The supplier, which is this panel.
5. The operator default, which applies to everything else.

So setting terms here affects everything sourced from that supplier without touching each product.

When to use it

When one supplier genuinely trades on different terms. A venue that wants fifty percent up front while your usual terms are twenty-five is a good reason.

If your terms are the same everywhere, leave every supplier inheriting and set the rule once at the operator level.

The fields

The same set as on a product: Deposit kind, the deposit figure, Deposit window, Balance due and Minimum notice, all in days.

See Set a customer payment policy for what each one does and how to read the preview.

While the panel is inheriting it says so, and shows no preview at that layer. That is expected rather than a fault.