A signed contract lands in your inbox. Your team issues an invoice three weeks later. The customer reads an invoice line item that doesn't match the scope they signed. Payment sits in their queue for 40 days while they ask for clarity. You follow up twice. They pay, but 23 days late. That's not a collection problem. That's a reconciliation problem—and it compounds across your book of business. Days Sales Outstanding (DSO) is the metric that reveals how much cash is trapped in accounts receivable at any given moment. A company with a $2M annual revenue and a DSO of 45 days has roughly $250,000 sitting unpaid. At a DSO of 60 days, that number climbs to $333,000. The difference is pure working capital you can't deploy until invoices clear. One of the fastest, least obvious ways to compress DSO is not to chase payment harder—it's to make sure what the customer receives matches what they signed. When line items, quantities, rates, and terms align between contract and invoice, payment friction drops. Customers pay faster because there's no ambiguity to resolve. Why invoices and contracts drift apart in the first place Most teams manage contracts and invoicing in separate tools or workflows. A contract sits in a folder or email thread. An invoice is generated from your accounting system or a template. Between the two systems, scope creep happens, rates change, and details slip. Real scenarios where this happens: Verbal change orders. The client asks for extra hours or features during the project. Your team delivers them. Nobody updates the contract or tells accounting. The invoice shows the original scope, the client sees items they didn't sign up for, or vice versa. Templated invoices don't reference the contract. Your accounting tool generates an invoice from a standard template. It never looks at the actual signed statement of work. Line items are generic ('consulting services') rather than specific to the deal. Multiple people, no handoff. Sales closes the deal and files the contract. Project delivery begins. Billing happens months later from a different team that never reads the contract. Terms, deliverables, and dates are all assumptions. Scope in the contract, pricing in a separate quote. You sign a contract that references a quote, but the invoice was generated from a different pricing sheet. The customer has three documents, none of them obviously in sync. No audit trail. If the contract or invoice changes, there's no record of when, why, or who approved it. Customer disputes take weeks to resolve because you can't prove what was agreed. Each of these scenarios delays payment by forcing the customer to stop, investigate, and ask questions. From their side, it feels like you don't have your house in order. From your side, it's working capital sitting idle. The reconciliation workflow that closes the gap The fix is a structured reconciliation workflow—a repeatable process that ensures every invoice references the contract it came from, and that every line item on the invoice matches the signed scope. This doesn't require new software if you're disciplined. It does require process discipline. Step 1: Make the contract the source of truth for billing When a contract is signed, extract and record the billing-relevant facts in a centralized place. This can be a spreadsheet, a CRM, or a dedicated contracts module—the medium matters less than consistency. Record: Customer name and billing entity Contract value and payment terms (net 30, net 60, etc.) Start date and end date Scope: specific deliverables, quantities, or hours Rate or fixed price Any exclusions (what's not covered) Billing schedule (lump sum, monthly, milestone-based, usage-based) Contract ID and signature date If you're using digital contract signing with an audit trail , pull this data from the signed document itself. If you're signing on paper, have someone manually extract it the day the contract is signed, not when invoicing begins. Step 2: Link every invoice to its source contract Before you generate an invoice, pull up the contract record. Create the invoice directly from the contract's billing data, not from a generic template. Every invoice should include: Contract ID or reference number (so the customer can link them) Line items that match the contract language and quantities exactly Rates that match the contract rate A note about what was delivered (e.g., 'May 2024 consulting services as per Statement of Work dated April 1, 2024') If the work performed doesn't match the contract, stop and reconcile before invoicing. Either the contract needs an amendment, or the invoice needs a credit note for out-of-scope work. Step 3: Automate the comparison for recurring or high-volume contracts If you send multiple invoices under one contract (e.g., monthly service invoices, milestone invoices), template the invoice line items from the contract itself. Many accounting platforms allow you to create a recurring invoice template linked to a specific cust