On this page Jump to section
Trace scope to billing
Compare the approved change with time, expenses, milestones, and invoice lines, keeping work performed before approval visible. The log can expose a customer-authorization question; it cannot add a charge or interpret the contract without the responsible owner.
Keep the request separate from its approval
Start a record when a change is requested, even if the customer has not approved it yet. Capture the project, request date, requesting person, original scope reference and the proposed change. Link to the actual request rather than summarizing away important conditions.
Use distinct statuses for requested, awaiting clarification, approved, rejected, implemented and billed. An email acknowledging receipt is not necessarily authorization to proceed. The project owner decides whether the evidence meets the organization's approval requirements; the assistant keeps the record and questions organized.
Connect scope, evidence and invoice references
A billing log should explain how a particular invoice line relates to the approved change. Keep a stable change reference throughout the workflow, including when documents receive new versions. This helps the reviewer distinguish a revised request from a second change.
- Original scope
- Record Project reference, agreed baseline and relevant source location.
- Review point What work was already included before this request?
- Requested change
- Record Requester, date, proposed deliverable and supporting message.
- Review point What exactly is different, and which questions remain open?
- Authorization
- Record Approver, date, approved version and any conditions.
- Review point Does the instruction cover the work and billing action being prepared?
- Work evidence
- Record Relevant time, expenses, completion records or milestone references.
- Review point Does the evidence match the approved scope and period?
- Billing outcome
- Record Invoice reference, line description, review status and delivery evidence.
- Review point Is the approved change represented once, with unresolved items clearly held?
Review the proposed billing handoff
Compare the approved version with the working invoice draft. Check project and customer identifiers, the described deliverable and the source references. Look for the same change appearing in an earlier invoice or another pending draft. Flag possible duplicates for review rather than deleting or editing a posted record on your own.
If work was performed before approval, preserve the sequence of events. Do not backdate the request or imply that authorization existed earlier. The project owner must decide how to handle the gap and what can be communicated to the customer.
Example: approval covers only part of a request
Suppose a customer requests two additional deliverables but approves only one in the returned document. The log should retain the complete request and the narrower approval. Mark the second deliverable as unresolved and keep it out of the prepared approved-change handoff unless the responsible owner provides further instruction.
If a later message approves the second deliverable, add a new dated authorization reference. Do not overwrite the earlier approval or make both items appear to have been approved at the same time. This example illustrates record organization; interpreting the agreement remains the responsible owner's task.
Close the loop after the invoice is sent
Record the approved invoice version, delivery date and destination using the organization's customer-contact controls. If the customer questions the charge, link that question to the change record and assign a response owner. Keep a dispute distinct from a request to correct an administrative error.
A completed billing-log entry links the request, approval, work evidence and invoice outcome. If any link remains missing, state the blocker and next action. Do not mark the entry complete merely because a draft invoice exists.
Accounts payable and receivable support can help maintain these records, prepare reviewer packets and follow up on missing documentation while your team retains billing authority.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.


