Financial services use case · Stripe + Xero + OpenAI + ServiceNow
Payment exception classification
Finance repeatedly investigates the same kinds of payment differences without consistent routing or an explanation attached. Unmatched payments reach the appropriate finance queue with a proposed category and supporting references.
Systems involved
What each system contributes
The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
Architecture
One governed run
How it starts: Reconciliation identifies a Stripe payment or settlement item that does not match the available Xero records.
Step by step
How the process runs
- 01
Gather reconciliation context
Read the Stripe transaction and the relevant Xero invoices, payments or bank transactions.
- 02
Describe the difference
Rules calculate known amount and currency differences and identify missing references before interpretation.
- 03
Classify the exception
The selected model compares the transaction context with approved exception definitions and proposes a category with its supporting evidence.
- 04
Route the investigation
A validated category maps to the appropriate ServiceNow queue, while uncertain or unfamiliar cases go to finance triage.
- 05
Carry out the decision
The assigned finance owner reviews the proposed treatment before a separate step performs any permitted Xero adjustment.
Control
Human decision and exception path
Human decision
The named finance owner approves reallocation, write-off, refund or another action that changes money or accounting records. Classification may route work under policy, but it does not authorize the financial action.
Exception path
- An unsupported or ambiguous category routes to general finance review rather than a guessed specialist queue.
- Missing transaction or invoice context keeps the case open for evidence gathering.
- Duplicate event and case references are checked before another investigation or accounting action is created.
Evidence
What gets audited
- Stripe and Xero references and calculated differences.
- Model classification, category definitions and cited context.
- ServiceNow assignment and finance decision history.
- Any approved accounting request and destination response.
Nexus runs on premises, in private or sovereign cloud, or air-gapped. Credentials stay in the vault, roles decide who can approve, and the execution record stays inside your deployment boundary.
Sovereignty and deploymentRelated
Patterns, connectors and next steps
- Stripe-Xero integration
Integration pattern · Billing events become reconciled accounting entries with exceptions reviewed.
- Stripe connector
43 pre-built actions
- Xero connector
41 pre-built actions
- OpenAI connector
25 pre-built actions
- ServiceNow connector
55 pre-built actions
- Compliance evidence
Evidence produced by the work itself.
- Lead to account and ERP handoff
Another financial services use case.
FAQ
Questions about this use case
- Does Nexus replace any of these systems?
- No. Each system keeps its own records. Nexus runs the process between them and records each decision.
- How does the run start?
- Reconciliation identifies a Stripe payment or settlement item that does not match the available Xero records.
- What if a step is not covered by a pre-built action?
- The model step runs against the AI provider you choose, including Anthropic, Google Gemini or a model you host yourself. Anything outside a pre-built action runs through an API, protocol or database call, or as Rules + Code in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the same approvals and audit.
- Can we define our own exception types?
- Yes; the workflow uses a versioned category set and routes model outputs only to allowed queues.
- Can classification alone mark a payment reconciled?
- No; reconciliation requires the configured evidence checks and finance-authorized resolution, not just a plausible label.
Use case review
Discuss this use case
Bring your version of the process. We will map the systems, approvals and evidence it needs.