Accounting CS Training for New Bookkeepers: Build Monthly Accounting Workflow Competence

By Vincent Howard, CPA | Managing Partner, Howard, Howard and Hodges | SkillAbility for Accounting Firms

Last updated: July 29, 2026  |  38-minute read

A new bookkeeper learns to open a client in Accounting CS.

The employee enters checks and deposits, imports a spreadsheet, clears bank transactions, posts a journal entry, and prints a profit-and-loss statement.

The firm assigns a monthly accounting client.

At review, the manager discovers:

• The employee worked in the wrong posting period and corrected the dates without evaluating the prior reports.
• The spreadsheet import mapped a liability account to an expense account.
• A bank statement line was imported twice and one copy was hidden inside a reconciliation adjustment.
• The bank account showed a finalized reconciliation, but old outstanding checks were never investigated.
• A payment was entered directly through the bank journal instead of being applied to the existing accounts-payable item.
• Payroll cash was entered, but payroll liabilities and employer taxes were not reconciled to the payroll source.
• A regular journal entry was used when the firm required an adjusting, reclassifying, tax, or potential entry subtype.
• The trial balance agreed internally, but the loan, fixed assets, sales tax, and owner accounts did not tie to independent schedules.
• The employee produced financial statements without confirming the balance basis, period, report options, or unusual month-over-month changes.
• The file was marked complete even though no close summary identified missing client information, unresolved differences, or reviewer decisions.

The employee learned software actions.

The employee had not yet demonstrated monthly workflow competence.

The real evidence chain is:

Accounting CS supports that chain.

Training must prove that the bookkeeper can protect it.

Who I Am and Why This Matters

I have practiced public accounting since 1990. I founded my accounting firm in 1993, merged it in 2001 to form Howard, Howard and Hodges, and helped grow the organization from three people to approximately 50 staff across multiple Florida locations and states. Our firm was named PASBA Firm of the Year in 2015.

I have watched firms move from manual ledgers and standalone write-up systems to integrated, hosted accounting environments that can process multiple clients, payroll, imports, trial balances, financial statements, and tax workflows.

The software changed.

The training failure stayed remarkably consistent.

Firms still confuse:

• Watching with doing
• Doing once with repeating reliably
• Completing a screen with completing the accounting cycle
• A balanced entry with a supported entry
• A finalized reconciliation with a valid reconciliation
• A printed report with reliable financial information
• Elapsed time with demonstrated readiness

Since 2020, I have built and run the SkillAbility accounting workforce development platform, used by more than 1,000 accounting professionals across dozens of PASBA firms.

Our standard is simple:

Training is complete when the employee can independently produce the required work product, explain what was done, identify what is missing or unusual, document the file, and escalate correctly on a different assignment.

Read How to Develop Accounting Staff Without Relying on Shadowing for the broader development model.

What Is Monthly Accounting CS Workflow Competence?

It combines six knowledge areas:

• Accounting knowledge: Debits, credits, transaction cycles, subledgers, cutoff, accruals, deferrals, reconciliations, financial statements, materiality, and internal controls
• Accounting CS product knowledge: Clients, services, posting periods, journals, transaction-entry modes, bank accounts, reconciliations, spreadsheet imports, QuickBooks integration, trial balance, journal-entry subtypes, reports, security groups, and Client Access
• Firm workflow knowledge: Source standards, close calendar, account ownership, import procedures, review statuses, workpapers, escalation, and delivery
• Client knowledge: Entity, industry, bank accounts, revenue, purchasing, payroll, debt, fixed assets, owners, taxes, reporting needs, and recurring exceptions
• Integration judgment: What entered through QuickBooks, spreadsheets, bank files, client staff, payroll, or another system; what could be incomplete, duplicated, or mapped incorrectly; and how it was independently checked
• Professional judgment: What is missing, stale, unusual, unsupported, material, outside scope, or beyond authority

A workflow-competent bookkeeper can answer:

• Am I in the correct client, service, journal, bank account, and posting period?
• What source supports this transaction?
• Did the transaction originate with the firm, the client, an import, a bank file, payroll, or QuickBooks?
• Does the transaction belong in a subledger rather than a direct journal or bank entry?
• Which balance basis and journal-entry subtype should this adjustment affect?
• Does the general ledger agree with independent evidence?
• Are outstanding or reconciling items valid, current, and explained?
• Do the financial statements reflect the intended period, basis, entity structure, and reporting format?
• What changed from the prior month, and why?
• What remains unresolved, and who must decide?

Why Product Instruction Does Not Prove Client Readiness

