Payment Application Business Processes

A Payment Application BP lets you track 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 specific 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.

Note:

Changes to a Payment Application BP design while records are in progress (in-flight) can cause data issues in pending records.

A project/shell can include multiple Base Commit BPs with associated Payment Applications and SOVs. When a shell is created from a template containing multiple Base Commit BPs—each generating different Payment Application SOVs—as well as multiple Change Commits that update those SOVs and multiple Payment Application BPs, all of these BPs and their corresponding SOV structures are automatically included in the newly created shell.

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:

Using Multiple Payments in a Single Shell

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.