Reconcile Stripe payments against Xero records

About Stripe and Xero

Stripe

Source

The Stripe integration connects your payment infrastructure to Well via MCP, pulling charges, invoices, subscriptions, refunds, and payout data into your workspace automatically.

Xero

Target

The Xero integration connects Well to your accounting platform for bidirectional data flow.

1. 1

   Connect Stripe

   Click Connect with Stripe; Stripe's MCP server handles authorisation. Stripe's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.

   • AuthOAuth 2.0
2. 2

   Map your accounts

   Well discovers Stripe's charges, refunds, payouts, customers, disputes, and subscription events and the the Xero draft bills queue populated by Hubdoc. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.

   • Auto-post above85% confidence
   • Overridemanual anytime
3. 3

   Connect Xero

   Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.

   • AuthOAuth 2.0
   • First syncup to an hour

01Will every Stripe record post to Xero automatically?

Not always. Within seconds of Stripe firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Xero email-in address and Xero drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

02How does Well match Stripe records to entries in Xero?

Every Stripe charge is scored against your open Xero sales invoices and existing customer records on customer name, amount, currency, and reference. Above 85% the charge collapses onto the right invoice and Stripe reconciliation builds the matched journal entry in Well's ledger, the ledger accounts mapped and the matched customer and payment pre-filled, ready for you to post to Xero. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.

03What happens to historical Stripe data when I first connect to Xero?

Stripe exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Xero ledger, and re-running the backfill is safe because Well tracks the Stripe record IDs and updates existing Xero entries instead of duplicating them.

04How does Well prevent duplicates when posting Stripe records to Xero?

Stripe sends each event with a stable resource ID that Well tracks against the Xero ledger. Webhook replays (which Stripe can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Xero entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

05Can I customise which Stripe fields are sent to Xero?

The default mapping covers every Stripe field your Xero chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Xero does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Xero is left exactly as it stands.

06How does Well authenticate with Stripe and Xero?

Stripe's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted in transit under TLS 1.3. Anything Well holds between Stripe and Xero is encrypted at rest and handled in line with GDPR.