Thomson Reuters describes Accounting CS as professional accounting software for firms serving multiple clients. The platform combines write-up, trial balance, payroll, financial-statement analysis, integrations, multi-user processing, security controls, customized reporting, and client access.

Official product source: Thomson Reuters Accounting CS overview.

That breadth is exactly why isolated software lessons are insufficient.

The software is a professional production environment.

The firm must define what acceptable production looks like.

What Current Product and Profession Research Tells Firms

Accounting CS is designed around integrated multi-client production

Thomson Reuters currently positions Accounting CS as a single professional platform for write-up, trial balance, payroll, financial statement analysis, client accounting, imports, and integration with other CS Professional Suite applications. It supports multiple users performing multiple tasks and allows firms to control client-visible information and monitor activity by date, time, and staff member.

This matters for training because the new bookkeeper is not simply learning bookkeeping.

The employee is learning a controlled production system where one action can affect:

• The general ledger
• Bank reconciliation
• Accounts receivable
• Accounts payable
• Payroll reporting
• Trial-balance bases
• Financial statements
• Tax and workpaper integrations
• Client-visible information

AI and automation are increasing the need for workflow judgment

The 2026 Thomson Reuters Future of Professionals research reports that 81% of tax and audit firm professionals regularly use AI in daily workflows. The same tax-and-audit report says 35% use AI tools their firms have not authorized, and 49% expect entry-level roles to decrease within two to three years.

The implication is not that a new bookkeeper should use AI indiscriminately inside Accounting CS.

The implication is that routine work is becoming more automated while the remaining human responsibility becomes more concentrated around:

• Source completeness
• Mapping and classification
• Exception detection
• Reconciliation
• Review
• Security
• Explanation
• Accountability

The AICPA’s 2026 Profession Ready Initiative likewise focuses on identifying early-career capability gaps and giving employers frameworks for developing high-performing professionals in an increasingly AI-driven marketplace.

External source: AICPA Profession Ready Initiative.

Understand the Accounting CS Operating Environment

Before teaching transactions, teach the environment.

Local, hosted, and remote access are not identical training contexts

Accounting CS may operate in a firm-managed environment, Thomson Reuters Virtual Office CS, Software as a Service, or another approved hosted environment.

Virtual Office CS provides remote access to CS Professional Suite applications while Thomson Reuters manages hosting, maintenance, and backups. Accounting CS Client Access requires a hosted environment because firm and client staff work in the same database.

Official sources:

• Virtual Office CS
• Accounting CS Client Access features

Teach the employee to identify five context fields before work begins

1. Environment: Local, hosted, Virtual Office, SaaS, or approved client-access environment
2. Client: Correct legal entity and client record
3. Service: Accounting, accounts receivable, accounts payable, payroll, workpapers, or another enabled service
4. Period: Correct fiscal year and posting period
5. Role: Firm staff, client staff, preparer, reviewer, payroll processor, or administrator

Train the stable process beneath the menus

Software versions, menu paths, supported integrations, and security options change.

The underlying questions remain stable:

• Which client and period am I changing?
• What source supports the change?
• What balances, reports, or connected systems will it affect?
• Can the client see or alter this information?
• Is this within my authority?
• What evidence must remain for the reviewer?

The Twelve Monthly Accounting CS Workflow Competence Gates

A balanced trial balance, finalized bank reconciliation, or printed financial statement does not prove a gate passed.

The supporting work does.

Define the Firm’s Accounting CS Operating Standard

Accounting CS is flexible.

That flexibility becomes inconsistency when each bookkeeper invents a personal workflow.

Standardize client and period setup

Document the firm’s rules for:

• Client IDs and descriptions
• Entity type
• Fiscal year end
• Monthly, quarterly, semiannual, or annual period frequency
• Accounting services enabled
• Journals and journal codes
• Chart-of-accounts structure
• Account classification and report codes
• Bank-account relationships
• Departments, locations, or segmented accounts
• Beginning balances
• Data-entry mode

Thomson Reuters’ client setup guidance notes that the fiscal year and period frequency drive period-end structure and may become restricted after transactions are entered. That makes setup review a control—not clerical housekeeping.

Official source: Add accounting information for an Accounting CS client.

Standardize transaction methods

Define when staff should use:

• Journal-entry mode
• Bank-account transaction mode
• Accounts-receivable processing
• Accounts-payable processing
• Payroll checks or payroll imports
• Spreadsheet imports
• QuickBooks integration
• Scheduled transactions
• Automatic journal-entry templates
• Reconciliation adjustments

The fastest screen is not always the correct accounting path.

Define review-ready

