Download a copy of the template
Meaning of the columns
Column | Description |
Date | The date when the transaction occurred. It can be provided in almost any format. Examples include:
If no timezone is provided, Syla will default to Australian Eastern Standard Time (AEST)
ISO8601 (recommended) We recommend using ISO8601 format where possible, as it avoids ambiguity and includes a timezone. Format: Example: |
Ledger Type | Use one of the standard ledger types to classify why the change in balance occurred.
You can enter the Name of any valid Ledger Classification available in Syla:
e.g. Deposit, Disposal, Acquisition, Brokerage Fee, ...
Note: Capitalisation and spacing do not matter. e.g. Brokerage Fee, brokerage fee, and brokeragefee are all valid. |
Amount | The amount your balance changed by. The direction (positive or negative) will be inferred based on the Ledger Type used.
e.g. a Deposit will increase your balance, a Withdrawal will decrease your balance. |
Asset | The common ticker code for the asset, e.g. BTC. |
Market Value (optional) | The total market value of the ledger in AUD.
e.g. if the Amount is 10, the Asset is BTC and the Market Value is 100,000. Then it means the total value of 10 BTC at the time of the transaction is $100,000 AUD. |
Description (optional) | Add an optional description to your transaction. |
Transaction Hash (optional) | Add an optional transaction hash to your transaction. |
Ledgers
Each row in the CSV template represents a Ledger that Syla imports. For example, a simple deposit can be entered as a single row in the CSV, like this:
Transactions
If multiple changes occur within the same transaction, you can add multiple rows to the CSV file, ensuring the Date is the same for all related rows.
All Ledgers with the same Date will be grouped into a single Transaction during the import process.
This allows you to represent complex transactions which contain multiple ledgers.
Example: BTC Purchase with AUD and Brokerage Fee
Here’s how you can enter a trade where Bitcoin is purchased for AUD, with a brokerage fee:
Notice how the date is exactly the same on each of the rows. This is how Syla knows to combine all these rows into a single transaction during the import.
Tip: There’s no limit on which Ledger types can be combined into transactions in Syla. Feel free to use whatever combination best represents and simplifies what occurred in the transaction.
Troubleshooting
If your template import isn't working, check for these common problems:
Error Messages
Syla usually reports import issues. Follow the instructions provided to fix errors in the file.Header Row
Ensure the header row (first row with column names) is included and unchanged from the template.Ledger Type
Verify the Ledger Type exactly matches a ledger name used in Syla. e.g. you can't use "Trade Fee" as this ledger type doesn't exist in Syla, instead use "Brokerage Fee". Refer to Positive Ledger Types and Negative Ledger Types for the complete list.Consistent Date Format
Use the same date format across all rows. Mixed formats may cause issues.
Use the same Date when Grouping Ledgers
If you're trying to group ledgers together, ensure all rows have the exact same date.
If you're still stuck, contact our support team through the in-app chat. We’ll help you identify and resolve the issue.
FAQ
Why are their blank lines in the template?
Why are their blank lines in the template?
Blank lines in the example template are optional and do not affect the import. They are included to clarify which rows share the same Date and will be grouped together during the import.