Building a Bank Financing Pack a Credit Analyst Can't Poke Holes In

The financing pack request usually lands with a deadline and a list: three years of historical statements, a 12-to-24-month projection, the covenant calculations if there’s an existing facility, and supporting schedules for anything unusual on the balance sheet. None of that is hard to produce once. What’s hard is producing it in a way that survives the credit analyst’s second read, the one where they ask why the projection’s working capital assumption doesn’t match what the historicals show.

That question is where most homemade packs fall apart. The historicals came from the accounting system, the projection came from a separate model someone built in Excel eighteen months ago, and the covenant calc lives in a third file that a different person maintains. Each piece is defensible on its own. Together, they don’t quite agree, and a bank’s credit team is specifically trained to notice.

One payload, not three files stitched together

A Rexfin financing pack renders from the same underlying model as everything else you produce: the reconciled statements, the projection, and any covenant calculations sit on one payload rather than three documents maintained separately. Ask for the PDF narrative and a supporting XLSX workbook for the same period, and the figures match, because both came from the same source rather than from two people reformatting the same numbers by hand and hoping nothing slipped.

That matters specifically for banks because a financing pack rarely gets read once. It gets requested, questioned, revised, and resent, often across several rounds before a facility closes or renews. If the historicals and the projection are structurally the same model, updating one figure updates every place it appears, the certificate, the pack, the workbook, instead of requiring someone to remember every location that number touches.

The export can’t leave broken

Before any pack, PDF, or XLSX leaves the system, it has to clear an export gate: the same check that verifies whether the model actually ties out. If a statement doesn’t balance, or a figure in the pack can’t be traced to its source, the export is blocked rather than produced with a caveat attached. That is a deliberately uncomfortable design choice: a bank financing pack is not a document you want to caveat your way around. It either reconciles or it doesn’t go out.

The pack also carries a content hash and an audit stamp, which is what makes a shared document tamper-evident. If a number gets edited after the pack is sent, the hash no longer matches, and anyone comparing versions can tell. For a document that a lender’s credit committee may hold onto for months while a facility is negotiated, that matters more than it sounds like it should.

Answering “where did this come from” without a delay

The follow-up question (how was the leverage ratio calculated, what’s behind the working capital assumption) is the actual test of a financing pack. If your covenant reporting already runs off one canonical calculation traced to source figures, that same trace is what answers the analyst’s question in the meeting instead of after a scramble back at the office. Any commentary attached to the pack is held to the same standard: the AI can describe what a number means, but it can’t cite a figure that hasn’t cleared verification, so a sentence about margin improvement only makes it into the pack if the number behind it is actually verified.

Where this sits alongside everything else

A financing pack usually isn’t a one-off request. It tends to recur every time a facility renews, and it often draws on the same underlying model as your regular board reporting cycle. If you’re assembling something similar for an equity raise rather than a loan, the mechanics are close enough to what’s covered in fundraising preparation and the due diligence data room that it’s worth reading alongside this one.

None of this decides which covenants a bank will ask for or how aggressive your projection assumptions should be: that’s still a negotiation between you and the lender. What a gated, single-source pack buys you is the part that shouldn’t be a negotiation at all: whether the numbers in front of the credit committee actually hold together. For more on how finance teams use Rexfin for recurring reporting obligations, see the finance team use cases hub.