How do I set up pay application software for retainage support and approval workflows with our accounting system?

Here’s a practical way to set up pay application software so it handles retainage and approval workflows cleanly with your accounting system.

1) Define your process first

Before configuring software, document:

• Who submits the pay application
• Who reviews/approves it
• How retainage is calculated
  • e.g. 10% held until substantial completion
  • different retainage rates by project or contract
• When retainage is released
• What accounting system is the source of truth for AP, job cost, and vendor balances

This prevents configuration gaps later.

2) Choose software that supports both retainage and workflow

Make sure the pay app platform can:

• Track original contract, approved change orders, previously billed, current work completed, retainage withheld, and amount due
• Support partial retainage release
• Route invoices/pay apps through custom approval steps
• Integrate with your accounting system via API, native sync, or import/export

If it can’t handle retainage at the line-item or schedule-of-values level, you’ll likely end up using spreadsheets again.

3) Map the retainage logic

Set up the retainage rules in the software:

• Retainage percentage
• Whether retainage applies to:
  • entire pay app
  • specific line items
  • labor/materials separately
• Cap or threshold rules
• Release events
  • final completion
  • milestone approval
  • owner approval
  • lien waiver received

If your accounting system also tracks retainage, map the fields carefully so both systems use the same logic.

4) Configure approval workflows

Typical workflow stages might be:

1. Preparer creates pay application
2. Project manager reviews quantities/progress
3. Accounting verifies amounts, coding, and retainage
4. Executive/finance approver approves over threshold
5. Final posting to accounting system

Common workflow rules:

• Approvals by amount threshold
• Approvals by project type
• Separate approvals for change orders
• Auto-escalation if someone doesn’t act within a set time

5) Set up the accounting integration

You’ll want the software to sync these records:

• Vendors/subcontractors
• Projects/jobs
• Contracts
• Change orders
• Pay applications / invoices
• Retainage balances
• Payments made
• GL coding / cost codes

Decide whether the accounting system will:

• Create the invoice/payable first and send it to pay app software, or
• Receive approved pay apps from the workflow tool and then generate the AP entry

Usually, the cleanest method is:

• pay app software = workflow + retainage calculation
• accounting system = financial posting + payment processing

6) Define field mapping carefully

At minimum, map:

• Vendor name and ID
• Project/job number
• Contract amount
• Change order amount
• Previous billed amount
• Current period amount
• Retainage withheld
• Net payable
• Cost code / account code
• Approval status
• Payment status
• Invoice number / pay app number

Test the mapping with a few sample projects before going live.

7) Build controls and exceptions

Put controls in place for:

• Mismatched contract totals
• Overbilling vs approved value
• Retainage release before approval
• Duplicate pay apps
• Missing lien waivers or backup docs
• Payments exceeding approved amounts

It’s helpful to have a “needs review” status for exceptions instead of forcing the item through the normal approval path.

8) Test the full lifecycle

Run test cases for:

• Standard monthly pay app with retainage
• Change order added mid-project
• Partial retainage release
• Final retainage release
• Rejected pay app returned for edits
• Sync failure between systems

Confirm the accounting system receives the right journal/AP data and that balances reconcile.

9) Train users and document the process

Create short SOPs for:

• Subcontractors / pay app preparers
• Project managers
• Accounting reviewers
• Approvers

Include screenshots or step-by-step instructions for:

• submitting a pay application
• approving/rejecting
• releasing retainage
• syncing to accounting

10) Reconcile regularly

Even with good software, reconcile monthly:

• Retainage ledger vs accounting system
• Approved but unpaid pay apps
• Contract balance vs cost-to-complete
• Payments made vs approvals

That helps catch integration issues early.

---

Recommended implementation order

1. Document retainage and approval rules
2. Configure projects/vendors/contracts
3. Set retainage logic
4. Build approval workflows
5. Integrate with accounting
6. Test and reconcile
7. Train users and go live

If you want, I can also give you:

• a sample workflow diagram
• a retail/contractor retainage setup checklist
• or step-by-step instructions for a specific accounting system like QuickBooks, Sage, Viewpoint, NetSuite, or Xero.