Agencies
Engagement to invoice to collection, on one record.
Scope, contractor evidence, milestone billing, receivables, and reporting stay tied to the engagement. Delivery drives the numbers.
- ScopeRetained
- ContractorsDocumented
- ExpensesCoded
- MilestoneApproved
- InvoiceIssued
- ReceivableOpen
- CollectionApplied
- ReportingAssembled
Engagement record
One central record. Every downstream question resolves against it.
Active engagement
Client · Brand refresh, phased
- Scope
- Retained scope + versioned changes
- Billing structure
- Milestone with retainer
- Contractor evidence
- Documented and current
- Expense support
- Coded to engagement
- Invoice status
- Milestone two, ready
- Receivables status
- One open, one collected
- Reporting classification
- Retained on P&L context
- Delivery evidence
- Linked per milestone
Engagement activity
- Client approved scope v1Opened
- Institution reviewed contractor evidenceMid-cycle
- Institution issued invoiceMilestone one
- AR recorded partial collectionApplied
- AR scheduled reminderFollow-up
Milestone billing
Delivery evidence becomes an invoice becomes a collection.
Focus
Milestone two · Ready for invoice
Approved delivery evidence has been retained. Billing runs on the standing cadence.
Approval
StepMilestone approved by client
Invoice readiness
StepLine items + evidence linked
Invoice issued
StepSent on cadence
Receivable
StepOpen on aging
Collection record
StepApplied when received
Reconciliation
StepLedger update retained
Interruptions
Where an engagement stops moving, and who owns each pause.
- Scope change requestedOwner: Client leadVersioned on engagementRouted
- Missing contractor recordOwner: Institution · OpsChased on request cadenceRouted
- Milestone not approvedOwner: ClientDelivery evidence in reviewRouted
- Invoice dispute openedOwner: Institution · ARReview record openedRouted
- Partial collection receivedOwner: ARApplied; balance remains openRouted
Project context
Delivery, cost, cash, and reporting stay in the same conversation.
Delivery stage
Milestone two, in review
Contractor costs
Coded to engagement
Billing status
One invoice open
Receivables
One collection applied
Reporting context reflects the engagement, not fabricated profitability figures.
Records retained
The records carried from engagement through collection.
Engagement financial record
Scope, billing, deliverables
Contractor-document checklist
Prepared for tax cycle
Billing schedule
Milestone cadence and status
Receivables review
Aging and open items
Project reporting
Engagement context in the pack
Connected services
Coverage that follows the engagement.
Bookkeeping & Close
- Input
- Engagement records
- Handoff
- Project-coded ledger
- Output
- Reviewed close
Review the close workspace →
Accounts Receivable
- Input
- Invoice cadence
- Handoff
- Follow-up + disputes
- Output
- Cash applied
See receivables cadence →
Accounts Payable
- Input
- Contractor + expense
- Handoff
- Approvals
- Output
- Ledger entry
See approvals →
Financial Reporting
- Input
- Reviewed close
- Handoff
- Engagement context
- Output
- Reporting pack
Understand the reporting pack →
Controller Support
- Input
- Reviewed close
- Handoff
- Standing agenda
- Output
- Sign-off record
See controller review →
CFO Advisory
- Input
- Reviewed record
- Handoff
- Scenario framing
- Output
- Decision context
Explore advisory context →
Questions from agency operators.
Contractor records are maintained through the year, tied to the engagement, and prepared for the tax cycle. Ownership sits with Institution; the licensed preparer files.