Vendor timing is a cash decision

Discipline is paying on purpose. Habit is paying early because the queue feels cleaner.

Founders often treat vendor payments as a weekly chore. Pay what is due, clear the queue, feel responsible. Sometimes that is correct. Sometimes it is a silent transfer of float from your company to someone else’s, made at the exact week your payroll trough is tightest.

Vendor timing is a cash decision. It belongs next to hiring and collections in the weekly forecast conversation, not in a separate “AP housework” bucket that never sees the thirteen-week view. When AP and the forecast live in different rooms, early payment becomes invisible until Friday’s bank balance delivers the news.

A week that looked fine until it did not

Consider a common pattern. Cash looks fine on Monday. A cluster of annual SaaS renewals and a contractor batch clear on Wednesday. Payroll hits Thursday. A large customer slips to next week. By Friday the account is tighter than anyone admitted in the staff meeting, and nobody can say which payment was optional.

The failure mode is not malice. It is separation: AP clears tickets, finance updates a forecast later, leadership hears “cash is fine” from last week’s opening balance. Timing decisions need the same object as the trough—otherwise early payment is invisible until it hurts. The fix is not slower AP. The fix is putting the batch next to the trough before anyone hits approve.

Another pattern: a relationship-driven prepay that felt cheap in isolation. The vendor was helpful during an outage; the team wants to show goodwill. Goodwill can be rational. Pretending goodwill was free float is not. Record the reason so the next cycle does not inherit a fake policy called “we always pay early for this vendor.”

A simple decision framework

1. Map the trough. Before approving early payment, look at the lowest cash point in the next four weeks. If the payment deepens that trough below a comfort line, it is not free discipline.

2. Price the discount. A two percent discount for paying fifteen days early is a financing decision. Compare it to your cost of capital and to trough risk. Run it like a decision, not a reflex.

3. Separate committed from discretionary. Rent and payroll are not the same species as a prepay that could wait. Label the batch so leadership sees the difference in one glance.

4. Name the owner. Someone with authority says yes or no. “We always pay early” is not an owner. If the person who wants the discount is also the only reviewer, you do not have a control.

5. Record the reason. If you prepay to save a relationship, say that. Do not pretend it was free. Reasons teach the next cycle; silence teaches folklore.

• Auto-paying everything the day the invoice arrives.
• Letting department heads negotiate terms that finance never sees.
• Ignoring concentration risk when one vendor can accelerate without notice.
• Using early payment as a substitute for fixing broken AP routing.
• Clearing the inbox on Friday afternoon without opening the trough view.
• Treating net-thirty as optional while calling yourself disciplined.

Discounts, FX, and renewals

Annual prepay discounts deserve a spreadsheet line, not a gut feel. Compare the discount to your cost of capital and to the trough risk. Sometimes the discount wins. Sometimes surviving the trough wins. Both can be rational; only one is honest for a given week. Put the comparison next to the payment request so the owner decides with both numbers visible.

International wires and FX timing add another layer. Paying early in a rising currency can be an accidental market bet. If nobody owns FX policy, do not invent one mid-payment-run. Hold wires that can wait until the weekly cash ritual has seen them—especially when the amount is material relative to the trough. Multi-entity companies should also confirm which entity’s cash is being moved; paying from the wrong stack can create a local trough even when consolidated cash looks fine.

Procurement tools that auto-approve renewals without finance visibility recreate the early-pay problem at software speed. Put renewals above a threshold on the forecast’s decision list. A renewal that “just happened” is still a cash decision that someone failed to surface. Calendar the renewals the same way you calendar payroll.

Collections and payables on the same page

Customer payment terms and vendor payment terms should be discussed together occasionally. Extending DSO while shortening DPO is a cash strategy, not two unrelated chores. Leadership should see both on the same page. If sales is stretching invoice due dates while AP is racing to pay early, the trough will tell on you before the board deck does.

Tarient puts vendor timing inside the weekly cash ritual so the trough is visible before the batch goes out. See cash forecasting and the cash forecast playbook. For a usable weekly view, read a forecast you can use on Tuesday.

1. Monday: trough refreshed from bank actuals and known payroll.
2. Before the AP batch: discretionary and early-pay items scored against the trough.
3. Owner decision recorded; habit payments without a reason get challenged.
4. Friday: confirm what cleared and what moved the trough versus plan.

Paying early is not always discipline. Paying on purpose—after the trough has been named—is. The cultural shift is small and powerful: ask “what does this do to the trough?” before “does this clear my inbox?” That question belongs in the same room as hiring and collections, every week, until early payment stops being an invisible habit and becomes a decision with a name.