Ramp-to-ERP Accounting Sync

Overview

Mirror ERP coding structures into Ramp, pull only eligible objects, post them once to the ERP, and send explicit success or failure receipts back to Ramp. Preserve entity boundaries and an auditable idempotency ledger.

Prerequisites

• Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary.
• Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation.
• Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved.
• Prepare approved secret storage and a sanitized evidence location.

Current Contract

• An API accounting connection is distinct from Ramp's direct ERP integrations; direct connections are blocked from API sync marking by default.
• Sync-ready filters differ by object type. Transactions and several objects use sync_status=SYNC_READY; bills use sync_ready=true.
• POST /developer/v1/accounting/syncs accepts an idempotency key, sync type, and explicit successful or failed object receipts.
• Multi-entity reads must be scoped with entity_id, and Ramp IDs used for accounting selections differ from ERP remote IDs.