Choose a use case
For the teams who run accounts payable, lending, and claims
What your business knows about documents has a shape.
It’s already there, in the work your people do every day. Kodexa’s AI can help you find it, test it against the answers your team already gave, and put it to work on the documents behind your operations.
What it learns is yours. Yours to read, change, and take with you.
Choose a use case, and watch it take shape
- document steps a month, on one audit trail
- 1.5M+
- Type II, independently audited
- SOC 2
- with customers in regulated industries
- Live
One use case Kodexa has worked on
Spreading
At a bank, that’s years of spreads, built by your analysts, one filing at a time. Kodexa learns from that work.
All it asks for is what you already hold: the spreads your analysts built, and the filings they built them from.
The Lab
You don’t have to draw the shape by hand.
An agent proposes a shape, runs it on real filings, scores it against the answers your analysts already gave, and studies what it missed. Then it tries again, and keeps going until the shape holds.
- 1
Run 1. A first guess. Something’s there, but it’s still blurred.
- 2
Run 2. It reads what it missed, and adjusts.
- 3
Run 3. The shape holds, and it’s ready to be trusted with real work.
What it found
What the filings don’t say, and no one had written down.
Here are six kinds of knowledge Kodexa found in the bank’s own spreads. Each one gives the shape a few more of its edges.
- 1
Where a line goes
Two lines carry the same label. One is operating cash flow, the other is investing.
Learned by where each one sits, so the two stay separate.
- 2
How a row is defined
Operating income is revenue less cost of sales and overheads, without other income.
The analyst’s own formula, learned from its parts.
- 3
How a figure is built
Undrawn commitment is the facility, less the letters of credit issued under it.
It isn’t printed anywhere. Kodexa found it because the arithmetic matched exactly.
- 4
When a line is split
Research cost is taken out of overheads and given a row of its own.
A note says it’s in there, and this desk takes it out.
- 5
Where a figure hides
Cash interest paid appears as a sentence in a note, and has no line on the statement.
Read from the sentence, for the year it names.
- 6
Which version to keep
When a later filing restates a year, this desk keeps the figure as first reported.
Learned row by row, since another desk may do it differently.
None of this is printed in a filing, and no one had written it up as a requirement. It was sitting in years of the bank’s own work.
Desk by desk
A bank doesn’t spread just one way.
Each desk has its own, and so do some borrowers. Kodexa learns each one, desk by desk, down to the borrower.
- The bankevery desk
- Debt maturities include finance leases, on every spread.
- Each deskevery borrower it covers
- For a utility, fuel is a cost of sales.
- One borrowerthis company only
- This company’s operating income is the analyst’s own formula.
Each lesson is kept only as widely as it holds true, so one desk’s habit doesn’t turn into another desk’s rule.
At one bank
Weeks,
not months.
The bank’s own past work was both the teacher and the exam.
Every business has its own
SpreadingInvoice handlingContract analysis is one shape, and yours will be another.
The same Lab can find it wherever a decision depends on documents. Pick a use case below to see how one of its rules was found.
What the business knows
“Spread a loan as short-term debt when it is due within twelve months, unless it comes from the owners.”
A credit policy, in one sentence.
One rule, found in three runs
- 62%
Run 1 tries: Spread each loan by when it falls due.
Most are loans from the owners. Your reviewers moved every one out of debt.
- 88%
Run 2 adds: A loan from the owners is treated like equity, because they won’t call it in.
Nearly all the rest are statements in thousands, read as single units.
- 97%
Run 3 adds: Read the units from the statement heading before spreading.
The cases left over are the unusual ones, and those go to a person.
Illustrative figures: agreement with your reviewers, on the same documents each run.
What you’re left holding
A loan from the owners is treated like equity.
Why: they won’t call it in ahead of the bank.
It’s in plain language, with the reason kept. No one had to sit down and write a rule.
What you’re left holding
What it learns is yours.
When your team keeps correcting the same thing, Kodexa writes it up as a rule for one of them to approve. That rule is specific to your business, and it stays with you. By the end you hold three things, and each of them is something you can read.
The plan
The steps it runs, in the order it runs them.
- Read the documentParse
- Say what it isClassify
- Pull out the factsExtract
- Check themValidate
- Ask when unsureReview
- DeliverConnect
The knowledge
Written in plain language, with the reason kept beside each note.
A loan from the owners is treated like equity.
Why: they won’t call it in ahead of the bank.
Read the units from the statement heading.
Why: a statement in thousands, read as single units, is out by a thousand times.
Recurring services don’t need a purchase order.
Why: nobody raises a PO for the lights.
Hold a recurring bill that is more than 15% up on last month.
Why: a jump usually means a billing error.
A later amendment replaces the clause it names.
Why: it’s the last thing both sides signed.
A notice date on a weekend moves to the Friday before.
Why: a notice sent on the Monday would arrive late.
The evidence
Each run’s score, measured against work your team had already reviewed.
- Run 162%
- Run 288%
- Run 397%
illustrative figures
It’s written plainly enough for your experts to read, and precisely enough for a machine to run. It’s kept as files, so you can see every change, and you can take them with you.
People stay in charge
The agent proposes, and your people decide.
The agent brings a proposed change, along with its evidence. Your expert reads it in plain language, so they can judge the rule itself without having to translate it into code first.
A change only goes live once one of your people has approved it.
Treat loans from the owners like equity
- Spread each loan by when it falls due.
- Due within twelve months is short-term.
- Added: A loan from the owners is treated like equity.
- Added: Why: they won’t call it in ahead of the bank.
- Same documents, scored before and after
- Every miss listed
Pay recurring services without a PO
- Pay an invoice when it matches a PO.
- And when the goods were received.
- Added: Recurring services don’t need a purchase order.
- Added: Why: nobody raises a PO for the lights.
- Same documents, scored before and after
- Every miss listed
Read renewal terms as amended
- Read the renewal terms from the renewal clause.
- Count the notice period back from renewal.
- Added: A later amendment replaces the clause it names.
- Added: Why: it’s the last thing both sides signed.
- Same documents, scored before and after
- Every miss listed
On the record
And you can always say why.
Code tends to keep only its latest version. In Kodexa, the knowledge used on a document is copied and stored with it, and that copy can’t be changed afterwards.
So when someone asks later, you can show what was done and why, as things stood on that day.
- MarchThe statement is spread
- JuneOwner loans now count as debt
- TodaySomeone asks why it was equity
Why was it equity?
It was a loan from the owners, and on that day those were treated like equity. Here is the note, exactly as it was.
A loan from the owners is treated like equity.
Why: they won’t call it in ahead of the bank.
copied in March · can’t be changed
- MarchThe invoice is paid
- JuneThe limit is tightened to 5%
- TodaySomeone asks why it was paid
Why was it paid?
It was 6.0% up on last month, and on that day the limit was 15%. Here is the note, exactly as it was.
Hold a recurring bill that is more than 15% up on last month.
Why: a jump usually means a billing error.
copied in March · can’t be changed
- MarchThe contract is summarised
- JuneNotice under 60 days is now flagged
- TodaySomeone asks why it wasn’t flagged
Why wasn’t it flagged?
Its notice period was 45 days, and on that day only periods under 30 days were flagged. Here is the note, exactly as it was.
Flag a notice period shorter than 30 days.
Why: that leaves too little time to line up a replacement.
copied in March · can’t be changed
What shape is your knowledge in?
Every business has its own. If you bring one decision that depends on documents, we’ll work with your experts to find its shape in the Lab.