“Ready for review” should mean:

• Expected source information is complete or exceptions are listed
• Imports reconcile to control totals
• Subledgers agree to the general ledger
• Bank accounts are reconciled to statements
• Material balance-sheet accounts have current support
• Journal entries are supported and correctly typed
• Trial-balance anomalies were investigated
• Financial statements are properly configured and reasonable
• Open items identify owner, deadline, and impact
• The reviewer handoff identifies actual decisions

Use the Workpaper Review Checklist to turn the standard into observable evidence.

Security Groups, Staff Access, and Client Access

Security is part of bookkeeping competence because permissions determine which clients, accounts, transactions, reports, and high-impact actions an employee can access.

Enable and design security groups intentionally

Accounting CS can assign firm staff to multiple security groups. Thomson Reuters notes that the highest privileges among those groups apply.

That means one overly broad group can override the restrictions in another.

Official source: Assign Accounting CS staff to security groups.

Build role-based groups such as:

• New-bookkeeper practice
• Routine monthly processing
• Accounts receivable
• Accounts payable
• Payroll processing
• Bank reconciliation
• Adjusting entries
• Financial reporting
• Reviewer
• Administrator

Grant access to selected clients and bank accounts

Accounting CS can restrict staff to selected clients and, where configured, selected bank accounts. Access to a client does not automatically mean the user should have every action privilege within that client.

Official sources:

• Grant staff access to clients
• Bank-account access privileges

Understand Client Access boundaries

Accounting CS Client Access allows authorized client staff to enter day-to-day accounting or payroll transactions in the same hosted database used by the firm. Thomson Reuters retains certain professional-accountant functions for the firm even when client staff have broad privileges.

Training must distinguish:

• Firm-originated transactions
• Client-originated transactions
• Client-visible reports and data
• Firm-only adjustments and review procedures
• Who can change client security groups
• Who owns client-entered errors

Review privileges after updates

Thomson Reuters security guidance notes that new screens, menu options, reports, or security groups introduced by updates may not automatically receive privileges.

Add security review to the firm’s update process.

Software access without role clarity is not readiness.

Client Setup, Posting Periods, Journals, and Beginning Balances

A new client can balance and still be configured incorrectly.

Begin with the engagement—not the setup screen

The employee should first understand:

• Legal entity and ownership
• Fiscal year
• Reporting frequency
• Cash or accrual needs
• Sales, purchasing, and payroll processes
• Bank, card, loan, merchant, and clearing accounts
• Tax and reporting obligations
• Departments, locations, or other segments
• Client-access responsibilities
• Deliverables and deadlines

Validate period architecture

Require a setup-control sheet showing:

• Current fiscal year end
• Period frequency
• Current posting period
• Prior-period status
• Year-to-date continuity
• Comparative reporting periods

A transaction with the right date can still affect the wrong workflow if the selected posting period or journal is wrong.

Validate journals

Document:

• Journal purpose
• Permitted transaction types
• Reference convention
• Report code where used
• Who may add, delete, or transfer journals
• How client-originated activity is identified

Reconcile beginning balances

For every new or converted client, require:

• Source trial balance
• Accounts-receivable detail
• Accounts-payable detail
• Bank and credit-card reconciliations
• Payroll and tax liabilities
• Debt schedules
• Fixed-asset schedules
• Prepaids and deposits
• Inventory where applicable
• Equity and retained-earnings continuity

Beginning balances are not complete merely because debits equal credits.

Source Documents, QuickBooks, and Spreadsheet Imports

Accounting CS can import data from spreadsheets and supported QuickBooks environments. Imports reduce manual entry but increase mapping, completeness, and duplication risk.

QuickBooks integration

Official Accounting CS guidance states that supported QuickBooks integration can import transactions, chart-of-accounts data, bank information, payroll items, vendors, employees, and other client data. It can also export selected information back to QuickBooks.

Official source: Accounting CS QuickBooks integration.

Require the employee to document:

• QuickBooks version and file
• Import date range
• Prior import cutoff
• Accounts and records included
• Account mapping
• Transaction count and totals
• Bank-account mapping
• Unsupported or rejected records
• Duplicate-prevention procedure
• Post-import trial-balance comparison

Spreadsheet imports

Accounting CS can import .XLS and .XLSX data through a mapping process. Thomson Reuters advises replacing formulas with values before import and supports multiple transaction types, including data originating from bank statements, point-of-sale systems, payroll sources, and accounting applications.

Official sources:

• Spreadsheet import overview
• Spreadsheet transaction imports

Use a five-part import control

