> ## Documentation Index > Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt > Use this file to discover all available pages before exploring further. # Campspot Integration: Setup and Sync > Request the Campspot integration from DualEntry to sync each campground and RV park's daily point-of-sale activity into your ledger automatically. [Campspot](https://software.campspot.com/) is management software for campgrounds and RV parks that handles reservations, front desk, camp store sales, and payments. The DualEntry Campspot integration syncs each park's point-of-sale (POS) activity into DualEntry once a day through Campspot's API, replacing the manual cycle of downloading flat files from Campspot and uploading them to your ledger. The Campspot integration is available, but DualEntry enables it for each account. It does not appear as a self-serve tile in the Integrations screen. To turn it on, contact your DualEntry account team or email [ask@dualentry.com](mailto:ask@dualentry.com). ## Prerequisites The Campspot integration posts to companies, accounts, and classifications that already exist in DualEntry. It does not create them, so a mapping that points to a missing or inactive record stops that part of the sync. Set the following up before you request the integration: * **Companies**: Create a DualEntry company for each legal entity that owns one or more parks. See [Multi-entity consolidation](../../platform-configuration/multi-entity-consolidation) for how companies and intercompany activity work. * **Chart of accounts**: Finalize your [chart of accounts](../../core-financials/general-ledger/chart-of-accounts) so the revenue, tax, and payment accounts that Campspot activity posts to exist and are active. Depending on how you run your parks, Campspot activity may include site rentals, camp store sales, fees, sales and lodging tax, and card payments. * **Classifications**: If you report by park, set up a [classification](../../platform-configuration/classifications) with one line per park, so you can tag Campspot activity by park in your reports. * **Campspot access**: Have a Campspot administrator ready to provide API access for each park you want to connect. ## How the Campspot integration works The Campspot integration replaces a file-based workflow with a daily API sync. Without it, your team downloads a file from Campspot for each park and uploads it to the ledger, a job that grows with every park you add. Once DualEntry enables the integration for your account, it runs on a daily schedule and does three things: 1. **Reads** the latest POS activity for each connected park from the Campspot API. 2. **Maps** that activity using the park-to-company and category-to-account mappings you set up with DualEntry, so each park's activity lands in the right company and on the right GL accounts. 3. **Records** the activity in your ledger, where it is available for [bank matching](../../core-financials/close-management/bank-match/index) against deposits and for period-end close. Campspot remains the system of record for reservations, guests, and POS transactions. DualEntry holds the accounting view of that activity. The integration suits operators who run several parks, often with each park held in its own legal entity, because those operators carry the most manual file work today. Single-park operators follow the same setup with one park to map. ## How to request the Campspot integration DualEntry sets up the Campspot integration with you rather than through a self-serve screen. Complete the [prerequisites](#prerequisites) first, then work through the park and account mappings with the DualEntry team before the first daily sync runs. 1. Contact your DualEntry account team or email [ask@dualentry.com](mailto:ask@dualentry.com) and say you want to connect Campspot. 2. Share the list of parks you want to sync and the DualEntry company each one belongs to. 3. Provide Campspot API access for those parks, following the steps DualEntry sends you. 4. Review the account mapping with DualEntry, so each Campspot revenue, tax, and payment category maps to a DualEntry GL account. 5. Agree on a sync start date with DualEntry. If you need activity from before that date, load it with [bulk import](../automation-and-developer-tools/bulk-import), which brings records into DualEntry from a CSV or XLSX file. 6. Compare the first few days of synced activity against Campspot's own reports for each park before you stop the manual download-and-upload process. After completing these steps, each connected park's Campspot activity appears in its DualEntry company every day without a manual upload. ## Troubleshoot Campspot sync problems Most Campspot sync problems trace back to a park or account mapping that no longer matches your DualEntry or Campspot setup. The table below lists common symptoms and what to check. | Symptom | Likely cause | What to do | | - | - | - | | A park's activity is missing for a day | The sync for that day failed, or the park's Campspot API access changed. | Check the sync status, then [retry or resync](../managing-syncs) the day. If it fails again, contact DualEntry support. | | Activity posts to the wrong company | The park is mapped to the wrong DualEntry company. | Ask DualEntry support to correct the park mapping, then resync the affected days. | | A sync fails on an account | A Campspot category points to a GL account that is missing or inactive, or a new category has no mapping yet. | Reactivate the GL account in your chart of accounts, or ask DualEntry support to map the new category. | | A new park is not syncing | The park was added in Campspot after setup. | Send DualEntry the park name and its DualEntry company so it can be added to the integration. | When you contact support at [ask@dualentry.com](mailto:ask@dualentry.com), include the park, the date that is missing or wrong, and the Campspot report total you expected. That lets the team compare the two without a round trip. ## Related Use these pages to compare the Campspot integration with other connectors and to find the next step after setup: * [Revenue and Accounts Receivable](./index): other integrations that bring sales and payment activity into DualEntry. * [Storage Solutions](../storage-solutions/index): daily-activity integrations for self-storage operators, such as [SiteLink](../storage-solutions/sitelink). * [Retry, resync, and archive](../managing-syncs): the sync actions available on every connector. * [Integrations](../index): the full connector catalog. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.