Construction Bank Reconciliation: Matching Bank Activity to the GL When You Write 800 Checks a Month
Bank reconciliation sounds straightforward: compare the bank statement to the general ledger, identify differences, reconcile to zero. In most industries it's a monthly checklist task. In construction, it gets harder. A mid-sized GC might write 600-1,000 payments per month across multiple accounts, include joint checks that don't clear like regular payments, receive wire transfers from construction lenders on draws, process retainage releases that aged for months, and handle intercompany transactions between related entities. Volume and complexity combine to make bank reconciliation a meaningful operational challenge.
Done well, bank reconciliation is more than a GL tie-out. It's a fraud detection tool, an error catcher, a cash management lens, and a discipline that keeps construction financials trustworthy. This post covers the specific mechanics for reconciling construction AP at scale.
How often to reconcile depends on volume and risk:
Reconciliation frequency considerations
- Monthly is standard — tied to the close cycle
- Weekly or daily for high-volume accounts — catches problems faster
- Real-time continuous reconciliation where automation permits
- Quarterly only if volume is genuinely low — risky at construction scale
High-volume operating accounts benefit from more frequent reconciliation. A monthly reconciliation of an account with 800 transactions per month is a big task; daily reconciliation of 40 transactions per day is manageable and catches issues same-day.
At scale, manual matching breaks down. Automated matching uses specific rules:
Automated matching rules
- Exact amount and date — auto-match when bank activity matches GL entry
- Amount match within date range — catches timing differences (check written Monday, cleared Wednesday)
- Check number match — book entry and cleared check match on check number
- Wire reference match — wire description matches payment record
- ACH reference match — ACH batch reference or individual trace
- Partial matching for aggregated transactions
Well-tuned matching handles 85-95% of transactions automatically. The remaining items need human review — and those are the ones that often indicate real issues (fraud, errors, missed entries).
Outstanding checks — written and recorded in GL but not yet cleared the bank — need tracking:
Outstanding check management
- Current outstanding (under 30 days) — normal float
- Aging outstanding (30-90 days) — investigation worth doing
- Aged outstanding (90+ days) — clear indication of problem
- Stale-dated (180+ days typically) — void and reissue or escheat to state
- Categorization by payee type — checks to vendors vs subs vs employees may age differently
Aged outstanding checks are common — payee lost it, moved, went out of business, or simply never deposited. Each requires resolution. Letting them accumulate creates a cash picture that doesn't match reality (bank balance reflects the check still outstanding; real available cash is different).
Aged outstanding checks are a favored disguise for fraud. A fraudulent check written to a legitimate vendor can sit "outstanding" for months without raising suspicion because aging outstanding items are common. Periodic review of aged outstanding — contacting payees to confirm non-receipt — catches these schemes.
Deposits recorded in GL but not yet on bank statement — the opposite of outstanding checks. In construction:
Deposits in transit considerations
- Customer payments (progress billings) received but not yet deposited
- Wire transfers initiated but not yet credited
- ACH deposits in pending status
- Joint check deposits that follow special routing
- Retainage release payments in transit
Deposits in transit for more than a few days warrant investigation. A delayed deposit may indicate a lost check, a banking error, or a timing difference that will self-correct — each requires different response.
Joint checks — payable to both a sub and their supplier/sub-sub — need special handling:
Joint check reconciliation
- Joint check written — debited from GC account
- Both payees must endorse before deposit
- Clearing can be slower due to endorsement handling
- Tracking requires confirmation both payees received and endorsed
- Disputes possible if payees disagree on allocation
- GC records should document the underlying payment allocation
Joint checks that don't clear on normal timing deserve investigation. The sub and their sub-sub may be disputing the allocation, one payee may have lost the check, or the payment routing may have gone wrong.
Construction loans add reconciliation complexity:
Construction loan draw reconciliation
- Draw request submitted based on pay application
- Lender inspection before fund release
- Wire transfer from lender to contractor account
- Funds then disbursed to subs and vendors
- Reconciliation needs to connect: pay app -> draw -> wire received -> disbursements made
- Retainage from lender reconciled separately
Draws are often wires; timing from draw request to fund availability affects project cash flow. Reconciliation needs to track not just the arrival of funds but whether amounts received match amounts expected.
Many construction companies have multiple bank accounts:
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Multi-account management
- Main operating account
- Payroll account (often separate)
- Money market / investment account for surplus cash
- Project-specific accounts for some owner-funded projects
- Entity-specific accounts for related companies
- Credit card clearing accounts
Each account has its own reconciliation. Cross-account transfers (moving money between operating and payroll) need tracking on both sides. Reconciling all accounts consistently ensures the full cash picture ties out.
Related-entity companies need intercompany reconciliation:
Intercompany reconciliation
- Parent company pays sub costs on behalf of subsidiary — intercompany receivable
- Subsidiary reimburses — intercompany payable clearing
- Consolidated view should have offsetting entries
- Timing differences common — one side books before other
- Periodic intercompany settlement
Intercompany reconciliation catches mis-postings and ensures consolidated financials are clean. Companies without intercompany discipline end up with "mystery" balances that distort both entities' financials.
Reconciliation exceptions need investigation:
Common reconciliation exceptions
- Amount differences — typos, partial payments, check alterations
- Duplicate entries — same transaction posted twice in GL
- Missing GL entries — bank activity not recorded
- Wrong account postings — transaction to wrong GL account
- Date differences — reversed dates, fiscal period errors
- Bank errors — rare but happen (wrong account credited, wrong amount)
Each exception has a root cause that should be identified and addressed. Recurring patterns in exceptions reveal process problems — consistent date errors suggest training issues; persistent mis-postings suggest approval workflow gaps.
Bank-side fraud controls complement reconciliation:
Positive pay and related controls
- Positive pay — bank only clears checks matching uploaded payment file
- ACH positive pay — authorized ACH debits only
- Check washing detection — altered checks flagged
- Large transaction alerts — notifications on unusual amounts
- User activity monitoring — bank login and payment initiation tracked
- Dual authorization required for wires above threshold
Positive pay catches check fraud that reconciliation would discover after the fact. Real-time fraud controls prevent loss; reconciliation identifies the amount and source after the fact. Both have value.
Reconciliation data supports cash management:
Cash management from reconciliation
- True available cash (bank balance less outstanding payments)
- Float analysis (average time checks outstanding)
- Payment pattern analysis (when do vendors typically deposit)
- Weekly cash forecast accuracy (actual vs forecast)
- Draw timing vs disbursement timing (project cash flow)
Sophisticated treasuries use reconciliation data for cash management decisions. A company that knows typical check clearing patterns can manage cash more tightly than one operating on gross bank balance.
Construction bank reconciliation is more operationally complex than in most industries due to payment volume, joint checks, construction loan draws, multiple accounts, and intercompany transactions. Systematic reconciliation with automated matching, disciplined outstanding item tracking, aged item investigation, multi-account coordination, and fraud control integration produces clean tie-outs while catching fraud, errors, and timing issues. Companies that treat reconciliation as a routine monthly checklist miss the control and intelligence value it provides. Companies that run reconciliation actively — as cash management, fraud detection, and error discovery — get more from the process than its baseline compliance purpose. In construction AP, reconciliation is one of the highest-leverage control activities.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts