Billing / Invoices Q&A

The following is a list of common questions, and NODE40’s answers, to various inquiries from customers regarding administrative matters for invoicing, renewals, etc. 

NODE40’s pricing is based on each “profile”. What is a “profile”?  If a company with several entities in its group desires separate data for each entity, does that mean that each entity is a separate “profile”?

• “Profile” refers to a collective set of sources loaded for each entity.

• For example, if a client has 4 entities that are part of a consolidated operation and the client and wants to have separate financial data for each, NODE40 would invoice the company for 4 profiles.

When does NODE40 invoice for a profile?

• We invoice within 30 days of the date that data is first loaded on NODE40 Balance. So if data is loaded on July 1, we will strive to send an invoice out during the month of July. 

The Order Form states that the profiles are billed at different tiers once a profile exceeds a transaction count (“Txn Count”) for that tier.  How are transaction counts determined?

• General. We have a tier-based pricing model based on transaction count (also known as “records” on the NODE40 Balance user interface). The transaction count details for our pricing tiers is in our Order Form. The transaction count includes all transactions for data loaded onto NODE40 (whether it is data from a Centralized Exchange, on-chain data, X-pub key, a custom upload, or other data). A transaction represents every movement of assets.  For example if Digital Asset A is exchanged for Digital Asset B, there are two movements that result in two transactions.  Additionally fees can be added as one more transaction if fees are paid in fiat or a digital asset other than the one exchanged (e.g., Digital Asset A for Digital Asset B with a fee paid in Digital Asset C (e.g., a stablecoin) or fiat). Also, each transfer is one transaction.

• Decentralized Finance (“DeFi”). Any movements of assets in a DeFi operation could result in multiple movements of assets. For example, if user engages in a DeFi operation to collateralize BTC to borrow USDC, the DeFi contract may programmatically create multiple asset movements to economically reflect the transaction (e.g., Wrap the BTC into wBTC first and then transfer the wBTC to collateral, etc.). We note this point because it is possible that two transactions plus a fee transaction on a DeFi protocol could result in several additional transactions. 

• Transaction count date. We count the transactions as of the last sync (update) to NODE40 Balance before the billing date. For example if there was a sync on your profile on July 1, 2024, we would count the transactions as of that date and issue an invoice in July.  

• Deleted profiles or ledgers.  The transaction count would not include deleted ledgers. It also does not count “test” profile data where you have tested our platform for a period of time. 

The Order Form states that the “Txn Count” for each type of tier is based on the aggregate transaction count for each profile, irrespective of the year of the transaction. How is the “aggregate” count determined? Also, if a profile’s “aggregate” count crosses over into a higher tier during my initial subscription (or renewal) year, how is that invoiced? 

• Our tier-based pricing model based on transaction count takes into account aggregate data (i.e., all data on our platform for all years).  If a customer adds transactions for a prior year and continues to add transactions for future years, all of those transactions are added to determine the tier. 

• If the transaction count for a profile during the subscription year (or any future renewal year) exceeds the current tier, the profile will be billed at a higher tier. We check transaction counts monthly and would send an invoice for the amount owed for the higher tier that month. 

• For example, if customer A creates a profile on July 1, 2023 for transactions in 2020-2022 with a transaction count of 9,000, we will bill for that tier in July of 2023.  If customer A adds 100,000 transactions in December 2023 for transactions in 2023 with an aggregate transaction count of 109,000, we will bill for a higher tier in December of 2023.

Where can I see my transaction count?

• To see your transaction count (also known as “records” on the NODE40 Balance user interface), login to NODE40 Balance and go to the “Timeline” view. You see the transactions count as "Records" in the Timeline view in the middle of the page. Here is a sample screenshot:  see "showing 1-50 of 9,222 records" which means there is an aggregate transaction count of 9,222.