QuickBooks Online Customer Credit Limit Document Review

August 23, 2026

Bottom line: every customer credit limit should be a documented decision with an approver, an effective date, and a visible exception path when the open balance or pending activity approaches or exceeds the approved amount.

Sidebar: Credit is a risk decision. Documentation keeps that decision reviewable and repeatable.

Why this review matters for AR and operations

A customer credit limit affects revenue timing, inventory commitment, and collection risk. When limits live only in memory or in a spreadsheet that was last updated six months ago, two problems emerge. A salesperson approves a new order that pushes a high risk customer beyond a threshold no one can verify, or a collections team places a hold that surprises the sales desk because the limit basis was never recorded. Both situations erode trust internally and with the customer.

For QBOAssistant clients, the VA often maintains the customer facing record in QuickBooks Online, including contact detail, terms, and custom fields used to carry credit context. The assistant may also prepare the report that shows open invoices, unbilled time or orders that will become invoices, and the resulting exposure. The VA does not decide creditworthiness, negotiate payment terms, or override a hold. A document review preserves that separation by keeping the limit, the approval, and the exception visible together.

Without a review trail, the rationale for a limit is lost when the reviewer changes. A new credit manager cannot answer whether the 50,000 limit reflects historical volume, a recent financial review, or a temporary accommodation during supply disruption. The document review reconstructs that context so future decisions build on it.

Define the population first

Start with a report set that shows current exposure. In QuickBooks Online this usually includes the Accounts Receivable Aging Detail as of the review date, the Open Invoices list, any pending estimates or sales orders that the business counts toward exposure, and the Customer List with any custom field or note that stores the credit limit. Export or save the population before proposing any change. Record the pull date, filters, preparer, and reviewer. If sub-customers are used for different locations or divisions, state whether exposure rolls up to the parent or remains separate by job. That scope note prevents a later assumption that a parent limit covered a job that was evaluated on its own.

Group exposure by customer. The useful grouping shows one customer with its open AR balance, pending orders or unbilled items, the stored limit, the calculated utilization, and the last review date for that limit. If the business treats certain items as non-credit exposure, such as cash on delivery orders or fully prepaid work, document the exclusion and where that class is reviewed.

State what is excluded. For example, intercompany customers or employees treated as customers may be tracked in a different lane, and customers on cash on delivery terms may have zero approved credit by definition. A clear exclusion list keeps the review complete for its defined population.

Record the evidence for each customer

For each customer in scope, keep a single row that ties together the operating and approval facts. Begin in QuickBooks: customer display name, customer ID or reference used internally, open AR balance, pending order or unbilled amount if the business includes it, stored credit limit, limit status such as current, under review, or temporary, and days since the last limit review. Add the revenue or payment history that supports limit thinking: average monthly invoices over the last quarter, average days to pay, and any prior hold or exception in the recent period, without adding financial opinions.

External support is the basis the reviewer used to set the limit: a credit application on file, trade reference notes, bank reference where applicable and appropriately stored, or internal guidance such as a policy threshold that assigns a default limit to new customers. Link the document location where it is stored under controlled access rather than copying sensitive data into the review queue. If the limit was modified after a payment pattern improved or deteriorated, link the specific payment history that triggered the change note.

Add the approval trail: who approved the current limit, on what date, for what term, and whether the approval was for an ongoing limit or a temporary increase tied to a specific order. Keep the approver and the evidence together so a later reviewer does not have to hunt for the email or meeting note that authorized the change.

Check three elements for every customer. First, the stored limit should match the approval on file, with no silent edit between reviews. Second, total exposure should be calculated consistently across customers, including or excluding pending items in the same way. Third, any exception such as utilization above 85 percent or an open balance that already exceeds the limit should be flagged as an exception rather than left as a silent overage.

Make exception handling predictable

Approaching threshold is the most common exception. A customer with a 25,000 limit has 23,500 in open AR and a pending estimate that will add 4,000 on acceptance. The review should flag that the next order would breach the limit and draft a specific question for the owner: hold until a payment is received, require a revised payment schedule, reduce the next order quantity, or approve a temporary increase with a stated expiration. The VA documents the scenario. The reviewer chooses.

