Every source. Every match. Every break explained.
Astridex reconciles what rules-based tools and spreadsheets can’t — DMS, toll host, carrier, payer, processor, bank, and ERP data — continuously, with a reason attached to every exception and a human on every judgment call.
- ▸Auto-match the routine, explain the rest.
- ▸Find breaks the day they happen, not at month-end.
- ▸Recover what you’re owed — then let the platform act on it.
Why reconciliation is broken
Rules-based matching only catches what someone anticipated. Everything else becomes an exception queue, found at month-end — after the money has already leaked.
Rules only match what you anticipated
A rules engine handles the case someone thought to write a rule for. Everything else — one-to-many, many-to-many, a new source format — becomes a manual exception.
Learn more →Month-end is too late to find a break
The worst breaks happen where sources sit outside the ERP: dealer systems, toll hosts, carrier invoices, payer remittances. They surface weeks after the money moved.
Learn more →Exceptions pile up without a reason
A red flag tells you something doesn’t match. It doesn’t tell you why — so a human has to reconstruct the story from scratch, every time.
Learn more →Ingest → Match → Explain → Resolve → Act
Ingest
Agents read every source in its native shape — EDI 835, DMS exports, toll host files, PDFs, portals, bank feeds — no manual re-formatting.
Match
One-to-many and many-to-many matching, with tolerances, fuzzy matching, and ML-suggested pairings — not just exact amount-and-date.
Explain
Every exception comes back with a proposed reason, not just a red flag.
Resolve
Routine exceptions clear automatically within the thresholds you set; judgment calls go to a human, with full context attached.
Act
Once the break is found, the rest of the platform acts on it — Collect chases the short-pay, Pay disputes the carrier, Close books it.
Reconciliation types
One matching model, applied to every kind of break.
Bank
Continuous matching across every account and entity.
Learn more →Payment & settlement
Processor and gateway settlement, netted to the deposit.
Learn more →Vendor & carrier invoice
Invoices matched to contracts, rates, and delivery evidence.
Learn more →Revenue & billing
Usage, contracts, and invoices kept in sync with the GL.
Learn more →Rebates & incentives
Claims matched to the credit memos that should follow.
Learn more →Intercompany
Cross-entity matching, elimination-ready.
Learn more →Balance sheet
Every GL account reconciled to its supporting schedule.
Learn more →Built for industries where the money doesn’t match
Office-technology dealers, tolling, freight, and healthcare billing first — plus the operational industries Astridex already reconciles for.
Office Technology & MPS Dealers
Meter reads, OEM rebates, and lease funding — reconciled against e-automate.
Learn more →Tolling & Mobility Payments
Passage-to-settlement reconciliation, not just trip-level matching.
Learn more →Shipping & Logistics
Beyond a three-way match — the full shipment-financial lifecycle.
Learn more →Healthcare Billing & RCM
Remit-to-deposit-to-contract reconciliation, at line level.
Learn more →Financial Services & Fintech
Reconciliation at scale, with an immutable audit trail.
Learn more →Retail & E-commerce
Processors, marketplaces, and stores, matched continuously.
Learn more →Hospitality & Restaurants
POS, cards, and bank deposits, reconciled every day.
Learn more →Real Estate & Property Management
Recurring AP and intercompany, reconciled across every entity.
Learn more →Outcomes finance teams see with Astridex
Across collections, payables, close, and procurement — measured on real customer workflows.
Reconciliation, proven
Every transaction matched, not a sample.
“Reconciling millions of transactions used to mean sampling and praying. Now every line is matched and the breaks surface the day they happen.”
Read the story →POS, cards, and bank deposits, every day.
“We reconcile POS, cards, and bank deposits every single day now. Month-end holds no surprises because the work never piles up.”
Read the story →Once the break is found, the rest of Astridex acts on it
- ▸Collect — recovers the short-pays and underpayments reconciliation surfaces.
- ▸Pay — disputes the carrier or claims the credit reconciliation found.
- ▸Insight — reports the leakage and forecasts around it.
- ▸Close — closes in days because the match already ran all period.
- ▸Knowledge — logs every reconciliation decision to one governed audit trail.
The life of an invoice
Watch a single bill flow through the agents — captured, matched, approved, paid, reconciled, and logged, all under your control.
Sources we reconcile
DMS, toll host, carrier, payer, processor, bank, and ERP data — any source with an API or a file feed.
Integrates with 500+ tools your team already uses — anything with an API.
Frequently asked questions
What is automated reconciliation, and how is it different from rules-based matching?
Rules-based matching only clears the exact cases someone anticipated. Automated reconciliation with AI matches one-to-many and many-to-many, with tolerances and fuzzy matching, and proposes a reason for every exception it can’t clear.
Can Astridex handle one-to-many and many-to-many matches?
Yes — most real reconciliation is one-to-many or many-to-many by construction (a settlement covering many transactions, a remit covering many claims). That is the default matching mode, not a special case.
How does Astridex handle sources without an API?
Astridex ingests native file formats — EDI, PDFs, portal exports, CSVs — as well as APIs. See the integration-status label on each industry page for what’s native versus file-based today.
How are exceptions explained?
Every unmatched item comes back with a proposed reason and the evidence behind it — not just a flag that something doesn’t match.
What does deployment look like?
Connect your systems read-only, and Astridex starts reconciling within days. You set the tolerances and approval thresholds before anything runs autonomously.
Is Astridex SOC 2 compliant?
SOC 2 Type II is in progress; ISO 27001 and GDPR practices are in place. See the Trust Center for current status and documentation.
How is Astridex priced?
A one-time setup fee plus a monthly fee linked to outcomes — a percentage of revenue recovered or loss prevented — with a pilot option. See the pricing page for the model.
Does Astridex replace BlackLine, Trintech, or FloQast?
Those tools are strong at balance-sheet close management. Astridex is built for operational, multi-source reconciliation — industries whose money moves through systems the ERP never sees.
Built for finance-grade trust
Human-in-the-loop approval on every financial action, role-based access, and a complete audit trail — by design.
See reconciliation on your data.
Connect your systems read-only and watch Astridex match what rules can’t — no slides.