The most important design decision in Olycor is a boundary: AI is allowed to interpret your data, and it is never allowed to compute a number a lender relies on. Those numbers come from a rules engine.
Deterministic means the same inputs and the same rule versions always produce the same output, with no probabilistic step in between. In Olycor, AI handles data interpretation, mapping columns, matching obligors, reading PDFs, while eligibility, advance rates, reserves, and concentration limits are computed by a versioned rules engine configured to your credit agreement.
Receivables data is messy in ways only judgment can fix, and lending math is exact in ways judgment must never touch. Most tools blur the two. Olycor splits them.
The handoff between the two jobs is inspectable. Every interpretation the AI makes is recorded as a decision with a confidence score, anything uncertain goes to a person, and only confirmed, structured data enters the calculation. That record is part of the lineage described in source-level auditability.
A borrowing base certificate is a signed compliance document. A servicer report feeds amortization triggers. The numbers on them create legal consequences: a materially wrong certificate can be a default under the credit agreement, and an overadvance discovered later usually must be repaid immediately. A number with those consequences cannot come from a system that might answer differently tomorrow.
Language models are probabilistic by construction. Ask one to sum a 4,000 row aging file and it will usually be right, which is precisely the problem: usually is not a standard any treasurer can sign under, and an error rate you cannot bound is worse than one you can. An occasional wrong digit in a $27,800,000 borrowing base is not a rounding issue. It is a misreporting event.
So the rules engine contains no model at all. An invoice is 91 days past due or it is not. An obligor group is over its 15 percent concentration limit by $312,000 or it is not. Arithmetic on facts, per the agreement, every time.
Every calculation run gets an ID and records exactly three things: the input snapshot, the rule versions, and the output. Rerun the June certificate in November, during a field exam, with the same inputs and versions, and you get the same result to the cent. Reviewers can test this whenever they want, and skeptical reviewers should.
Repeatability is also what makes review meaningful. When the preparer and the approver look at a run, they are looking at the same deterministic artifact, not two refreshes of a live spreadsheet that may have shifted between them. And when a number changes between two runs, the cause is always identifiable: the inputs changed, or a rule version changed. There is no third possibility, which is exactly the property a variance question needs.
Deterministic does not mean generic. Two facilities can define the same concept differently: one excludes receivables 90 days past invoice date, another 60 days past due date; one caps any single obligor at 10 percent, another at 20 percent with named exceptions; cross-aging thresholds range from 25 to 50 percent. Olycor encodes your definitions from your documents, so the engine computes your facility, not an industry average of one.
Every configuration is versioned. An amendment that moves the advance rate from 85 to 87.5 percent becomes a new rule version with an effective date, an author, an approver, and a note pointing at the amendment. Old reports keep the versions that produced them. The rule set is auditable history, the same way the data is.
Olycor is an early-stage product handling sensitive financial data, and we would rather be precise than impressive. Certifications such as SOC 2 and ISO 27001 are on our roadmap and are not yet attested; we do not claim them, and you should not accept the claim from any early-stage vendor without a report. What exists today: encryption in transit and at rest, role-based access with separation between preparer and approver, tenant isolation, and audit logging of user and system actions. We share our current control documentation and roadmap with prospective customers under NDA, and we expect your security team to ask.
Or browse the full receivables finance glossary and the eligibility rule library.
Last updated July 9, 2026. Olycor does not provide legal, tax, accounting, or credit advice. Facility terms, eligibility criteria, and reserve mechanics vary by credit agreement; your agreement governs.
Olycor is onboarding borrowers who want AI on the messy part of the job and code on the part that gets signed.