Do you use the Partner Entity and what for?
32 views
Skip to first unread message
Jim Clay
Feb 15, 2012, 5:18:36 PM2/15/12
to NetSuite.org - Grantees
We have implemented the financial side of NetSuite and are preparing
to bring our Donor Relations side over from another system. One of
the questions I have been wondering about is the "Partner" entity
record. Does anyone use this and how? We have short term and long
term volunteers go to Africa and work with our operations team there
and was wondering if that would be a good use for this record type?
The one thing we need to track with our volunteers is the donations
designated to support them and their mission trip. I am wondering if
the Partner record could be useful for this?
Jim Clay
to bring our Donor Relations side over from another system. One of
the questions I have been wondering about is the "Partner" entity
record. Does anyone use this and how? We have short term and long
term volunteers go to Africa and work with our operations team there
and was wondering if that would be a good use for this record type?
The one thing we need to track with our volunteers is the donations
designated to support them and their mission trip. I am wondering if
the Partner record could be useful for this?
Jim Clay
David Geilhufe
Feb 15, 2012, 8:45:53 PM2/15/12
to NetSuite.org - Grantees
Keep in mind the "partner" and "vendor" entities are just other
dimensions of the customer entity. They carry with them specific
functionality... vendors can ship you product and you can pay for that
product. Partners can sell your items and you can give partners
commissions on their sales. Partners can also log into your system and
enter data if you allow it (i.e. create new donor records, for
example).
If the business goals is to track the revenue earmarked for a specific
trip, I would suggest this:
Each volunteer is a new constituent (i.e. customer record).
Add a custom check box to the customer record to track the long term
volunteers or just use the volunteer check box provided in SuiteDonor.
(now you can generate a search that lists all your volunteers by
looking for all the constituent records with the volunteer box
checked)
Under the long term volunteer, create a project for their mission to
create their donations to their mission.
If others are donating to the mission, I'd either create a custom
record for the missions -- when you get a donation, you can specify
the mission it is for - or I would create a list of missions in the
"class" list and code each transaction appropriately.
Then you can build a report that tracks revenue and expenses by
filtering the transactions according to the custom field or the class.
dimensions of the customer entity. They carry with them specific
functionality... vendors can ship you product and you can pay for that
product. Partners can sell your items and you can give partners
commissions on their sales. Partners can also log into your system and
enter data if you allow it (i.e. create new donor records, for
example).
If the business goals is to track the revenue earmarked for a specific
trip, I would suggest this:
Each volunteer is a new constituent (i.e. customer record).
Add a custom check box to the customer record to track the long term
volunteers or just use the volunteer check box provided in SuiteDonor.
(now you can generate a search that lists all your volunteers by
looking for all the constituent records with the volunteer box
checked)
Under the long term volunteer, create a project for their mission to
create their donations to their mission.
If others are donating to the mission, I'd either create a custom
record for the missions -- when you get a donation, you can specify
the mission it is for - or I would create a list of missions in the
"class" list and code each transaction appropriately.
Then you can build a report that tracks revenue and expenses by
filtering the transactions according to the custom field or the class.
Mark Petzold
Feb 15, 2012, 10:04:04 PM2/15/12
to netsu...@googlegroups.com
I'm not sure if this will help but since we do the same thing I'll explain how we do it.
Our philosophy is that if Netsuite is built to do something a certain way it's best not to complicate things and try to bend it to our way.
Sometimes it's ok to have more that one record for an entity. Take employees for example. I am an employee and a donor so I have an employee record and a donor record. Nothing wrong with that.
People that work overseas (short and long term) get entered into Netsuite as customers and as items. We track all the personal stuff (having to do with the trip) on the customer record. The item record is where all the financial stuff happens. Do you ever see having fundraising online for these people? Like this ...
http://www.fhcanada.org/s.nl/c.364464/it.A/id.13792/.f You'll likely want them as an item record then.
PS: You could even link the two records with a custom field if necessary.
Hope that helps a bit.
-------------------------------------------------
Mark Petzold
Director of Information Technology
FH Canada
www.PovertyRevolution.org
"It's about thriving communities, not dependancy."
-------------------------------------------------
Mark Petzold
Director of Information Technology
FH Canada
www.PovertyRevolution.org
"It's about thriving communities, not dependancy."
--
You received this message because you are subscribed to the Google Groups "NetSuite.org - Grantees" group.
To post to this group, send email to netsu...@googlegroups.com.
To unsubscribe from this group, send email to netsuiteorg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/netsuiteorg?hl=en.
Jim Clay
Feb 16, 2012, 7:55:25 PM2/16/12
to NetSuite.org - Grantees
Thanks Mark - That is a great way of dealing with it. I will look
into implementing that for us.
Jim
On Feb 15, 7:04 pm, Mark Petzold <mark.petz...@fhcanada.org> wrote:
> I'm not sure if this will help but since we do the same thing I'll explain
> how we do it.
>
> Our philosophy is that if Netsuite is built to do something a certain way
> it's best not to complicate things and try to bend it to our way.
>
> Sometimes it's ok to have more that one record for an entity. Take
> employees for example. I am an employee and a donor so I have an employee
> record and a donor record. Nothing wrong with that.
>
> People that work overseas (short and long term) get entered into Netsuite
> as customers and as items. We track all the personal stuff (having to do
> with the trip) on the customer record. The item record is where all the
> financial stuff happens. Do you ever see having fundraising online for
> these people? Like this ...http://www.fhcanada.org/s.nl/c.364464/it.A/id.13792/.f You'll likely want
> >http://groups.google.com/group/netsuiteorg?hl=en.- Hide quoted text -
>
> - Show quoted text -
into implementing that for us.
Jim
On Feb 15, 7:04 pm, Mark Petzold <mark.petz...@fhcanada.org> wrote:
> I'm not sure if this will help but since we do the same thing I'll explain
> how we do it.
>
> Our philosophy is that if Netsuite is built to do something a certain way
> it's best not to complicate things and try to bend it to our way.
>
> Sometimes it's ok to have more that one record for an entity. Take
> employees for example. I am an employee and a donor so I have an employee
> record and a donor record. Nothing wrong with that.
>
> People that work overseas (short and long term) get entered into Netsuite
> as customers and as items. We track all the personal stuff (having to do
> with the trip) on the customer record. The item record is where all the
> financial stuff happens. Do you ever see having fundraising online for
> them as an item record then.
>
> PS: You could even link the two records with a custom field if necessary.
>
> Hope that helps a bit.
>
> -------------------------------------------------
> Mark Petzold
> Director of Information Technology
> FH Canada
>
> www.PovertyRevolution.org
> "It's about thriving communities, not dependancy."
>
>
> PS: You could even link the two records with a custom field if necessary.
>
> Hope that helps a bit.
>
> -------------------------------------------------
> Mark Petzold
> Director of Information Technology
> FH Canada
>
> www.PovertyRevolution.org
> "It's about thriving communities, not dependancy."
>
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages