Research question
How can a small business test whether costs intended for customer reimbursement were completely and accurately carried from a vendor transaction into a customer invoice and ultimately collected? QuickBooks Online can mark expenses billable and associate them with a customer or project. That feature creates useful links, but it does not prove the source was valid, the customer agreed to the charge, the correct amount reached an invoice, or the invoice was paid.
This study proposes an evidence-chain method for QBOAssistant clients. It treats recovery as a sequence of separately testable events rather than a single report total. The output is an exception file for owner or accounting review, not an instruction to invoice every marked cost.
Why recovery is a linkage problem
A reimbursable cost can fail at several points. The vendor transaction may lack support. The cost may be assigned to the wrong customer. A user may forget the billable flag. The cost may appear in an invoice at the wrong amount, be intentionally excluded under a fixed-fee agreement, be credited later, or remain in an unpaid invoice. Looking only at unbilled charges catches one class of failure and misses the rest.
The business terms matter as much as the QBO configuration. A receipt can prove that money was spent without proving the customer owes reimbursement. A contract can authorize a category of pass-through costs without proving a particular purchase belongs to the engagement. An invoice can prove that the business requested payment without proving collection. Evidence must therefore be matched to the proposition it supports.
Methodology
Define a customer-project-period population before reviewing outcomes. Start from source expenditures that policy or contract might permit the business to recover, not merely those already marked billable. Depending on the workflow, the population may come from expense, check, credit-card, or bill transactions plus supporting receipts and vendor credits.
Assign each source a stable case identifier. Capture vendor, transaction date, amount, tax treatment if relevant, customer or project, billable state, markup, source-document reference, and the applicable agreement clause or approval. Then trace forward to any linked invoice line, subsequent credit or void, payment application, and remaining receivable. Preserve both gross source cost and the amount presented to the customer; do not net exceptions prematurely.
Classify cases as properly recovered, validly nonrecoverable, awaiting invoice, invoiced and open, partially recovered, misassigned, duplicated, unsupported, credited, or unresolved. The classification rule should be written before reviewers see aggregate recovery rates.
Five links in the chain
The source link asks whether the vendor-side transaction represents a real business cost and has adequate support. The entitlement link asks whether the agreement, policy, or specific approval permits charging that customer. The assignment link asks whether QBO points to the correct customer and project. The presentation link asks whether the cost reached an invoice accurately and understandably. The settlement link asks what happened after invoicing.
These links should remain distinct. For example, an airfare receipt may be genuine and correctly assigned, but the customer agreement may cap travel recovery. A $500 cost invoiced at $550 may be correct under an authorized markup or incorrect under a pass-through-only agreement. A paid customer invoice may include the line, but an unapplied payment or later credit can complicate the apparent outcome.
Population completeness
Testing only QBO records already marked billable creates a circular result: omitted flags disappear from the review. A stronger population begins with cost categories, vendors, projects, cards, or employee reimbursements that plausibly contain recoverable spending. The reviewer then tests whether each item should or should not enter the billable workflow.
Completeness also requires vendor credits and refunds. If a supplier refunds a cost after it was billed to a customer, the business may need a customer-facing decision under the agreement. The administrative record should connect the original cost, vendor recovery, owner decision, and any customer credit. It should not assume the accounting or contractual result.
Worked example
Suppose a consultant pays a $420 permit fee for Project Alder. The receipt and card charge agree. The customer agreement permits permit fees at cost, and the expense is assigned to Project Alder, but it was not marked billable. The invoice for the month includes a generic $500 disbursement line entered manually.
The source and entitlement links are supported, while presentation is ambiguous. The manual line might include the permit plus another cost, or it might be unrelated. Matching only on amount would miss it; treating the $420 as unbilled without reviewing the invoice support could duplicate the charge. The reviewer should request the invoice-line composition and approval record, then classify the case. If the $500 consists of the $420 permit and an authorized $80 filing fee, the missing system link is a traceability defect rather than a recovery loss.
This example illustrates why a link exception and a financial exception are not identical. Both should be reported, but they call for different decisions.
Measures and interpretation
Useful measures include source-cost population, supported recoverable amount, amount linked to invoices, amount collected, valid exclusions, open invoice amount, unresolved amount, median days from cost to invoice, and exception counts by failure point. Counts should accompany percentages and dollar totals. Large values and old items deserve visibility, but thresholds belong to the business owner or accounting policy.
A low invoice-link rate can reflect missed workflow, fixed-fee arrangements, deliberate absorption, or incomplete documentation. A long lag may reflect billing cadence rather than neglect. Recovery percentage should not become an employee scorecard because incentives can encourage inappropriate customer charges or premature invoicing.
Administrative workflow
A QBO support specialist can assemble the candidate population, export billable-transaction and invoice details, attach source references, identify broken links, age unresolved cases, and document owner decisions. The specialist can also verify that an authorized invoice or credit appears as approved.
The specialist should not interpret a contract, decide that a customer owes a disputed cost, invent a markup, alter a closed-period source transaction, or apply a payment to force apparent recovery. Contract interpretation, revenue recognition, sales-tax treatment, write-offs, and material accounting decisions must be escalated to the designated owner, accountant, tax adviser, or legal reviewer.
Controls for ongoing use
At intake, require customer or project assignment and source evidence for candidate recoverable costs. At billing cutoff, review both marked-billable items and a risk-based population of plausible omissions. After invoicing, preserve the invoice link and separately monitor open receivables. When credits, refunds, or disputes occur, reconnect them to the originating case rather than opening an unlinked adjustment.
Access should follow least privilege. Receipts and agreements may contain payment, travel, or personal information that does not belong in a broad exception report. The working file can use references and restricted attachments instead of reproducing every sensitive field.
Limitations
This is a control design, not a finding about any client. QBO plans, settings, and interfaces differ. Third-party expense, time, billing, and payment systems can break native links or add authoritative records. Customer agreements vary, and a QBO billable designation does not establish a legal right to payment.
The method cannot determine whether revenue should be recognized, whether a cost is deductible, whether a markup is taxable, or whether a disputed charge is collectible. Manual invoice descriptions may prevent automated matching. Sampling can miss rare categories, and a complete documentary chain can still contain false information. Conclusions should state the population, period, systems, matching rules, and unresolved assumptions.
Conclusion
Billable-cost recovery is best evaluated as a five-link chain: source, entitlement, assignment, presentation, and settlement. Starting with the plausible cost population avoids the blind spot created by reviewing only items already flagged as billable. By separating traceability defects from actual recovery outcomes, QBOAssistant can surface actionable exceptions while leaving commercial and accounting judgment with the authorized reviewer.