Business Line of Credit OCR: What the Base Excludes

Lending OCR content is thorough on the documents every commercial credit file shares: bank statements, tax returns, financial statements. What it consistently skips is the document specific to an asset-based small business line of credit, the borrowing base certificate, a recurring report that determines how much of the line is actually available to draw, calculated fresh every reporting period against the business's current accounts receivable and inventory, not a fixed number set once at approval.

This is the actual mechanics of that certificate, what makes a receivable ineligible for the calculation, and why extraction alone, without the eligibility logic underneath it, produces a borrowing base that overstates real availability, a gap sitting squarely inside automated loan verification for this specific product.

Why an asset-based line of credit isn't a fixed number

A term loan has a fixed original balance that only goes down. A revolving line of credit secured by business assets works differently: the maximum amount actually available to draw, the borrowing base, moves with the value of the collateral backing it, primarily accounts receivable and, for businesses that carry it, finished goods inventory. As receivables grow, the base grows and more becomes available. As receivables age past a lender's eligibility cutoff or get written off, the base shrinks, sometimes below the amount currently drawn. This is why a borrowing base certificate, a short, recurring report the borrower submits monthly, quarterly, or on whatever cadence the credit agreement specifies, exists at all: the approved credit limit on the line and the actual currently available amount are two different numbers, and only the second one, recalculated from the current certificate, tells a lender what is really safe to advance today.

The formula, and the advance rates that shrink raw collateral into usable base

The standard calculation: borrowing base equals eligible accounts receivable multiplied by an AR advance rate, plus eligible inventory multiplied by a separate, generally lower inventory advance rate. Advance rates vary by lender and collateral quality, but AR advance rates commonly land around 70 to 80%, and finished-goods inventory advance rates commonly land around 50%, reflecting the fact that inventory is harder and slower to convert to cash than a receivable already owed by a paying customer.

Collateral	Raw value	Typical advance rate	Contribution to base
Eligible accounts receivable	$150,000	70%	$105,000
Eligible finished-goods inventory	$50,000	50%	$25,000
Total borrowing base	$200,000 raw collateral		$130,000 available

Note the word "eligible" doing real work in both rows. The advance rate applies only after ineligible receivables and ineligible inventory have already been stripped out of the raw figures, which is exactly the calculation step most extraction-focused OCR content never explains.

The four exclusion categories that make a receivable ineligible

Not every dollar on an accounts receivable aging report counts toward the base. Four exclusion categories are standard across most asset-based lending agreements, though exact thresholds vary by lender and are set in the specific credit agreement.

Aging. Receivables past a defined age, commonly 90 days from invoice date, are excluded entirely, since a receivable unpaid that long is a meaningfully weaker collateral claim than one still within normal payment terms.

Concentration. If a single customer represents more than a defined share of total receivables, commonly in the 20 to 25% range, the excess above that concentration cap is excluded, even if those specific invoices are current and unpaid on time. The logic: a base overly reliant on one customer's continued solvency is a riskier base than one spread across many customers, regardless of any individual invoice's own age or status.

Affiliate and related-party receivables. Invoices to a sister company, a parent entity, or an owner-related business are excluded, since these are not arm's-length transactions and cannot be relied on as genuinely independent collateral the way a receivable from an unrelated customer can.

Contra accounts. If the business both sells to and buys from the same customer, and that customer could offset what they owe against what the business owes them in a dispute or default scenario, the overlapping amount is typically netted out of the eligible receivable for that customer specifically.

Inventory eligibility gets screened the same way, on different criteria

Inventory collateral goes through its own eligibility screen, parallel in structure to the receivable rules but built around different risk factors. Raw materials and work-in-progress inventory are commonly excluded entirely, or advanced at a materially lower rate than finished goods, since unfinished inventory is further from being sellable and harder to value if the lender ever needs to liquidate it. Slow-moving or aged inventory, sitting unsold past a defined period, faces the same logic as an aged receivable: the longer it sits, the weaker its claim to represent real, recoverable collateral value. Consigned inventory, goods held on behalf of another party rather than owned outright by the borrower, is typically excluded entirely, since the borrower does not have clear title to pledge it as collateral in the first place. A pipeline that extracts a single inventory total from a balance sheet, the same failure mode as the AR summary-total problem, has no way to apply any of these three inventory-specific exclusions either.

A worked example of eligible versus raw

A business reports $150,000 in total accounts receivable on its aging schedule. Of that, $18,000 is more than 90 days past invoice date, excluded entirely. Of the remaining $132,000, one customer represents $40,000, against a 25% concentration cap that, applied to the $132,000 eligible pool, caps that single customer's contribution at $33,000, excluding $7,000 above the cap. No affiliate or contra issues this period. Eligible receivables: $132,000 minus $7,000, or $125,000, not the $150,000 the raw aging report shows. Applied at a 70% advance rate, that is $87,500 of actual borrowing base contribution from receivables, meaningfully below the $105,000 a pipeline that skipped the eligibility screening entirely and applied the advance rate to the raw $150,000 figure would have calculated.

The overadvance trigger, and why it is a compliance event, not a rounding footnote

