Build a Billable Expense Markup Approval Log in QuickBooks Online

Published November 3, 2026

Most billable expense problems do not begin with a missing receipt. They begin with a markup that someone changed, waived, or applied twice, and nobody can show who approved it. A markup approval log gives the team a short, dated record that connects the expense, the rate, the approver, and the customer invoice. The log is not a second billing system. It is the evidence layer that makes the existing QuickBooks Online workflow reviewable. It matters most when a customer disputes a charge, when a new account manager inherits a project, or when the team cannot tell whether a rate was intentionally changed or entered by mistake.

Why markup needs an explicit approval record

A billable expense markup often sits inside a project or customer record where the rate is easy to edit and hard to trace. The person entering the bill may know the agreed rate, while the person reviewing the invoice may not. When the two disagree, the team usually reconstructs the decision from email, which is exactly the situation the log is meant to prevent. The approval record also separates the calculation from the decision. A VA can compute a markup, compare it with the agreement, and flag a difference. The account manager or owner decides whether the customer should see the new rate. Keeping those roles distinct protects both the customer relationship and the person preparing the invoice.

Capture the expense and the billing link

Start with the expense transaction in QuickBooks Online. Record the vendor, the date, the amount, the project or customer, and the billable status. If the expense is not marked billable, do not add a markup entry until the billing owner confirms that the charge should be passed through. Then record the invoice or pending invoice that will carry the markup. A markup log without a destination is only a note; the reviewer needs to see which customer document will reflect the change. If the expense is split across several invoices, record each allocation and the basis for the split.

Record the rate, the source, and the approver

The rate field should show whether the markup is a percentage or a fixed amount, and it should include the basis, such as cost plus ten percent or a flat handling fee. Record the source of the rate: the customer agreement, a project change order, a written email approval, or the standard policy. A rate without a source cannot be defended when the invoice is questioned. The approver should be a named person, not a team or a shared inbox. Record the approval date and the exact scope that was approved. If the approval covers one invoice, do not apply it to later invoices without a new decision. If the approval covers a period, record the start and end dates and the next review point.

Handle waivers and exceptions separately

A waiver is not the same as a missing markup. When the team decides not to charge a markup, record the reason, the person who approved the waiver, and the customer or project affected. That record prevents a later reviewer from assuming the charge was forgotten or that the rate was entered incorrectly. Exceptions should also cover unusual calculations, such as a markup on a partial credit, a mixed-rate invoice, or an expense that was re-billed after a correction. Write the exception in plain language and link the supporting document. Do not overwrite the original entry; add the exception beside it so the history remains visible.

Review the log before the invoice is sent

The pre-invoice review should confirm three things: the expense is billable, the rate matches an approved source, and the destination invoice is the correct customer document. If any of those is missing, the invoice waits for the owner rather than relying on an assumption. A short checklist is enough when the log fields are complete. The review should also look for patterns. Several waivers from one account manager may indicate a policy problem, while repeated rate differences from one vendor may indicate a contract or data issue. The pattern is a process signal, not a performance score, and it should lead to a specific change with an owner and a date.

Reconcile the log to the invoice

After the invoice is posted, reconcile the markup entry to the invoice line. Confirm the amount, the customer, and the description match the approved record. If the invoice was revised, keep the earlier version and note what changed. A reviewer should be able to follow the path from the original expense to the final customer charge without opening a private message thread. A monthly reconciliation should sample ordinary charges, waived charges, and corrected charges. Check that every sampled invoice has a matching log entry and that every log entry has a destination. Disagreements should be routed to the billing owner with the specific gap rather than resolved by editing the log to fit the invoice.

Close with a record the customer team can read

At the end of the project or billing cycle, summarize the markup entries, the waivers, and the open exceptions. Keep the summary short and link it to the source documents. The customer team should be able to read one entry and understand what was charged, why, and who approved it. A good markup log does not eliminate disagreements about price. It makes the team's decision visible before the customer asks, and it gives the next reviewer a defensible answer. That is a stronger position than a clean invoice that cannot be explained.