1. Population: What records should be included?
2. Mapping: Where should each field and account go?
3. Control totals: What count and dollar totals should reconcile?
4. Exceptions: What failed, defaulted, duplicated, or required manual mapping?
5. Destination review: Did the trial balance, subledgers, bank accounts, and reports change as expected?

Do not make the import file the workpaper

The file proves what was sent.

The workpaper must prove what was accepted and how the resulting books were validated.

Transaction Entry and Complete Accounting Cycles

Accounting CS supports journal-based and bank-account-based transaction entry. The screen used should follow the accounting event and the firm’s standard.

Official source: Accounting CS transaction-entry options.

Revenue cycle

Train the employee to connect:

• Customer or source system
• Invoice or sales record
• Revenue account
• Receivable
• Payment
• Deposit
• Merchant fees
• Bank reconciliation
• Aging and bad debt

Purchasing cycle

• Vendor
• Bill or purchase document
• Expense, asset, or prepaid classification
• Payable
• Payment
• Bank activity
• Vendor balance
• 1099 or tax-related attributes where relevant

Cash transaction cycle

Teach the difference between:

• Recording an accounting event
• Recording a bank movement
• Applying cash to an existing subledger item
• Transferring between accounts
• Correcting an error
• Creating a reconciliation-only adjustment

Owner and related-party activity

New bookkeepers should distinguish:

• Business expense
• Owner contribution
• Distribution or draw
• Shareholder or partner loan
• Personal expenditure
• Payroll or guaranteed payment
• Reimbursement

Scheduled and automatic entries

Scheduled transactions and automatic journal-entry templates can improve consistency.

They can also repeat an obsolete assumption every month.

Require periodic review of:

• Amount or calculation
• Accounts
• Posting period
• Reversal settings
• Source support
• Start and end dates
• Client-specific changes

Bank Reconciliation Competence

Bank reconciliation is not the act of checking boxes until the difference reaches zero.

It is the process of proving that the ledger and bank statement represent the same cash activity, subject to valid timing differences.

Accounting CS bank reconciliation captures statement dates, beginning and ending balances, deposits, additions, checks, and payments. It supports current, pending, and finalized reconciliations, bank-statement imports, initial open items, and reconciliation analysis.

Official sources:

• Reconcile bank accounts
• Reconciliation Analysis tab

Teach the reconciliation in five stages

1. Validate the statement: Correct account, period, beginning balance, ending balance, and completeness.
2. Validate the ledger population: Correct GL account, bank account, posting period, and imported activity.
3. Match valid activity: Clear transactions only when the statement and ledger item represent the same event.
4. Investigate differences: Missing, duplicate, stale, reversed, edited, or incorrectly dated transactions.
5. Conclude: Explain outstanding items, document adjustments, and finalize only when the evidence supports it.

Control initial open items

Initial open items can support conversion from another accounting system.

They can also be misused to force a reconciliation.

Require:

• Source reconciliation
• Original transaction date
• Amount
• Reason the item is not in current ledger activity
• Expected clearance
• Reviewer approval

Control reconciliation adjustments

A reconciliation adjustment should explain a real difference and follow the firm’s posting policy.

It should not become a suspense mechanism for unexplained errors.

Review old outstanding items

Require investigation thresholds for:

• Old checks
• Old deposits
• Repeated reconciling items
• Negative or unusual bank balances
• Reconciliations reopened after finalization

For broader reconciliation training, see Month-End Close Training for Staff Accountants.

Accounts Receivable, Accounts Payable, and Payroll Interfaces

Accounts receivable

The employee should prove that:

• Customer detail agrees to the control account
• Invoices and credits are complete
• Payments are applied correctly
• Unapplied cash is investigated
• Aging is reasonable
• Bad debt or adjustments are supported
• Client-entered activity is reviewed

Accounts payable

• Vendor detail agrees to the control account
• Bills, credits, and payments are complete
• Duplicate vendors and bills are identified
• Payments are applied to the correct items
• Old credits and debits are investigated
• Unrecorded liabilities are considered

Accounting CS Client Access can be configured so client staff process accounts receivable or accounts payable while the firm controls security groups and professional-accountant functions.

Official sources:

• Enable AR for client staff
• Enable AP for client staff

Payroll interfaces

Whether payroll is processed in Accounting CS Payroll or imported from another system, the monthly accounting employee may need to reconcile:

• Gross wages
• Employee taxes and deductions
• Employer taxes and benefits
• Net pay
• Payroll cash
• Payroll liabilities
• Tax deposits and filings
• Department or location allocations
• General ledger postings

Payroll cash matching does not prove payroll accounting is correct.

