Account reading / Mar–Aug 2026Arrival → repayment pattern
Capital arrivesRepayment begins
Each event / two marks3 events
Detected by pairing each arrival to the recurring repayment pattern that follows it.
Financial intelligence / Funding event detection
Know themomentnew capitalhas arrived.
A funding event leaves two marks in an account: money in, and a repayment pattern that starts shortly after. Covmont’s agents find both, and read them as one event.
3 funding events / detected Capital + repayment echo
What goes in. What comes back.
An inflow on its own is not a funding event. The pattern that follows is what makes it one.
What arrives
Period readMar–Aug 2026
Inflows over $5,00019
Recurring outflow groups11
Connected accounts2
Capital arrivalRepayment beginsStill repaying
What comes back / dated3 events
Most recent / Aug 2026 / $25,000 Three capital arrivals, each matched to a repayment pattern that begins shortly after.
Mar 2026
earliest detected3 of 3
still repaying
earliest detected3 of 3
still repaying
01 / Find arrival
Larger inflows are separated from ordinary revenue and internal movement.
02 / Match repayment pattern
Recurring outflows are matched by timing, amount, and counterparty pattern.
03 / Read one event
Capital and the repayment trail are returned as one dated funding event.
What the agent
derives.
Each of these is read from the account itself, not asserted by the business.
Funding date
When the capital actually landed, rather than when an agreement was dated.
Derived from inflow timingFunded amount
The size of the inflow attributed to the event, kept distinct from ordinary operating revenue.
Derived from normalized inflowsRepayment start
The first outflow in the recurring pattern that begins against the funding event.
Matched against recurring outflow groupsRepayment pattern
Daily, weekly, or monthly—the shape of the obligation, not just its size.
Derived from pattern spacingCounterparty class
Whether the pattern matches a traditional lender, an alternative funder, or a card facility.
Matched against known pattern familiesStill-open status
Whether the repayment pattern is still running at the end of the period read.
Derived from the last matched outflowThree events, one account.
Synthetic example / not a real business
Event timeline / detectedMar–Aug 2026
Event 01$40,000 capital arrivalRepayment begins 13 Mar · weekly · still open
−$1,580 / wkEvent 02$18,000 capital arrivalRepayment begins 18 Jun · daily · still open
−$286 / dayEvent 03$25,000 capital arrivalRepayment begins 12 Aug · weekly · still open
−$1,040 / wkEvent readings
3 arrivals → 3 repayment trails Arrival + weekly repayment patternMatched across 25 recurring outflows
Arrival + daily repayment patternMatched across 52 recurring outflows
Arrival + weekly repayment patternMatched across 3 recurring outflows
A funding event changes what we know.
The event can be detected without seeing the agreement.
Funding can be identified from the account activity itself. The counterparty agreement does not need to be part of the process.
Connected accounts define what can be detected.
Funding activity can be detected across the accounts available to Covmont. Activity outside those accounts remains outside the view.
Not every recurring outflow means new funding.
A supplier moving to weekly terms can resemble repayment activity. When the activity isn’t clear, the agent leaves it unresolved.
Pricing remains separate from detection.
The funding event establishes that capital arrived and repayment began. It does not establish the cost of the financing.
Inside the detectionCapital arrival
Repayment pattern
Dated event
Repayment pattern
Dated event
$83,000Total capital detected across three events.
48%March event22%June event30%August event3 of 3Still repaying
Early access
Build what’s next with Covmont.
See how Covmont can help you deliver better outcomes with AI.