Create an Invoice Discount Approval Workflow in QuickBooks Online

October 8, 2026

Bottom line: Treat invoice discounts as a controlled evidence workflow, not a bookkeeping shortcut. Gather discount requests, authority limits, margin context, credit memos, and customer communication; preserve the original request; separate preparation from approval; and record the final QuickBooks transaction ID. That structure improves period accuracy while keeping accounting, tax, banking, and policy decisions with the people authorized to make them.

Define the decision before touching QuickBooks

Write one sentence describing the decision the reviewer must make. Name the company, account, period, amount, counterparty, requested action, deadline, and business reason. A vague instruction such as “fix the balance” is not sufficient because it does not say which source controls, who can approve the change, or what a correct ending state looks like.

For invoice discounts, distinguish observable facts from conclusions. The assistant can document dates, identifiers, attachments, balances, workflow status, and differences. The owner, controller, accountant, tax professional, payroll administrator, or payment approver decides the treatment that falls within their authority. Record uncertainty as an exception rather than hiding it in a memo or miscellaneous account.

Use a stable case ID across the intake record, support folder, review note, and QuickBooks memo where policy permits. Keep sensitive bank, payroll, tax, and identity data in its approved restricted system. The working register should link to protected evidence instead of copying confidential values into a broadly shared spreadsheet.

Assemble the source packet

Start with the primary record and then collect corroborating evidence. A complete packet for this workflow normally includes discount requests, authority limits, margin context, credit memos, and customer communication. Add the relevant QuickBooks export before changes, the account or customer/vendor history, and any prior approval that shaped the current state. Preserve files as received; do not overwrite the original with an annotated version.

Check legal entity, currency, date range, time zone, account, transaction type, and unique reference on every source. Documents that look related may belong to another entity or period. Where a screenshot is necessary, capture enough context to identify the record, but retain an export or system reference whenever possible because screenshots are difficult to search and recompute.

Create a source index with filename or system link, issuer, document date, amount, purpose, access restriction, and the claim it supports. Mark missing, contradictory, or stale support. A reviewer should be able to see which fact came from which record without following an undocumented chat thread.

Build the working register

Use columns for case ID, counterparty, QuickBooks transaction ID, source date, posting date, amount, currency, account, class or location, project, current status, proposed action, evidence link, exception reason, preparer, reviewer, approval time, completion time, and follow-up owner. Add workflow-specific fields rather than forcing important details into free-text notes.

Keep the current state and proposed state side by side. This allows the reviewer to evaluate the delta and prevents the working file from implying that an unapproved change already happened. Formula cells should be locked or visibly distinguished from inputs, with control totals that tie to the relevant QuickBooks report.

Deduplicate by more than amount. Compare date, counterparty, reference, bank trace, invoice or bill number, payment method, and transaction ID. Similar amounts can be legitimate; different amounts can represent the same underlying event after fees, splits, or partial settlement. Record the reason for every merge, exclusion, or retained duplicate candidate.

Work through a realistic exception

Consider a sales representative requesting a 12 percent concession after an invoice is already overdue. The first task is not to post a balancing entry. Reconstruct the event sequence, label each supported component, and identify the exact unresolved decision. Tie the known pieces to their source records and calculate the difference without assuming what caused it.

Prepare options for the authorized reviewer. Each option should show the proposed QuickBooks action, accounts and periods affected, supporting evidence, control or customer impact, and required downstream follow-up. If the facts do not support an option, say so. A concise, evidence-backed question usually produces a safer answer than a long narrative that mixes facts and recommendations.

After a decision, record the approver, timestamp, selected option, and any conditions. Then execute only the approved mechanical steps. Capture new transaction IDs and preserve reversals, voids, or superseded records. Never delete evidence merely because the final decision differs from the initial request.

Apply access and approval boundaries

Use least-privilege access. The person assembling support does not automatically need permission to release cash, change sensitive master data, alter payroll, unlock a closed period, or approve their own work. Named credentials and multi-factor authentication improve traceability. Shared logins weaken the audit trail and make exception investigation slower.

For high-risk changes, require an independent channel. Do not verify a sensitive request using contact information supplied only in that same request. Use the organization’s trusted directory, executed contract, prior verified record, or another approved source. Document the method and outcome without exposing secrets in the register.

Set monetary and policy thresholds for review, but do not let a low amount override a high-risk pattern. Repeated small transactions, first-time destinations, unusual urgency, changed contact details, closed periods, and unsupported adjustments deserve attention even when each item falls below a normal approval limit.

Post and verify the approved result

Before entry, confirm the company file, date, accounting basis, account mapping, tax code, class, location, project, customer or vendor, and attachment policy. Search again for an existing transaction. Use the approved effective date and description; do not backdate work merely to make a report appear complete.

After posting, rerun the same report used for the baseline and compare the expected change with the actual change. Check related subledgers, bank or card registers, aging, project reports, and reconciliation status where relevant. A correct-looking general-ledger total can still conceal a broken customer, vendor, payroll, tax, or project record.

Store the before-and-after totals, QuickBooks ID, posting time, preparer, reviewer, and any remaining exception. If the approved action did not produce the expected result, stop and reopen the case. Do not stack a second unsupported adjustment on top of the first.

Review the queue on a fixed cadence

Review open cases by age, value, risk, deadline, and dependency. Separate “waiting for source,” “waiting for approval,” “approved for entry,” “posted pending verification,” and “complete.” Those states make bottlenecks visible and prevent an email reply from being mistaken for completed work.

Useful measures include opening cases, new cases, resolved cases, median resolution time, value awaiting approval, items reopened, missing-evidence rate, and recurring root causes. Interpret measures with context. A rise in exceptions can reflect better detection, seasonal volume, a system change, or weaker inputs; it is not automatically evidence of poor performance.

Finish with a short decision record and the next preventive action. That action might be a required field, earlier document request, revised permission, recurring review, or clearer owner. The goal is not only to close today’s case, but to make the next invoice discounts case easier to recognize and resolve.

Practical handoff checklist

• Preserve the original request and primary evidence.
• Tie the working population to a dated QuickBooks export.
• Show current and proposed states separately.
• Route accounting, tax, payment, payroll, and policy decisions to authorized reviewers.
• Record approval before changing the books or releasing value.
• Verify the result in both the general ledger and affected subledger.
• Retain transaction IDs, exceptions, and the final decision record.

For general record-retention context, review the IRS business recordkeeping guidance and the SBA financial management guidance. Product-specific steps should be checked against current QuickBooks Online help. Compare the available QuickBooks VA services and contact QBOAssistant to turn the workflow into a controlled recurring handoff; authorized professionals retain judgment and approval.