The payroll registers, liability schedules, bank activity, and general ledger must agree.

Trial Balance, Journal-Entry Types, and Adjustments

Accounting CS supports multiple journal-entry subtypes and balance bases. That is powerful, but it means the bookkeeper must understand not only the debit and credit but also where the entry should appear.

Journal-entry subtypes

Thomson Reuters documents entry types such as:

• Regular entries
• Adjusting entries
• Reclassifying entries
• Tax entries
• Potential entries

Official source: Accounting CS journal-entry subtypes.

The firm should define:

• Which subtype is used for monthly book adjustments
• Which subtype is reserved for reviewer or year-end work
• Which balances and reports each subtype affects
• Who may post or convert potential entries
• How reclassifying and tax entries move through connected workflows

Support every adjustment

Each entry should include:

• Purpose
• Source or calculation
• Period
• Accounts
• Journal and subtype
• Balance basis
• Reversal instruction
• Financial-statement effect
• Preparer and approver
• Workpaper reference

Review the trial balance as a diagnostic tool

A trial balance review should identify:

• Unexpected debit or credit balances
• Suspense and clearing accounts
• Stale receivables and payables
• Negative assets or liabilities
• Unusual owner or equity activity
• Duplicate or inactive accounts with balances
• Large month-over-month changes
• Accounts without current support
• Balance-basis differences
• Entries posted after review

The trial balance is not a proof of accuracy.

It is a map of where proof is required.

Month-End Close and Financial Reporting

A bookkeeper has not completed the month because all source transactions were entered.

The close converts transaction activity into reliable financial information.

Use a six-phase close

Reconcile material balance-sheet accounts

Depending on the client, this may include:

• Bank and credit cards
• Accounts receivable
• Accounts payable
• Payroll liabilities
• Sales tax
• Loans and interest
• Fixed assets and accumulated depreciation
• Prepaids, deposits, and deferred revenue
• Inventory
• Intercompany and clearing accounts
• Owner or equity accounts

Produce reliable reports

Before release, confirm:

• Correct client
• Correct period and comparative period
• Correct balance basis
• Correct entity, department, or location filters
• Correct account grouping and report format
• All approved entries included
• Material balances tied to workpapers
• Open limitations disclosed
• Reports agree with the reviewed trial balance

Analyze the result

Require the preparer to explain:

• Material revenue changes
• Gross-margin changes
• Large or unusual expenses
• Cash changes
• Receivable and payable aging
• Debt and liquidity changes
• Owner activity
• Unresolved data or accounting issues

For the broader development pathway, read Client Accounting Services Training: Build CAS Staff Who Can Close, Explain, and Advise.

Review, Audit Trail, and Reviewer Handoff

Accounting CS can monitor activity by date, time, and staff member, and transactions may reflect whether they originated with firm or client staff.

The reviewer should use system evidence and workpapers together.

Build a reviewer sequence

1. Confirm client, period, services, and scope.
2. Review source-completeness and import-control documentation.
3. Review accounts-receivable, accounts-payable, payroll, and other subledgers.
4. Inspect bank reconciliations and old outstanding items.
5. Review material balance-sheet reconciliations.
6. Review journal entries by subtype, preparer, date, and support.
7. Inspect trial-balance anomalies and comparative changes.
8. Review financial-statement configuration and explanations.
9. Resolve open items and return specific rework.
10. Confirm final status and delivery.

Use a decision-ready handoff

The reviewer should assess accounting, risk, and judgment.

The reviewer should not have to discover the status of the month.

Integrations and Data-Transfer Controls

Accounting CS can exchange information with QuickBooks, spreadsheets, bank files, payroll sources, CS Professional Suite products, and client-access workflows.

Every connection introduces a control question.

Use an integration inventory

For each client, document:

• Source system
• Data entering Accounting CS
• Data leaving Accounting CS
• Frequency and cutoff
• File format or utility
• Account mapping
• Control totals
• Failure or rejection process
• Duplicate risk
• Responsible employee
• Reviewer

Use completeness, accuracy, and uniqueness tests

1. Completeness: Did every expected record enter?
2. Accuracy: Did each record enter with the correct client, period, type, account, amount, and attributes?
3. Uniqueness: Did any record enter twice, through two sources, or after a prior cutoff?

Protect two-way workflows

When information can be exported back to QuickBooks or used by another CS Professional Suite application, define:

• System of record
• Approved direction of transfer
• Cutoff date
• Who may export
• How adjustments are communicated
• How duplicate or overwritten information is prevented

“The integration handled it” is not an accounting conclusion.

