QuickBooks Pro 2013 Video Training: Build Real Skills

Why Desktop Accounting Training Still Earns Its Place

Every few months a headline declares desktop accounting dead. Then you walk into a small construction office, a nonprofit back room, or a family-run retail shop and find a perfectly healthy company file that has been maintained on a local install for a decade. The books balance. The accountant is happy. The owner knows exactly where every dollar went.

That is the reality video training has to serve. Not every learner is chasing the newest platform; many are trying to become genuinely competent in the tool that already runs their business. Structured video tutorials are unusually good at this because they show the interface, the click path, and the result in one continuous motion. You see the invoice form, you see the item list populate, you see the total change, and you see the journal entry behind it. Text instructions can describe that sequence, but they rarely teach the rhythm of the software.

This guide is organized as a practical training plan. It covers what the software does well, how to set up a safe practice environment, the transaction order that keeps a ledger clean, reconciliation as the core confidence skill, reporting, a two-week video learning sprint, common mistakes, and file-health decisions. If you teach, onboard, or support small business bookkeeping, you can adapt it directly.

What QuickBooks Pro 2013 Handles Well, and Where It Shows Its Age

The program was designed for a single small business or a very small team working on a local network. Within that scope it is fast, predictable, and deeply featured.

Strengths worth learning properly:

• Local performance. Reports run against a local file, so list-heavy operations feel immediate.
• Mature transaction flows. Estimates, progress invoicing, purchase orders, job costing, and class tracking are all present.
• Report depth. The report center includes dozens of variations on the same handful of core statements, which is powerful once you learn to filter.
• Offline reliability. No connection, no session timeout, no browser tab to lose.

Limits you should plan around:

• No automatic bank feeds. You import statements or enter transactions manually, so reconciliation discipline matters more.
• Collaboration is file-based. Multiple users need local network setup; remote teamwork means remote desktop tools.
• Operating system drift. Older installers can fight with newer system updates, printing drivers, and PDF export.
• No built-in receipt capture or OCR. You keep a parallel folder structure for documentation.
• Reporting is static. You export to a spreadsheet when you need to reshape data.

Understanding this split prevents a lot of frustration. Learners who expect cloud conveniences from a desktop install blame themselves for problems that are simply architectural.

Set Up a Practice Company Before You Touch Real Books

The fastest way to learn a bookkeeping program is to break a fake company file first. Create a practice company with sample data or build one from scratch, then deliberately make mistakes you would never risk in live books: duplicate an invoice, delete a reconciled transaction, post a bill twice.

Build a Chart of Accounts That Matches Your Reporting

Most beginners inherit a chart of accounts and never question it. In training, question everything. A useful exercise is to sketch the profit and loss statement you want to read, then work backwards to the accounts required.

Practical rules:

• Keep the account list short. Twenty-five to forty accounts covers most small businesses.
• Use subaccounts for detail you actually report on, not for every vendor.
• Reserve one "Ask My Accountant" or "Uncategorized" account so nothing blocks data entry.
• Decide early whether you will use class tracking, job costing, or locations. Retrofitting them later is tedious.

Preferences That Change Everything Later

A handful of preferences determine whether your future self has an easy or painful audit. Walk through them slowly during training.

• Audit trail: turn it on. It records who changed what and when, and it is the single most valuable setting for troubleshooting.
• Automatically recall last transaction: convenient for recurring bills, dangerous for similar-but-different entries. Learn it, then decide per workflow.
• Warn when posting a transaction to a closed period: leave it on, and set a closing date.
• Sales tax: configure rates and agencies before entering sales, otherwise you will be cleaning up taxable versus non-taxable items for weeks.
• Items: set up service, inventory, and discount items deliberately. Items drive the accounting behind invoices, so sloppy item setup produces sloppy statements.
• Backup reminders: use them, but understand that a reminder is not a verified backup.

The Transaction Order That Keeps Your Ledger Clean

