# CPA Billing Implementation Scope Ledger

Use this editable planning ledger to commission one billing workflow. It is a recommendation, not an authorization to access client data, send invoices, migrate history, or make commercial decisions.

| Deliverable | Existing native capability | Missing business instruction | Implementation assignment | Firm owner | Implementer owner | Handover output | Exclusion |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Source-system inventory |  |  |  |  |  |  |  |
| Native-feature fit check |  |  |  |  |  |  |  |
| Client and item mapping |  |  |  |  |  |  |  |
| Billable-work definition |  |  |  |  |  |  |  |
| Agreement and exception capture |  |  |  |  |  |  |  |
| Draft-preparation boundary |  |  |  |  |  |  |  |
| Office and template routing |  |  |  |  |  |  |  |
| Integration-direction map |  |  |  |  |  |  |  |
| Historical-data boundary |  |  |  |  |  |  |  |
| Team handover and maintenance |  |  |  |  |  |  |  |

## Worked sample: DEMO-WIP-014

| Item | Classification | Scope decision |
| --- | --- | --- |
| Standard monthly fee | Native recurring invoice setup | Confirm the current system can prepare an unsent recurring draft with approved fields and reviewer path. |
| Client-specific held time | Policy-dependent selection | Record the eligible work, hold/release condition, client/service/period and responsible approver. |
| Opening accounts receivable | Excluded historical-data migration | Do not import, reconcile or change historic balances unless that project is separately scoped. |