Add wallet and transactions manually

To manually import transactions, go to Wallets > Track account/wallet > Import transactions manually.

How does it work?

Each transaction needs to be tied to a wallet, so that Multis can compute the balance of the wallet containing the manually imported transactions.

When creating a manual wallet, the following information needs to be filled:

• Wallet name: This will appear on your transaction history and exports.

• Wallet description: This will only appear on the wallets tab, for internal purposes

• Wallet ID: This allows Multis to dissociate wallet. You can define this ID the way you want. It will have no impact on the rest.

To import transactions, download the sample CSV by clicking on the button. We recommend working within our sample to make sure the entries are in the appropriate format.

Once done, be sure to import the file on Multis in a CSV format.

Data collected must be accurate and according to the requirements mentioned below.

Good to know

• You can add as many transactions to a manually created wallet.

• Transactions can be added later to a manually created wallet

• You can have multiple manually created wallet.

Columns requirements

transactionDate

• This column must be filled.

• This is the date at which the transaction happened

• Date format must be ISO-8601 (YYYY-MM-DD). Examples include:

  • 20230810

  • 2023-08-10

  • 2023-08-10 12:59

  • 2023-08-10 12:59:59

  • 2023-08-10 12:59:59.999

  • 2023-08-10 12:59:59.999Z <-timezone

  • 2023-08-10 12:59:59.999+02:00 <-timezone

  • 2023-08-10T12:59

  • 2023-08-10T12:59:59

  • 2023-08-10T12:59:59.999

  • 2023-08-10T12:59:59.999Z <-timezone

  • 2023-08-10T12:59:59.999+02:00 <-timezone

orderType

• This column must be filled and typed in lower case.

• Accepted orderType: withdraw, deposit

• To record a swap, you'll need to create one withdraw and one deposit line, with the same transaction id.

• To record a mass payment, you'll need to create as many withdraw or deposit transfers line with the same transaction id.

txID

• This column must be filled.

• The ID can be set by yourself, according to your internal standards. We do not require the crypto transaction hash

• Every ID corresponds to a single transaction, but multiple movements may share the same hash if they belong to the same transaction, for instance for a swap or a mass payment.

asset

• This column must be filled and typed in capital case.

• Multis maintains a token whitelist. If you wish to import transactions involving a custom token, follow these steps:

  • Go to Settings in your Multis workspace > Token whitelist > Add token

• Asset symbols should be like on Coingecko and/or Coinmarketcap

amount

• This column must be filled.

• This is expressed in the currency of the asset column.

• The integer part and the decimal part must be separated by a single dot. The comma is not a valid separator, only the dot is.

feeAsset

• This column can be left empty

• This is the asset in which the fees are paid.

feeAmount

• This column can be left empty

• This is expressed in the currency of the feeAsset column.

• The integer part and the decimal part must be separated by a single dot. The comma is not a valid separator, only the dot is.

counterpartyAddress

• This column must always be filled.

• 0x address for crypto transactions

• If the 0x address match one of your contact in your Multis address book, it will be automatically enrich accordingly.

note

• This column can be left empty

• If filled, no restrictions on formatting.

• This will appear as the note of the transaction in your history and exports

category

• This column can be left empty and typed in lower case.

• If filled, the category needs to match one category of your workspace. To add a new category, first create it on Accounting > Categories > Create. Once done, you'll be able to input transactions with this category assigned

• Category should be formatted with lowercases and with "-" instead of spaces

  • Cash Expenses on Multis should be cash-expenses on the CSV

  • Internal should be internal

• This will appear as the category of the transaction in your history and exports