unapplied cash
current tool
Sits in a suspense account until someone reconciles it by hand.
Kaiva agent
Matches remittance to invoice from the bank file and posts it, same day.
Free, and it does not expire. 3 servers, 200K tool calls a month, 3 seats - no card.
Free tier
Free is a plan, not a trial
No card, no clock, no downgrade email. Most builders never leave it.
Two ways in
Nothing to write, nothing to host
npx @kaiva/bridge push my-api --openapi <spec-url>Any MCP client
Works with what you already use
Open & listed
Public source, public registry
§ 01 · how bridge works
Three steps, no infrastructure.
Point Kaiva at Postgres or an OpenAPI spec and get a live MCP endpoint your agents can call. No server to write. Nothing to host.
01
Connect
Paste a Postgres connection string or an OpenAPI URL. Kaiva introspects the schema and proposes tools, nothing is exposed until you say so.
02
Secure
Choose exactly which tools are exposed, mark them read-only, and require approval for the ones that write. Keys are scoped per server.
03
Point your agent at it
Copy the config block into Cursor, Claude Code, or your own SDK client. Every call it makes lands in your audit log, in real time.
kaiva agents · for finance teams
Your cash is stuck in the exceptions.
Your AR system already applies the clean payments. Kaiva works what it leaves behind, the unreadable remittances, the short-pays, the broken promises. Every action is posted to a working-capital ledger in euros and days, attributed against a held-out control, and reversible for 30 days.
Runs inside your own environment (your cloud, your access controls, no data reaching Kaiva's servers) or EU-hosted by us if you'd rather we run it. Either way, sits on top of the stack you already bought, no migration.
§ 02 · the leak map
Six places cash stops moving, and what moves it.
A five-day swing in DSO frees more cash than a two-percent cost cut. This is where those days hide.
short payments
current tool
Flagged as a discrepancy, then queued for a human to chase.
Kaiva agent
Classifies the deduction, gathers proof, and drafts the claim or the write-off.
disputed invoices
current tool
Emailed back and forth until the customer or the rep gives up.
Kaiva agent
Opens a dispute case, routes it, and tracks it to a euro resolution.
broken promises-to-pay
current tool
Logged in a spreadsheet nobody re-reads.
Kaiva agent
Watches the date, and re-engages the moment a promise slips.
parked credits
current tool
Duplicate and on-account credits age quietly against the balance.
Kaiva agent
Surfaces them, proposes the application, and books it on approval.
dunning gaps
current tool
A fixed reminder cadence that treats every account the same.
Kaiva agent
Sequences outreach by risk-weighted recovery, not by calendar.
§ 03 · the wedge
We don’t want your clean eighty percent.
Your team already handles the payments that arrive clean and matched. We only touch the exceptions, the fifth of your ledger that eats the working capital. Send us one month of incoming payments, and we’ll tell you exactly how many days of cash are trapped in it before you commit to anything.
the diagnosis question → how much of your DSO is exceptions?
Eight purpose-built agents work these six leaks behind the scenes. You deal with the outcome, not the roster. See the agents →
§ 04 · cash conversion twin
Change the policy. See last quarter replay before anyone is contacted.
Move a lever. Kaiva re-runs your real historical transactions against the new policy and shows the cash and the risk, so nothing is tried live on a customer first.
replay · 12,412 historical invoices · 90 days
dunning trigger
day 7 → day 4
cash pulled forward
+€612K
added dispute risk
+0.4%
§ 05 · ease of governance
Governance you can do, not just document.
One console. Policy, simulated run, reversible receipt. Your risk team follows the whole thread (from the rule on the left to the cash on the right) in fewer clicks than approving an expense report.
Declare the rule, the boundaries, the people.
Five fields. No YAML marathon, no policy engine PhD. Kaiva compiles your declaration into typed contracts every subsequent run is checked against.
Outcome declared cash.recovery · dunning workflow
signedAutonomy budget set max 3 touches · 500 accounts/day
signedGuardrails attached contact.hours.v1 · dispute.pause.v1
signedApprovers assigned @finance-lead (sponsor) · @compliance (risk)
pendingSimulate on last quarter's data. Ship only when it passes.
Kaiva replays the proposed policy against real historical AR runs and surfaces where a guardrail would have fired, how much cash it pulls forward, and what the honest lift looks like.
Replayed on 12,412 past invoices Jan 1 – Mar 31 · 90 days
cleanContact-hours guardrail never breached 0 violations · 100% clean
passProjected cash pulled forward +€184K · net of a held-out control
readyDual approval recorded @finance-lead 10:04 · @compliance 10:09
signedA receipt is the only thing real in AI.
Every run posts to the ledger with its inputs, guardrail results, and the outcome it booked against. Reversible for 30 days by default. Exportable as a signed audit pack.
Immutable, tenant-scoped, exportable on request enforced at write-time
immutableAttributed via a held-out control cohort h_8812 · conf 0.94
attestedReversible until Apr 24 one-click rollback · full reattribution
liveExportable as audit pack PDF · JSON-LD · signed bundle
readyPolicy · dunning.agent.v1compiled
outcomecash.recovery · dunning workflowedit
agentdunning.agent · v1.0edit
autonomyAct within budget · operator can pause at any timeedit
outreach touches3/invoiceceiling 5 · current avg 3
daily accounts500/dceiling 900 · current pace 412/d
guardrailscontact.hours.v1 · dispute.pause.v1 · dnc.list.v1edit
approvers@finance-lead (sponsor) · @compliance (risk)edit
Simulation · Q1 replay§ 12,412 runs · 0 breaches
sim duration 38sguardrail hits 0approvers signed 2/2
receipt · led_7af1·0c82posted 10:42 · today
+€18,420CASH
credit · remittance matched · INV-88213
agentdunning.agent · v1.0trace r_9c14…2f
holdoutattributed, net of controlsee cohort
attributionconf 0.94explain
guardrails✓ all passedview checks
signed by@finance-lead · @compliancepolicy v1.0
§ 06 · why the number survives audit
A confidence score is not an audit trail.
Measured against accounts we deliberately left untouched. You are billed on the gap between worked and holdout, a number your auditor can reproduce, not a model's self-reported score.
worked cohort vs. holdout · days to cash
−6.2 days attributed, net of the holdout
§ full methodology on the governance page
§ 07 · who is behind it
Built by the people who ran the finance transformations.
Operators who carried the collections number, wrote the MSAs, and rebuilt order-to-cash from the inside, not a lab that discovered finance last quarter.
About the team →§ 08 · the engagement
Four weeks to a receipt.
One leak, one agent, one fixed fee. No licence, no migration, no professional-services crater.
in scope
- One exception workflow, instrumented end to end
- A held-out control and an agreed baseline
- Every action logged and reversible, in euros and days
- A receipt you can take to the CFO in four weeks
not in scope
- A platform licence or per-seat subscription
- Ripping out your AR system
- A six-month data-lake migration
- Touching your clean, matched payments
Send us one month of exceptions.
Book a cash leak review →Building agents rather than buying them? Start with Bridge, free →