Connect Campfire to Cryptoworth, import your chart of accounts, and map your journal accounts. Then review your crypto journals before sending them to Campfire.
Connecting the app does not post journals. You choose when to send approved entries.
Before you start
You need the correct Cryptoworth entity and access to the matching Campfire account.
Your Campfire administrator must approve an API user that can read GL accounts and post the required journal entries.
An API key lets Cryptoworth connect to Campfire. Use a dedicated API user for this connection.
1. Create your Campfire API key
The Campfire pictures show a public example account. Use your own user name and email address. Account details and API keys are hidden.
In Campfire, click Settings in the left sidebar.
Scroll to Developer and select API Keys.
Click New User. Some Campfire versions call this Create User.
Enter a clear Name, such as Cryptoworth Integration, and an Email managed by your organization.
Set the access approved by your Campfire administrator.
The pictured form uses Is Super User. Other versions use role names such as admin, clerk, and view only. A view-only user cannot post journals; a clerk can post draft entries. Have your administrator confirm the access needed for this connection.
Check the API user details, then click Save.
On the saved API user, click Create API Key.
Copy the key shown in API Token and store it securely before closing the window.
Campfire displays the full key only once. The key in the picture is hidden.
2. Connect Campfire in Cryptoworth
Open the correct entity in Cryptoworth. Go to Integrations > Apps.
Find Campfire, then click its Connect button.
Paste your Campfire API key into API Key.
The example leaves the field empty to keep credentials private.
Check that the key belongs to the intended Campfire account, then click Connect.
3. Import your chart of accounts
A chart of accounts is the list of GL accounts in Campfire. Import it so Cryptoworth can use those accounts when it builds journals.
Go to Subledger > GL Sync > Chart of Accounts.
Open the dropdown beside New.
The next two pictures show the Campfire import menu in an older Cryptoworth layout. Use the current path above to reach Chart of Accounts.
Choose Sync Accounts with the Campfire logo.
Select the accounts you need, or choose the option to import all accounts.
Click Next, then Submit. Check the imported account names and GL account IDs.
Importing accounts does not post journals. If Sync Accounts is missing, first confirm that Campfire is connected.
For the full import procedure, see Importing Your Chart of Accounts.
4. Map your journal accounts
Mapping tells Cryptoworth which Campfire GL account should receive each journal line.
Open the GL account mapping for your connected Campfire app. Map the required defaults, then save your changes.
What you are mapping | What to choose |
Crypto asset balance | The GL account that holds your digital assets. |
Realized gains and losses | The gain and loss accounts used by your accounting policy. |
Transaction and network fees | The appropriate fee or expense account. |
NFTs, if used | The GL account used for NFT holdings. |
For example, Digital Assets and Network Fees are possible account names. Use your own chart of accounts.
Use classification, connection, or asset mapping when your reporting needs more detail. These can route a type of activity, a wallet or exchange, or a specific token to its own GL accounts.
Check the saved mappings before syncing. An account that exists in Campfire still needs to be imported and mapped in Cryptoworth.
See General Ledger Account Mapping for the mapping procedure.
5. Review the journals before posting
First, reconcile your crypto records and complete the classifications and fair market values. Run a cost basis calculation for the period you want to post. Review Checks and the results. Publish the approved transaction values and wait for publishing to finish.
Then use this order:
Open Subledger > GL Sync > Sync.
Select the reviewed, published Calculation. Under Connected To, select your Campfire connection.
Choose Realized. Review any ERP Readiness issues and correct the required setup.
Open Sync to GL. Under VIRTUAL, choose your Campfire connection and review the scope before starting the virtual sync.
Virtual sync prepares journals inside Cryptoworth for review. It does not send them to Campfire.
After the virtual sync finishes, open Journals, then Journals (ERP) under Connected Accounting System (ERP).
This picture shows the shared ERP journal view in a demo portfolio. Its table is empty and the connection details are hidden. It does not show a completed Campfire posting.
Check the period, source references, debit and credit accounts, fees, and gains or losses. Debits and credits must balance. Resolve any issues before posting.
For the full review workflow, see How to Review, Correct, and Sync Crypto Journals to Your ERP.
6. Post the approved journals and check the result
When the journals are approved, return to Sync. Confirm the calculation, Campfire connection, and Realized scope. Open Sync to GL and select your Campfire connection under ERP. Review the posting scope, then confirm it.
This ERP sync sends journal entries to Campfire. Selecting the Realized tab alone does not post anything.
Open GL Sync > History and match the operation's Service, Type, Status, and Calculation.
The example history has no sync records. In your portfolio, wait for the operation to finish and confirm that it was an ERP posting to Campfire, rather than a virtual sync.
Finally, open Campfire and check the journals there. Match the dates, GL accounts, debit and credit amounts, and references to the reviewed Cryptoworth journals.
In the Cryptoworth Campfire walkthrough, the journals are reviewed under Accounting > General Ledger. Filter to the same posting period and open an entry. Its details include references such as the Cryptoworth ledger ID and on-chain transaction ID.
Keep the sync record and journal references with your close or audit workpapers.
If something does not work
Problem | What to check |
Campfire will not connect | Check that you copied a Campfire API key without extra spaces. Confirm that the key is active and its role permits the connection's work. |
The account import list is empty | Check the existing Cryptoworth chart first. The accounts may already have been imported. |
A GL account is missing from mapping | Confirm that it exists in the intended Campfire account, import it, then return to mapping. |
ERP Readiness shows an issue | Review the connection, imported accounts, required defaults, and affected mappings. |
No journals appear in Campfire | Check History. A virtual sync stays inside Cryptoworth. Also check the Campfire account and date filter. |
A job is running, fails, or times out | Read its status and error. Check Campfire for entries already created before retrying. |
Campfire rejects a journal | Follow the returned error. Check the posting period, account availability, and integration permissions. |
Contact Cryptoworth support through the in-app chat if you need help. Include the entity, calculation ID, sync time, and error text. Keep the API key out of the message.