The Complete 30-Day Accounting CS Training Plan

Days 1–5: Environment, accounting, security, and workflow foundations

Objectives

• Learn the firm’s Accounting CS environment and current version
• Identify clients, services, journals, bank accounts, and posting periods
• Learn security groups, client restrictions, and Client Access distinctions
• Review the firm’s chart, source, import, reconciliation, journal-entry, close, and review standards
• Practice routine product navigation using current Thomson Reuters guidance

Evidence

• Security and access scenario test
• Correct practice-client and period selection
• Firm workflow knowledge assessment
• Transaction-path decision exercise

Days 6–10: Client setup and complete transaction cycles

Objectives

• Configure a realistic practice client
• Validate fiscal year, period frequency, services, journals, accounts, and bank relationships
• Reconcile beginning balances
• Process revenue, purchasing, cash, owner, debt, and asset cycles
• Protect accounts receivable and accounts payable

Evidence

• Client-setup control sheet
• Beginning-balance reconciliation
• Source-to-ledger transaction test
• Subledger-to-GL tie-out

Days 11–15: Imports, client activity, and bank reconciliation

Objectives

• Perform a controlled spreadsheet import
• Review a QuickBooks or equivalent import workflow
• Identify firm-originated and client-originated activity
• Import or enter bank-statement data
• Complete a valid bank reconciliation
• Investigate old and unusual reconciling items

Evidence

• Import mapping and control-total worksheet
• Duplicate and rejection test
• Finalized bank reconciliation tied to the external statement
• Outstanding-item analysis

Days 16–20: Payroll interfaces, balance-sheet reconciliations, and adjustments

Objectives

• Reconcile payroll reports, cash, liabilities, and ledger activity
• Reconcile debt, fixed assets, taxes, prepaids, clearing, and equity accounts
• Prepare supported regular, adjusting, reclassifying, tax, and potential entries as permitted
• Use correct posting periods, journals, subtypes, and balance bases

Evidence

• Balance-sheet reconciliation package
• Payroll reconciliation
• Supported journal-entry set
• Subtype and basis assessment

Days 21–25: Trial balance, reporting, planted errors, and review

Objectives

• Review the trial balance for unusual balances and unsupported accounts
• Produce correctly configured financial statements
• Investigate material changes
• Find mapping, posting-period, subledger, bank, payroll, and entry-type errors
• Respond to review points without damaging the audit trail

Evidence

• Planted-error detection score
• Trial-balance review notes
• Financial-statement package
• Corrected workpapers and review responses

Days 26–30: Independent capstone and client-readiness decision

Objectives

• Complete a different practice client without step-by-step navigation
• Own the month from source completeness through reviewer handoff
• Meet a realistic close deadline
• Explain material changes in plain language
• Escalate an issue outside authority
• Earn a scoped live-work decision

Evidence

• Independent capstone file
• 100-point competency scorecard
• Manager-approved live-work scope
• Written permissions, restrictions, and checkpoints

Use scenario-based training for accountants to expose mistakes before a client deadline or manager review absorbs the first attempt.

The 30/60/90-Day Live-Work Progression

Days 31–60: Controlled routine monthly work

The employee may receive a defined class of clients with:

• Approved client and service access
• Limited complexity
• Required source-completeness checkpoint
• Required bank and subledger review
• Required preparer close checklist
• Manager approval for imports, new mappings, journal templates, unusual adjustments, security changes, and client-facing conclusions

Days 61–90: Expanded responsibility based on evidence

Expand scope only when:

• First-pass acceptance improves
• Repeated review notes decline
• Import and mapping errors are found before review
• Reconciliations are timely and supported
• Subledger shortcuts disappear
• Journal-entry support is complete
• Close deadlines are met without sacrificing quality
• Reviewer handoffs are decision ready
• Escalation occurs at the right time

After day 90: Independence remains scoped

A bookkeeper may be independent on routine monthly write-up and still require direct supervision for:

• New conversions
• Complex QuickBooks or spreadsheet integrations
• Payroll setup and corrections
• Inventory
• Consolidated or segmented clients
• Material estimates
• Owner and related-party transactions
• Tax-sensitive entries
• Financial-statement design
• Security or Client Access administration
• Advisory conclusions

Read Staff Accountant Competency Checklist: When Is a New Hire Ready for Client Work?.

100-Point Accounting CS Workflow Competency Scorecard

Suggested readiness rule: Require at least 80 points overall, no zero in any category, no unresolved security or integrity failure, and manager approval of the permitted client and task scope.

A high total cannot compensate for a failed reconciliation, unauthorized access, or unsupported adjustment.

