Your runway model isn't wrong.
Its inputs are stale.
The inputs to a runway number,
kept current.
A runway model has the same handful of inputs no matter who builds it. We read each one where it already lives, on the cadence it already changes, and keep it reconciled — so the projection is never run on month-old numbers. Each input is its own blueprint; this page is how they feed the model.
Four feeds in, one sheet out.
Each upstream blueprint owns its inputs. They reconcile into the canonical sheet you already model on — same formulas, same layout, fresh numbers. The destination is yours; the feeds are ours.
Multi-Entity Treasury
Cash position across every bank, entity, currency — polled hourly into the canonical row.
Owned AR Runtime
Receivables aging from Zoho, bucketed by days-late, refreshed through the day.
Wire-to-Invoice Reconciliation
Every wire matched to its open invoice the moment it lands — collected MTD is fact, not guess.
Monthly Expense Audit
Bills, AP pipeline, and expense lines synced four times a day, classified and audited.
Google Sheets
The runway sheet itself — your formulas, your assumptions, our inputs.
Monday-morning pull. Midweek surprise.
We run this on ourselves.
HKR's own runway sheet runs on these four feeds. Three entities, three banks, three currencies. Treasury polled hourly. Zoho synced four times a day. Wire-to-invoice matched as it lands. AP+expense audited monthly. The arithmetic in our sheet is ours; the inputs underneath it are the same code that ships to yours.
The Monday-morning runway number is never the stale part. When a big bill posts midweek, the sheet moves the minute it posts — not the minute someone next opens it.
This blueprint fits
when…
You run across multiple entities, currencies, and banks, and the runway model is only ever as fresh as the last manual data pull.
You already have a runway sheet or an FP&A tool — it's the inputs that lag, not the math.
Someone on the team spends mornings copy-pasting balances and AR aging into a model before anyone can trust the number.
A late customer payment or a large bill can move the picture, and today you find out weeks after it happened.
Single entity, single currency, single bank. The payoff scales with complexity.
Your ERP already gives you a real-time consolidated cash, AR, and AP view you trust.
Questions you're
probably asking.
Correct, and that's deliberate. We keep the inputs — cash, AR, AP, expenses — live and reconciled. The curve is computed by your model or your FP&A tool, on assumptions you own. We make sure it's never run on stale numbers. If you want the forward math itself, that's a forecasting platform's job, and live inputs are the cleanest thing you can feed it.
Same numbers, same arithmetic. The difference is who pulls the inputs. Today someone does it by hand, monthly, and the model goes stale the day after. Here the balances refresh hourly, Zoho syncs four times a day, and overdue AR and incoming wires surface as they happen. The model reads live actuals instead of a month-old snapshot.
Those are forecasting platforms — they model scenarios and render board packs off a snapshot you give them. This is the runtime that keeps the snapshot fresh. A larger finance org runs both: the platform on top, the live-inputs layer underneath. If your model lags because nobody refreshes the inputs, that's exactly where this lands.
Not in this feed. Workforce cost lives in your HRIS, and folding it into the cash layer would blur two systems. Headcount-cost modeling is its own blueprint — link it to your runway model separately if you want it in the curve.
Both. Balances are kept per bank-entity-currency and rolled into a consolidated view — three entities in our own setup, however many you run. Your model can read either: per-entity for operational decisions, consolidated for the board number.
Overdue receivables and incoming customer wires post to the channel your finance team already watches, the moment they happen — not on a weekly digest. The balance sheet itself is the always-current reference; the alerts are for the few things that need a human's eyes today.
About two weeks. Week one: wire each bank feed and your Zoho or equivalent GL into the canonical sheet. Week two: reconcile against your last close so the live numbers match what you already trust. After that the feeds run on their own rhythm.
See it run.
A 30-minute walkthrough on HKR's own live inputs — balances across three banks, Zoho synced through the day, the overdue sweep that fires when an invoice ages past due. The same code that ships to yours.