You're probably closer to a covenant breach than you think

Most commodity traders track their lending facilities in spreadsheets that are updated weekly. Their covenants are checked quarterly. The gap between those two frequencies is where breaches happen.

The spreadsheet is always a step behind

A revolving credit facility isn't a static instrument. Every drawdown reduces available headroom. Every repayment restores it. Every new trade creates a potential drawdown. Every delayed shipment extends an existing one. The utilisation changes daily — sometimes hourly — and your spreadsheet was last updated on Monday.

Here's what that looks like in practice. You have a $15M revolving facility with Bank A, with a utilisation covenant at 85%. On Monday, your spreadsheet showed 72% utilisation. By Thursday, you've drawn down $1.2M against a cocoa shipment, $0.8M against a coffee contract, and a $0.5M repayment that was due Wednesday has been delayed because the buyer's bank is slow on the LC. Your actual utilisation is now 83%. You're two drawdowns away from breaching the covenant, and nobody in the building knows it.

What a real facility dashboard looks like

finPhlo maintains a live view of every lending facility, updated with each drawdown, repayment, and trade event. Not a summary that someone compiles — a calculated position derived from actual transactions.

Bank C is in breach. Bank A is two drawdowns away. If your trading desk is about to book a new shipment that requires a $1M drawdown, which facility should it go against? The answer is obvious when you can see it. It's invisible when you can't.

The facility lifecycle

Every lending facility follows a lifecycle. Most systems handle origination and closing. The hard part is everything in between — the daily operational management that determines whether the facility works for your business or constrains it.

Origination

Capture the facility terms: limit, currency, tenor, interest basis (fixed or floating + benchmark + margin), repayment method and frequency, drawdown minimums and maximums, covenant thresholds, and expiry date. finPhlo stores the full term sheet — not a summary, the actual parameters that govern the facility's operation.

Drawdown management

Every utilisation request is linked to a specific trade — a purchase order, a shipment, or an invoice. The system validates the drawdown against the facility's available headroom and covenant thresholds before the request is submitted. If the drawdown would push utilisation above 80% on a facility with an 85% covenant, the system warns. If it would breach, it blocks.

finPhlo supports all standard drawdown types:

• Pre-shipment — linked to purchase orders, released on shipment confirmation
• Post-shipment — linked to sales orders, released on buyer payment
• Receivables — linked to invoices, released on collection
• Inventory — linked to warehouse receipts, mark-to-market against commodity prices
• Gap funding — short-term, released on next scheduled inflow

Interest and fee tracking

Interest accrues daily on each drawdown. For floating-rate facilities, the benchmark rate (SOFR, EURIBOR, SONIA) is updated automatically, and the all-in cost (benchmark + margin) is calculated per drawdown. This matters more than it sounds — a $2M drawdown at SOFR + 2.5% costs differently depending on when SOFR last reset, and most spreadsheets get this wrong by using a stale rate.

Facility fees — commitment fees on undrawn amounts, arrangement fees, annual review fees — are tracked separately and accrued against the right accounting periods. Your finance team doesn't need to calculate these manually at month-end.

Repayment scheduling

Repayments can be bullet (single payment at maturity), amortising (equal instalments), or linked to trade settlement (repay when the buyer pays). finPhlo generates the repayment schedule from the facility terms and tracks actual versus scheduled payments. If a repayment is missed or late, the system flags it — because a late repayment on one facility might trigger a cross-default on another.

Covenant monitoring that actually prevents breaches

Checking covenants quarterly is like checking your speed once an hour — you'll find out you're speeding eventually, but not before the ticket. finPhlo monitors continuously, against live utilisation data, with configurable warning thresholds.

The typical setup:

• Green zone (0-75% of covenant threshold) — normal operations, no alerts
• Amber zone (75-90% of threshold) — daily monitoring, treasury team notified
• Red zone (90-100% of threshold) — immediate alert to CFO, new drawdowns require explicit approval
• Breach (>100%) — system blocks new drawdowns on the facility, generates notification to both treasury and senior management

The value isn't in detecting a breach after it happens — every system can do that. The value is in the amber alert three days before the breach, which gives you time to accelerate a repayment, redirect a drawdown to a different facility, or negotiate a temporary limit increase with the bank.

Multi-bank visibility

Commodity traders rarely have a single lending relationship. Three banks is typical, five is not unusual. Each bank sees their own facility. Nobody sees the aggregate picture except your CFO — and until now, that picture was assembled in a spreadsheet.

finPhlo provides the consolidated view:

• Total facility limits across all banks and currencies
• Aggregate utilisation — how much of your total borrowing capacity is deployed
• Available headroom by currency — where can you draw next, and in which currency
• Facility concentration — are you over-reliant on one bank? What happens if they reduce your limit?
• Maturity profile — when do facilities expire? How much refinancing risk do you carry?

This consolidated view is what your bank asks for when you're negotiating a new facility. If you can produce it in real time from a system rather than spending three days assembling it from email threads and spreadsheets, the conversation starts differently. Banks lend to companies they trust. A proper facility management system is a trust signal.

When the facility renewal conversation starts

Facility renewals are won or lost on data. Your bank wants to see: utilisation history (have you used the facility efficiently?), covenant compliance track record (any breaches?), collateral coverage (is the security adequate?), and business trajectory (are you growing or contracting?).

finPhlo maintains this data over the full life of the facility. When renewal discussions begin — typically 3-6 months before expiry — you can produce the complete history in minutes. More importantly, you can present it from a system that demonstrates active management, not from a spreadsheet that was hastily assembled for the meeting.

The result, consistently: better terms on renewal. Lower margins, higher limits, fewer reporting requirements. The bank sees a borrower who manages their facilities professionally, and prices accordingly.