Skip to content
Construction invoice follow-up

A controlled follow-up process for Alberta construction invoices.

A practical construction invoice follow-up process for Alberta subcontractors: organize the record, assign approvals, prepare restrained reminders, and keep the next action visible.

General awareness, not legal advice. Customer facts and qualified Alberta counsel control any legal action or deadline.

The invoice is usually in accounting. The follow-up record is everywhere else.

An accounting system can show an amount due while the practical payment record lives across sent email, project documents, phone notes, owner memory, and a spreadsheet. The result is inconsistent follow-up, weak handoffs, and dates that are noticed too late.

A controlled process gives each selected invoice one record, one internal owner, one approver, and one visible next action. It should preserve relationships while making exceptions impossible to hide.

Six steps from invoice intake to a clear next move.

  1. 01

    Accept and identify the invoice

    Record the invoice number, payer, project, original amount, current outstanding amount, internal owner, and where the source document lives.

  2. 02

    Confirm the controlling facts

    Record customer-supplied receipt dates, work or supply dates, known payment events, and whether the project is private construction or a separate public-works context.

  3. 03

    Check the invoice and evidence

    Use a consistent Proper Invoice observation checklist where it applies. Link the contract, change orders, delivery evidence, approvals, and payer correspondence rather than relying on memory.

  4. 04

    Assign the next action and approver

    Choose one next action: verify receipt, request a status, supply a missing document, prepare a reminder, record a dispute, or escalate for qualified review.

  5. 05

    Prepare restrained follow-up

    Use the customer's voice, reference the invoice clearly, ask for a specific status or missing item, and avoid unsupported legal threats or invented urgency.

  6. 06

    Review the queue every week

    Confirm what changed, what is blocked, which approvals are waiting, which dates are approaching, and which invoices require a different path.

Minimum useful record

What every selected invoice should show.

  • Invoice identifier, payer, project, original amount, and outstanding amount
  • Internal owner and named reminder approver
  • Customer-supplied receipt, work, supply, and known payment dates
  • Invoice, contract, change-order, delivery, and correspondence links
  • Latest payer status, dispute flag, and missing-information flag
  • One next action, one due date, and one accountable person

Ask for a specific update without turning the message into a threat.

EXAMPLE — CUSTOMER REVIEW REQUIREDSubject: Payment status for INV-1042

Hello [name], I'm following up on INV-1042 for [project], currently showing an outstanding balance of [amount]. Could you confirm its approval and expected payment status, or let us know if anything is missing from the record? Thank you.

This example is an operating starting point, not a universal template. The customer checks the facts, relationship context, contract terms, and any dispute before sending.

Some invoices need review, not another reminder.

Pause the standard follow-up sequence when the payer disputes the work or amount, the project or jurisdiction is unclear, required evidence is missing, a statutory notice may be involved, legal action is being considered, or the proposed message would threaten consequences. Preserve the record and assign the correct human reviewer.

Rate Automation is not a law firm or collection agency. The platform's invoice module organizes the operating record and prepares customer-approved follow-up; qualified counsel confirms legal rights, filings, and enforcement.

Construction invoice follow-up FAQ

How often should a construction invoice be reviewed?

A weekly review is a practical operating rhythm for selected material invoices. Each review should confirm the outstanding amount, latest payer status, next action, owner, approver, and any missing evidence or date-awareness flag.

Should every reminder be automatic?

No. Founding-pilot reminders are prepared for a named customer approver and sent by the customer from its own identity. Disputes, missing documents, relationship concerns, and legal-risk flags require human review.

What should happen when an invoice is disputed?

Stop the ordinary reminder path, preserve the invoice and supporting record, record what was disputed and when, assign a human owner, and obtain qualified advice when the dispute may affect legal rights or next steps.

Related official information: Alberta prompt-payment rules.

Invoice follow-up founding pilot

Bring one real invoice. See the controlled process.

Thirty days, up to 25 selected invoices, one Alberta entity, two named users, and customer-approved, customer-sent follow-up.

Book a 15-minute fit call