Construction billing software best practices vary by state because prompt payment laws, retainage caps, lien waiver formats, and filing deadlines all depend on where your project is located. A billing configuration that keeps you compliant in Texas may violate requirements in California. This state-by-state guide shows you the specific requirements your billing software must handle in the states where GCs operate most frequently.

A 2025 AGC survey found that 42% of multi-state GCs had experienced a compliance violation caused by applying home-state billing rules to an out-of-state project. Your billing software must adapt to each jurisdiction automatically.

How State Laws Shape Billing Software Requirements

Three categories of state law directly affect how you configure your billing software.

Prompt payment statutes set the maximum number of days you can hold a subcontractor's payment after you receive money from the owner. Deadlines range from 7 days in some states to 30+ days in others. Your software must calculate these deadlines per project.

Retainage statutes cap the percentage you can withhold and dictate when you must release it. Some states have different rules for public and private projects. Your software must apply the correct rules based on project type and location.

Lien waiver statutes mandate specific waiver forms in certain states. Using a non-statutory form in these states may not provide valid lien protection. Your software must generate or validate the correct forms for each state.

State-by-State Billing Requirements: Top 20 Construction States

State	Prompt Pay (Private)	Prompt Pay (Public)	Max Retainage	Statutory Lien Waiver
California	30 days	7 days	5%	Yes (Civil Code 8132-8138)
Texas	35 days	7 days	10% (public only)	Yes (Property Code Ch. 53)
Florida	30 days	25 days	10%/5% after 50%	Yes (Stat. 713.20)
New York	None (private)	15 days	5% (public)	No
Illinois	30 days	30 days	10%	No
Pennsylvania	14 days	14 days	No statutory cap	No
Ohio	None (private)	30 days	10% (public)	No
Georgia	None (private)	15 days	10%	Yes (O.C.G.A. 44-14-366)
North Carolina	7 days	7 days	5% (public)	No
Virginia	60 days	60 days	5%	No
Colorado	None (private)	7 days	5% (public)	No
Washington	30 days	30 days	5% (public)	No
Arizona	7 days	7 days	10%	No
Tennessee	30 days	30 days	5% (public)	No
Michigan	None (private)	30 days	10%	Yes (MCL 570.1115)
Massachusetts	30 days	15 days	5% (public)	No
Minnesota	30 days	30 days	5%	No
Maryland	30 days	30 days	10% (retainage)	No
Louisiana	30 days	30 days	10%	No
Oregon	30 days	30 days	5% (public)	No

Case Study: California Billing Compliance

California has some of the strictest billing compliance requirements in the country. Here is how a mid-market GC configured their billing software to stay compliant on a $15M mixed-use project in Los Angeles.

Prompt payment setup. The team configured a 7-day payment countdown for public work and 30-day for their private components. The software triggered alerts at 5 days, 3 days, and 1 day before each deadline. Late payment interest calculated automatically at 2% per month.

Retainage configuration. Retainage set at 5% for all subcontractors, matching California's statutory cap. The system tracked retainage at the line-item level and flagged retainage release when each subcontractor's scope reached substantial completion.

Lien waiver automation. The software generated California statutory conditional waivers (Civil Code 8132) with each pay application request and unconditional waivers (Civil Code 8134) after payment cleared. Non-statutory forms were blocked from the system entirely.

Result. Over 18 months of billing, the GC processed 240 subcontractor pay applications with zero prompt payment violations, zero retainage disputes, and a complete lien waiver chain for every subcontractor.

Case Study: Texas Multi-Project Configuration

A large GC operating 8 projects across Texas configured their billing software with state-specific settings that handled the differences between public and private work.

Prompt payment. The 7-day deadline applied to their 3 public projects. Their 5 private projects used the 35-day deadline. The software applied the correct deadline based on the project's classification during setup.

Retainage. Public projects used the 10% statutory cap. Private projects used contract-specific rates ranging from 5% to 10%. Each project carried its own retainage profile in the system.

Lien waiver forms. Texas statutory waiver forms loaded automatically for all projects. The system tracked interim conditional waivers, interim unconditional waivers, final conditional waivers, and final unconditional waivers as four separate document types.

