Payment applications are created to capture work or progress against a contract and usually forms the basis of an invoice.
Payment applications in Cost have a built-in process that controls the submission, review, and approval of the payment application. When a contract is shared, the downstream can submit a payment application but the upstream controls the assessment and approvals.
Payment applications go through several steps from creation, submission, assessment, and approval. In some cases payment applications can be created and approved in one step.
On shared contracts, payment applications can be created by either the downstream or the upstream organization.
New payment applications and the assessment are created as drafts which remain private until the status is changed. Draft payment applications can be deleted on shared contracts, however once they progress to submitted or approved they cannot be deleted. Only the status can be changed.
There are opportunities for the downstream organization to retract a submitted payment application, or for the upstream to send it back by requesting a resubmission. The upstream organization can retract an approved payment application for editing, or send it back for resubmission.
On non-shared contracts, your organization can create, edit, update the status, and delete payment applications.
When payment applications are created, they take a snapshot of the contract pay items. These typically don’t update even if a contract change is approved, or another payment application is added.
Payment applications are sequential in Cost, with the values from prior payment applications being reflected in the current one. The sequence no. is displayed on the payment application grid.
Before being submitted, draft payment applications can be updated with the latest contract values. Also, the latest payment application in the 'assess' stage can be updated.
Follow these steps if you have created a payment application and need to update the contract values.
Payment applications can be created for contracts that are in the proceed, approved, and defects & liability status.
Payment applications automatically show the contract pay items that existed when the payment application was created. If you add contract pay items after creating the payment application, they will not automatically appear. You may be able to use the update draft process to bring in new or updated pay items.
As the upstream, when you receive a submitted payment application you can assess the requested amounts and either accept the application as-is, or enter a different amount and justification for each item.
On contracts that are not shared, you can still go through this process after creating and submitting the payment application, or you can create and immediately approve the payment application following the steps in the previous section.
The upstream organization can use the request revision action if a payment application needs to be updated after it was submitted, This typically occurs when there is a data entry error or mistake in the requested amounts or documentation and attachments are missing. The upstream organization can add an explanation as a summary or per item to explain what the downstream organization needs to amend.
Note: Only the upstream organization on a shared contract can use the request revision action. Downstream organizations can retract submitted payment applications on shared contracts to make amendments before it is approved.
Share a private attachment: