Agent skill · software engineering · jeremylongshore
ramp-core-workflow-b
Implement a reconciled two-way Ramp accounting integration for chart-of-accounts data and sync-ready spend objects. Use when exporting transactions, bills, reimbursements, transfers, or cashbacks to an ERP. Trigger with "Ramp accounting sync" or "Ramp ERP integration".
Why this skill is useful
Adds executable scripts for managing corporate card transactions and syncing to accounting systems that aren't in public docs.
What it needs
Requires curl, npm installed locally. Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 syncstatus=SYNCREADY; bills use syncready=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 entityid, and Ramp IDs used for accounting selections differ from ERP remote IDs. Instructions 1. Inventory entities, object types, chart fields, remote IDs, tax/vendor relationships, direct integrations, owners, and the reconciliation period. 2. Push or update chart-of-accounts structures in bounded validated batches; retain Ramp IDs and ERP remote IDs in a typed mapping table. 3. Fetch each eligible object type with its documented ready-to-sync filter and paginate completely within one entity at a time. 4. Post to the ERP using a stable source-object key, then record the ERP reference and only afterward submit the Ramp success receipt; submit structured failure receipts for rejected objects. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-core-workflow-b