The platform
The whole operating day, in one system that explains itself.
FactorFox is built for the institution that funds. Factors, asset based lenders, purchase order funders and reverse factoring providers. Not for the business looking for money. Everything on this page is written for the people who decide whether money moves today.
What follows is not a feature list with twelve boxes on it. It is a day, in the order a funding company actually lives it, from the brief that lands before the first coffee to the packet that is sealed after the last release.
Operating day · one book · one record
Illustration- 07:00
Owner brief, whole book
CriticalTwo items require you. One approval is blocked because you raised it.
- 08:12
Intake, 41 documents
AttentionTwo near duplicates held. One extraction failed and is named, not guessed.
- 10:30
Schedule SCH-2214 at the gate
AttentionEight of eight gates passed. Awaiting a second officer.
- 11:05
Re underwrite triggered
Material event on Bluewater Foods. Run versioned, coverage 62%, confidence 71%.
- 14:40
Collections worklist
Two promises lapsed overnight. Ordered by exposure, not by age.
- 17:15
Close and seal
ClearCovenant position within every threshold. Concentration reaches its limit in eleven days.
How to read this
Two layers, and only one of them is new.
Underneath, FactorFox is a system of record. Schedules, purchases, advances, reserves, fees, cash application, payables, the ledger that has to reconcile. That layer has to be correct and it has to be dull. We have been building it for this industry since 2002, and the parts of it you will not think about are the parts we spent the longest on.
On top sits the layer people notice. It reads the record as it changes, decides what deserves a named person’s attention today, and hands that person the reason, the evidence and the action in the same breath. It is not a reporting module. It never asks you to go looking.
The distinction matters when you are comparing platforms, because every system in this category can store an invoice. The question is what happens in the four hours after the invoice is stored, when concentration under one debtor name has quietly moved across three clients and nobody has run the report that would show it.
The unifying rule is simple. Nothing in FactorFox states a conclusion it cannot open. Every signal, exception, recommendation and proposed action carries a reference into the records that produced it, captured when the decision was made rather than refreshed underneath it later.
The operating day
Seven moments, and what the platform is doing in each one.
Read this as the shape of a day at a funding company. Every capability below belongs to a moment, and the links in the next section take you to how each one works.
- 07:00
The brief lands before anyone opens the platform
Six fixed questions, answered against the scope each person actually carries. Where is risk and why. Which decisions require me now. What changed since the last brief. Where is cash and what can move safely. What is likely to happen next. Am I within covenant. The second brief of the day states the difference rather than repeating the book, and the same answers reach web, Microsoft Teams and a phone from one endpoint.
- Intake
Documents arrive and become facts, or become named gaps
Invoices, schedules, bills of lading, rate confirmations, assignment notices and remittances land by email, portal or SFTP. Extraction produces structured fields with a confidence on each one. Duplicates and near duplicates are fingerprinted within the client and across the whole portfolio, because the second submission of the same load is rarely an accident on the day it matters. A document that fails extraction is reported as failed. It is never quietly guessed.
- Pre funding
Every schedule meets its gates before anyone talks about releasing money
Verification status, invoice size against the client's own median, submission timing against the client's own pattern, credit limit utilisation on both sides, and the specific gate that is holding a schedule with the reason written out. A bank account change sits under a human only hold and automated approval of it is refused outright, not merely discouraged.
- Release
Money moves, or a named person is told exactly why it did not
Availability is computed, the release is proposed, four eyes applies and the approval is recorded with the actor, the evidence, the policy version and the origin. Payment files are built by rail and by bank. If the requester tries to approve their own release, the platform refuses them by name. That refusal survives every surface, including the phone.
- Through the day
The book is re underwritten as it changes, not on an annual cycle
Every material event triggers a fresh run, each run is versioned immutably, and confidence and coverage are reported separately so nobody confuses being sure with being able to see. Payment velocity, dilution movement, concentration migration and aging tipping are measured against the book's own history rather than an industry average that describes nobody.
- Afternoon
Collections works a list ordered by exposure, not by age alone
Promises that lapsed overnight, cases that reopened themselves with the reason stamped on them, contact history and the last verified balance in one place. A follow up projects into the officer's calendar, and deleting the calendar entry does not close the case, because the case is the record and the calendar is a projection of it.
- Close
The day is finished, and can still be proven three years later
Cash applied, proposed and unapplied with the source of each proposal named. Reserve movement and fee accrual with the entries behind them. Covenant position with days to breach on the current trajectory. Audit packets sealed, with a database trigger that refuses mutation, so the examiner window is a retrieval rather than a reconstruction.
Every capability
Twelve capabilities, one record underneath all of them.
Grouped by the moment in the day they belong to rather than by the department that owns them, because the department boundary is where most operations lose an exception.
Intelligence
The layer that decides what a named person needs to know today, and proves it.
Role based briefings
Six fixed questions answered against the scope a person actually carries, with an escalation lane for anything material outside it.
Intelligence with evidence
What sits behind a conclusion, how it is captured at run time, and why sealed packets cannot be edited later.
Continuous underwriting
Re underwriting on every material event, immutable run versions, gate policy and asymmetric automation.
Exposure
Where the money is at risk, measured as movement rather than as a static bucket.
Debtor and client risk
Concentration migration under one debtor name, dilution movement, payment velocity and aging tipping.
Covenant monitoring
Facility limits, eligibility, advance rates, reserves and reporting obligations, with days to breach.
Borrowing base
Eligibility rules, ineligibles, reserves and availability, computed from the same records the brief quotes.
Intake and integrity
Everything that happens between a document arriving and a schedule being fundable.
Document intelligence
Extraction with per field confidence, near duplicate fingerprinting, and failures reported as failures.
Fraud detection
Invoice size deviation, unusual submission timing, duplicate paper across the portfolio, bank account change holds.
Client onboarding
The file assembled with checks already run, gaps named, and the credit memo packet built as you go.
Cash and books
What moves the money and what proves the money moved correctly.
Collections
A worklist ordered by exposure and promise history, with cases that reopen themselves and say why.
Treasury
What can move safely today, payment files by rail and by bank, and net availability with days to zero.
Accounting and close
Cash applied, proposed and unapplied, reserve movement, fee accrual, and audit packets sealed for the examiner.
Refusals
The most useful thing to know about a platform is what it will not say.
Anything can produce a number. A number produced when the underlying facts are missing is worse than no number, because somebody will fund against it. These are the refusals built into the product.
| FactorFox will not | Why that is deliberate |
|---|---|
| Show a delta it cannot prove | If there is no prior observation, it offers to take a first observation rather than reconstructing a yesterday that was never recorded. Risk observations are append only at the database level. |
| Assert that a carrier's operating authority, insurance or safety score was verified | Those fields are captured, never verified, and the relevant gate is explicitly forbidden from asserting them. The refusal is what stops a credit memo from carrying a fact nobody checked. |
| Approve a bank account change automatically | It is the single most expensive email a factoring company receives. The change sits under a human only hold and the automated path is closed, not configurable. |
| Report a covenant as compliant when the data is missing | It reads awaiting a live source and names the source. Zero is a value. Absence is not, and reporting one as the other is how a certificate gets signed against nothing. |
| Let the requester approve their own release | Four eyes lives underneath every surface, so it cannot be avoided by moving to Teams or to a phone. In solo mode an AI counter review is logged where the second officer's name would sit, and it refuses outright when any underlying fact has changed since the request was raised. |
| Pretend a dark source is a live one | Several external credit and legal sources are declared and unconfigured. The platform reports itself blind on those and lowers coverage rather than presenting an empty result as a clean one. |
Every dismissal of a signal is recorded with a written reason and the name of the person who dismissed it. That record is the raw material a calibration loop needs, and calibration is the next thing we build. We are not going to tell you the models already learn from outcomes, because today every weight is a pinned constant.
Where it runs
One endpoint, four places you meet it.
There is no second brain and no separate mobile product. An answer on a phone and an answer on screen cannot disagree, because they are the same answer.
Web
The full operating surface. Queues, files, gates, the borrowing base, the ledger and every evidence trail behind them.
Microsoft Teams
Controlled releaseBriefing tab, chat dialogue with sources named, signal cards that change real state, and approvals with four eyes enforced.
Mobile
The same surfaces, phone sized, with the same controls. Built for the person who is in a car when the release needs a second officer.
Country packs
Local credit sources, payment rails and invoicing requirements, rather than a United States product with the spelling changed.
Straight answers
What operators ask before the first demonstration
Is FactorFox a system of record, or an intelligence layer on top of one?
Both, and that is the point. The ledger underneath holds schedules, purchases, reserves, fees, cash application and payables, and it has been built for this industry for more than twenty years. The layer above reads that ledger continuously and decides what deserves a person's attention. An intelligence layer bolted onto somebody else's database can only see what that database chose to expose. Ours sees the transaction as it is written.
Do we have to adopt all of it at once?
No. Most operators start with the part of the day that hurts, usually intake and verification or the morning brief, and widen from there. The capabilities share one record, so adding a second one does not mean a second implementation. What you cannot do is take the conclusions without the records behind them, because a conclusion with no evidence is exactly the thing this platform exists to stop shipping.
What happens when a data source we depend on is not connected?
The platform says so on the surface where it matters and reports coverage separately from confidence. A covenant that needs data FactorFox does not hold reads awaiting a live source and names the source rather than reporting zero. A verification gate that cannot reach a register refuses to assert the fact instead of implying it was checked. Reporting itself blind is a feature, and it is the one that keeps the rest of the screen believable.
Who in a factoring company actually opens the platform every day?
Operations and collections live in it. Credit officers and underwriters arrive on events. Owners, executives and treasury are often briefed without opening it at all, in Microsoft Teams or on a phone, and only come in when they follow a link into the evidence. Scope follows responsibility, so the person who owns forty clients is briefed on the forty rather than on the whole book.
Does the same platform run asset based lending, not just factoring?
Yes. Factoring, asset based lending, purchase order funding and reverse factoring run on the same records with different eligibility, advance and reserve behaviour. A borrowing base with ineligibles and reserves is the asset based lending surface. A schedule of purchased invoices is the factoring surface. Operators running more than one product get one book, one covenant position and one brief across all of it.
Related
Bring your hardest morning to the demonstration.
Tell us the day that went wrong: the concentration nobody saw, the duplicate that funded, the covenant certificate signed against a number you could not open. We will show you where the platform would have stopped it and what evidence it would have carried.