New users get into trouble because they enter transactions in the order they happen in real life rather than the order the software expects. Learn the canonical sequences.

Customers: Estimates, Invoices, Payments, Deposits

1. Create or select the customer, and confirm terms, tax status, and default accounts.
2. If the work is quoted, start with an estimate.
3. Convert the estimate to an invoice, or invoice directly for simple sales.
4. Record the payment against the invoice, not as a generic deposit.
5. Group payments into a bank deposit if you take multiple payments in one trip.

The step people skip is matching payments to invoices. When payments land in a holding account and never get applied, customer balances look wrong and aging reports become useless.

Vendors: Purchase Orders, Bills, Bill Payments

1. Issue a purchase order for committed spend.
2. Receive items or receive against the bill, so inventory stays accurate.
3. Enter the vendor bill with the correct expense or item lines.
4. Pay the bill through bill payment, not a direct check, unless you deliberately want a check that bypasses accounts payable.

Skipping the bill step is the most common small business error in any accounting program. Writing a check straight to an expense account hides what you owe, breaks aging, and makes job cost reporting incomplete.

Banking: Checks, Card Purchases, Transfers

Enter checks, card purchases, and transfers consistently, and use the same naming conventions so reconciliation is quick. Transfers deserve special care: a transfer between two bank accounts must never be recorded twice, once in each account, or you will chase a phantom difference forever.

Bank Reconciliation: The Skill That Builds Real Confidence

Reconciliation is where learners discover whether they actually understand the software. It is also the best diagnostic tool in the program.

A reliable process:

1. Confirm the statement beginning balance matches the prior reconciliation ending balance. If it does not, stop and fix the previous period first.
2. Enter the statement ending balance and date.
3. Work through items in date order, clearing each one the statement shows.
4. Investigate anything unusual: duplicate amounts, amounts that appear twice with opposite signs, or a transaction that vanished.
5. Do not force a difference. A forced adjustment hides an error that will surface later.
6. Print or save the reconciliation report and the discrepancy report before closing the month.

Common causes of stubborn differences:

• A transaction edited after it was reconciled.
• A payment applied to the wrong invoice.
• A transfer recorded in only one account.
• Sales tax or payroll liability payments posted to the wrong period.
• Bank fees entered as a payment to a vendor instead of an expense.

When you can reconcile a busy account in ten minutes without stress, you have finished the core of the training. Everything else is refinement.

Reports That Answer Questions Instead of Creating Them

Reports intimidate beginners because the list is long. In practice, five reports cover most needs.

• Profit and loss, compared to prior period and budget.
• Balance sheet, with a quick scan of unusual balances.
• Accounts receivable aging, to drive collections.
• Accounts payable aging, to schedule payments.
• Sales by customer or by item, to understand what actually sells.

Then learn the mechanics that make reports trustworthy:

• Set the correct date range and basis (cash or accrual) every time.
• Filter by class, customer, or item to isolate a segment.
• Memorize the exact configuration you use monthly so comparisons are consistent.
• Export to a spreadsheet when you need to pivot, chart, or combine data.
• Save a PDF copy with the date range in the file name.

A useful training exercise is to change one filter and predict how the numbers will move before you run the report. That single habit builds real fluency.

Designing a Video-Based Learning Plan

Watching is not learning. A tutorial only works when you interleave watching with doing.

A Two-Week Sprint

Day 1-2: Interface tour, preferences, and a practice company setup.

Day 3-4: Customers and sales cycle, including estimates and payment application.

Day 5-6: Vendors, bills, and payment scheduling.

Day 7: Banking entries and transfers.

Day 8-9: Reconciliation, repeated until it feels routine.

Day 10: Reporting and memorized reports.

Day 11: Items, sales tax, and payroll-related liability accounts.

Day 12: Backup, restore, and file troubleshooting.

Day 13: Job costing or class tracking for your specific industry.

Day 14: Build a one-page checklist of your own monthly close.

How to Practice Actively

Use these techniques to convert passive viewing into retention:

