Revenue, customers, seasons.
Read as this business trades.
Behavioral understanding for lending to companies, sole traders and seasonal producers. Neumetria reads what is true of a business’s cash behaviour now, with what confidence, on data through when. It runs the credit policy you published against that read and keeps the record. The outcome is yours.
Three subjects.
One declaration.
You declare who you are lending to when you create the actor: a company, or a person, and whether that person trades. Neumetria never infers it. The declaration decides which half of the ledger a measurement runs over and which body of law the record answers to.
A legal person with its own account. Every row is business activity. Payroll is an outflow, revenue is what comes in, and the owner’s drawings are visible as what they are.
A freelancer, a contractor, a shop owner trading in their own name. One account carries both the household and the trade, and the same bank feed delivers both.
A farmer, a fisher, a seasonal tourism operator. Revenue arrives in a harvest, a catch season or a summer; inputs are bought months before it does; public payments follow their own calendar.
One account.
Two kinds of money.
A sole trader’s groceries and their stock purchases arrive from the same account in the same shape. Splitting that ledger at the door would make the one question a lender most wants answered, how commingled this account is, impossible to ask.
So every row carries a sphere: business, personal, or unclear. For a company, every row is business by construction. For a trading person it is read row by row, and the share that could not be placed is served as a measurement in its own right rather than hidden.
A correction is made once. The business says this order was stock, not a gift, or this counterparty is always personal, and the verdict stays applied. Business measurements read only the business sphere; the consumer read of a trading person keeps reading the personal one.
A sole trader is a natural person whatever they trade as. The consumer protections stay on: the route to a person, the explanation and the contest that CCD2 Art. 18(8) names, and the oversight posture AI Act Annex III 5(b) attaches to creditworthiness assessments of natural persons. The record carries the declared capacity, so the posture is visible, not assumed.
A company is outside the consumer instruments. The same policy engine runs, the same record is kept, and the regime your policy declares says which law it answers to. The declared capacity is on every assessment, so a later reader can see which posture applied without re-deriving it.
What the business sphere
measures.
Every measurement carries its confidence, an as-of date and the rows it was computed over, and abstains by name when the history is too thin. These are readings of the ledger, not forecasts about it.
What the business takes in over the year, how it moves, and how much of it is really its own rather than a platform’s or a refund’s.
Whether the business depends on a few customers or a few suppliers, and how much of its revenue comes back from customers who have paid before.
The weight of wages on revenue and whether they go out on time, a cash view of margin that is never the accounting figure, and how long the balance would carry the fixed costs.
Whether tax went out when the schedule says it should. A missed period is a finding that stays in the record until it resolves, so a later reader can see it was checked.
What the owner takes out of what the business makes, how often the owner has to put money in, and for a trading person, how mixed the two ledgers are.
How many lenders are being repaid at once, and whether the cash the business generates covers it. Beside the bureau, not instead of it.
The shape of the business’s own year, read against itself rather than against a monthly template. The full family is below.
How long customers take to pay, what is overdue and with whom, and how much of what was billed was actually collected.
The season is the behaviour,
not the noise.
A farmer’s year has a harvest in it. A fisher’s has a closed season. Read against a monthly template, both look like irregular income. Read against their own year, the question a lender actually has becomes askable: is this season normal for this business.
This season against the same season in earlier years. For a seasonal business it is the only growth figure that means anything, and the monthly trend is set aside where the season would masquerade as one.
Whether what is in the account carries the business through its quiet months, read from where it stands in its own cycle now. The next inflow is a season away, not a payday away, and the reading knows it.
Whether what the business owes falls in the months money arrives or in the months it does not. A schedule that lands in the off-season is visible as a structure, before it is visible as a missed payment.
How far ahead of the revenue the inputs are bought: seed, fuel, feed, nets. The working-capital need stated as a measurement rather than as a loan request.
Subsidies, quota and grant payments as a share of revenue, with their own cadence kept separate, because they are reliable in timing and decided somewhere else in amount.
How a season’s revenue moved against that season’s weather, for the businesses whose year the weather writes.
An optional second feed:
the invoices.
A bank account shows the cash. An invoice ledger shows what is owed, by whom, since when. Push the invoices a business issues and receives and the receivables measurements come on: how long customers take to pay, what is overdue and with whom, and how many invoices found the credit that settled them.
The field names are the ones the European e-invoicing standard already uses, EN 16931 as carried over Peppol, so an export from any compliant system maps onto the format without a vocabulary of ours. That standard is becoming the way invoices exist: Belgium and Poland mandated domestic business-to-business e-invoicing in 2026, France starts in September 2026 with small businesses following in 2027, Germany phases issuance in across 2027 and 2028, and the EU’s cross-border mandate follows in July 2030.
An invoice is an obligation with an expected settlement, not a transaction, and the bank credit that pays it is matched to it. An invoice that is never paid still ages.
Declare the subject.
Read the business.
The same two-call integration as every surface here, with one field more on the actor and one more format on the feed.
We execute your policy.
We never decide.
The read is ours. The outcome is yours.
Neumetria reads the ledger and executes the policy version you published, under the oversight you chose. Your conditions, your thresholds and your outcome words run exactly as written, and the run is kept with the facts it saw.
These measurements are new. They are read from the ledger, they carry no outcome history yet, and nothing here is calibrated against how business credit performed. We say so because the alternative is to let you find out.
Teams lending to companies and sole traders who want the business’s own cash behaviour beside the accounts and the bureau, with the record that reconstructs the assessment.
Teams advancing against receivables or revenue who want the ledger read continuously: what is owed, by whom, how late, and how concentrated.
Teams lending into a season who want the year read as the business lives it: the same season against earlier ones, the off-season runway, and a schedule that lands where the revenue does.
Read the business as it trades.
If you lend to companies, sole traders or producers, add the business read, the ledger and the record between your data and your policy.