Counterparty data collection and analysis

Raw material in.Decisions out.

Fern asks your counterparties for their data, reads whatever comes back, and returns checked analysis you can trace to the source.

Request a demo

I

They send it
every way.

Every quarter your team chases the same counterparties for the same numbers. What comes back is a different file from each of them, and someone re-keys it into the model by hand.

Spreadsheets

Exported from a dozen systems, with merged headers, subtotals and a tab nobody explains.

PDF reports

Tables locked in a page layout that changes whenever the sender changes accountant.

Scans

Printed, signed, scanned at an angle and attached to an email as an image.

Email threads

The number you need sits in the third reply, next to an apology for the delay.

The work isn't the analysis. It's getting to a table you can trust, and that is the part Fern does.

II

One loop,
start to finish.

Fern runs the whole reporting cycle, from the first request to the finished deck, with a person approving each number before it is used.

  1. IAsk

    Requests go out on schedule

    Each counterparty gets a request for exactly what you need, when it's due, and polite follow-ups until it arrives.

  2. IICollect

    Whatever comes back

    Replies arrive by email, upload or shared folder, in any format, and land against the right counterparty and period.

  3. IIIRead

    Into one clean table

    Every file becomes the same structured record, whatever the layout it arrived in.

  4. IVCheck

    Reviewed and traced

    Anything unusual is flagged for a reviewer, and every value links back to the place on the page it came from.

  5. VDeliver

    Analysis, ready to send

    Trends, breaches and comparisons arrive as dashboards, a branded deck and a draft memo.

III

For teams that depend on
other people's reports.

Fern starts with four workflows where the data arrives late, in mixed formats, and matters to a decision.

Real estate owners and lenders

Rent rolls and operating statements

  • Rent rolls
  • Operating statements
  • Budgets

Management fee charged at 7% against a 5% cap in the agreement.

Banks and asset-based lenders

Borrower and covenant reporting

  • Compliance certificates
  • Financial statements
  • Borrowing bases

Certificate reports 3.9x leverage; the attached financials work out to 6.0x.

Insurance brokers and carriers

Renewal data from clients

  • Property schedules
  • Loss runs
  • Exposure data

A claim on last year's loss run is missing from this year's.

Franchisors and multi-unit operators

Unit-level reporting

  • Unit P&Ls
  • Sales reports
  • Royalty statements

Royalty paid at 4% of sales where the agreement says 7%.

Findings shown are illustrative examples of what Fern flags.

IV

Built for work that
gets audited.

The numbers Fern produces end up in credit decisions and investor reports, so the controls come first.

Traced to source

Every value opens the original file at the exact place it was read from.

A person signs off

Nothing reaches a report until a reviewer has approved it, and every correction is kept.

Tamper-evident history

Each action is written to an audit trail that shows if anything was later changed or removed.

Access by role

Single sign-on, permissions by team and counterparty, and sensitive fields masked for those who don't need them.

Your data stays yours

Each customer's data is kept separate, with retention rules and legal holds you set.

V

Raw material in.
Decisions out.

Tell us what you collect, from whom, and how often, and we'll show you Fern on documents like yours.

Request a demo Or write to hello@fernhq.app