At or over limit is a stronger exception. An open balance of 31,000 against a 30,000 limit requires an immediate owner note, not just a queue entry. Record the overage amount, the oldest invoice composing the overage, and any payment already in transit that may bring the balance down. Do not release new orders automatically while the review is pending. Hold the account in the exception queue with a clear status.

New customer without a documented limit is a setup exception. The QuickBooks record may show no limit, or a new customer was created with a placeholder value that does not reflect policy. Flag the account as limit approval pending. Include the expected handling under policy, such as a defined starter limit for verified customers, and ask the reviewer to confirm.

Limit expired is another pattern. A temporary increase that was approved through August 31 is still active on September 5 because no one revoked it. Flag the expiration failure as its own exception, separate from utilization. The question should ask whether to revert to the standing limit, extend the temporary terms, or reassess based on recent payment performance.

Stale limit review is a calendar exception. A customer's limit has not been reviewed for twelve months despite growing volume. Flag the account as review due based on the time threshold the business uses. The VA can note that the balance and payment history are ready for the next review session rather than proposing a new limit in the queue.

Build the packet the owner can review

A working packet should fit on one file with links and clear ownership. Start with a cover sheet that names the business, review date, population definition, preparer, reviewer, and the count of accounts in each exception type. That header tells the owner where risk concentrates before the detail does.

Follow with the exception table, one row per customer that is at or approaching threshold, over limit, pending setup, expired temporary, or due for periodic review. Each row carries customer identification, open AR, pending amounts, stored limit, utilization, last review date, approval reference and evidence link, exception type, impact note, and owner. An impact note can be brief and factual: next order would exceed limit by 2,500, overdue invoice 45 days included, or new customer limit pending before first shipment.

Include a holdings note that lists customers intentionally excluded from the hold logic, with approved reason and expiration where relevant. Include a pending approvals section that separates customers waiting on documentation from customers waiting on an approver.

Add a cutoff note that defines whether pending estimates are included in utilization and as of what date the exposure was calculated. That single sentence often resolves half the follow up questions a reviewer would otherwise ask.

Use simple statuses such as within limit, approaching threshold, hold pending payment, temporary increase awaiting expiration, new customer approval pending, or review due. Close an exception only when the approved limit is stored, the hold is released or maintained with a documented instruction, or the temporary terms have a new expiration on file.

Cadence, ownership, and quality checks

For active receivables clients, run the review monthly and again before any large order release that would materially change exposure. The VA refreshes balances and pending queues, links approval evidence, drafts specific questions for exceptions, and presents the packet on a fixed day. The owner or credit approver reviews exceptions, documents approvals, and decides whether sales may proceed. Between cycles, the VA flags any new order that would breach the threshold the same day rather than waiting for the next monthly pass.

Archive the packet with the aging export and the approval links so an accountant or auditor can trace why a customer was allowed to exceed the prior limit or why a limit was kept conservative despite volume.

A reviewer should be able to answer quickly after reading the packet: which customers are within limit, which are approaching it, which are over it, which new customers need a documented limit before product ships, and which temporary approvals have expired.

Helpful quality checks include asking whether every limit on file has an approver and date, whether every high utilization case was flagged before the next order shipped, whether any new customer was assigned a limit without approval, whether any temporary increase lacked an expiration, and whether any hold was released without a documented instruction.

The QuickBooks bookkeeping VA service outlines preparation boundaries for AR controls. For terms context, pair this with the QuickBooks AR aging review.

What good looks like

Good looks like credit discussions that happen before a shipment or service delivery, not after a balance has already grown uncomfortable. Sales knows the limit and the hold reason. Finance knows the approval and the evidence it rested on. Customers experience a clear, consistent message about why a limit or a payment before shipment is required. And the VA never has to infer creditworthiness from balance alone.

Next step

Pilot the review on fifteen customers that represent the spread of risk: three low volume, three steady, three high volume, three new this quarter, and three that have hit a hold before. Build exposure rows, link approvals, and draft a concise question for each exception that would let the owner decide without reworking the file. Review the packet for clarity. Keep fields that made the decision easy, remove fields that added noise, and reuse the approved packet on the monthly cadence. That measured start turns a scattered credit discussion into a controllable workflow without changing approval authority in QuickBooks Online.