Connect Rillet to Cryptoworth, import your chart of accounts, and map your journal accounts. Then review your crypto journals before sending them to Rillet.
Before you start
You need access to the correct Cryptoworth entity and the matching Rillet organization. If API access is not available, ask your Rillet contact to enable it first.
An API key lets Cryptoworth connect to Rillet. Have your administrator approve a key with write access for journal posting. A read-only key cannot create journal entries.
1. Create your Rillet API key
These Rillet pictures come from public example accounts. Use your own organization and key name. The key-generation form is blank in the example, and the generated key is hidden.
In Rillet, click your account name or account icon in the lower-left corner.
Select Organization Settings.
In Settings, select API Access.
Click Create API key.
In API Key Name, enter a clear name, such as Cryptoworth Integration.
Leave Read-only unchecked so the key can post journal entries.
Check the name and access, then click Create API Key.
The button is disabled in the blank example. Enter your key name before creating the key.
Copy the full key from Your API key and store it securely before closing the window.
Rillet shows the full key only once. The key in this picture is hidden.
Rillet explains API access in Getting Started with Rillet.
2. Connect Rillet in Cryptoworth
Note: Connecting the app does not post journals. You choose when to send approved entries.
Open the correct entity in Cryptoworth. Go to Integrations > Apps.
Find Rillet, then click its Connect button.
Paste your Rillet API key into API Key.
The example leaves the key field empty to keep credentials private.
Check that the key belongs to the intended Rillet account, then click Connect.
How Rillet setup differs from other connectors
Setup point | What to do for Rillet |
Connection method | Use a Rillet API key. There is no browser sign-in step in this connector form. |
API access | Have Rillet enable access before creating a key in Organization Settings. |
Credentials | Cryptoworth asks for one API key. The form has no Client ID, Client Secret, certificate, or Redirect URL fields. |
Key permissions | Use write access for journal posting. A read-only key cannot create journal entries. |
Test environments | The current Cryptoworth form has no environment selector. Confirm sandbox support with Cryptoworth before using a test key. |
The account import, mapping, and journal review steps use Cryptoworth's shared GL workflow.
3. Import your chart of accounts
A chart of accounts is the list of GL accounts in Rillet. 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. Choose Sync Accounts for Rillet.
Select the accounts you need, or choose Sync 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 Rillet is connected.
For the full import procedure, see Importing Your Chart of Accounts.
4. Map your journal accounts
Mapping tells Cryptoworth which Rillet GL account should receive each journal line.
Open the GL account mapping for your connected Rillet 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.
Add more detail when your reporting needs it:
Classification mapping: Use the right income, expense, or other account for each type of activity.
Connection mapping: Give a wallet or exchange its own accounts.
Asset mapping: Give an asset, such as BTC or ETH, its own accounts.
Check the saved mappings before syncing. An account that exists in Rillet still needs to be imported and mapped in Cryptoworth.
See General Ledger Account Mapping for the mapping procedure.
5. Review the journals before posting
Start with reconciled crypto records, complete classifications, and correct fair market values.
Run a cost basis calculation for the period you want to post. Review Checks and the transaction results. Publish the approved transaction values and wait for publishing to finish.
For help with this part, see How to Run a Calculation.
Open Subledger > GL Sync > Sync.
The GL pictures below show shared navigation in a demo portfolio. They have no Rillet posting result, and the connection details are hidden.
Select the reviewed, published Calculation. Under Connected To, select your Rillet connection.
Choose Realized. Review any ERP Readiness issues and correct the required setup.
Open Sync to GL. Under VIRTUAL, choose your Rillet connection. Check the scope, then start the virtual sync.
Virtual sync prepares journals inside Cryptoworth for review. It does not send them to Rillet.
After the virtual sync finishes, open Journals, then Journals (ERP) under Connected Accounting System (ERP).
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
Return to Sync. Confirm the calculation, Rillet connection, and Realized scope. Open Sync to GL and choose your Rillet connection under ERP. Check the posting scope, then confirm it.
This ERP sync sends journal entries to Rillet. Selecting the Realized tab alone does not post anything.
Open GL Sync > History. 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 Rillet, rather than a virtual sync.
Open Rillet and check the journals there. Match the dates, GL accounts, debit and credit amounts, and references to the reviewed Cryptoworth journals.
Keep the Rillet journal references and Cryptoworth sync record with your close or audit workpapers.
If something does not work
Problem | What to check |
You cannot find API Access in Rillet | Ask your Rillet contact to enable access. Confirm that you are in the intended organization. |
Rillet will not connect | Check the copied key and confirm that it is active. If it is a test key, confirm that the Cryptoworth connection supports that environment. |
Connection works but journal posting is rejected | Have your administrator check write access. A read-only key cannot create journals. Also follow the job's error for period or account restrictions. |
A GL account is missing | Check the account in Rillet, import the chart of accounts again, and review the mapping. |
ERP Readiness shows an issue | Correct the connection, account import, required defaults, or affected mappings, then re-check. |
History shows success but Rillet has no entries | Confirm that the operation used the ERP destination. A virtual sync does not post to Rillet. Check the organization, period, and references too. |
A job is still running or its result is unclear | Check the existing job and Rillet for partial posting before retrying. Keep the job details so you can avoid duplicate journals. |
Rillet reports a rate limit | Let the existing operation settle and follow the returned error. Avoid starting repeated sync jobs. |
If you need help, contact Cryptoworth through the in-app chat. Include the entity, calculation ID, sync time, and error text. Do not send the API key.