General Discussions

@Brandon Combs I'd love to hear how this is going for you as we're considering implementing Salesforce.​ While I'm not yet sure what data we might integrate, I'd be interested to hear what type of data you're thinking of pulling in and then how you'd use that within Vena.

Also, thanks for asking that data security question! Always important to keep that top of mind during any integration.

@Brandon Combs I'd love to hear how this is going for you as we're considering implementing Salesforce.​ While I'm not yet sure what data we might integrate, I'd be interested to hear what type of data you're thinking of pulling in and then how you'd use that within Vena.

Also, thanks for asking that data security question! Always important to keep that top of mind during any integration.

Hey Brandon and Brendan! I work on the finance team in Vena so thought I could share my experience as a finance user. We have used our salesforce integration to calculate commissions on a monthly basis for years and have loved it. My biggest piece of advice is to use a functional email address rather than someone's personal work email to create the connection as you can have some rework if they change teams and their access changes. 

Our latest advancement is to bring in customer status and notes from salesforce so we can use them for our weekly collections forecasting. We bring in our invoices from our ERP and then the status field and any notes about the customer to Vena so we can view everything in one place and base our expectations on a complete data source. I have limited salesforce experience so it took me a little time to figure out the scope of data I wanted and how to write the SOQL but it was smooth sailing after that.

My biggest concern with the integration was what if the data I'm integrating is bad (misentered by someone and not verified). We have a few different checks in place to make sure the data has been reviewed by the sales team and the finance team to overcome this, but you can also lock the ARR field after it has been reviewed so it can't be retrospectively updated by anyone outside of finance and this was an important addition for our peace of mind.

Hope this helps!

@Brandon Combs I'd love to hear how this is going for you as we're considering implementing Salesforce.​ While I'm not yet sure what data we might integrate, I'd be interested to hear what type of data you're thinking of pulling in and then how you'd use that within Vena.

Also, thanks for asking that data security question! Always important to keep that top of mind during any integration.

Hey Brandon and Brendan! I work on the finance team in Vena so thought I could share my experience as a finance user. We have used our salesforce integration to calculate commissions on a monthly basis for years and have loved it. My biggest piece of advice is to use a functional email address rather than someone's personal work email to create the connection as you can have some rework if they change teams and their access changes. 

Our latest advancement is to bring in customer status and notes from salesforce so we can use them for our weekly collections forecasting. We bring in our invoices from our ERP and then the status field and any notes about the customer to Vena so we can view everything in one place and base our expectations on a complete data source. I have limited salesforce experience so it took me a little time to figure out the scope of data I wanted and how to write the SOQL but it was smooth sailing after that.

My biggest concern with the integration was what if the data I'm integrating is bad (misentered by someone and not verified). We have a few different checks in place to make sure the data has been reviewed by the sales team and the finance team to overcome this, but you can also lock the ARR field after it has been reviewed so it can't be retrospectively updated by anyone outside of finance and this was an important addition for our peace of mind.

Hope this helps!

@Brandon Combs I'd love to hear how this is going for you as we're considering implementing Salesforce.​ While I'm not yet sure what data we might integrate, I'd be interested to hear what type of data you're thinking of pulling in and then how you'd use that within Vena.

Also, thanks for asking that data security question! Always important to keep that top of mind during any integration.

Hey Brandon and Brendan! I work on the finance team in Vena so thought I could share my experience as a finance user. We have used our salesforce integration to calculate commissions on a monthly basis for years and have loved it. My biggest piece of advice is to use a functional email address rather than someone's personal work email to create the connection as you can have some rework if they change teams and their access changes. 

Our latest advancement is to bring in customer status and notes from salesforce so we can use them for our weekly collections forecasting. We bring in our invoices from our ERP and then the status field and any notes about the customer to Vena so we can view everything in one place and base our expectations on a complete data source. I have limited salesforce experience so it took me a little time to figure out the scope of data I wanted and how to write the SOQL but it was smooth sailing after that.

My biggest concern with the integration was what if the data I'm integrating is bad (misentered by someone and not verified). We have a few different checks in place to make sure the data has been reviewed by the sales team and the finance team to overcome this, but you can also lock the ARR field after it has been reviewed so it can't be retrospectively updated by anyone outside of finance and this was an important addition for our peace of mind.

Hope this helps!

@Brandon Combs I'd love to hear how this is going for you as we're considering implementing Salesforce.​ While I'm not yet sure what data we might integrate, I'd be interested to hear what type of data you're thinking of pulling in and then how you'd use that within Vena.

Also, thanks for asking that data security question! Always important to keep that top of mind during any integration.