Skip to content
FactorFox

Borrowing base

Availability is a number somebody has to defend.

Written for the person who signs the certificate. In an asset based lending shop that is the portfolio manager or the field examiner. In a factoring company it is whoever answers the bank when the rediscount line is drawn. Both are being asked the same question: what is actually there, net of everything, and prove it.

FactorFox computes availability inside the system that holds the collateral, so the number and the evidence are the same object.

Borrowing base · as of 14:00

Compressing
Gross assigned receivables
4,182,600
Less ineligible, aged and cross age
(391,240)
Less concentration excess, one obligor
(214,900)
Eligible collateral
3,576,460
At advance rate, per policy
3,040,991
Less dilution and dispute reserves
(186,300)
Less outstanding advances
(2,611,400)
Net availability
243,291

Days to zero: 6, on this client’s own funding pattern and collection velocity. Driven by the concentration excess, which appeared four days ago.

Policy v7 · sealed certificate BB-4471 · every line opens into its evidence

Illustration of the availability stack. The layer order, the movement attribution, the policy version stamp and the sealed certificate reference are the platform’s own. Every figure shown comes from a seeded demonstration book.

Why this exists

The spreadsheet is not the problem. The fact that only one person can read it is.

Every operation of any size has a workbook that produces the borrowing base. It usually works. It fails at the two moments that matter: when the person who built it is away, and when somebody asks why the number moved.

The base is rebuilt every morning by hand, from an export that is already an hour old, and it goes out with one person's initials on it.
Availability is computed from the live collateral records, and every figure on the certificate opens into the invoices, credits, cash and reserve movements that produced it.
An invoice drops out of eligibility for a reason nobody writes down, and three weeks later nobody can reconstruct why availability fell.
Each ineligible carries the rule that removed it, the date the rule applied and the value it took out. The reason is part of the record rather than part of somebody's memory.
The advance rate in the agreement, the advance rate in the policy memo and the advance rate in the formula are three different numbers.
One versioned eligibility policy per client. The certificate names the version it was computed under, so changing a rule produces a new certificate rather than quietly restating the last one.
Nobody notices availability compressing until a client asks for money and the answer is no, which is a phone call rather than a plan.
Net availability is projected forward from that client's own funding pattern and collection velocity. Days to zero reaches the briefing before the funding request reaches the desk.

The computation

Five layers, applied in an order you can argue with.

Gross collateral. Everything assigned, at face, as of a fixed date and time. Not a rolling number that moves while you read it. A borrowing base with no as of stamp is an opinion.

Ineligibles. The rules that remove collateral from the pool, applied in policy order, each one recording what it removed and why. This is where most of the argument in asset based lending actually happens, so it is the layer that carries the most evidence.

Advance rates. Applied per collateral class and per client, not as one house rate. Where a client’s dilution has moved against it, the policy can step the rate down on a schedule instead of leaving it at the number somebody agreed to two years ago.

Reserves. Dilution, disputes, priority payables such as unpaid payroll taxes and landlord claims, and any specific block an officer has set. A reserve set by a person records the person, the reason and the date, and it appears on the certificate as a named line rather than as a silent haircut.

Net availability. Eligible collateral at advance, less reserves, less what is already outstanding. Then the part that changes behaviour: the same number projected forward, with days to zero attached to it.

Order matters

Cross age before concentration produces a different answer from concentration before cross age, and both are defensible. What is not defensible is a system that will not tell you which one it did.

The policy fixes the order, the certificate records it, and a field examiner can follow the same sequence by hand and land on the same figure.

Ineligibles

The categories that decide the number

These are the rules the platform applies and records. Which of them you switch on, and at what thresholds, is your credit policy and nobody else's.

Ineligibility categories and how each is applied
CategoryHow it is applied
Aged past dueInvoices beyond the client's aging cutoff, measured from invoice date or due date as the policy states, with the cutoff recorded on the certificate.
Cross ageWhen a stated percentage of an obligor's balance is past due, the whole obligor balance leaves the pool. The trigger percentage and the obligor that tripped it are both named.
ConcentrationBalance above the obligor ceiling is removed, expressed as a percentage of eligible collateral. The excess is attributed to the obligor rather than appearing as an unexplained fall.
Contras and offsetsWhere the obligor is also a supplier to the client, the offsetting payable is netted. This one is usually found by an examiner rather than by a system, which is the argument for holding it in the system.
Foreign obligorsIneligible unless covered by credit insurance or a letter of credit, with the covering instrument attached as evidence and its expiry watched.
Government receivablesIneligible unless an assignment of claims is on file. The document is the evidence and its absence is stated rather than assumed.
Affiliate and intercompanyRemoved on the party relationship, not on a name match, because name matching is how affiliates get missed.
Disputed and credit memoAn open dispute case removes the disputed amount while it is open. Closing the case returns it, and both movements are dated.
Retainage and progress billingHeld out until the retention condition is satisfied. Construction books live or die on this line.
Extended datingTerms beyond the policy maximum are removed or advanced at a reduced rate, as the policy states.
UnverifiedWhere the policy requires verification before an invoice counts, an unverified invoice is not eligible. Verification status comes from the verification record itself, not from a checkbox somebody ticked.
Unapplied cashCash received but not yet applied reduces the pool rather than sitting outside it, so availability never counts money twice.

Certificate production

From as of date to a sealed document

