BORROWING BASE · GUIDE

50 borrowers, 50 formats: getting borrowing base data into one consistent shape

Why certificate formats multiply, what it costs your portfolio view, and what one consistent shape actually requires.

6-minute read

Every borrower speaks a different spreadsheet

One borrower sends an Excel file with aging buckets of 30, 60 and 90 days. Another sends a PDF with 31–60 and 61–90. A third sends a scan of a signed form, with the agings attached separately, sometimes.

Each format is reasonable on its own. Together, they mean your team spends month-end translating instead of reviewing.

Aging
Amount
Current
1,284,500
30 days
412,300
60 days
96,750
90 days
31,200
Less ineligibles
(58,900)
Borrower AEXCEL
Buckets: 30 / 60 / 90 days
Line items: ineligibles as one total
File type: spreadsheet
Borrowing Base Certificate
31–60402,100
61–9088,400
Over 9027,650
Cross-aged(14,200)
Foreign(22,000)
Contra(9,300)
Borrower BPDF
Buckets: 31–60 / 61–90
Line items: ineligibles itemised
File type: fixed-layout document
Certificate of Borrowing Base
Total receivables
Eligible
Aging report: see attached
Signed
Borrower CSCAN
Buckets: in a separate aging file
Line items: totals only on the form
File type: scanned signed form

Why it matters above the analyst level

You can't compare what isn't the same shape

Ineligibles and concentrations mean different things borrower to borrower, so portfolio totals are only as reliable as the translation behind them.

Every new borrower adds a new format

Capacity grows with the number of formats, not just the number of facilities.

The translation lives in people's heads

When the analyst who knows a borrower's file is away, month-end slows down.

Three common fixes, and where they stall

APPROACHWHAT HAPPENSWHERE IT STALLS
Mandate one templateBorrowers are asked to switch formatsAdoption is slow, and older formats keep arriving
Analysts normalize by handThe team rekeys everything into a master spreadsheetWorks, but every certificate costs analyst time, and errors are hard to catch
Build an internal toolIT or a data team builds intake and mappingJoins the IT backlog; maintenance never ends

What one consistent shape actually requires

  1. 1

    Common field definitions

    One set of field definitions, so "eligible receivables" means the same thing for every borrower.

  2. 2

    Borrower terms on top

    Each borrower's own agreement terms applied on top of the common shape.

  3. 3

    Capture at the point of arrival

    Submissions captured where they arrive, with a record of when.

  4. 4

    Calculation on submission

    Calculation that happens on submission, not after rekeying.

How Covarity handles it

Borrowers submit through Covarity's borrower portal. Each submission lands in one consistent structure, eligibility rules and limits are applied automatically, and availability is calculated without rekeying.

There are two ways for borrower data to come in, and you choose which one applies to each borrower.

OPTION 1

Certificate entry

The borrower keys in their certificate in the Client Portal. It's the same information they prepare today, entered in one place instead of sent as a file.

OPTION 2

Full listings

The borrower submits full receivables and inventory listings, so your team can analyse the collateral at a finer level of detail.

The choice is yours, borrower by borrower, based on your appetite for risk and the size of the loan. Many lenders keep smaller loans on certificates and move larger loans to full listings.

Borrower portal submission view with document upload fields
Borrower portal: submission view
Covarity financial statement view in one consistent structure
Portfolio view: all borrowers in one structure

See 50 formats become one

A 20-minute walkthrough of how borrower submissions come in and what your team sees.

Book a 20-minute walkthrough

Connect with a solutions expert