Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Download
Standard view
Full view
of .
Look up keyword
Like this
1Activity
0 of .
Results for:
No results containing your search query
P. 1
PSAAX2009SP1UserGuideUpdate_PayWhenPaid

PSAAX2009SP1UserGuideUpdate_PayWhenPaid

Ratings: (0)|Views: 8|Likes:
Published by Ahmed Farag Ibrahim

More info:

Published by: Ahmed Farag Ibrahim on Nov 14, 2012
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

07/05/2014

pdf

text

original

 
May 2009Page 1
© 2009 CGS
Pay when Paid
AX2009 SP1 USER GUIDE UPDATE
 
Pay when Paid May 2009
Page 2
© 2009 CGS
Overview
Pay when Paid (PwP) is used to assure customer acceptance of subcontracted work and also tomanage project cash flow. This is accomplished by not paying the subcontractor until payment for their work is received by the end customer. Manually keeping track of which subcontract invoice isrelated to which customer invoice and selecting the appropriate subcontractor invoices for paymentcan be a very laborious task. The PwP feature within PSA automates both the relationship of customer to subcontractor invoice as well as the subcontract invoice selection process.PwP processing
can be “activated” at either the vendor or the project/task level. The activation
value can also be defined at the Vendor Group and Project Contracts, and then default into therelated vendor and project.
Setup
The following section details the steps that are required to setup the Pay when Paid functionality.
I. Parameter setup
1. PSA Parameters
PSA Menu 
 
Setup 
 
PSA Parameters 
 
Project - Activity tab 
a.
Default Pwp setting 
 –
Since both the project and the employee master files have aPwP flag, the system needs a way to determine which setting has priority over theother.The value of the
Default Pwp setting 
determines which master file setting haspr 
iority. If the setting is set to “Project –
Activity,
” then the default setting
for the
“Override Vendor Pwp” on
the project (shown below) will be checked. This meansthat the PwP setting on the project has priority.
If the value is set to “Vendor,” then the default setting for the “Override Vendor Pwp”
on the project will be unchecked. This means that the PwP setting on the vendor has priority.b.
Fully paid threshold amount 
 
 –
this amount defines the threshold that will constitute afull payment by the customer and will therefore release payments for the relatedinvoices to the subcontractors. Usually this setting will be set to a value greater than0.00 so that vendor payments are not held up because of a very small shortpayment by the customer.c.
Fully paid threshold percent 
 
 –
the percent defines the threshold that will constitute afull payment by the customer and will therefore release payments for the relatedinvoices to the subcontractors. Usually this setting will be set to a value greater than0.00 so that vendor payments are not held up because of a very small shortpayment by the customer.d.
Override employee expenses 
 
 –
checking this field will allow employee expensereports to bypass the PwP process and get paid regardless of customer payment.
 
Pay when Paid May 2009
Page 3
© 2009 CGS
II. Vendor setup
1. Vendor Group
Accounts Payable Menu 
 
Setup 
 
Vendor groups Pay when paid 
 –
The value of this field, which activates PwP functionality, will default to allof the vendors who are part of the vendor group. Changing the value of this field will notupdate the PwP field on the related vendors within the Group; it will only be applied to newvendors.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->