Foreign-currency reconciliation
A deposit in dollars or euros against a policy in pesos, dollars, or euros, with a dated conversion.
orbit cashmatch
/
Reconciliation · Payments
/
In PoC
A deposit in dollars. The right policy, at that day's exchange rate.
orbit cashmatch reconciles foreign-currency deposits against policies in another currency: it reads the bank document, runs nine rules across three layers, and applies the payment using the exchange rate of the day the money arrived. Every decision keeps the evidence behind it. Today it is a proof of concept with the real services already wired in.
orbit cashmatch
reconciliation · payments
01 · Context
The problem we are solving.
The collections desk receives a deposit in dollars and has to decide which policy it belongs to. The bank sends a SWIFT with no clear reference, or a statement with the payer's name misspelled. The policy is in another currency, so it must be converted, and converted at the rate of the day the money arrived, not today's. Someone does that by hand, and when the auditor asks why that deposit went to that policy, the answer lives in that person's head.
02 · What it is
orbit cashmatch in one sentence
A three-layer probabilistic reconciliation engine. It reads the bank document, extracts the fields, and runs nine rules against the universe of policies: deterministic first, programmatic next, and only when those fall short does it escalate to a language model with the best candidates. Every result carries its score, the textual evidence behind each rule, and the exchange rate it used with its date.
03 · How it works
Four steps. No magic.
From the bank document to the applied payment, with the evidence kept at every step.
01
The document comes in
A SWIFT, a statement, a receipt, or a loose PDF. It is read with the document extraction service and its fields are structured.
02
The policy is searched
Nine rules score every candidate: exact reference, converted amount, time proximity, payer similarity, currency corridor, counterparty, tax ID, and account.
03
It resolves or escalates
Above the threshold the deposit applies itself. If not, it escalates to the language model with the best candidates, and if it still does not resolve it goes to human review. The engine invents nothing.
04
The evidence stays
Every match records which rule contributed what, with which text, and with which exchange rate from which date. The whole run exports to Excel.
04 · What it does
Where it goes to work.
The modules that exist today and run with the real services wired in.
Automatic application
The deposit applies itself when the score clears the threshold the organization configured.
Exception queue
What the engine cannot resolve reaches a person with its candidates and score, not blank.
Auditing a decision
Anyone can reconstruct why that deposit went to that policy, rule by rule.
Tuning the policy
Rule weights and thresholds move from the interface and the next run uses them.
An audit file
The run exports to Excel with a summary, the matches, event-by-event traceability, and the rates used.
05 · Benefits
What changes when you have it.
Five differences from reconciling foreign-currency deposits by hand.
Request demo1
The right rate, not today's
If the deposit arrived on 28 April, the conversion uses the Banxico FIX of 28 April. That is accounting traceability, not an approximation.
2
Three layers before giving up
Deterministic, programmatic, and only if needed a language model. You pay for the model on the hard cases only.
3
It does not invent
With no candidate inside the time horizon, the deposit goes to human review instead of landing on the closest-looking policy.
4
Evidence travels with the decision
Every rule leaves the text that triggered it, so the audit does not depend on anyone's memory.
5
It tunes without a redeploy
Weights and thresholds change from the interface. No ticket, no waiting for the next release.
06 · Before and after
What changes, side by side.
An honest comparison between how your team reconciles today and with orbit cashmatch.
Before / Without orbit cashmatch
Today's day-to-day
- ✕ Each foreign-currency deposit is applied by hand, document by document
- ✕ Conversion uses the rate of whatever day someone got to it
- ✕ A misspelled payer breaks the search
- ✕ The reason for the application lives in the head of whoever did it
- ✕ Changing a criterion is a ticket to IT
After / With orbit cashmatch
The day-to-day with the engine
- ✓ Nine rules score every candidate across three layers
- ✓ Conversion uses the FIX of the deposit's own date
- ✓ Payer similarity is one more rule, with its own weight
- ✓ Every rule leaves its textual evidence in the file
- ✓ Weights are adjusted from the interface
07 · Industries
Where it applies today.
Built for foreign-currency premium collection. The architecture serves any reconciliation of deposits against receivables.
01 / Insurance
Foreign-currency premium collection
It is the process the proof of concept was built for.
02 / Banking
Deposits against receivables
Applicable by architecture. No case yet.
07 · Video
Let us see it in action.
The foreign-currency portfolio dashboard, the nine-rule protocol with its hard gates, and the run history with its audit file. Recorded in the platform.
08 · Contact
Let's see it with your operation.
In 30 minutes we tell you whether orbit cashmatch fits your process, what it integrates and what it doesn't, and what a pilot looks like. If it doesn't fit, we tell you that too.
Run the discovery with rocky