Realistic Accounting CS Training Scenarios

Scenario 1: The wrong posting period

A new bookkeeper enters June transactions while July is selected as the posting period. The trainee must identify the effect on reports, correct the transactions, inspect related entries, and document whether prior outputs must be reissued.

Scenario 2: The spreadsheet mapping error

A payroll import maps employer payroll tax to wage expense and employee withholding to a second wage account. The trainee must reconcile the import totals, correct mappings, remove or reverse the bad population, and verify the rerun.

Scenario 3: The finalized bank reconciliation that is wrong

The reconciliation difference is zero, but one statement line was imported twice and an adjustment offsets it. The trainee must trace the population, remove the artificial solution, and reconcile to the external statement.

Scenario 4: The subledger bypass

A vendor payment is entered directly through the bank account instead of being applied to the existing payable. Cash is correct, but accounts payable remains overstated. The trainee must repair the accounting path.

Scenario 5: The old outstanding check

A check has remained outstanding for eight months. The trainee must review the original transaction, contact information, replacement or void evidence, applicable state or firm procedure, and reviewer decision.

Scenario 6: The wrong journal-entry subtype

A year-end tax entry is posted as a regular monthly entry and changes the book financial statements. The trainee must understand balance bases, choose the proper correction, and explain the reporting effect.

Scenario 7: The beginning balances that “balance”

The converted trial balance nets to zero, but receivables, payables, loans, and retained earnings do not agree with supporting detail. The trainee must expose the structural differences before processing continues.

Scenario 8: The client-entered transaction

A Client Access user modifies a vendor and records a payment in the wrong bank account. The trainee must identify the origin, correct the transaction, preserve accountability, and decide whether client permissions or instruction should change.

Scenario 9: The payroll cash shortcut

Net payroll clears the bank, but payroll liabilities and employer taxes do not tie to the payroll register. The trainee must complete the payroll-to-ledger reconciliation.

Scenario 10: The report that tells the wrong story

The profit-and-loss statement is printed on the wrong balance basis and excludes an approved adjustment. The trainee must correct report options, tie the statements to the reviewed trial balance, and explain the difference.

Scenario 11: The unsupported equipment entry

A large debit is coded to repairs. The invoice includes equipment, installation, and a service plan. The trainee must identify the classification question, gather facts, propose treatment, and escalate the final decision.

Scenario 12: The reopened reconciliation

A previously finalized reconciliation is unfinalized after the client supplies new activity. The trainee must identify what changed, reperform the affected procedures, update workpapers, and alert the reviewer.

What the Firm Should Measure

Do not judge Accounting CS training by course completion or transaction volume alone.

See Accounting Onboarding KPIs: 12 Metrics That Show Whether New Hires Are Becoming Productive.

The goal is not more transactions per hour.

The goal is more accepted, review-ready months with fewer repeated corrections and less manager rescue.

Common Accounting CS Training Mistakes

Mistake 1: Training only menu paths

The employee knows where to click but cannot explain the accounting event or downstream effect.

Mistake 2: Using an empty practice client

The employee never experiences incomplete sources, prior-period issues, old outstanding checks, client-entered transactions, or messy imports.

Mistake 3: Ignoring posting-period discipline

Transactions are corrected by date without evaluating the reporting and workflow effects.

Mistake 4: Treating import completion as import validation

Mapped data enters the system, but counts, totals, rejected rows, duplicates, and destination accounts are not tested.

Mistake 5: Teaching zero-difference bank reconciliation

The employee learns to force the difference to zero instead of proving the cash balance.

Mistake 6: Allowing subledger shortcuts

Direct bank or journal entries create correct cash while leaving receivables, payables, or payroll balances wrong.

Mistake 7: Giving broad security to avoid inconvenience

The firm exposes clients, bank accounts, payroll, adjustments, and administration before competence requires it.

Mistake 8: Ignoring journal-entry subtypes and balance bases

The debit and credit balance, but the wrong reports and connected workflows change.

Mistake 9: Treating trial balance as proof

The employee sees balanced debits and credits but never reconciles the balances to independent evidence.

Mistake 10: Printing reports before completing the close

The statements look polished while missing entries, unresolved balances, or wrong report options remain.

Mistake 11: Measuring speed without accepted quality

Fast work that returns for correction does not create firm capacity.

Mistake 12: Using live clients as the first complete practice month

The manager discovers the development gap at the most expensive point in the workflow.

Read Accounting Workforce Development: Build Capacity From Within for the broader system.

Frequently Asked Questions About Accounting CS Training for New Bookkeepers

