Project Accounting

[Vince Clark]

Two areas I am investigating:

1) Billing for projects other than by the hour. Right now I am mostly concerned with daily or weekly rates and am not addressing other types of billing such as fixed price, milestone/progress billing, etc.
I've gone thru the services in Project Manager related to generating invoices and the associated services called in the accounting component to get rates. The periodType entity already has values defined for weekly, monthly, and quarterly, but not daily. I added a RATE_DAY periodType and was about to try and use it, when I realized that the rate screen under party manager and project manager (rate for a resource) has this field hard coded to RATE_HOUR.
Upon further investigation I see that when defining rates for a workeffort you are able to set the periodType. So I guess I'm looking for some guidance on what else needs to be done in project manager to take advantage of this.

2) Capturing different rates for customers and contractors. Customer rates would be used when generating AR invoices, contractor rates would be used when generating AP invoices.
Very early in my investigation on this one. My initial guess is that you would:
Create an agreement between company and customer
Create an agreement between company and contractor

From here I'm stuck. Two possible paths:
Agreement Work Effort Appls
Agreement Items

Work Effort Appls seems like the logical choice, as it allows you to reference a specific work effort (project) for the agreement. But this would not get down to the resource level. For example we may charge different rates for different resources. This also would not deal with two different rates (customer and contractor) since with workeffort doesn't capture the rates that way. It just captures a single rate for a resource. So as far as I can tell rates on projects are implicitly intended to be used as a customer rate.

If you think about this from a pricing perspective I just need a way to capture a "purchase" price and "sale" price, and use the correct price for a resource on AR and AP invoices. Again, looking for some guidance.

[BJ Freeman]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

just some quick thoughts.
I would have basic services in projects that calculate cost.
this leaves the manipulation of resources in project services.
these could be used in projects for different what if's.
the Agreement work efffort appls would also be just for projects and
stay in the projects services. if you break this down small enough you
can do by items.

the accounting appication would the store the Invioce generated by the
projects.
Accounting would then process invoices as a generic thing.

Vince M. Clark sent the following on 2/14/2009 4:31 PM:

> Two areas I am investigating:
>
> 1) Billing for projects other than by the hour. Right now I am mostly concerned with daily or weekly rates and am not addressing other types of billing such as fixed price, milestone/progress billing, etc.
> I've gone thru the services in Project Manager related to generating invoices and the associated services called in the accounting component to get rates. The periodType entity already has values defined for weekly, monthly, and quarterly, but not daily. I added a RATE_DAY periodType and was about to try and use it, when I realized that the rate screen under party manager and project manager (rate for a resource) has this field hard coded to RATE_HOUR.
> Upon further investigation I see that when defining rates for a workeffort you are able to set the periodType. So I guess I'm looking for some guidance on what else needs to be done in project manager to take advantage of this.
>
> 2) Capturing different rates for customers and contractors. Customer rates would be used when generating AR invoices, contractor rates would be used when generating AP invoices.
> Very early in my investigation on this one. My initial guess is that you would:
> Create an agreement between company and customer
> Create an agreement between company and contractor

I agree
>
>>From here I'm stuck. Two possible paths:
> Agreement Work Effort Appls
use this to track actual work. to compare against Budget.
> Agreement Items
i would use the Agreement Items for general things like Rate Caps, skill
sets to use, Goals, Scope, overview of a project. Sort of like budget.
>
> Work Effort Appls seems like the logical choice, as it allows you to reference a specific work effort (project) for the agreement. But this would not get down to the resource level. For example we may charge different rates for different resources. This also would not deal with two different rates (customer and contractor) since with workeffort doesn't capture the rates that way. It just captures a single rate for a resource. So as far as I can tell rates on projects are implicitly intended to be used as a customer rate.
>
> If you think about this from a pricing perspective I just need a way to capture a "purchase" price and "sale" price, and use the correct price for a resource on AR and AP invoices. Again, looking for some guidance.
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJl3TQrP3NbaWWqE4RAkWwAKDCrqRR2IJTm8tAXAjv/1YXPHXOmACeOsZM
Co37p6+3UfuqyU4ZsNziJXk=
=WG0Y
-----END PGP SIGNATURE-----

[hans_bakker]

On Sat, 2009-02-14 at 17:31 -0700, Vince M. Clark wrote:
> Two areas I am investigating:
>
> 1) Billing for projects other than by the hour. Right now I am mostly concerned with daily or weekly rates and am not addressing other types of billing such as fixed price, milestone/progress billing, etc.
> I've gone thru the services in Project Manager related to generating invoices and the associated services called in the accounting component to get rates. The periodType entity already has values defined for weekly, monthly, and quarterly, but not daily. I added a RATE_DAY periodType and was about to try and use it, when I realized that the rate screen under party manager and project manager (rate for a resource) has this field hard coded to RATE_HOUR.

