Integration
ProcureAI and FinanceAI are not a new system of record. They sit next to the ERP, P2P, and banking platforms you already run — reading with least privilege, explaining exceptions with quoted evidence, and leaving approvals and posting with your team.
Purchase orders, supplier master, chart of accounts, approval matrices, and payment files remain in Coupa, SAP, Oracle, NetSuite, Dynamics, Workday, or your core banking stack. Agents do not re-home that data or bypass the workflows your auditors already understand.
Master-data changes, vendor onboarding decisions, and journal posting still require the people and roles you have defined. Stellitron Intelligence coordinates checks and narratives; it does not issue POs, sign contracts, or release treasury payments on its own.
ProcureAI focuses on procurement and AP documents: three-way match before payment, contract clause cross-checks when price drifts, supplier screening with analyst disposition, and recovery audits on AP exports. FinanceAI focuses on bank reconciliation to the ledger, KYC pack review, and month-end close prep — each with rules first, quoted evidence, and maker-checker approval before post.
Example · ProcureAI
ProcureAIThree-way match on every line, with holds when price or quantity drifts from the PO and goods receipt.
HoldPayment blocked pending buyer review
Example · FinanceAI
FinanceAIMatches bank lines to the ledger and proves when the unexplained difference is zero.
Needs infoReturn to preparer with cited break
Every enterprise pilot follows the same sequence: prove read access, map fields in sandbox, run a batch with humans in the loop, then — only if you want it — enable narrow write-back paths your security team approves.
Exact API names vary by tenant and release. The lists below are the practical minimum we ask for in discovery — not a promise that every scope exists on your edition.
Agents read open POs, receipts or accruals, invoice lines, and supplier records your AP team already reconciles in Coupa. Invoice and Contract agents sit beside that flow; buyers see holds and clause citations in ProcureAI while status in Coupa updates only after approval.
What IT typically provides
Pilots usually start with OData services or IDoc extracts for purchase orders, goods movements, and vendor invoices. Match and hold logic runs in ProcureAI; optional hold codes or invoice blocks post to SAP only after your AP lead signs off.
What IT typically provides
No. Coupa, SAP S/4HANA, Oracle, NetSuite, Dynamics, Workday, and your core ledger stay authoritative for master data, approvals, and posting. The agents read what they need, prepare evidence-backed exceptions, and wait for a person before anything consequential changes.
We do not claim certified partnerships with ERP or P2P vendors. Connectors are built and tested with your team during a pilot, using your sandbox and your security review.
Yes. Many pilots begin with anonymised or synthetic data, or with CSV and Excel exports your AP team already produces. Live read-only APIs are added when mapping is trusted and security approves scopes.
Public trials use Stellitron-hosted workspaces on dummy documents. Enterprise pilots can run in your cloud account or VPC so data residency matches your policies. Network allow-lists and secrets stay in your control.
Only actions your team explicitly approves — for example a payment hold on a disputed invoice or a proposed bank-fee journal held for controller sign-off. Bulk posting, approval-chain changes, and autonomous payments are out of scope.
ProcureAI and FinanceAI each document connector patterns on their own sites. This page explains the shared philosophy on stellitron.com: complement the system of record, read-only first, human approval on every consequential step.
A GOOD PLACE TO START
A conversation about your goals, constraints, and next step.