The certificate is not a report that gets regenerated. It is a record that gets sealed.

  1. Fix

    The as of moment is set

    Collateral, cash, credits and reserves are taken as they stood at that instant. Everything downstream refers to that stamp, which is what makes two people computing the same base able to disagree productively.

  2. Apply

    Policy runs in its stated order

    Ineligibles in sequence, advance rates by class, reserves last. Each step writes what it did, so the certificate carries its own working rather than just its conclusion.

  3. Reconcile

    Movement against the last certificate is explained

    Availability rarely moves for one reason. The movement is decomposed into new collateral, collections, newly ineligible balances, reserve changes and advances taken, and the pieces add up to the difference.

  4. Review

    A person accepts or refuses it

    Where the policy requires it, a second officer counter reviews. The counter review refuses outright if any underlying fact has changed since the run, because approving a stale computation is worse than approving nothing.

  5. Seal

    The document becomes immutable

    Sealed packets cannot be mutated. A database trigger refuses the write. A correction is a restatement that stands beside the original and names what changed, which is the only version of a correction an examiner will accept without a conversation.

  6. Deliver

    It goes where it has to go

    To the client, to the file, or up to your own lender under your rediscount reporting obligation. Outbound delivery passes the same wall as every other channel, so nothing reaches a real counterparty from a test environment.

Collateral performance

The base tells you what you can lend. These tell you whether you should.

A borrowing base is a photograph. Collateral performance is the film, and it is where the trouble shows up first.

Dilution movement

Credits, short pays and deductions as a share of what was billed, tracked against the client's own history rather than a portfolio average. Rising dilution is the earliest honest signal that an advance rate is wrong.

Payment velocity by obligor

How this obligor actually pays, across the network, not what its terms say. An obligor slowing from thirty eight days to sixty two moves every client who sells to it.

Concentration change

Including exposure gathering under one debtor name across several clients, which is the concentration that never appears on any single client's certificate.

Turn and aging drift

The pool getting older before it gets smaller. Aging drift precedes cross age triggers, which means it precedes an availability fall you could have called a fortnight earlier.

Credit limit utilisation

How much of an approved obligor limit is in use, and how fast it filled. A limit that goes from thirty per cent to full in a week is a question, not a milestone.

Availability compression

Net availability falling on a trend, with days to zero. This is the signal that turns a funding refusal into a scheduled conversation.

For factors with a rediscount line

Your bank runs a borrowing base on you. It helps to run the same one first.

A factor drawing on a bank line is a borrower whose collateral is other people’s receivables. The bank applies eligibility rules to your book that look a great deal like the rules you apply to your clients: aging cutoffs, obligor concentration, cross age, ineligible client classes, reserves against dilution, and a certificate on a stated cycle. The difference is that when your bank disagrees with your number, you do not get to explain it in the margin.

Running the same computation continuously at the top of your own house changes two things. You know before your lender does, which means an ineligible concentration is something you manage rather than something you receive a letter about. And you arrive at the field exam with dated evidence instead of a workbook, which shortens the exam and changes what the examiner concludes about your controls.

For a factor without a line yet, the same machinery builds the track record that gets one. FactorFox ships a default covenant pack modelled on how bank rediscount facilities are actually written, so you can operate against realistic tests from the first month. Every surface states plainly that these are FactorFox covenants and not anyone’s contract. When you sign a real facility, the clauses you actually agreed to replace them, and the agreement clause is quoted on the covenant as its evidence.

Where a covenant needs data FactorFox does not hold, such as controlled collection percentage on a bank feed that is not wired, it says it is awaiting a live source and names the source. It does not report zero. A zero is a fact and a blank is a different fact, and confusing the two in front of a lender is expensive.

Straight answers

What a portfolio manager asks first

Can we run our own eligibility rules, or are we buying someone else's opinion?

Your own. Eligibility is a policy object per client: aging cutoffs, cross age percentage, concentration ceilings, obligor level overrides, the treatment of contras, foreign obligors, government receivables, retainage and dating terms. The policy is versioned, and a certificate names the version it was computed under, so a rule change produces a new certificate rather than silently restating an old one.

How does this handle a client whose collateral is inventory as well as receivables?

Each collateral class carries its own eligibility policy and its own advance rate, and availability is the sum of the classes less reserves and less what is already funded. Inventory eligibility depends on data the platform can only hold if you give it to it. Where a class depends on a source that is not wired, the line says it is awaiting a live source and names the source rather than reporting zero, because a zero and a blank are different facts.

What does days to zero actually measure?

It projects net availability forward from the client's own funding pattern and its own collection velocity, not from an industry average. It is a projection and the platform labels it as one. The value is in the ordering: it tells a portfolio manager which four clients out of two hundred will be asking for money they do not have, while there is still a week to do something about it.

Is the certificate something we can hand to a bank?

That is what it is built for. It is fixed to an as of date, sealed, and its figures carry evidence references into the underlying invoices, credits, cash and reserve movements. A sealed packet cannot be mutated, because a database trigger refuses the write. Correcting a certificate creates a restatement that stands beside the original rather than replacing it.

We are a factor, not an asset based lender. Does a borrowing base apply to us?

It applies twice. Client by client it is the discipline that decides what you can safely advance against a schedule. At the top of the house it is what your rediscount lender applies to you, using your clients' receivables as its collateral. Factors who only ever computed the first one tend to discover the second during a field exam.

What happens when an obligor goes over its concentration limit overnight?

The excess becomes ineligible under the rule that produced it, availability moves, and the movement is attributed to that obligor rather than appearing as an unexplained drop. Concentration is also watched across clients, so exposure gathering under one debtor name in three different client files is visible as one number instead of three unremarkable ones.

Bring us a certificate you argued about.

We will rebuild it in FactorFox against your own eligibility rules and show you the movement decomposition for the day it moved and nobody could say why.