in accounting you can define these with any periodtype under rates and
can be easily changed to any period type in party and project manager.
The data model allows for this.

> Upon further investigation I see that when defining rates for a workeffort you are able to set the periodType. So I guess I'm looking for some guidance on what else needs to be done in project manager to take advantage of this.
>
> 2) Capturing different rates for customers and contractors. Customer rates would be used when generating AR invoices, contractor rates would be used when generating AP invoices.
> Very early in my investigation on this one. My initial guess is that you would:
> Create an agreement between company and customer
> Create an agreement between company and contractor

sure you can do this, however the RateAmount entity already allows for
this without using the agreement although that can also be a solution.

>
> >From here I'm stuck. Two possible paths:
> Agreement Work Effort Appls
> Agreement Items
>
> Work Effort Appls seems like the logical choice, as it allows you to reference a specific work effort (project) for the agreement. But this would not get down to the resource level. For example we may charge different rates for different resources. This also would not deal with two different rates (customer and contractor) since with workeffort doesn't capture the rates that way. It just captures a single rate for a resource. So as far as I can tell rates on projects are implicitly intended to be used as a customer rate.
>
> If you think about this from a pricing perspective I just need a way to capture a "purchase" price and "sale" price, and use the correct price for a resource on AR and AP invoices. Again, looking for some guidance.
--
Antwebsystems.com: Quality OFBiz services for competitive prices

[hans_bakker]

Hi BJ,
see comments inline....

On Sat, 2009-02-14 at 17:50 -0800, BJ Freeman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> just some quick thoughts.
> I would have basic services in projects that calculate cost.

currently in accounting grouped together as rate services

> this leaves the manipulation of resources in project services.
> these could be used in projects for different what if's.
> the Agreement work efffort appls would also be just for projects and
> stay in the projects services. if you break this down small enough you
> can do by items.
>
> the accounting appication would the store the Invioce generated by the
> projects.
> Accounting would then process invoices as a generic thing.

that is how it is now...

>
> Vince M. Clark sent the following on 2/14/2009 4:31 PM:
> > Two areas I am investigating:
> >
> > 1) Billing for projects other than by the hour. Right now I am mostly concerned with daily or weekly rates and am not addressing other types of billing such as fixed price, milestone/progress billing, etc.
> > I've gone thru the services in Project Manager related to generating invoices and the associated services called in the accounting component to get rates. The periodType entity already has values defined for weekly, monthly, and quarterly, but not daily. I added a RATE_DAY periodType and was about to try and use it, when I realized that the rate screen under party manager and project manager (rate for a resource) has this field hard coded to RATE_HOUR.
> > Upon further investigation I see that when defining rates for a workeffort you are able to set the periodType. So I guess I'm looking for some guidance on what else needs to be done in project manager to take advantage of this.
> >
> > 2) Capturing different rates for customers and contractors. Customer rates would be used when generating AR invoices, contractor rates would be used when generating AP invoices.
> > Very early in my investigation on this one. My initial guess is that you would:
> > Create an agreement between company and customer
> > Create an agreement between company and contractor
> I agree
> >
> >>From here I'm stuck. Two possible paths:
> > Agreement Work Effort Appls
> use this to track actual work. to compare against Budget.
> > Agreement Items
> i would use the Agreement Items for general things like Rate Caps, skill
> sets to use, Goals, Scope, overview of a project. Sort of like budget.
> >
> > Work Effort Appls seems like the logical choice, as it allows you to reference a specific work effort (project) for the agreement. But this would not get down to the resource level. For example we may charge different rates for different resources. This also would not deal with two different rates (customer and contractor) since with workeffort doesn't capture the rates that way. It just captures a single rate for a resource. So as far as I can tell rates on projects are implicitly intended to be used as a customer rate.
> >
> > If you think about this from a pricing perspective I just need a way to capture a "purchase" price and "sale" price, and use the correct price for a resource on AR and AP invoices. Again, looking for some guidance.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFJl3TQrP3NbaWWqE4RAkWwAKDCrqRR2IJTm8tAXAjv/1YXPHXOmACeOsZM
> Co37p6+3UfuqyU4ZsNziJXk=
> =WG0Y
> -----END PGP SIGNATURE-----

--
Antwebsystems.com: Quality OFBiz services for competitive prices