QuickBooks Online Advanced, Set Up and Run Right

QBO Advanced is a subscription tier of QuickBooks Online, not a separate accounting system. The double entry engine underneath is the same one running in Simple Start and in Plus. What the higher tier buys is administrative reach. You get more user seats, custom user roles, batch entry of invoices and bills, approval routing that sends a transaction to a second person before it posts, deeper class and location tracking, custom fields on transactions, and a reporting layer that sits on top of the ledger. For a company that has outgrown a single bookkeeper and now has four people touching the books, that reach earns its keep. A shop pushing 12,000 dollars a month through accounts payable with one approver almost never needs it. A distributor pushing 480,000 dollars a month across two divisions with four approvers usually does. The question is never whether the features are good. The question is whether anyone will use them.

Judge the decision in cost per hour saved rather than in feature count. Say the upgrade runs about 2,400 dollars more per year than the tier below it. If batch invoicing and recurring bill entry cut six hours a month out of your controller’s close, and that controller costs 60 dollars an hour fully loaded, the tier pays for itself with room to spare. That is 4,320 dollars of recovered staff time measured against 2,400 dollars of added subscription cost. If nobody changes how they work, the same 2,400 dollars buys a longer feature list and nothing else. We have watched a client move up a tier, keep entering every bill one at a time, then ask why the close still ran nine days. The file did exactly what it was told. Nobody told it anything new.

The mistake we see most often is treating the upgrade as a cure for a reporting problem that is really a chart of accounts problem. A profit and loss statement with 240 accounts does not become readable because the file can now build a custom report. It becomes readable when someone collapses the account list down to the 45 lines an owner actually manages and pushes the remaining detail into classes. Structure comes first and the software follows behind it. The IRS expects books that support every number reported on a return, a standard the agency sets out in its guidance on recordkeeping. Publication 583 walks a growing company through what to keep and how long to keep it, and the agency page on operating a business lays out the rest of the compliance calendar.

Two limits deserve a mention before anyone signs an order form. QBO Advanced is still QuickBooks Online underneath. Inventory costing runs on average cost with no layered options, which matters if your industry prices on specific identification. Revenue recognition is not automated, so a software company spreading a 36,000 dollar annual contract across twelve months will still keep a spreadsheet schedule and post monthly journal entries by hand. Multi currency handling stays blunt next to a mid market system such as NetSuite or Sage Intacct, and a firm invoicing in euros often finds the exchange gain and loss accounts hard to explain to a reviewer. Knowing where the tier stops saves a painful second migration eighteen months later.

We usually run a two month diagnostic before recommending any tier change. We count transaction volume. We count the people entering data. We look at how long the last close really took, then read the prior year working papers for forced entries and plugged balances. That review sits inside our bookkeeping work, and the planning conversation that follows it sits inside tax strategy consulting. Sometimes the answer is no. A five person firm with clean books and one approver is usually better served staying on the lower tier and buying two more hours of monthly review. Federal rules drive most of this, though state treatment of the underlying income varies, and our clients in Austin, Chicago, Los Angeles, Miami, and New York City each carry a different state layer on top of the same federal return.

Intuit keeps moving automation behind its higher plans, so a company planning real growth should model the switch during a quiet quarter instead of during a rushed year end.

Internal control in a small company usually fails at one point. Everyone signs in as the administrator. Once four people share a single login, the file can still tell you that an invoice was voided at 11:42 on a Tuesday, but it cannot tell you which human did it. QBO Advanced answers that problem with custom roles and named seats. You can build a role that lets a salesperson create an estimate without ever seeing payroll. A clerk can enter bills without approving a payment. An outside reviewer can read every report and touch nothing. Once each person has a named seat, the audit log carries a name next to every change, and that single fact changes how a team behaves. People are more careful when their name lands on the entry.

The audit log records who touched a transaction and what the values looked like before the change. That history matters in two situations. The first is an internal problem. A bookkeeper who cuts a check to a personal vendor and then deletes the bill leaves a trail that a shared administrator login would have erased completely. The second is an outside examination. When the IRS opens a correspondence exam and asks how a 12,000 dollar deduction was supported, the answer lands better if the file can show the entry date next to the attached receipt and the name of the person who approved it. The agency page on understanding an IRS notice or letter describes what a first contact usually asks a taxpayer to produce. No return is beyond an audit, and no software removes every audit risk, but a file with a clean change history shortens the conversation and lowers the professional fees that come with it.

Consider a construction company with 4,800,000 dollars in revenue and a two person accounting department. Before the change, both people held full administrative rights, and the owner learned about a duplicate vendor payment of 12,000 dollars only when the vendor called to return the money. After the change, bill entry and bill approval sat with different people, and any payment run above 5,000 dollars needed a second approval inside the file. The control cost nothing beyond the seat license. It caught a second duplicate of 3,400 dollars within a quarter and a misposted subcontractor invoice a month after that. Segregation of duties is not a large company idea. It is the cheapest fraud control a small company owns, and the tier makes it possible without hiring anyone.