Result. The firm processed $42M in subcontractor payments across all 8 projects with documented compliance on every payment. Their surety company cited the billing documentation as a factor in increasing their bonding capacity by $5M.

Case Study: Florida Retainage Reduction

Florida's retainage reduction rule catches GCs who do not configure their software to adjust rates mid-project.

A GC running a $22M hotel project in Miami set their initial retainage at 10%, matching Florida's allowance for the first 50% of the project. Their software was configured to reduce retainage to 5% automatically when the project crossed the 50% completion threshold.

The configuration. The billing software tracked overall project completion based on the aggregate percentage complete across all subcontractor SOVs. When the weighted average crossed 50%, the system reduced the retainage rate on all new billing to 5%. Existing held retainage remained at the original amounts.

What happened without this configuration on a prior project. The same GC had previously run a project without the automatic reduction. They held 10% retainage through project completion. Three subcontractors filed formal complaints, and the GC paid $18,000 in excess retainage plus interest.

Configuring Your Software for Multi-State Operations

If you operate in multiple states, follow this process for each new project.

Step 1: Identify the project state. Seems obvious, but GCs with national operations sometimes configure projects using their headquarters state by default.

Step 2: Load the state compliance profile. If your software supports state profiles, select the correct one. If not, manually enter the prompt payment deadline, retainage cap, and lien waiver requirements.

Step 3: Verify public vs. private classification. Many states have different rules for public and private projects. A misclassification applies the wrong deadlines and retainage limits.

Step 4: Check local amendments. Some cities and counties add requirements beyond state law. For example, certain California municipalities require prevailing wage compliance on private projects above a dollar threshold. Your billing software should accommodate these local layers.

Step 5: Test the configuration. Process a sample pay application through the system before the first real billing cycle. Verify that retainage calculates correctly, prompt payment deadlines populate accurately, and the correct lien waiver forms generate.

What to Do When State Laws Change

State legislatures modify construction billing laws regularly. Your billing software configuration needs a maintenance schedule.

Annual review. Every January, review the prompt payment statutes, retainage laws, and lien waiver requirements for every state where you have active projects. Update your state profiles accordingly.

Legislative monitoring. Subscribe to construction law updates from the AGC, your state contractors association, and a construction law firm. When a new law passes, update your billing software before the effective date.

Vendor updates. Ask your billing software vendor whether they update state compliance rules automatically. Enterprise platforms typically push state law updates to your system. Mid-tier platforms may require manual updates.

For a complete overview of billing platforms, read our pillar guide on Subcontractor Billing Software.

FAQs

How many state compliance profiles do I need in my billing software? You need one profile for every state where you have active or planned projects. If you operate in 12 states, build 12 profiles. Each profile should include separate settings for public and private projects, giving you up to 24 configurations for 12 states.

What if my billing software does not support state-specific configurations? Switch to a platform that does. Operating without state-specific configurations is a compliance risk that grows with every project. If switching is not immediate, maintain a manual compliance spreadsheet alongside your software and review it against every pay application.

How do I handle projects that span state lines? Apply the billing requirements of the state where the physical construction work occurs. If a project spans two states (such as a pipeline or highway), apply the stricter requirements across the entire project or segment the billing by state line. Consult your construction attorney for projects that cross jurisdictions.

Do federal projects follow state billing rules? Federal projects follow the Miller Act and federal prompt payment regulations, not state laws. Your billing software should have a separate federal compliance profile. Federal prompt payment rules generally require payment within 14 days of receiving payment from the government, and retainage is typically limited to 10%.

How often do state prompt payment laws change? Significant changes happen every 2-3 years in most states. Minor adjustments (interest rate changes, form updates) can happen annually. The 2024-2025 legislative cycle saw 12 states modify their prompt payment or retainage statutes, the highest number in a two-year period since 2018.

Can I use one set of billing terms for all states to simplify administration? You can standardize your billing process, but you cannot standardize the compliance parameters. Use the same workflow (submit, validate, approve, pay) across all states, but configure the deadlines, retainage rates, and waiver forms per state. The process is uniform; the rules inside the process are not.

See How SubcontractorAudit Handles Multi-State Compliance

SubcontractorAudit includes pre-built state compliance profiles for all 50 states, automatic retainage calculations, and prompt payment deadline tracking. Request a demo and see how the platform adapts to your project locations.