• Pause and reproduce every step in your practice company before continuing.
• Keep a running "oops log" of every mistake and the fix.
• Explain each workflow out loud as if training a colleague; gaps in understanding become obvious.
• Rebuild one workflow from memory the next day without the video.
• Test with deliberately messy data, because clean sample files hide edge cases.

Video is also the best medium for interface-heavy software because muscle memory matters. You learn where the buttons are by watching hands move to them.

Common Mistakes, Fixes, and Troubleshooting

Duplicate transactions. Search by amount and date, then delete or void the duplicate. Voiding preserves the audit trail; deleting does not.

Deleting instead of voiding. Void anything that touched a reconciled period. Deletion creates reconciliation mysteries that can take hours to untangle.

Recording a check as a bill payment before the bill exists. Create the bill first so payables aging stays accurate.

Misusing the undeposited funds holding account. Apply payments to invoices and group them into a single deposit; do not let the holding account accumulate a balance.

Editing a closed period. Reopen only with a documented reason, make the change, and re-close the period with a fresh closing date.

Multi-user errors. Confirm the file is hosted on the designated machine, that hosting is enabled, and that all users are on compatible versions.

Printing and PDF alignment. Check the printer driver and form settings before blaming the software; most alignment issues are driver-level.

Corrupted file symptoms. Slowness, error codes, or a file that will not open usually mean it is time to run the built-in verify and rebuild utilities. Work on a copy, and keep a recent backup before attempting repairs.

Payroll liabilities out of balance. Reconciling payroll liability accounts against payroll reports is a monthly habit, not an annual cleanup.

File Health, Backups, and the Migration Question

Training should include maintenance, because most panic calls are file or backup problems, not accounting problems.

• Back up on a schedule, and store at least one copy off the machine.
• Verify backups by restoring to a test folder and opening the file. An unverified backup is a guess.
• Keep a portable company file for sharing with an accountant, but never treat it as your primary backup.
• Change the administrator password policy if more than one person touches the file.
• Record your closing date and who has permission to override it.

Then the migration question. Desktop software is not a life sentence, but moving platforms mid-year is rarely wise. Decide on your criteria: whether you need remote collaboration, automatic bank feeds, receipt capture, or integrations with other tools. If you do migrate, plan the cutover at a fiscal boundary, reconcile everything first, and keep the old file readable for historical reporting. Never merge accounts during migration; map them deliberately and document the mapping.

FAQ

How long does it take to become competent? With daily practice on realistic data, most people handle sales, expenses, and reconciliation within two to three weeks, and reporting fluency within a couple of months.

Should I learn on sample data or my own books? Both. Practice on sample data to make mistakes safely, then apply the workflows to your real file with a backup in place.

What if my accountant uses different settings? Ask before you change preferences. Tax basis, closing dates, and account structure should be consistent between your file and your accountant's expectations.

Is it worth learning an older desktop version at all? Yes, if it runs your business. Core bookkeeping logic transfers directly, and understanding transactions deeply makes any future platform switch easier.

How often should I reconcile? Monthly at minimum, more often for high-volume accounts. Frequent reconciliation turns a day-long project into a twenty-minute routine.

Do I need video tutorials if the help files exist? Help files explain features; videos teach workflow order and interface rhythm. Most learners need both.

Can I use AI assistants to speed this up? AI is useful for drafting checklists, explaining accounting concepts, and generating practice scenarios. It cannot see your file, so verification stays with you.

What is the single most important habit? Backing up and verifying before any structural change, and reconciling before closing a period.

Mastery of a bookkeeping program is not memorization. It is a repeatable sequence: set up cleanly, enter transactions in the right order, reconcile without forcing differences, report consistently, and maintain the file. Video tutorials accelerate that sequence by showing it in motion. Follow the two-week plan once, then repeat only the workflows that gave you trouble. Within a month, the software stops feeling like an obstacle and starts functioning as what it always was: a ledger you control.