When the recalculated borrowing base falls below the amount currently drawn on the line, the borrower is in an overadvance position, a real, defined trigger under most credit agreements that typically requires an immediate paydown to bring the drawn balance back within the recalculated base, or additional qualifying collateral to restore it. This is not a soft warning. A pipeline that calculates the base incorrectly, overstating it by skipping eligibility exclusions the way the worked example above shows, can mask a genuine overadvance that the credit agreement actually requires action on, right up until a lender's own audit or field exam recalculates the certificate correctly and finds the borrower already in breach.

Dilution: the trend a single certificate can't show, but a sequence can

A single borrowing base certificate is a snapshot, but the more useful signal often lives in the trend across several consecutive certificates: dilution, the rate at which a business's receivables get reduced by credits, returns, discounts, or write-offs rather than actually collected in cash. A business with rising dilution, more of its invoiced revenue evaporating into credits and returns each period rather than converting to collected cash, is showing early signs of either a quality problem with what it is selling or a customer base under its own financial stress, well before that shows up as an outright default or an overadvance event. Calculating dilution requires comparing each period's certificate against the prior ones, tracking gross invoiced receivables against actual cash collected over the same window, a genuinely different kind of check than validating any single certificate in isolation, and one that only becomes possible once a pipeline is storing and reconciling certificate data period over period rather than treating each submission as a standalone document to extract and discard.

This is the practical argument for building borrowing base extraction as a running, comparable dataset rather than a one-off form-reading exercise. A lender that can only answer "is this period's certificate internally consistent" is missing the earlier warning sign that shows up only in the shape of the trend across several periods together.

Where extraction needs to route: line-item aging, not a summary total

The practical extraction requirement this creates: a borrowing base certificate pipeline needs the full accounts receivable aging schedule, invoice by invoice or at minimum customer by customer with an aging bucket attached, not just the single summary total most bank statement or financial-statement OCR is tuned to pull. Aging-bucket detail is what makes the 90-day exclusion possible to apply at all, and per-customer totals are what makes the concentration cap calculable. A pipeline extracting only "total AR: $150,000" from a balance sheet has nothing to apply either exclusion rule against, and will hand underwriting the raw, overstated figure by default, a different but related version of the credit-limit-versus-balance error covered in our HELOC document OCR piece, wrong input field, right-looking output.

What I would check in your current borrowing base pipeline

Ask whether your extraction actually pulls a full aging schedule with per-customer, per-invoice detail, or just a summary AR total that has nowhere to apply eligibility rules against. Then ask whether the 90-day aging exclusion, the concentration cap, and the affiliate exclusion are actually encoded as calculation steps applied to that detail, or whether the advance rate gets applied directly to a raw, unscreened figure. Confirm what happens automatically when a recalculated base falls below the outstanding balance, since an overadvance is a defined credit-agreement event that deserves an explicit, immediate workflow trigger, not something a reviewer needs to notice by comparing two numbers manually every reporting period. And ask whether certificate data actually gets stored and compared period over period to surface dilution trends, or whether each submission is validated and then effectively discarded, the same forward-looking discipline covered from the deposit-pattern angle in our loan stacking detection piece, applied here to a business collateral trend instead of a consumer deposit pattern.

Frequently asked questions

What is a borrowing base certificate?
A recurring report, typically submitted monthly or quarterly, that recalculates how much of an asset-based line of credit is actually available to draw, based on the business's current eligible accounts receivable and inventory, not the original fixed credit limit approved at closing.

What makes a receivable ineligible for the borrowing base?
Commonly four categories: receivables aged past a defined threshold, typically 90 days from invoice date; the portion of any single customer's receivables above a concentration cap, typically 20-25%; affiliate or related-party receivables; and contra amounts owed back to a customer who is also a vendor.

What are typical advance rates for accounts receivable and inventory?
Accounts receivable advance rates commonly land around 70-80% of eligible receivables. Finished-goods inventory advance rates commonly land around 50%, reflecting that inventory is slower and less certain to convert to cash than an already-invoiced receivable.

What happens when the borrowing base falls below the outstanding balance?
This is an overadvance, a defined trigger under most credit agreements typically requiring an immediate paydown or additional qualifying collateral to restore the balance within the recalculated base. It is a compliance event, not a routine fluctuation.

Why isn't a summary accounts receivable total enough to calculate a borrowing base?
Because the aging exclusion and concentration cap both require line-item or per-customer detail to apply. A single AR total has nowhere to apply either rule against, which leads to the advance rate being applied to a raw, unscreened figure that overstates real availability.

Does the borrowing base calculation apply to a HELOC-style consumer line the same way?
No. A consumer HELOC uses a fixed approved credit limit for HCLTV purposes regardless of draw status. A business asset-based line recalculates its actual available base every reporting period against fluctuating collateral, a materially different, ongoing calculation rather than a static one set at origination.

A borrowing base certificate looks, at a glance, like a simple report to extract: some totals, an advance rate, a resulting number. The eligibility screening underneath those totals is where the real calculation lives, and it is exactly the layer most lending OCR content, focused on getting the raw numbers off the page accurately, never actually reaches. Written by Nupura Ughade.