The common mistake is building the roles once and never revisiting them. Staff move around. A clerk promoted to office manager keeps the old permissions and picks up new ones, and after three years the role list describes a company that no longer exists. Put a reminder on the calendar to review the user list twice a year, and pull a departed employee’s access on the day they leave rather than the week after. Payroll access deserves a review of its own, since the same file usually holds the wage detail that feeds employment taxes and the quarterly Form 941. A payroll register visible to the whole staff creates a human problem long before it creates a tax problem.

We build the role map with the client rather than handing over a template, because the right split depends on who actually does the work each week. That design work sits inside our bookkeeping engagement, and the questions it raises about owner compensation and entity structure sit inside tax strategy consulting. A file with named users and a live audit log is also the file a lender wants to see when a line of credit comes up for renewal, since it tells the credit officer that the numbers were reviewed by someone other than the person who entered them.

Set the permissions while the team is small, because retrofitting control onto a department of nine costs far more than designing it for a department of three.

No, and the two solve different problems. An account answers what the money was spent on. A class or a location answers which part of the business spent it. When a company blurs that line, the account list swells and every report gets harder to read. We often meet a file where someone created separate expense accounts for rent at the north shop and rent at the south shop, then repeated the pattern for utilities and insurance until the chart carried 300 lines. Rebuilt properly, that file has one rent account and two locations. QBO Advanced then produces a profit and loss statement by location without anyone touching the account list again.

Here is the practical version. A restaurant group with two locations books 1,900,000 dollars of revenue in the year. Under the old structure, the owner could see total food cost but not food cost by store. After the rebuild, the north store showed food cost at 31 percent of sales and the south store at 38 percent, a spread of about 12,000 dollars a quarter on comparable volume. That gap turned out to be a portioning problem at one station, not a pricing problem across the group. The tier did not find the problem. Segment reporting made the problem visible, and a manager who could read the report found it in an afternoon.

The common mistake is letting transactions post without a class. A file where 8 percent of expenses land in the unclassified bucket produces reports that never quite tie, and people stop trusting them within two months. Turn on the warning that flags a transaction missing a class, and run an unclassified report as part of every close before the books are locked. The second common mistake is using classes to track something that belongs in a customer or a project field, such as a single job that runs for six weeks. Classes work best for parts of the business that will still exist in three years.

Custom fields are the quiet companion to class tracking, and most teams underuse them. A field on the sales transaction that captures the referral source, or a field on the vendor record that stores a contract expiration date, gives you sorting power that no account structure can match. Reports built on those fields can be scheduled and sent by email on a set day, which is how a spread out team keeps a monthly rhythm without another meeting. Keep the field list short. A file carrying 22 custom fields turns into its own maintenance project, and the person who designed it rarely stays long enough to explain the logic to a successor.

Segment tracking also has real limits. The balance sheet by class report only works when every side of an entry carries the same class, and most files fail that test on payroll and on transfers between bank accounts. Revenue recognition is another gap. If your company collects cash in advance, the class field does nothing to move that money into the right period, and you still need a deferred revenue account with a monthly release entry. Your method of accounting governs the timing, and the rules for choosing or changing a method appear in Publication 538. Which expenses may be deducted at all is a separate question covered by Publication 535, and the underlying documentation standard runs back to the agency guidance on recordkeeping.

Clean segment data pays off directly at tax time. A partnership allocating income across two lines of business needs numbers that hold up when the Form 1065 schedules are built, and an S corporation reporting on Form 1120-S faces the same test when owners want to understand where their K-1 income came from. We design the class structure alongside the return rather than after it, through our bookkeeping work and the planning that happens in tax strategy consulting.

Design the account list and the class list together before the next fiscal year opens, because renaming segments midyear leaves you with comparative reports nobody can use.

Migrate a broken file and you own the same problems at a higher monthly rate. Before any move to QBO Advanced, reconcile every bank account and every credit card through the last closed month, then print the reconciliation reports and keep them somewhere outside the software. Clear the undeposited funds account. We regularly open a file holding 12,000 dollars of stale deposits parked there since two summers ago, each one a customer payment recorded twice. Agree the accounts receivable aging and the accounts payable aging back to the general ledger control balances. Look hard at opening balance equity, which should be zero in any file that was set up correctly and rarely is.

Then work through the balance sheet line by line. Inventory on the balance sheet should agree to a physical count, not to whatever the software believes. Negative quantities are a warning sign that someone sold an item before receiving it, and those errors distort cost of goods sold in both directions. The fixed asset list deserves the same care, because the book asset schedule should reconcile to the depreciation detail supporting Form 4562. A client of ours carried a delivery van at 24,000 dollars in the ledger years after selling it for 9,000 dollars, which meant the gain never got reported and the depreciation kept running. That is a tax problem wearing a bookkeeping costume.

