A recurring invoice checklist is the small set of checks that keeps a monthly billing cycle from depending on memory. For a virtual assistant, the checklist should connect the billing date to the source records, the contract terms, and the approval path. An invoice that is accurate but late can still damage a client relationship. The checklist exists to make both accuracy and timing visible.
Start from the billing date, not the invoice date
Record the date the client expects to receive the invoice and work backward from it. A cycle that starts on the day the invoice is due has no room for a correction. The assistant should note the internal cut-off for approval and the client's payment terms. These dates are different and should not be merged into one reminder.
Check whether the billing date falls on a weekend or a client holiday. Move the internal preparation earlier rather than assuming the client will accept a late invoice. Record the adjusted date and the reason in the cycle log. A predictable adjustment is easier to explain than a missed deadline.
Confirm the billing period with the contract or the client's purchase order. A monthly cycle may run from the first to the last day, while another client uses a mid-month anniversary. The assistant should not infer the period from the previous invoice. A wrong period creates a credit and a second approval cycle.
Verify the source records before drafting
List the records that support the invoice, such as timesheets, delivery confirmations, or usage reports. Check that each record covers the same period as the invoice. The assistant should mark any record that is missing or late. An invoice built on an incomplete record will need a correction later.
Reconcile the totals in the source records against the billing system. A difference may come from a missed entry, a duplicate line, or a rate that changed mid-period. The assistant should record the difference and who resolved it. Do not carry an unexplained variance into the client-facing document.
Keep a copy of the source records with the invoice packet. The client may ask for backup months later, and the assistant should not have to reconstruct it. Label the packet with the period and the version. A clear packet shortens the next audit or dispute.
Match the invoice to the contract terms
Check the rate, the currency, the tax treatment, and the payment terms against the current agreement. A rate that changed in the contract should not wait for the client to notice. The assistant should record the clause or amendment that supports the figure. A verbal promise is not enough evidence for a rate change.
List every recurring line item and confirm that it still applies. A service that was paused last month may not belong on this invoice. The assistant should also look for new items that were approved during the period. Both omissions and extra lines create questions.
Apply the agreed rounding and discount rules exactly as written. A small rounding difference can look like an error when the client compares invoices across months. Record the rule beside the calculated line. Consistency is easier to defend than a case-by-case explanation.
Route approvals before the cut-off
Name the person who approves the invoice and the backup who can approve when they are away. The assistant should send the packet early enough for a real review. A request that arrives at the cut-off is only a notification. Record the approval time in the cycle log.
Give the approver a short summary of what changed since the last invoice. Highlight new line items, removed items, rate changes, and any variance from the source records. The summary should link to the supporting file rather than repeat it. An approver who has to hunt for the change will either delay or approve blindly.
Record any conditional approval and the step that remains open. An approver may accept the amount but ask for a corrected description before sending. The assistant should not treat that as a full approval. The invoice leaves only when every condition is closed.
Record what changed since the last cycle
Keep a short change log beside the invoice packet. Note new services, ended services, rate changes, credits, and one-time charges. The log should also record the person who approved each change. This makes the next invoice faster to prepare and easier to explain.
Compare the current invoice to the prior one before sending. A line that moved without an explanation may be a data entry error. The assistant should investigate before the client sees it. A two-minute comparison can prevent a credit memo.
Carry unresolved questions into the next cycle with an owner and a due date. A question that disappears from the checklist will usually return as a client complaint. The assistant should review open items at the start of each cycle. The log is a working record, not a museum.
Reconcile payment and close the cycle
Record the invoice number, the send date, the amount, and the expected payment date. When payment arrives, match it to the invoice and note any short payment or deduction. The assistant should route a discrepancy to the owner rather than adjust the record alone. A closed cycle has evidence for both the charge and the payment.
Send a polite follow-up when payment passes the agreed terms. The message should reference the invoice, the due date, and the person to contact with a question. Keep the tone neutral and avoid speculation about intent. A documented follow-up protects the relationship and the record.
Close the checklist with a short note on what slowed the cycle down. Maybe a source record arrived late, or an approval path changed. The assistant should propose one fix for the next cycle. A checklist that never changes is not learning from its own history.
Key takeaways
Work backward from the client's expected invoice date and set an earlier internal cut-off. Confirm the billing period from the contract rather than the prior invoice. A late but accurate invoice still creates avoidable friction. Record the adjusted internal date whenever a weekend or holiday moves the preparation earlier.
Reconcile timesheets, delivery records, and usage against the billing system before drafting. Keep the supporting packet with the invoice. An unexplained variance should never reach the client. Label the packet with its period and version so a later reviewer can match it to the invoice without asking.
Check rates, currency, tax, and payment terms against the current agreement. Summarise changes for the approver and record any conditional approval. An invoice leaves only when every condition is closed. A rate change should point to the clause or amendment that authorizes it rather than to a verbal promise.
Log what changed since the last cycle and compare the new invoice to the old one. Track payment and follow up against the agreed terms. Close each cycle with one concrete improvement. The change log should also record who approved each new line so the next invoice can be prepared faster.
Continue building the workflow
Related support: onboarding operations support, contact us. The Internal Revenue Service - Recordkeeping for small businesses explains how businesses should keep records that support reported income and expenses.
Related reading
Create a vendor renewal calendar for a virtual assistant
A working renewal calendar that records the notice window, the approval path, the contract terms that decide the renewal, and the default action when an owner does not respond.
Set a document signature routing sheet for a virtual assistant
A routing sheet that fixes the signer order, the version each signer sees, the reminder cadence, and the filed copy so a virtual assistant can manage signatures without chasing the wrong person.
