At a glance
- A borrowing base certificate recalculates eligible collateral against the credit agreement's own formula every period; the arithmetic is mechanical, the exceptions aren't.
- The check table below sets out rule, source document, computation, tolerance, and escalation owner for the checks a credit team's own review already runs.
- Tying the certificate to the AR aging and the general ledger is a separate check from recalculating eligibility; a tie-out checklist is below.
- Over-advances, covenant waivers, and concentration exceptions stay with the credit officer or portfolio manager — automation prepares the numbers, not the decision.
What is a borrowing base certificate?
A borrowing base certificate is the periodic report that recalculates a borrower's eligible accounts receivable and inventory against the formula in its asset-based lending (ABL) credit agreement, showing how much of the facility is available. The OCC's Comptroller's Handbook defines a borrowing base as the collateral base, agreed to by the borrower and lender, that limits the amount of funds the lender will advance to the borrower, specifying the maximum amount that can be borrowed in terms of collateral type, eligibility, and advance rates [1].
How often a certificate is due depends on the borrower's risk: lenders may require one as frequently as daily, with aging and inventory reports attached [1]. One publicly filed ABL credit agreement, for example, sets its own monthly delivery deadline for the certificate [2] — a cadence that doesn't transfer to the next agreement unchanged.
The borrowing base check table
Every certificate review repeats the same checks: rule, source document, computation, tolerance, and escalation owner.
| Rule | Source document | Computation the agent performs | Tolerance | Escalation owner |
|---|---|---|---|---|
| Aging and delinquency | AR aging report; the credit agreement's eligibility definition | Flag invoices past the agreement's own cutoff — commonly three times the stated terms, e.g., 90 days on 30-day terms [1]. | None — binary, not a range | Analyst confirms the cutoff against current agreement wording |
| Cross-aging (whole-account exclusion) | AR aging report; credit agreement cross-aging clause | Compute each customer's delinquent share; past the agreement's threshold, exclude that customer's whole balance, not just the delinquent invoices [1]. | Set by the agreement | Credit officer confirms before a whole account drops out |
| Concentration limits | AR aging report; credit agreement concentration clause | Divide each customer's eligible receivables by the total and cap the excess over the agreement's limit [1]. | The agreement's limit; an exception is documented | Portfolio manager approves any exception |
| Contra-accounts and affiliate receivables | AR aging; AP vendor master; borrower's disclosed affiliate list | Match AR customer names against AP vendor names and disclosed affiliates to catch offsetting or related accounts [1]. | None — a match is a flag | Analyst verifies before excluding or keeping the account |
| Government and foreign receivables | AR aging report; credit agreement eligibility definition | Flag government-billed or non-domestic accounts; eligibility often depends on extra support the agreement specifies, such as a letter of credit or an insurance policy for foreign receivables [1]. | Eligible only with the agreement's required documentation | Credit officer confirms documentation is on file before including |
| Dilution | Credit memo and returns ledger; invoiced receivables | Compute the share of invoiced receivables lost to discounts, returns, allowances, and credit losses — the agreement's own dilution rate [1]. | Per the agreement's dilution reserve trigger | Field examiner or credit officer reviews a rising trend |
| Inventory eligibility | Inventory report; credit agreement inventory clause | Exclude consigned, work-in-process, aged-or-obsolete, and location-excluded inventory the report flags [1]. | Per the agreement's inventory eligibility definition | Analyst confirms exclusions with the inventory report owner |
| Advance rate and gross availability | Credit agreement advance-rate clause; eligible AR and inventory totals | Apply the agreement's advance rate to eligible receivables and inventory to compute gross availability | None — deterministic once eligibility is set | None; changing the rate is a credit decision |
| Reserves | Credit agreement reserve clause | Subtract any required reserve the agreement lists — the cost to liquidate the collateral, dilution of accounts, or inventory obsolescence — from calculated availability [1]. | Per the agreement's current reserve list | Credit officer confirms the reserve list each period |
| Availability and minimum-availability | Credit agreement commitment and covenant clauses; the loan balance | The lower of the borrowing base or the commitment, less outstandings, tested against any minimum-availability covenant [1]. | None — deterministic | Credit officer, for any shortfall or over-advance |
Thresholds vary by agreement; treat the table as the checklist and the current agreement as the answer key.
Which ineligibles should be recalculated on every certificate?
The categories to recheck every period are the ones commonly designated ineligible [1]; the aging shows days past due, but it doesn't apply the agreement's exclusions:
- Delinquent and cross-aged accounts, once a customer's receivables cross the agreement's own aging cutoff.
- Balances over a customer's concentration limit, recalculated against the current aging, not carried forward.
- Contra-accounts and affiliate receivables, matched against the borrower's accounts-payable and affiliate lists.
- Government receivables, which carry their own documentation requirements, and foreign receivables, whose eligibility often requires a letter of credit or an insurance policy the agreement specifies.
- Inventory that is consigned, held at a location the agreement excludes, or already marked aged or obsolete on the current inventory report.
None of these is a one-time setup check: a concentration share moves whenever sales shift, and an account current last period can cross the delinquency cutoff this period. Recalculating the full set against the latest reports keeps a certificate honest.
How do you reconcile a borrowing base to the AR aging and general ledger?
A certificate that doesn't tie to the borrower's own books isn't worth much. A field audit runs a similar check: the OCC's handbook describes reviewing the borrower's books, records, and accounting systems, and testing records by inspecting collateral and examining invoices and supporting documentation [1].
An automated review should run that same tie-out before a certificate reaches a portfolio manager, not after availability has already been relied on.
- Tie the certificate to the aging report
Match the certificate's AR total and eligible-AR figure to the aging report dated the same cutoff, not a prior one.
- Tie the aging report to the GL
Match the aging report's total to the GL accounts-receivable balance for the same period; investigate any gap instead of assuming it's timing.
- Explain any difference
Trace a gap to invoicing cutoff, cash applied late, or credit memos posted after the aging ran, and record who confirmed it.
- Trace eligible AR to its exclusions
Confirm the certificate's eligible-AR figure equals the aging total less every ineligible category, line by line, not as a single adjustment.
- Tie inventory to its report and the GL
Match the certificate's inventory figure to the inventory report and the GL inventory balance, or document the variance.
- Compare exceptions to the last certificate
Flag any item ineligible last period that's eligible this period with no documented reason, and route it back.
Can AI read eligibility rules from the credit agreement?
Yes, as a first pass. A credit agreement's borrowing base section is already written as a formula: the loan agreement establishes how the borrowing base is determined and how frequently it is recalculated [1].
- Extract: the advance rate, the eligible-collateral definition, the exclusion list, and the certificate's required frequency and form.
- Confirm: which other defined terms an exclusion cross-references, and whether a later amendment has changed the clause.
How specific that structure gets, and how much it differs agreement to agreement, is visible in public filings. One ABL credit agreement requires the borrower to deliver, "[w]ithin twenty(20) days of the end of each month (or more frequently if required by Bank), a completed Borrowing Base Certificate in such form as Bank shall require" [2] — specific to that one filed agreement.
Reading the rule is the easier part; confirming it against the current agreement before it drives a certificate still takes a person — the same human-in-the-loop principle covered in our article on human-in-the-loop AI governance.
Which borrowing base exceptions need portfolio manager approval?
An automated check can compute every number above; it can't decide an exception is acceptable. That pattern — a system flags, a named person approves — is described in our page on document review with human approval.
- An over-advance beyond the limit the agreement allows — approved under the lender's own loan policy and supported by an assessment of the borrower's cash flow [1].
- A covenant waiver — documented with the reason, whether at underwriting or later in the loan's life [1].
- An exception to a concentration limit — approved for a specific circumstance that offsets the concentration risk, with the reason recorded [1].
- A new or disputed ineligible category the check table doesn't already code for, until the credit agreement's own language is confirmed.
How often should borrowing base certificates be tested?
Certificate frequency scales with risk: an ABL lender often requires certificates and supporting documentation on a weekly or monthly basis [1], with some borrowers required to submit them as often as daily depending on risk profile and collateral [1]. The collateral behind them gets a separate field audit, often quarterly or more frequently if risk dictates; the cycle can tighten to weekly or daily in a high-risk or workout relationship [1].
When this doesn't apply
- Your borrowing base already runs inside a loan or collateral-management system; extend what you have before building a parallel one.
- File volume is low enough that one analyst's queue never backs up, and the tie-out already takes minutes.
- The credit agreement's defined terms are inconsistent or get amended without being re-keyed centrally; fix that drift before automating a certificate that depends on it.
- The slow step is the credit decision on a flagged exception, not the arithmetic; automating the recalculation won't shorten a decision waiting on judgment.
Where to start: a first scoped workflow
Borrowing base review is one document-heavy step inside the broader loan underwriting document workflow; start with accounts receivable — an ABL borrowing base is usually skewed toward it [1]. It reads the certificate, aging, and agreement terms from the existing loan or collateral-management system and returns flagged exceptions there, not a parallel ledger.
- Pick one collateral type
Start with accounts receivable before adding inventory.
- Run it against a closed certificate
Reproduce, line by line, a certificate the team already approved, without using the output for any live decision.
- Confirm the rules against the current agreement
Have a credit officer check every extracted rule — advance rate, concentration limit, ineligibles — against the agreement in effect today.
- Set the tie-out as a gate
Decide in advance that a certificate doesn't reach the portfolio manager until it ties to the AR aging and the GL, or every gap is explained.
- Name the approver for each exception type
Assign who confirms an over-advance, a covenant waiver, or a concentration exception, recorded the way a manual override already is.
Frequently asked questions
What is a borrowing base certificate?
A borrowing base certificate is the periodic report a borrower files to recalculate its eligible accounts receivable and inventory against the formula in its credit agreement, confirming how much of the facility remains available. The lender sets the frequency: weekly, monthly, or daily for a higher-risk borrower.
Which ineligibles should be recalculated on every certificate?
Delinquent and cross-aged accounts, balances over a concentration limit, contra-accounts and affiliate receivables, government receivables with their own documentation requirements, foreign receivables whose eligibility often requires a letter of credit or an insurance policy, and inventory that is consigned, excluded by location, or obsolete. Each can change period to period, so a review recalculates the full set each time.
How do you reconcile a borrowing base to the AR aging and general ledger?
Tie the certificate's totals to the AR aging report for the same cutoff date, then tie the aging report to the GL accounts-receivable balance. Trace any gap to cutoff timing, unapplied cash, or late credit memos, and confirm eligible AR equals the aging total less every ineligible category.
Can AI read eligibility rules from the credit agreement?
As a first pass, yes — a borrowing base section is already written as a formula: an advance rate, eligible collateral, exclusions, and a reporting schedule. A person still has to confirm cross-referenced terms and check the extraction against the current agreement before it drives a certificate.
What borrowing base exceptions require portfolio manager approval?
An over-advance beyond the agreement's limit, a covenant waiver, and an exception to a concentration limit all call for a named approver, documented with the reason. A new or disputed ineligible category the check rules don't already cover should route to a person too.
How often should borrowing base certificates be tested?
Certificates are due as often as the lender's schedule sets — weekly, monthly, or daily for higher-risk borrowers. The collateral behind them gets a separate field audit on a cycle set by risk, which can tighten to weekly or daily audits in a high-risk relationship.
Related reading
- Loan underwriting document workflow covers the workflow this review sits inside.
- Document review with human approval covers the reviewer pattern applied to exceptions.
- Human-in-the-loop AI governance covers keeping overrides with a named person.
- Underwriting document workflow audit trails covers what evidence a certificate review should keep.
- AI agent implementation describes how a system like this is scoped, tested, and handed over.
More in Lending operations
Cross-Document Validation in Loan Files: Rules That Catch Income and Identity Mismatches
A cross-document validation rule table for loan files: how pay stubs, W-2s, tax returns, and bank deposits should be compared, with tolerances and routing.
Loan Covenant Monitoring Automation: Build, Buy or Layer an AI Agent on Your Portfolio System
Loan covenant monitoring automation: compare buying point software, extending your LMS, or building a custom agent, with a covenant test register template.
Financial ServicesMortgage Condition Clearing Automation: What an AI Agent Clears, What the Processor Keeps
Mortgage condition clearing automation, sorted by type: which conditions an AI agent can draft as satisfied, which need a person, and who signs off.
Mortgage Companies