--- title: "Claims and billing - Stacksync" description: "Move X12 837 claims and 835 remittances between providers, clearinghouses, and your ERP in real time, fully audited and replayable, so denials don't pile up." canonical: https://www.stacksync.com/use-case/claims-and-billing last_modified: 2026-07-05 --- Stacksync × Supabase Miami: **AI-Native Operations** Oct 13 [Reserve your spot](https://www.stacksync.com/events/2026-10-13-supabase-miami) Audited, replayable X12 claims flow # Claims and billing from encounter to payment > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Route X12 837 claims and 835 remittances between your practice systems, clearinghouses, and NetSuite or SAP the moment a claim is ready, fully audited and replayable so finance can trace every dollar. [Book a demo](https://www.stacksync.com/book-a-demo) [Talk to a solutions architect](https://www.stacksync.com/book-a-demo) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Where claims and revenue leak ## Three reasons claims stall before they're paid. A clean claim crosses four systems and two EDI standards before it pays. Each handoff is a place revenue gets stuck or lost. 01 - Lost in EDI ### An 837 leaves but no 835 ever returns A claim posts to the clearinghouse and then goes dark. Without acknowledgment tracking, billing teams discover the gap weeks later when the remittance never lands in the ERP. RELIABILITY 02 - Manual posting ### 835 remittances re-keyed by hand Payers return 835 files that someone types into NetSuite line by line. The lag delays cash posting and every keystroke risks a mismatch finance has to chase. LATENCY 03 - No replay ### A retry double-bills the payer When a submission retries, naive pipelines fire a second 837. The payer flags a duplicate claim, the denial bounces back, and AR ages while staff untangle it. IDEMPOTENCY PLATFORM ## Six products. One Platform. Replace many legacy vendors. Every tool Stacksync replaces is one fewer vendor, one fewer bill, one fewer integration to maintain. [Start building now](https://www.stacksync.com/book-a-demo) ### [Two-way sync](https://www.stacksync.com/two-way-sync) Changes made in one platform automatically update across all connected systems in real time, eliminating data silos and reducing errors. Replaces: Heroku Connect and Salesforce Data 360 Heroku Connect Salesforce Data 360 ### [Workflow automation](https://www.stacksync.com/workflow-automation) Stop building brittle API scripts. With Stacksync, you can trigger complex automated workflows using simple SQL commands. Replaces: Workato and Boomi ### [AI Agents](https://www.stacksync.com/ai-agents) Expose every enterprise system to your agents through a single MCP layer. Claude, ChatGPT and Gemini get production-grade tools without custom glue code. Natively available in: Claude and ChatGPT and Gemini Claude ChatGPT Gemini ### [Event queues](https://www.stacksync.com/event-queues) Handle massive traffic spikes without losing a single event. Queues buffer your data during surges, ensuring strict ordering and reliable delivery. Replaces: Kafka and Amazon SQS and Confluent Kafka Amazon SQS ### [Database hosting](https://www.stacksync.com/database-hosting) Interact with your CRM, ERP, and payment tools as if they were just another table in your database. Say goodbye to rate limits and complex API documentation. Replaces: AWS RDS and Self-hosted databases AWS RDS Self-hosted databases ### [EDI](https://www.stacksync.com/edi) Transform legacy EDI complexity into simple database interactions. Stacksync automatically parses incoming EDI documents directly into your database tables. Replaces: SPS Commerce and TrueCommerce [Start building now](https://www.stacksync.com/book-a-demo) Connectors ## Every system a claim touches, on one sync. Stacksync ships pre-built two-way connectors for the practice systems, clearinghouses, and ERPs claims run through, with idempotent writes, full audit logs, and event replay. Practice & EHR 05 - Epic - Cerner - athenahealth - eClinicalWorks - NextGen Healthcare EDI & clearinghouse 05 - X12 837 - X12 835 - Redox - Availity - Change Healthcare ERP & finance 05 - NetSuite - SAP - Workday - Oracle DB - Microsoft 365 Reporting & alerts 05 - Snowflake - BigQuery - Postgres - Slack - Twilio Custom payer rules, X12 segment overrides, and your own claim schema are first-class, no scripting required. [Browse all 1,000+ connectors](https://www.stacksync.com/connectors) SECURITY ## Security teams trust Stacksync As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers. [Learn more about security](https://www.stacksync.com/security) | | | | --- | --- | | | SOC 2 Type II | | | ISO 27001 | | | HIPAA BAA | | | GDPR | | | CCPA | | | DPF US-EU-UK-CH | → SECURITY WITH BENEFITS ### SSO & SCIM Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more. ### Alerts Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options. ### Secure connection options Securely connects to your systems with: [OAuth 2](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more Common questions ## Common questions about claims and billing sync. The concerns every revenue-cycle and finance team raises before automating X12 claims off manual posting. [Talk to a solutions architect](https://www.stacksync.com/book-a-demo) ### Do you track 837 acknowledgments and matching 835s? Yes. Every 837 is keyed and tracked, and the returning 277 or 835 reconciles against it automatically, so an unpaid or unacknowledged claim surfaces instead of going silent. ### How do you prevent duplicate claim submissions? Every sync is idempotent, keyed on the claim ID. A retried or replayed submission updates the existing claim rather than firing a second 837, so payers never see a duplicate. ### Is the full claim lifecycle auditable for compliance? Yes. Each segment exchange is logged with timestamp, payer, and amount, and every event is replayable, so finance and auditors can trace any claim end to end. ### Can we post 835 remittances straight into the ERP? Yes. Parsed 835 line items map to NetSuite or SAP postings in the visual mapper and post in real time, so cash lands without manual re-keying. ## Stop chasing lost claims by hand. Post every 835 in real time. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)