Agent skill · marketing growth · jeremylongshore
navan-core-workflow-b
Implement reconciliation of contracted Navan expense data with an ERP or finance control plane. Use when operating the Expense API or a direct accounting integration. Trigger with "sync Navan expenses", "reconcile Navan spend", or "export Navan transactions".
Why this skill is useful
Provides specific patterns for integrating Navan expense reporting with ERP systems and automating workflows that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires navan account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Navan Expense Data Reconciliation Overview Implement reconciliation of contracted Navan expense data with an ERP or finance control plane. This workflow produces an auditable decision or artifact before any live action. Prerequisites Access to the selected tenant's current Navan Help Center and contracted integration documentation. A named business owner and data owner for the travel or expense workflow. A non-production evidence set with secrets and traveler data removed. Current Contract Navan publicly confirms an Expense API for custom ERP systems and direct accounting integrations. Transaction, receipt, reimbursement, approval, and settlement schemas are tenant-specific and must not be guessed from marketing pages. Authentication Separate read-only reconciliation access from any approval, reimbursement, card, or accounting write capability. Limit downstream access to finance roles with an explicit business purpose. Instructions 1. Define the accounting period, entities, currencies, and source record classes. 2. Capture documented identifiers, amount semantics, lifecycle timestamps, and correction behavior. 3. Land source records and evidence hashes without exposing receipt contents in logs. 4. Map accounts, cost centers, tax, projects, and currencies through versioned rules. 5. Reconcile totals and record-level lineage before posting or export. 6. Route exceptions to a human queue and publish only after finance approval. Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. Approval Boundaries Any posting, approval, reimbursement, card action, policy change, or release of receipt data requires explicit authorized-human approval. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/navan-core-workflow-b--095b4c