Vendor data is where most migrations quietly fail. Every vendor who might receive a Form 1099 needs a current Form W-9 on file, with the legal name, the tax classification, and the taxpayer identification number entered into the vendor record rather than kept in an email folder. Set the 1099 tracking flag correctly during the cleanup instead of in January, when nobody can reach a subcontractor who moved. The reporting rules themselves sit on the agency page for Form 1099-NEC, and the broader documentation standard appears in the guidance on recordkeeping.

Users and permissions belong in the migration plan as well. Decide who will hold the primary administrator seat before the conversion rather than after it, and keep that seat with an owner or a controller instead of an outside consultant who may not be around next year. Map each employee to the narrowest role that still lets them finish their work. Attachments need a plan too. Receipts and vendor contracts stored inside the legacy file do not always travel cleanly during a conversion, so export them separately and confirm the document count on both sides before retiring the old data. A company with 8,000 attached documents should open at least fifty of them at random after the move and confirm each one still opens.

A few settings are effectively one way, so decide before the migration rather than after. Turning on multi currency cannot be reversed in a QuickBooks Online file, and neither can several account type choices. Pick the first closing date and set a closing password on day one, because a file without one lets a well meaning clerk post a correction into a year that was already filed. We have seen a 12,000 dollar reclass land in a closed prior year, which turned a fifteen minute fix into an amended return conversation with the owner.

The common mistake is running the migration in the middle of a quarter to hit an arbitrary deadline. Move at a period boundary, ideally the first day of a fiscal year, and keep the legacy file readable for at least three years so the prior data stays available for any exam. Our team handles this sequence as part of bookkeeping, and the entity questions that surface during cleanup get answered inside tax strategy consulting. Plan on four to six weeks for a company with two years of history and considerably more for anything carrying inventory.

Start the cleanup a full quarter before the target cutover date, because every hour spent tidying the old file saves several inside the new one.

No. An upgrade adds capacity, and capacity does not reconcile anything. Reconciliation is a human comparison between what the bank says happened and what the ledger says happened, and no tier performs that judgment for you. If the operating account has not been reconciled since March, moving to QBO Advanced in September gives you nine unreconciled months in a nicer interface. Fix the ledger first. Then upgrade. Doing it in that order also gives you a clean starting balance, which makes every report produced afterward defensible to an outside reader.

Month end close is a checklist, not a feature. Reconcile the cash accounts and the credit cards. Tie the payroll expense in the ledger to the payroll provider reports, including the wage totals that flow through employment taxes. Review the balance sheet for anything that should have cleared, then read the profit and loss statement against the prior month and ask about every swing over a set threshold. One client set that threshold at 12,000 dollars and found a duplicated insurance accrual in the first month of using it. The approval routing in the higher tier does help a close finish on time, because it stops transactions from sitting in one person’s inbox for a week, but the discipline still belongs to a human being with a calendar.

Contractor reporting is the other place where owners expect the software to save them and it does not. The file only issues an accurate Form 1099 if the vendor record was set up correctly, if a Form W-9 is on file, and if payments were coded to accounts mapped to the right box. Payment method matters too. Amounts paid by credit card or through a third party settlement network are generally reported by the processor on Form 1099-K, so including those same payments on your own Form 1099-NEC double reports the contractor. Rent and certain other payments still belong on Form 1099-MISC rather than on the newer form. A contractor paid 46,000 dollars during the year, half by check and half by card, gets a form from you covering the check portion only.

One more expectation deserves correcting. The higher tier does not change your method of accounting, your entity type, or the filing deadlines you face. A cash basis company stays on cash basis until it files for a change, and an accrual company still has to record its accruals by hand. The software will happily produce a report labeled accrual from data that was entered on a cash basis, and an owner who trusts that label ends up making decisions on numbers that were never assembled properly. Ask your accountant which basis the reports actually reflect before you hand them to a bank or a prospective buyer.

The common mistake is calling the books audit ready because the software is expensive. Readiness comes from reconciled accounts, source documents attached to transactions, and a change history that shows who approved what. No file is beyond an audit, and nobody can promise a particular outcome with the IRS or with a lender. What clean books do is shorten the response time and reduce the odds that a small question grows into a large one. A bank underwriting a 750,000 dollar facility will ask for interim statements, and a file that ties to the tax return without a page of reconciling adjustments moves through credit review noticeably faster.

If your ledger is behind and the year end is approaching, request a consultation and we will scope the cleanup before recommending any tier change. That work runs through our bookkeeping team, the owner level planning happens in tax strategy consulting, and the personal filings that depend on the business numbers are handled alongside our work on individual tax returns. Federal rules govern the reporting itself, while state treatment varies across the metros we serve.

Get the ledger current first, then let the added capacity of the higher tier carry a business that is already keeping its own books honestly.