What is the best way to train a new bookkeeper in Accounting CS?

Combine current Thomson Reuters product instruction with the firm’s own complete practice client. Require the employee to configure the client, validate sources and imports, process full transaction cycles, reconcile bank and balance-sheet accounts, prepare supported journal entries, review the trial balance, produce financial statements, document open items, and submit a reviewer handoff.

How long should Accounting CS training take?

A focused 30-day plan can establish baseline monthly workflow competence when the employee works in the software regularly and receives structured feedback. Follow that with a 30/60/90-day controlled live-work progression. Complex payroll, conversions, integrations, consolidations, and reporting require additional development.

Is Accounting CS bookkeeping software?

Accounting CS is professional accounting software designed for accounting and CPA firms serving multiple clients. Thomson Reuters positions it as combining write-up, trial balance, payroll, financial-statement analysis, integrations, security, reporting, and client-access capabilities.

Can Accounting CS import QuickBooks data?

Yes. Accounting CS supports integration with currently supported QuickBooks Pro, Premier, and Enterprise environments and can import transactions and selected setup records. QuickBooks Online account balances can also be imported through supported spreadsheet workflows. Firms should verify current version support before each workflow.

Can Accounting CS import spreadsheet transactions?

Yes. The Spreadsheet Import wizard supports .XLS and .XLSX files and maps source columns to Accounting CS fields. Training should require control totals, mapping validation, rejected-row review, duplicate testing, and post-import reconciliation.

How should new bookkeepers be trained on bank reconciliation in Accounting CS?

Teach them to validate the external statement, confirm the correct ledger population, match only identical accounting events, investigate missing and duplicate activity, analyze old outstanding items, support adjustments, and finalize only when the ledger agrees with the bank statement.

What is the difference between clearing bank items and reconciling the bank account?

Clearing identifies ledger items that appear on the statement. Reconciliation proves the statement and ledger agree after valid timing differences. A zero difference can still be wrong if activity is missing, duplicated, misdated, or offset with an unsupported adjustment.

What should a new bookkeeper know about Accounting CS posting periods?

The employee should confirm the client’s fiscal year, period frequency, current posting period, transaction date, journal, and downstream reporting effect. Correct dates alone do not guarantee the transaction is in the correct workflow period.

What are Accounting CS journal-entry subtypes?

Accounting CS supports entry categories such as regular, adjusting, reclassifying, tax, and potential entries. The firm should define which staff may use each type and which balance bases and reports each type should affect.

What is Accounting CS Client Access?

Client Access allows authorized client staff to enter approved accounting or payroll activity in the same hosted database used by the accounting firm. The firm controls security groups and retains certain professional-accountant functions.

What security access should a new bookkeeper receive?

Provide the minimum client, service, bank-account, transaction, report, and action privileges required for the approved training or live-work scope. Review combined security-group privileges because the highest privilege among assigned groups may apply.

What should an Accounting CS practice client include?

Include realistic client setup, beginning balances, bank statements, sales and purchasing records, receivables, payables, payroll data, debt and fixed-asset schedules, spreadsheet and QuickBooks imports, client-entered transactions, deliberate missing information, old reconciling items, incorrect mappings, unsupported entries, and expected financial statements.

How do I know when a new bookkeeper is ready for client work?

Use an independent capstone and competency scorecard. Require accurate processing, valid imports, supported reconciliations, correct journal entries, reliable reports, clear documentation, professional communication, appropriate escalation, and manager approval of a specific live-work scope.

What should firms measure after Accounting CS training?

Measure first-pass acceptance, repeated review notes, import-error detection, reconciliation exception aging, subledger bypasses, journal-entry support, close timeliness, reviewer minutes, manager rescue, and escalation quality. Course completion is useful, but accepted work is the outcome.

To bookkeepers who can close the month—not just enter it,

Vincent Howard, CPA
Managing Partner, Howard, Howard and Hodges
SkillAbility for Accounting Firms

Accounting CS, Accounting CS Payroll, Accounting CS Client Access, Virtual Office CS, Software as a Service for CS Professional Suite, Workpapers CS, QuickBooks, and related product names are trademarks or services of their respective owners. SkillAbility is not Thomson Reuters or Intuit and does not represent that this article replaces current vendor training, product documentation, licensing terms, security guidance, technical support, or professional advice.

© 2026 SkillAbility for Accounting Firms. This article provides general educational information and does not replace accounting, payroll, tax, audit, legal, employment, cybersecurity, software, professional-standards, or regulatory advice. Features, integrations, security options, supported versions, and hosted-service availability may vary by license, environment, permissions, product version, and date.