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 renewal year (as applicable) exceeds the current tier, the profile will be billed at a higher tier effective at the beginning of the subscription year or renewal year (as applicable). 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 effective for the the subscription year that began on July 1, 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.

How does pricing work for renewals past Year 1?

• We price (and invoice) for each profile annually. So if you signed up for NODE40 and loaded all of your sources on July 1, 2024, we would invoice for usage for the period of July 1, 2024 through June 30, 2025 based on the transaction count model discussed above. On July 1, 2025, assuming there is a renewal, you would start a new renewal year for the period of period of July 1, 2025 through June 30, 2026 and we would invoice you again that month of July 2025 and so on for each year.

• As mentioned above, we have a tier-based pricing model based on transaction count based on aggregate data (i.e., all data on our platform for all years). If your transaction count on the renewal date (or any future date during the renewal year) exceeds the current tier, your billing will be moved to a higher billing tier.

How do renewals work if my company is a third-party service provider and the profiles that being renewed are for another client (e.g., CPA firm A loads profiles for client 1, 2 and 3)?

• Let’s explain with an example. Assume the CPA firm's contract starts in March 2024 and lasts 3 years through March 2027.   If a client is onboarded in September 2024, the client profile is invoiced based on transaction counts for the period of Sept 2024 through August 2025 (which can include transactions going numerous years back into history based on the aggregate transaction count billing discussed above).  The renewal is Sept 2025 for that profile.  The renewal pricing will be based on all transactions stored on NODE40's platform including the transactions loaded during the Sept 2024 through August 2025 customer account period plus any additional transactions loaded during the Sept 2025 through Sept 2026 renewal period.  Under this structure, assuming the CPA firm contract expires with no renewal in March 2027, we would still allow access to use our platform through the August 2027 expiration date for that profile. 

The Order Form indicates that NODE40 charges a flat fee for each instance where one or more Solana addresses is loaded. How does that work?

• For purposes of efficiency and reduction of data costs, NODE40 charges a flat fee for each instance where one or more Solana address is loaded. For example, assume the flat fee is $100 per instance where where one or more Solana address is loaded. If a customer has ten Solana addresses and the customer loads five addresses on January 1 and five addresses on February 1, the customer will incur a $200 fee (i.e., $100 for the five addresses loaded on January 1 and $100 for the five addresses loaded on Febuary 1). Alternatively, if the customer had loaded all ten addresses on one day (e.g., January 1), the customer would have incurred a $100 flat fee.