On this page Jump to section
Roll the retainer forward
Show opening balance, receipts, applications, invoices, credits, and ending balance as separate movements. Flag cross-project, cross-period, duplicate, and disputed candidates. The owner or accountant approves application and revenue treatment under the engagement terms.
Define the customer, project and review period
Begin with the engagement reference and the specific customer and project records the reviewer has named. A customer may have several projects or agreements with different instructions. Do not assume that a balance associated with the customer is available for every project.
Record the review period and the date of the source export. Keep the agreement, receipt evidence, invoice references and existing application records in the approved document location. If the opening balance cannot be traced to an agreed starting record, make that the first question rather than building a seemingly complete schedule on an uncertain number.
Make each movement traceable
- Opening position
- EvidenceThe prior approved schedule or source record, with its cutoff date.
- Review questionDoes it belong to this customer, agreement and project?
- New receipt
- EvidenceThe receipt reference, date, amount and supporting customer communication.
- Review questionDoes the documentation identify the intended project and purpose?
- Proposed application
- EvidenceThe invoice reference, requested amount, request source and approval status.
- Review questionHas the authorized reviewer approved this particular application?
- Credit or refund question
- EvidenceThe source request and any existing record, kept separate from ordinary invoice applications.
- Review questionWho must decide the treatment and authorize any resulting action?
- Ending position
- EvidenceThe documented movements and the resulting source balance at the same cutoff.
- Review questionWhat difference remains unexplained, and who owns it?
Separate a request from a posted application
Label each item according to its actual state: requested, awaiting evidence, approved, implemented or checked. A request to apply a retainer is not proof that the application has occurred. An approval is not proof that the resulting record matches the approval.
Use separate references for the request, decision and implemented record. If a reviewer changes the requested amount, preserve the original request and the later decision. This lets the next person understand the sequence without searching through unrelated messages or mistaking an earlier draft for the final instruction.
Investigate differences without forcing a balance
Check whether the records use the same cutoff, project reference and currency before describing a difference as an error. Look for repeated references, missing source documents, an application recorded outside the review period or an unresolved customer instruction. Record these as candidates for review, not conclusions.
Do not create a balancing entry, move a receipt to another project or approve a refund to make the schedule reconcile. The assistant's output is an evidence-backed question packet. Accounting treatment and contractual interpretation remain with the authorized reviewers.
An illustrative cross-project request
A customer has two projects. The source packet identifies a receipt for project A, while a new message asks for an application against an invoice on project B. The assistant records both project references, attaches the original receipt instruction and links the new request.
The item remains awaiting review until the authorized owner confirms whether the requested use is permitted and provides implementation instructions. The assistant does not treat the shared customer name as sufficient authorization. After an approved action is completed, the resulting record is linked back to the decision so both project histories remain understandable.
Return a decision-ready packet
Deliver the movement schedule, source index, unresolved questions and approval references together. Make it clear which items are ready for review and which still need a document or customer clarification. Give each unresolved item an owner and next-review date.
When the review closes, retain the agreed schedule and its cutoff, the reviewer's decision, and the references used to check implementation. A later change should create a new version or dated entry rather than silently replacing the earlier result.
For recurring accounts payable and receivable support, agree on project identifiers, document access and approval responsibilities before the assistant begins. The scope should distinguish administrative preparation from decisions about retainer use, revenue treatment, credits and refunds.
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.


