Payment Application Business Processes

A Payment Application BP lets you track the payment information using the standard payment application method, such as tracking retainage, stored materials, past payments, and so on. Each Payment Application BP record references a particular Base Commits record. The line items on the Payment Application BP will reflect the line items on the Base commits as well as any associated Change Commits.

A project/shell can include more than one Base Commit BP with Payment Applications and SOVs. When a shell is created from a shell template that has multiple Base Commit BPs which creates different payment application SOVs, multiple Change Commits that updates different payment application SOVs and multiple payment application BPs, those business processes are automatically included in the created shell with the SOV structures.

When multiple Base Commit BPs are included in a project/shell, you can:

Create multiple Base Commit records that create different payment application SOVs
Create multiple Change Commit records that update different payment application SOVs
Create multiple payment application records that update different payment application SOVs
Create multiple payment application SOV structures
View new SOV nodes that display the log of the Base Commit records that creates the Payment Application SOV structure
Note: If the sum of costed lines ranges between a -0.01 to 0.01 difference from the originating line item values, the system does not generate an error or prevent the BP record from moving to the next step.

For more information, watch the following video:

Payment Application BPs, and associated Base Commits and Change Commits, are designed in uDesigner. For more information, refer to the Unifier uDesigner User Guide. Your Company Administrator can include or remove SOV restrictions when setting up a Base Commit BP or a negative Change Commit (negative change order) BP.