Monthly Close

Monthly Close

Operational skill for period-end close procedures in C-corporations. The monthly close converts a month of raw transactions into reliable financial statements through a strict five-phase sequence. Skipping phases or reordering creates compounding errors.

Target turnaround: 5-7 business days for routine clients; 10 business days for complex (multi-entity, inventory, payroll).

Close Sequence Overview

The close follows five phases in strict order. Each phase gates the next.

1. Transaction Completeness — every economic event for the period is recorded 2. Reconciliation — balance sheet accounts tied to independent third-party evidence 3. Adjusting Entries — accruals, deferrals, depreciation, lease and revenue entries 4. Review and Reporting — trial balance, financial statements, variance analysis 5. Period Lock — lock the period, archive documents, deliver client package

Phase 1: Transaction Completeness

Complete before any reconciliation work begins.

• Clear the bank feed inbox — review and categorize all downloaded transactions; do not leave unmatched items
• Post all invoices issued during the month (AR); review aging for collectibility
• Enter all bills received (AP); match to POs where applicable
• Post payroll — if external provider (ADP, Gusto), post summary journal entry for gross wages, employer taxes, withholdings, and net pay. Never record net payroll only; this understates wages and omits employer tax liabilities
• Categorize all credit card charges; match to receipts
• Record cash transactions — petty cash, owner draws, capital contributions
• Post recurring journal entries — rent straight-lining, insurance amortization, loan interest accruals

Invoke bookkeeping:reconciliation as prerequisite — all accounts must be reconciled before Phase 3.

Phase 2: Reconciliation

Reconcile every balance sheet account to independent evidence. Do not proceed to adjusting entries until all reconciliations are complete and differences are investigated.

• Bank accounts — reconcile each account to the statement ending balance
• Credit cards — reconcile each card to the issuer statement
• Loans — tie balances to lender statements; verify principal/interest split
• Intercompany — if multi-entity, confirm intercompany balances net to zero
• AR — tie aging total to the GL control account
• AP — tie aging total to the GL control account

Bank Reconciliation Decision Thresholds

• Difference < $5 — write off to miscellaneous income/expense; document in close memo
• Difference $5–$100 — investigate one round; if unresolved, write off with manager approval
• Difference > $100 — must resolve before closing; escalate if unresolved after 2 business days

Outstanding checks > 90 days require investigation; > 180 days may trigger escheatment review.

Phase 3: Adjusting Entries

Post entries that align recognition with the accounting period.

Standard Adjustments

• Accrued expenses — expenses incurred but not yet billed (utilities, professional fees, interest). Reverse prior-month accruals first to avoid double-counting when the actual bill arrives.
• Accrued revenue — revenue earned but not yet invoiced (milestone completions, time-based services)
• Prepaid amortization — expense the current-month portion of prepaid insurance, rent, subscriptions
• Depreciation and amortization — post monthly depreciation for fixed assets; amortize intangibles. Invoke accounting-foundation:chart-of-accounts for asset class ranges and accumulated depreciation contra accounts.
• Inventory adjustments — if applicable, adjust for shrinkage, obsolescence, lower-of-cost-or-market
• Deferred revenue — recognize the portion earned during the month per ASC 606
• Payroll tax true-up — reconcile accrued payroll taxes to actual deposits; adjust variance

Missing Document Handling

• Client missing documents at close — accrue based on best estimate, reverse next month. Note in close memo and follow up with client.
• Payroll not posted by Day 3 — accrue based on prior month; reverse when actual posts.
• Prior-period adjustment discovered — post to current period if immaterial; restate prior period if material (materiality = 5% of net income or $5,000, whichever is less).

Lease Accounting — ASC 842

All leases with terms > 12 months must be recognized on the balance sheet as a right-of-use (ROU) asset and corresponding lease liability. Classification (finance vs. operating) determines the expense pattern, not whether the lease appears on the balance sheet.

Finance lease — meets any one of: ownership transfer, purchase option reasonably certain to exercise, term >= ~75% of economic life, PV of payments >= ~90% of fair value, specialized asset with no alternative use. Two P&L line items: amortization expense (straight-line on ROU) and interest expense (effective interest on liability). Front-loaded total expense.

Operating lease — does not meet any finance criteria. Single straight-line lease expense. ROU amortization is a plug (total expense minus interest on liability).

Monthly journal entries:

• Operating: Dr Lease Expense (straight-line), Cr Cash; adjust ROU Asset and Lease Liability for interest accrual and principal reduction
• Finance: Dr Amortization Expense, Cr ROU Asset; Dr Interest Expense, Dr Lease Liability, Cr Cash

Short-term exemption: leases <= 12 months at commencement with no purchase option may be excluded from balance sheet recognition. Election is by asset class. Expense on straight-line basis.

Lease modifications: if modification adds distinct right of use at commensurate price, treat as separate lease. Otherwise, remeasure liability at revised discount rate and adjust ROU asset. Reassess classification at modification date.

Maintain an external amortization schedule per lease tracking: opening liability, interest, payment, closing liability, opening ROU, amortization, closing ROU. Journal entries in the accounting system are driven from this schedule.

For full classification criteria, IBR determination, practical expedients, transition guidance, and disclosure requirements, see references/lease-accounting-asc842.md.

Revenue Recognition — ASC 606

The five-step model governs when and how much revenue to recognize:

1. Identify the contract — approval, identifiable rights, payment terms, commercial substance, probable collection. If collection is not probable, cash received is a deposit (liability), not revenue. 2. Identify performance obligations — each distinct good or service is a separate PO. A series of substantially similar services (e.g., monthly cleaning) may be a single PO. 3. Determine transaction price — fixed + variable consideration (discounts, bonuses, penalties). Apply the constraint: include variable consideration only when a significant revenue reversal is highly improbable. 4. Allocate to POs — by relative standalone selling price (SSP). Methods: adjusted market, expected cost plus margin, residual (last resort). 5. Recognize revenue — over time or at a point in time per control transfer criteria.

Over-time recognition (any one met): customer simultaneously receives and consumes benefits (recurring services); entity creates asset customer controls as created; asset has no alternative use and entity has right to payment for performance to date. Measure progress via input (cost-to-cost) or output (milestones) methods.

Common C-corp patterns:

• Product sales — point-in-time at delivery/shipment
• Service contracts — over-time, criterion 1 (simultaneous receipt/consumption)
• SaaS/subscriptions — over-time, ratably over period
• Bundled arrangements — identify each PO, allocate by SSP, recognize per satisfaction pattern

Monthly close actions: recognize deferred revenue earned during the month (Dr Deferred Revenue, Cr Revenue); accrue unbilled revenue for over-time POs (Dr Contract Asset, Cr Revenue); reassess variable consideration estimates.

For variable consideration constraint detail, contract modifications, principal vs. agent, licensing, and effective date log, see references/revenue-recognition-asc606.md.

Phase 4: Review and Reporting

• Trial balance — verify debits equal credits; scan for anomalies (negative assets, credit expense accounts, suspense account balances)
• Financial statements — generate P&L, Balance Sheet, Cash Flow Statement. Invoke accounting-foundation:financial-statements for presentation requirements.
• Variance analysis — compare to prior month and budget. Investigate variances exceeding materiality threshold (typically 10% or $1,000, whichever is greater).
• Analytical review — compute key ratios (current ratio, gross margin, DSO); flag anomalies
• Close memo — document all adjustments, open issues, and items requiring client attention
• Manager/partner review — second set of eyes on financial statements and reconciliations before delivery

For platform-specific execution, invoke qbo-integration:qbo-bookkeeping.

Phase 5: Period Lock

• Lock the period — set the closing date and password in the accounting system to prevent unauthorized posting to prior periods. Configure separate lock dates for accountant vs. client access if the system supports it.
• Archive supporting documents — bank statements, reconciliation reports, adjustment memos
• Deliver client package — financial statements, management letter (if applicable), action items

Year-End Close Extensions

Year-end close adds: close revenue (4xxx) and expense (5xxx–9xxx) to Income Summary, transfer net income to Retained Earnings (3200), close Dividends Declared (3500) to Retained Earnings. Invoke accounting-foundation:chart-of-accounts for year-end closing entry mechanics and equity account structure.

Internal Controls During Close

The close process itself is a key control activity. Apply COSO 2013 principles proportionate to entity size.

Segregation of Duties

Four functions should be separated: authorization, custody, recording, reconciliation. When staff size prevents full segregation (common in small C-corps), implement compensating controls:

• Owner review — owner independently reviews bank statements, canceled checks, and monthly financials. This is the single most important compensating control.
• External reconciliation — engage outside accountant for monthly or quarterly bank reconciliations
• Rotation of duties — periodically rotate responsibilities to prevent concealment and cross-train staff

Key Close Controls

• Bank reconciliation performed by someone other than the person recording transactions or handling cash
• Approval thresholds for expenditures (e.g., > $500 requires owner sign-off, > $5,000 requires dual approval)
• Journal entry posting restricted to authorized personnel via accounting system user roles
• Audit log reviewed for unexpected entries — the system should track all user activity in a log that cannot be edited or deleted
• Period-lock password prevents unauthorized posting to prior periods

Deficiency Handling

• Material weakness — reasonable possibility of material misstatement not prevented/detected; requires immediate remediation and disclosure
• Significant deficiency — less severe but merits governance attention; address within one to two quarters
• Deficiency — track and address as resources allow

For the full COSO five-component/17-principle framework, IT general controls, control documentation methods, and testing procedures, see references/internal-controls-coso.md.

Platform Execution

For platform-specific execution, invoke qbo-integration:qbo-bookkeeping.

Supporting References

Read these for deeper detail on specific topics:

• references/monthly-close-sop.md — Full 34-step close procedure with numbered checklist, pre-close preparation steps, and decision tables for bank reconciliation thresholds and missing-document handling. Read when walking through the close step-by-step or training new staff.
• references/lease-accounting-asc842.md — Complete ASC 842 guidance: five finance-lease classification criteria with bright-line thresholds, initial and subsequent measurement mechanics for both lease types, short-term exemption rules, modification accounting, practical expedients (package of three, hindsight, portfolio, non-lease components), disclosure requirements, account setup and journal entry templates, and effective date log through ASU 2024-02. Read when setting up a new lease, handling modifications, or preparing lease disclosures.
• references/revenue-recognition-asc606.md — Full five-step model with detailed guidance on each step, over-time vs. point-in-time criteria, variable consideration constraint, contract modifications (three treatments), principal vs. agent determination, licensing (right-to-access vs. right-to-use), common C-corp revenue patterns, recording templates, and effective date log through ASU 2024-13. Read when evaluating a new revenue arrangement or complex contract modification.
• references/internal-controls-coso.md — COSO 2013 five-component/17-principle framework, small entity considerations, common detective and preventive controls for C-corps, IT general controls for cloud accounting environments, segregation of duties with compensating controls, control documentation methods (narratives, flowcharts, matrices), testing effectiveness (inquiry, observation, inspection, reperformance), deficiency classification and communication requirements. Read when designing controls, responding to audit findings, or assessing control environment.

Cross-Plugin References

• Invoke bookkeeping:reconciliation — prerequisite: all balance sheet accounts must be reconciled before Phase 3
• Invoke accounting-foundation:chart-of-accounts — for depreciation asset class ranges, contra accounts, year-end closing entry mechanics, and period-close account structure
• Invoke accounting-foundation:financial-statements — for statement presentation requirements and financial statement generation during Phase 4
• Invoke qbo-integration:qbo-reporting — for platform-specific report generation (P&L, Balance Sheet, Trial Balance with period comparison) during Phase 4

Cross-Plugin Consumers

• tax-prep:form-1120-prep — clean closed financials are the starting point for tax return preparation
• tax-prep:tax-planning — book-tax differences identified during close feed planning analysis
• financial-planning:budgeting-forecasting — closed actuals provide budget-vs-actual variance data

Internal Controls — COSO 2013 Framework

Guidance for designing, implementing, and evaluating internal controls using the COSO 2013 framework, with focus on small/mid C-corporations.

Tier: 3 (evergreen framework — COSO 2013 is the current authoritative version)

Skills: bookkeeping-review, financial-statement-preparation, engagement-management, audit-support

Contents

• Overview
• Five Components and 17 Principles
• Small Entity Considerations
• Common Controls for C-Corps
• IT General Controls
• Segregation of Duties
• Documenting Controls
• Testing Effectiveness
• Deficiency Classification
• Accounting System Controls
• Decision Points
• References

---

Overview

The Committee of Sponsoring Organizations of the Treadway Commission (COSO) published the updated Internal Control — Integrated Framework in 2013, superseding the original 1992 framework. It is the most widely accepted framework for designing and evaluating internal controls over financial reporting (ICFR) in the United States.

Internal control is defined as a process, effected by an entity's board of directors, management, and other personnel, designed to provide reasonable assurance regarding the achievement of objectives in three categories:

• Operations: effectiveness and efficiency of operations
• Reporting: reliability of financial reporting
• Compliance: compliance with applicable laws and regulations

The framework consists of five interrelated components supported by 17 principles. All five components and all relevant principles must be present and functioning for the system of internal control to be effective.

---

Five Components and 17 Principles

Control Environment

The foundation — sets the tone of the organization and establishes the basis for all other components.

1. Integrity and ethical values: management demonstrates commitment to integrity and ethical values through actions, policies, and culture 2. Board oversight: the board of directors (or equivalent oversight body) demonstrates independence from management and exercises oversight of internal control development and performance 3. Organizational structure: management establishes reporting lines, authority, and responsibility in pursuit of objectives — clear organizational chart, defined roles 4. Competence commitment: the organization demonstrates commitment to attract, develop, and retain competent individuals aligned with objectives — hiring, training, performance evaluation 5. Accountability: the organization holds individuals accountable for their internal control responsibilities — performance measures, incentives, consequences

Risk Assessment

The process of identifying and analyzing risks to achieving objectives, forming the basis for how risks should be managed.

6. Specify objectives: the organization specifies objectives with sufficient clarity to enable identification and assessment of risks — financial reporting objectives must be consistent with the applicable framework (GAAP, tax basis, etc.) 7. Identify and analyze risks: the organization identifies risks to achieving objectives across the entity and analyzes risks to determine how they should be managed — consider both internal and external factors 8. Assess fraud risk: the organization considers the potential for fraud in assessing risks — fraudulent reporting, misappropriation of assets, corruption. Addresses incentive/pressure, opportunity, and rationalization (fraud triangle) 9. Identify and analyze significant changes: the organization identifies and assesses changes that could significantly impact the system of internal control — new business lines, acquisitions, IT system changes, regulatory changes, key personnel turnover

Control Activities

The actions established by policies and procedures that help ensure management directives to mitigate risks are carried out.

10. Select and develop control activities: the organization selects and develops control activities that contribute to mitigating risks to acceptable levels — preventive and detective controls addressing identified risks 11. Select and develop IT general controls: the organization selects and develops general control activities over technology to support the achievement of objectives — access controls, change management, operations, program development 12. Deploy through policies and procedures: the organization deploys control activities through policies that establish expectations and procedures that put policies into action — documented, communicated, consistently applied

Information and Communication

The information necessary to carry out internal control responsibilities and the communication channels to support it.

13. Use relevant, quality information: the organization obtains or generates and uses relevant, quality information to support the functioning of internal control — timely, accurate, complete, accessible 14. Communicate internally: the organization internally communicates information, including objectives and responsibilities for internal control, necessary to support the functioning of internal control — upward, downward, and across the organization 15. Communicate externally: the organization communicates with external parties regarding matters affecting the functioning of internal control — regulators, auditors, customers, vendors, shareholders

Monitoring Activities

Assessments to ascertain whether the components of internal control are present and functioning over time.

16. Select, develop, and perform ongoing and/or separate evaluations: the organization selects, develops, and performs evaluations to ascertain whether the components of internal control are present and functioning — ongoing monitoring (embedded in processes) and separate evaluations (periodic assessments) 17. Evaluate and communicate deficiencies: the organization evaluates and communicates internal control deficiencies in a timely manner to parties responsible for taking corrective action, including senior management and the board as appropriate

---

Small Entity Considerations

The COSO framework applies to entities of all sizes, but implementation looks different in smaller organizations:

• Less formal documentation: policies may be communicated verbally or through demonstrated behavior rather than written manuals. The key is that controls exist and function, not that they are formally documented.
• Owner-manager involvement: in small entities, the owner-manager often directly performs or closely oversees key controls. This involvement can be an effective control itself but creates concentration risk if the owner-manager is the source of fraud risk.
• Fewer personnel: makes traditional segregation of duties difficult or impossible. Compensating controls (owner review, independent reconciliation, external oversight) become critical.
• Simpler IT environment: may use a single cloud-based accounting system with limited customization. IT general controls focus on access management, backup, and data integrity rather than complex change management processes.
• Proportionate documentation: documentation requirements scale with entity size. A small entity does not need the same level of formal documentation as a public company, but must document enough to demonstrate controls are designed and operating.
• Board oversight: many small C-corps lack a formal independent board. Owner oversight, advisory boards, or engagement of external advisors (CPA, attorney) can serve as compensating mechanisms.
• Culture over documentation: in small entities, the control environment often depends more on the tone set by ownership than on written policies. Ethical culture, demonstrated integrity, and clear expectations are the primary control environment elements.

---

Common Controls for C-Corps

Detective Controls (Identify errors or irregularities after they occur)

• Bank reconciliation: monthly reconciliation of all bank accounts to the GL by someone other than the person who records transactions or handles cash (see bk/bank-reconciliation.md)
• Monthly financial review by management: owner or manager reviews P&L and balance sheet, investigates variances to budget or prior period (see bk/monthly-close-sop.md)
• Accounts receivable aging review: periodic review of outstanding receivables to identify collection issues, unauthorized write-offs, or lapping
• Physical inventory counts: periodic (at least annual) physical counts compared to perpetual records; investigate and adjust variances
• Vendor statement reconciliation: compare vendor statements to AP records to detect missed invoices or duplicate payments
• Payroll review: review of payroll register by someone not involved in payroll processing — verify employees, rates, hours, deductions

Preventive Controls (Prevent errors or irregularities before they occur)

• Approval limits for expenditures: defined thresholds requiring management approval (e.g., purchases >$500 require owner sign-off, >$5,000 require two approvals)
• Dual signatures on checks: require two signatures on checks above a threshold (e.g., $2,500 or $5,000)
• Authorized signer list: maintain a current list of persons authorized to sign checks, approve expenditures, and execute contracts
• Purchase order system: require POs for purchases above a threshold to create an audit trail and authorization record
• New vendor approval: require approval before adding new vendors to the system to prevent fictitious vendor fraud
• Access controls to accounting system: limit system access by role; restrict journal entry posting to authorized personnel
• Backup procedures: regular automated backups of accounting data (cloud systems typically handle backup automatically; for desktop systems, verify backup schedule)

---

IT General Controls

IT general controls (ITGCs) support the reliability of information produced by IT systems. For small C-corps using cloud-based accounting systems, the scope is narrower than for entities with on-premises systems.

Access Management

• User provisioning: grant access based on job responsibilities; assign appropriate system roles (administrator, accountant, standard user, reports-only)
• Termination procedures: revoke access promptly when employees leave or change roles
• Password policies: enforce strong passwords; enable two-factor authentication (2FA) on the accounting system and banking portals
• Periodic access reviews: review user lists quarterly to verify appropriateness of access levels

Change Management

• Chart of accounts changes: require approval before adding, modifying, or deactivating accounts to prevent unauthorized GL structure changes
• System configuration changes: document changes to accounting system settings (company info, accounting preferences, tax settings, automation rules)
• Integration changes: review and approve connections to third-party apps (payment processors, payroll, bank feeds)

Operations

• Data backup: cloud-based accounting systems typically provide continuous backup. For desktop installations, verify backup is performed and tested regularly.
• Disaster recovery: document access procedures if primary systems are unavailable (accounting system login credentials stored securely, backup contacts for IT support)

Audit Log

The accounting system should maintain an audit log tracking: user, date/time, action (created, modified, deleted), entity affected. Use for monitoring and investigation.

---

Segregation of Duties

The principle of segregation requires that no single person should control all aspects of a transaction. Four functions should be separated where possible:

1. Authorization: approving transactions (e.g., approving a purchase order, authorizing a wire transfer) 2. Custody: physical control of assets (e.g., handling cash, holding inventory, signing checks) 3. Recording: entering transactions into the accounting system (e.g., posting journal entries, recording deposits) 4. Reconciliation: verifying recorded transactions against independent records (e.g., bank reconciliation, inventory counts)

Small Entity Compensating Controls

When segregation is not possible due to limited staff:

• Owner review: the owner-manager reviews all bank statements, canceled checks, and monthly financial statements independently. This is the single most important compensating control in a small entity.
• Bank statement review: owner receives bank statements (paper or electronic) directly and reviews for unusual transactions before handing to the bookkeeper
• Surprise audits: periodic unannounced reviews of cash, inventory, or expense reports
• External reconciliation: engage an outside accountant to perform monthly or quarterly bank reconciliations
• Dual control over cash: require two people for cash counts, bank deposits, and safe access
• Rotation of duties: periodically rotate responsibilities to prevent concealment of irregularities and to cross-train staff
• Mandatory vacations: require employees in sensitive positions to take consecutive time off, allowing others to perform their duties and potentially uncover irregularities

---

Documenting Controls

Methods

• Narrative descriptions: written descriptions of processes, identifying who does what, when, and what controls exist at each step. Most common for small entities.
• Flowcharts: visual representation of transaction flow from initiation to recording, with control points marked. Useful for complex processes.
• Control matrices: structured format mapping financial statement assertions to risks to controls to test procedures. Used in formal assessments.

Control Matrix Structure

For each significant process (revenue, purchasing, payroll, treasury):

• Assertion: what the financial statement claims (existence, completeness, accuracy, cutoff, classification, rights/obligations, presentation)
• Risk: what could go wrong (fictitious revenue, unrecorded liabilities, misclassified expenses)
• Control: the activity that mitigates the risk (approval required, reconciliation performed, segregation of duties)
• Frequency: how often the control operates (per transaction, daily, weekly, monthly, quarterly, annually)
• Control owner: who performs the control
• Evidence: what documentation the control produces (signed approval, reconciliation report, exception log)

---

Testing Effectiveness

Four methods for evaluating whether controls are operating as designed:

1. Inquiry: ask personnel who perform the control about their procedures, how they handle exceptions, and what they do if the control identifies an issue. Inquiry alone is generally insufficient. 2. Observation: watch the control being performed in real time. Provides evidence for a single point in time only. 3. Inspection of documentation: examine the evidence produced by the control — signed approvals, completed reconciliations, exception reports, audit logs. Most common method for detective controls. 4. Reperformance: independently re-execute the control to verify it produces the expected result. Most reliable method but also most resource-intensive.

Effective testing typically combines methods: inquiry + inspection (most common), inquiry + observation, or inquiry + reperformance for high-risk areas.

---

Deficiency Classification

Internal control deficiencies are classified by severity:

• Deficiency: a control is designed, implemented, or operated in a way that does not allow management or employees to prevent or detect misstatements on a timely basis. Exists when a control is missing or not operating effectively, but the risk of material misstatement is low.
• Significant deficiency: a deficiency, or combination of deficiencies, that is less severe than a material weakness yet important enough to merit attention by those charged with governance. Indicates a reasonable possibility that a more-than-inconsequential misstatement will not be prevented or detected.
• Material weakness: a deficiency, or combination of deficiencies, such that there is a reasonable possibility that a material misstatement of the financial statements will not be prevented or detected on a timely basis. Requires disclosure and remediation.

Communication Requirements

• Audit engagements (AU-C 265): significant deficiencies and material weaknesses must be communicated in writing to management and those charged with governance
• Review engagements (AR-C 90): no specific requirement to evaluate or report on internal controls, but the accountant should communicate any material weaknesses discovered during the review
• Compilation and preparation: no internal control evaluation or communication requirement, but the accountant should consider communicating deficiencies discovered in the course of the engagement

---

Accounting System Controls

Cloud-based accounting systems typically provide built-in features that support internal controls:

• User roles: assign role-based access with the minimum permissions necessary for each user's responsibilities (e.g., administrator, standard user, reports-only)
• Audit log: review the system audit log that tracks all user activity — who created, modified, or deleted transactions. The log should be immutable (not editable or deletable by any user). Use for monitoring and investigation.
• Period lock: set a closing date and password to prevent unauthorized changes to prior periods. Configure separate lock dates for accountant vs. client access if the system supports it.
• Two-factor authentication: enable for all users, especially those with administrative or accountant-level roles
• Bank feed rules: automate categorization but review for accuracy. Overly broad rules can miscategorize transactions. Periodically audit rules for continued appropriateness.
• Approval workflows: use system-provided approval workflows for purchase orders and expenses where available; otherwise use manual approval processes with documented evidence
• Granular permissions: where the system supports it, configure granular control over what users can view, create, edit, and delete in each functional area (sales, expenses, banking, payroll, reports)
• Activity feed: review recent activity across all users as a quick visual check for unexpected entries

For platform-specific execution, invoke qbo-integration:qbo-bookkeeping.

---

Decision Points

• Framework selection — COSO 2013 is the default for US entities. Smaller entities may use the AICPA's "Internal Control — A Tool for the Audit Committee" for a simplified approach. COBIT is used for IT-focused assessments.
• Scope of assessment — for small C-corps not subject to SOX, focus on high-risk areas: cash and treasury, revenue recognition, significant estimates, related party transactions, and payroll. Full-scope assessment is typically not cost-justified.
• Formality of documentation — scale to entity size and risk. A small single-location C-corp with simple operations may document controls through brief narratives. A multi-location entity with complex transactions needs control matrices and flowcharts.
• Segregation of duties infeasible — when staff size prevents proper segregation, document the compensating controls in place (owner review, external reconciliation). Acknowledge the residual risk to governance.
• IT controls scope — for cloud accounting system users, the cloud provider manages infrastructure, application, and database controls. Entity-level IT controls focus on access management, configuration, and integration management. No need to test data center controls.
• Frequency of monitoring — ongoing monitoring (embedded in daily operations) is preferred over separate evaluations (periodic assessments). For small entities, monthly owner review of financial statements combined with accounting system audit log review provides adequate monitoring.
• Remediation priority — material weaknesses require immediate remediation. Significant deficiencies should be addressed within a reasonable timeframe (one to two quarters). Deficiencies should be tracked and addressed as resources allow.
• Cost-benefit — controls must be cost-justified. A control that costs more to implement than the risk it mitigates is not reasonable. Small entities should focus on high-impact, low-cost controls (bank reconciliation, owner review, access restrictions).

---

References

• COSO. "Internal Control — Integrated Framework." Committee of Sponsoring Organizations of the Treadway Commission, 2013.
• COSO. "Internal Control over Financial Reporting — Guidance for Smaller Public Companies." 2006 (supplemental guidance applicable to smaller entities generally).
• AICPA. AU-C Section 265, Communicating Internal Control Related Matters Identified in an Audit.
• AICPA. AU-C Section 315, Understanding the Entity and Its Environment and Assessing the Risks of Material Misstatement.
• AICPA. "Audit Guide: Assessing and Responding to Audit Risk in a Financial Statement Audit."
• ISACA. COBIT 2019 Framework (IT governance and controls).

Lease Accounting — ASC 842

Guidance for recognizing, measuring, and recording leases under ASC 842 (Leases).

Tier: 2 (effective date log — ASC 842 has adoption dates and subsequent amendments)

Skills: bookkeeping-monthly-close, bookkeeping-review, tax-provision, financial-statement-preparation

Contents

• Overview
• Lease Classification
• Initial Measurement
• Subsequent Measurement
• Short-Term Lease Exemption
• Lease Modifications
• Practical Expedients
• Disclosure Requirements
• GL Account Setup
• Decision Points
• Effective Date Log
• References

---

Overview

ASC 842 requires lessees to recognize virtually all leases with terms greater than 12 months on the balance sheet. The lessee records a right-of-use (ROU) asset and a corresponding lease liability at lease commencement. This standard replaced ASC 840, which allowed operating leases to remain off-balance-sheet.

Core principle: a lease conveys the right to control the use of an identified asset for a period of time in exchange for consideration. Control exists when the lessee directs the use of the asset and obtains substantially all its economic benefits.

---

Lease Classification

Leases are classified as either finance or operating at commencement. Classification determines the expense pattern, not whether the lease appears on the balance sheet (both types do).

Finance Lease Criteria

A lease is a finance lease if it meets any one of these five criteria:

1. Ownership transfer — the lease transfers ownership of the asset to the lessee by the end of the lease term 2. Purchase option — the lease grants a purchase option that the lessee is reasonably certain to exercise 3. Lease term — the lease term is for the major part of the remaining economic life of the asset (bright-line guidance: typically 75% or more) 4. Present value — the present value of lease payments plus any residual value guarantee equals or exceeds substantially all of the fair value of the asset (bright-line guidance: typically 90% or more) 5. Specialized asset — the underlying asset is so specialized that it has no alternative use to the lessor at the end of the lease term

If none of these criteria are met, the lease is an operating lease.

---

Initial Measurement

Lease Liability

Lease liability = present value of remaining lease payments, discounted at:

• Rate implicit in the lease — if determinable (rare for lessees)
• Lessee's incremental borrowing rate (IBR) — the rate the lessee would pay to borrow on a collateralized basis over a similar term in a similar economic environment

Lease payments included in the measurement: fixed payments (less lease incentives), variable payments based on an index or rate, exercise price of purchase option (if reasonably certain), termination penalties (if lease term reflects exercise), and residual value guarantees.

Variable payments tied to usage or performance (e.g., per-mile charges) are excluded from the liability and expensed as incurred.

ROU Asset

ROU asset = lease liability + initial direct costs (e.g., commissions, legal fees) + lease payments made at or before commencement (prepaid rent) - lease incentives received.

---

Subsequent Measurement

Operating Leases

• Lease expense: recognized on a straight-line basis over the lease term as a single line item (typically within operating expenses)
• Lease liability: reduced by the cash payment, increased by interest (discount rate applied to opening liability balance)
• ROU asset: amortized as a plug — total lease expense minus the interest on the liability equals the ROU amortization for the period
• Result: level expense each period, with front-loaded interest and back-loaded amortization

Finance Leases

• Amortization expense: ROU asset amortized on a straight-line basis over the shorter of the lease term or the useful life of the asset (amortization expense, separate from interest)
• Interest expense: computed using the effective interest method on the lease liability balance
• Result: front-loaded total expense (interest is highest in early periods, declining over time)
• Two line items on the income statement: amortization expense and interest expense

---

Short-Term Lease Exemption

Leases with a term of 12 months or less at commencement (with no purchase option the lessee is reasonably certain to exercise) may be excluded from balance-sheet recognition.

• Election is made by asset class (e.g., exempt all short-term equipment leases, but not short-term vehicle leases)
• If elected, expense lease payments on a straight-line basis (or other systematic basis if more representative)
• Disclose the election and short-term lease cost in the footnotes
• A lease that is short-term at commencement but is later modified to extend beyond 12 months must be reassessed and recognized on the balance sheet

---

Lease Modifications

A modification is a change in the scope or consideration of a lease not part of the original terms.

• Separate lease treatment: if the modification grants an additional right of use that is distinct AND the increase in consideration is commensurate with the standalone price (adjusted for the contract), treat as a separate new lease
• Not a separate lease: remeasure the lease liability using a revised discount rate at the modification date, and adjust the ROU asset by the same amount. If the modification decreases scope, reduce the ROU asset proportionally and recognize any gain/loss
• Reassess classification at the modification date

---

Practical Expedients

Transition Package (Package of Three)

Entities may elect as a package (all or none) to not reassess at transition: 1. Whether existing contracts are or contain leases 2. Lease classification for existing leases 3. Whether initial direct costs qualify for capitalization

Hindsight Practical Expedient

Allows use of hindsight when determining lease term (e.g., whether renewal options are reasonably certain) and assessing impairment of ROU assets at transition. Elected separately from the package of three.

Other Expedients

• Portfolio approach: apply to a portfolio of leases with similar characteristics if the result is not materially different from individual application
• Non-lease components: lessee may elect, by asset class, to combine lease and non-lease components (e.g., common area maintenance in real estate) and account for as a single lease component

---

Disclosure Requirements

• Lease cost by type: finance lease (amortization + interest), operating lease cost, short-term lease cost, variable lease cost
• Maturity analysis: undiscounted future lease payments by year for the next five years and thereafter, reconciled to the lease liability
• Weighted-average remaining lease term (separately for operating and finance)
• Weighted-average discount rate (separately for operating and finance)
• Supplemental cash flow information: cash paid for leases, ROU assets obtained in exchange for lease liabilities
• Qualitative disclosures: nature of leases, significant assumptions and judgments, restrictions or covenants

---

GL Account Setup

Most accounting systems do not have a dedicated lease accounting module. Manual account setup and journal entries are required.

Required Accounts

• ROU Asset — Operating Leases: create as a non-current asset (or current asset if term < 1 year remaining). Name: "Right-of-Use Asset — Operating"
• ROU Asset — Finance Leases: create as a non-current asset. Name: "Right-of-Use Asset — Finance"
• Lease Liability — Current: create as a current liability. Name: "Lease Liability — Current Portion"
• Lease Liability — Non-Current: create as a long-term liability. Name: "Lease Liability — Long-Term"
• Lease Expense: use existing rent/lease expense account for operating leases
• Amortization Expense: use depreciation/amortization expense account for finance leases
• Interest Expense — Finance Leases: use existing interest expense account

Monthly Journal Entry — Operating Lease

1. Debit Lease Expense (straight-line amount) 2. Credit Cash / AP (actual payment) 3. Debit or Credit ROU Asset (plug to balance — difference between straight-line expense and interest on liability) 4. Debit Lease Liability (principal portion of payment) 5. Credit Lease Liability (interest accrual — discount rate x opening liability)

Monthly Journal Entry — Finance Lease

1. Debit Amortization Expense (straight-line on ROU asset) 2. Credit Accumulated Amortization / ROU Asset 3. Debit Interest Expense (effective interest on liability) 4. Debit Lease Liability — principal reduction 5. Credit Cash (actual payment)

Amortization Schedule

Maintain an external amortization schedule (spreadsheet) for each lease tracking: opening liability, interest, payment, closing liability, opening ROU, amortization, closing ROU. Journal entries in the GL are driven from this schedule.

For platform-specific execution, invoke qbo-integration:qbo-bookkeeping.

---

Decision Points

• Lease vs service contract — if the customer does not control an identified asset (e.g., vendor can substitute equipment freely), it is a service, not a lease. No ASC 842 treatment.
• Renewal options — include in lease term only if reasonably certain to exercise. Factors: economic incentive, business need, leasehold improvements, termination penalties, history of renewals.
• IBR determination — for private companies without public debt, estimate based on secured borrowing rate of similar term. Document the methodology.
• Short-term election — evaluate by asset class. If most leases in a class are short-term and amounts are immaterial, the exemption reduces complexity significantly.
• Embedded leases — review service contracts, outsourcing agreements, and IT hosting arrangements for embedded lease components.
• Materiality — private companies may use materiality to limit the number of leases recognized. Document the threshold and rationale.

---

Effective Date Log

• ASC 842 (ASU 2016-02): effective for public business entities for fiscal years beginning after December 15, 2018 (calendar year 2019). Effective for all other entities for fiscal years beginning after December 15, 2021 (calendar year 2022).
• ASU 2018-10: codification improvements to ASC 842 (clarifications, corrections)
• ASU 2018-11: targeted improvements — optional transition method allowing application at adoption date rather than earliest comparative period
• ASU 2019-01: codification improvements — sales-type lessor transition, cash flow statement classification
• ASU 2020-05: effective date deferral for private companies (deferred to 2022)
• ASU 2021-09: discount rate for lessees that are not public business entities — allows risk-free rate election by asset class
• ASU 2023-01: common control leases — allows private companies to use written terms and conditions (not legally enforceable terms) for common control arrangements; effective for fiscal years beginning after December 15, 2023
• ASU 2024-02: profits interests and similar awards — clarification of scope for certain compensation arrangements; effective for fiscal years beginning after December 15, 2024

---

References

• FASB ASC 842, Leases
• FASB ASU 2016-02, Leases (Topic 842)
• FASB ASU 2023-01, Common Control Arrangements (Topic 842)
• FASB ASU 2024-02, Profits Interests (Topic 842)
• Deloitte. "A Roadmap to Applying the New Leasing Standard." Deloitte Accounting Research Tool.
• PwC. "Leases Guide." PwC Viewpoint.
• AICPA. "Accounting and Auditing Guide: Leases."

Monthly Close SOP

Standard operating procedure for month-end close of bookkeeping clients.

Tier: 3 (evergreen, no year indexing needed)

Skills: bookkeeping-monthly-close, bookkeeping-review, client-deliverables

Contents

• Overview
• Pre-Close Preparation
• Phase 1: Transaction Completeness
• Phase 2: Reconciliation
• Phase 3: Adjusting Entries
• Phase 4: Review and Reporting
• Phase 5: Period Lock
• Common Pitfalls
• Platform Execution
• Decision Points
• References

---

Overview

The monthly close converts a month of raw transactions into reliable financial statements. It follows a strict sequence: completeness first, then reconciliation, then adjustments, then review. Skipping steps or reordering creates compounding errors.

Target: close within 5-7 business days after month-end for routine clients; 10 business days for complex (multi-entity, inventory, payroll).

---

Pre-Close Preparation

Complete before Day 1 of close:

1. Obtain bank statements for all accounts (checking, savings, money market, credit cards, loans) 2. Obtain merchant processor statements (Stripe, Square, PayPal) 3. Confirm payroll is posted — verify payroll provider ran and data is in the GL 4. Collect client-supplied documents — invoices, receipts, contracts signed during the month 5. Review prior month's open items — any unresolved reconciling items or pending adjustments

---

Phase 1: Transaction Completeness

Ensure every economic event for the period is recorded before reconciling.

6. Review and categorize bank feed transactions — clear the bank feed inbox; do not leave unmatched items 7. Record accounts receivable — post all invoices issued during the month; review aging for collectibility 8. Record accounts payable — enter all bills received; match to POs where applicable 9. Post payroll entries — if using external provider (ADP, Gusto), post summary journal entries for gross wages, employer taxes, withholdings, and net pay (see bk/payroll-recording.md) 10. Record credit card charges — categorize all charges; match to receipts 11. Record cash transactions — petty cash, owner draws, capital contributions 12. Post recurring journal entries — rent straight-lining, insurance amortization, loan interest accruals

---

Phase 2: Reconciliation

Reconcile balance sheet accounts to independent third-party evidence.

13. Bank reconciliation — reconcile every bank account to the statement ending balance (see bk/bank-reconciliation.md) 14. Credit card reconciliation — reconcile each card to the statement (see bk/credit-card-reconciliation.md) 15. Loan reconciliation — tie loan balances to lender statements; verify principal/interest split 16. Intercompany reconciliation — if multi-entity, confirm intercompany balances net to zero 17. Accounts receivable reconciliation — tie AR aging total to the GL control account 18. Accounts payable reconciliation — tie AP aging total to the GL control account

Rule: Do not proceed to adjusting entries until all reconciliations are complete and differences are investigated.

---

Phase 3: Adjusting Entries

Post entries that align revenue and expense recognition with the accounting period.

19. Accrued expenses — record expenses incurred but not yet billed (utilities, professional fees, interest) 20. Accrued revenue — record revenue earned but not yet invoiced (milestone completions, time-based services) 21. Prepaid expense amortization — expense the current-month portion of prepaid insurance, rent, subscriptions 22. Depreciation and amortization — post monthly depreciation for fixed assets; amortize intangibles 23. Inventory adjustments — if applicable, adjust for shrinkage, obsolescence, lower-of-cost-or-market 24. Deferred revenue recognition — recognize the portion earned during the month 25. Payroll tax true-up — reconcile accrued payroll taxes to actual deposits; adjust if needed

---

Phase 4: Review and Reporting

26. Run trial balance — verify debits equal credits; scan for unusual balances (negative assets, credit expense accounts) 27. Generate financial statements — Income Statement, Balance Sheet, Statement of Cash Flows 28. Variance analysis — compare to prior month and to budget; investigate variances exceeding materiality threshold (typically 10% or $1,000, whichever is greater) 29. Analytical review — compute key ratios (current ratio, gross margin, DSO) and flag anomalies 30. Prepare close memo — document adjustments made, open issues, and items requiring client attention 31. Manager/partner review — second set of eyes on financial statements and reconciliations before delivery

---

Phase 5: Period Lock

32. Lock the period in the accounting system — prevents accidental posting to closed months 33. Archive supporting documents — bank statements, reconciliation reports, adjustment memos 34. Deliver client package — financial statements, management letter (if applicable), action items

---

Common Pitfalls

• Recording net payroll instead of gross — understates wages expense and omits employer tax liability; always record the full journal entry
• Skipping balance sheet reconciliation — reconciling only the bank account and ignoring AR, AP, prepaids, and loans; errors accumulate silently
• Posting to locked periods — if the period lock date is not set, late entries slip into prior months and invalidate delivered financials
• Ignoring stale outstanding checks — checks outstanding >90 days should be investigated; >180 days may need escheatment review
• Accrual omission — forgetting to accrue large month-end expenses (rent if paid in arrears, utilities, contract labor) distorts the P&L
• Bank feed over-reliance — auto-matching rules can create duplicates or miscategorize; always review matches manually
• Not reversing prior-month accruals — accruals from the prior month must be reversed to avoid double-counting when the actual bill arrives
• Unclear task ownership — when multiple team members touch the close, tasks fall through cracks; use a checklist with assigned names

---

Platform Execution

For platform-specific execution (period lock, reconciliation workflow, recurring transactions, bank feeds, reporting), invoke qbo-integration:qbo-bookkeeping.

---

Decision Points

---

References

• FloQast. "Month-End Close Checklist." https://floqast.com/blog/month-end-close-checklist
• AICPA. Statements on Standards for Accounting and Review Services (SSARS)

Revenue Recognition — ASC 606

Guidance for recognizing revenue from contracts with customers under ASC 606.

Tier: 2 (effective date log — ASC 606 has adoption dates and subsequent amendments)

Skills: bookkeeping-monthly-close, bookkeeping-review, tax-provision, financial-statement-preparation

Contents

• Overview
• Five-Step Model
• Over-Time vs Point-in-Time
• Variable Consideration
• Contract Modifications
• Principal vs Agent
• Licensing
• Common C-Corp Patterns
• GL Account Setup and Recording
• Decision Points
• Effective Date Log
• References

---

Overview

ASC 606 establishes a single, comprehensive framework for recognizing revenue from contracts with customers. The core principle: recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to be entitled to in exchange for those goods or services.

ASC 606 replaced industry-specific guidance (ASC 605 and related subtopics) with one model applicable across all industries.

---

Five-Step Model

Step 1: Identify the Contract

A contract exists when all of the following criteria are met:

• Approval: parties have approved the contract (written, oral, or implied by customary business practices)
• Rights identified: each party's rights regarding goods or services are identifiable
• Payment terms: payment terms are identifiable
• Commercial substance: the contract has commercial substance (future cash flows are expected to change)
• Probable collection: it is probable that the entity will collect the consideration it is entitled to

If criteria are not met, consider whether payments received are a deposit (liability) rather than revenue.

Step 2: Identify Performance Obligations

A performance obligation (PO) is a promise to transfer a distinct good or service (or a bundle). A good or service is distinct if both:

• Capable of being distinct: the customer can benefit from the good or service on its own or together with other readily available resources
• Distinct within the contract: the promise is separately identifiable from other promises (not highly interrelated, does not significantly modify or customize another promised good/service, not highly dependent on other promises)

A series of distinct goods or services that are substantially the same and have the same pattern of transfer (e.g., monthly cleaning service) may be treated as a single PO.

Step 3: Determine the Transaction Price

The transaction price is the amount the entity expects to be entitled to, including:

• Fixed consideration: stated contract price
• Variable consideration: discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties. Estimate using either expected value (probability-weighted) or most likely amount, whichever better predicts the outcome.
• Significant financing component: if timing of payments differs significantly from transfer of goods/services (>1 year), adjust for the time value of money. Practical expedient: ignore if period between payment and transfer is one year or less.
• Non-cash consideration: measure at fair value at contract inception
• Consideration payable to a customer: reduce the transaction price unless the payment is for a distinct good or service from the customer

Step 4: Allocate the Transaction Price

Allocate the transaction price to each PO based on relative standalone selling price (SSP). Methods to estimate SSP:

• Adjusted market assessment: estimate the price customers in the market would pay
• Expected cost plus margin: forecast costs to satisfy the PO, add an appropriate margin
• Residual approach: permitted only when SSP is highly variable or uncertain; allocate residual amount after allocating observable SSPs to other POs

Discounts are allocated proportionally to all POs unless observable evidence indicates the discount relates entirely to one or more (but not all) POs.

Step 5: Recognize Revenue

Recognize revenue when (or as) each PO is satisfied by transferring control of the promised good or service to the customer.

---

Over-Time vs Point-in-Time

Over-Time Recognition

Revenue is recognized over time if any one of these criteria is met:

1. Simultaneous receipt and consumption: the customer simultaneously receives and consumes the benefits as the entity performs (e.g., recurring services — cleaning, payroll processing) 2. Customer-controlled asset: the entity's performance creates or enhances an asset the customer controls as it is created (e.g., building on customer's land) 3. No alternative use + right to payment: the entity's performance creates an asset with no alternative use to the entity, and the entity has an enforceable right to payment for performance completed to date (e.g., custom manufacturing)

Measuring Progress Over Time

• Input methods: measure progress based on inputs (costs incurred, labor hours, machine hours). Cost-to-cost is most common: revenue = (costs to date / total estimated costs) x transaction price.
• Output methods: measure progress based on outputs (units produced, milestones reached, surveys of performance). Used when outputs directly measure value transferred.

Point-in-Time Recognition

If none of the over-time criteria are met, revenue is recognized at the point in time when control transfers. Indicators of control transfer: entity has present right to payment, customer has legal title, customer has physical possession, customer has significant risks and rewards, customer has accepted the asset.

---

Variable Consideration

Constraint

Include variable consideration in the transaction price only to the extent it is highly probable (IFRS: "highly probable"; US GAAP: "probable") that a significant reversal of cumulative revenue recognized will not occur when the uncertainty is resolved.

Factors increasing the risk of reversal: susceptibility to external factors, long resolution period, limited experience with similar contracts, broad range of possible outcomes, practice of offering concessions.

Reassessment

Reassess the estimated transaction price (including the constraint) at each reporting date. Changes are recognized as revenue adjustments in the period of change (cumulative catch-up).

---

Contract Modifications

A contract modification is a change in scope, price, or both that is approved by the parties.

• Separate contract: treat as a separate contract if the modification adds distinct goods/services AND the price increase reflects standalone selling prices. Account for prospectively.
• Not a separate contract — distinct remaining goods/services: treat as termination of the old contract and creation of a new one. Reallocate consideration (including unrecognized amounts from original contract) to remaining POs.
• Not a separate contract — not distinct remaining goods/services: treat as part of the original contract. Update progress measurement cumulatively (catch-up adjustment).

---

Principal vs Agent

Determines whether to recognize revenue gross (principal) or net (agent/commission):

• Principal: controls the good or service before transfer to the customer. Indicators: primary obligation for fulfillment, inventory risk, pricing discretion. Recognize gross revenue.
• Agent: arranges for another party to provide the good or service. Does not control the good/service before transfer. Recognize net revenue (fee or commission).

Evaluate on a per-PO basis — an entity can be principal for some POs and agent for others within the same contract.

---

Licensing

Two types of licenses:

• Right to access (dynamic IP — brand, software updated frequently): recognize over time as the entity performs; the customer benefits from ongoing access to the licensor's IP
• Right to use (static IP — completed software, music, film): recognize at point in time when the license is transferred; the customer can use the IP as it exists at grant

Factors determining the type: entity undertakes activities that significantly affect the IP, customer is exposed to effects of those activities, activities do not result in transfer of a separate good/service.

---

Common C-Corp Patterns

• Product sales (wholesale/retail): typically point-in-time at delivery or shipment (depending on shipping terms). Variable consideration for returns — estimate return liability and refund asset.
• Service contracts (consulting, professional services): typically over-time under criterion 1 (simultaneous receipt/consumption). Use input methods (hours) or output methods (deliverables).
• Long-term construction: over-time under criterion 3 (no alternative use + right to payment). Cost-to-cost method most common.
• Software licenses: right-to-use (point-in-time) if no significant ongoing updates; right-to-access (over-time) if continuous updates are integral.
• SaaS/subscription: over-time under criterion 1. Recognize ratably over the subscription period.
• Bundled arrangements (hardware + software + support): identify each PO, allocate by SSP, recognize each PO per its satisfaction pattern.
• Warranties: assurance-type (included in sale price, not a separate PO — accrue estimated cost) vs service-type (extends beyond assurance — separate PO, defer revenue).

---

GL Account Setup and Recording

Account Setup

• Revenue accounts: create separate revenue accounts for each significant PO type or revenue stream (product sales, service revenue, license revenue, subscription revenue). Enables disaggregated reporting.
• Deferred Revenue / Contract Liability: create as a current liability. Name: "Deferred Revenue" or "Contract Liability". Used when cash is received before PO is satisfied.
• Unbilled Revenue / Contract Asset: create as a current asset. Name: "Unbilled Revenue" or "Contract Asset". Used when revenue is recognized before invoicing (over-time recognition with billing in arrears).

Recording Patterns

Point-in-time (product sale):

• Upon delivery: Debit Accounts Receivable, Credit Revenue

Over-time (service contract, monthly recognition):

• Billing: Debit Accounts Receivable, Credit Deferred Revenue (if billed in advance)
• Monthly recognition: Debit Deferred Revenue, Credit Service Revenue
• Or if billed in arrears: Debit Unbilled Revenue, Credit Service Revenue; upon billing: Debit Accounts Receivable, Credit Unbilled Revenue

Bundled arrangement:

• Split invoice across PO revenue accounts based on SSP allocation. Use journal entry or line-item detail on the invoice.

Tracking

Most accounting systems do not have native contract-level ASC 606 tracking. Use sub-customers or projects to track revenue by contract, classes or tags to categorize revenue by PO type, custom fields on invoices for contract reference, and external schedules for complex arrangements (multi-year, variable consideration).

For platform-specific execution, invoke qbo-integration:qbo-bookkeeping.

---

Decision Points

• Contract existence — if collection is not probable, do not recognize revenue. Reassess when circumstances change.
• Distinct POs — when goods/services are highly interrelated or significantly customized together, they are likely a single PO (e.g., design + build in construction).
• SSP not directly observable — use adjusted market or expected cost plus margin. Document methodology and rationale. Residual approach is a last resort.
• Variable consideration — apply the constraint conservatively. If significant uncertainty exists, exclude from the transaction price until resolved.
• Bill-and-hold — revenue can be recognized before delivery only if: customer requested the arrangement, separate identified risk of loss, asset is identified and ready, no ability to use the asset or direct it to another customer.
• Materiality — for small C-corps with simple revenue streams, ASC 606 often does not change outcomes vs legacy guidance. Document that the analysis was performed.
• Returns — estimate expected returns using historical data. Record refund liability (credit to AR) and asset for right to recover product (debit inventory-like account).

---

Effective Date Log

• ASC 606 (ASU 2014-09): effective for public business entities for fiscal years beginning after December 15, 2017 (calendar year 2018). Effective for all other entities for fiscal years beginning after December 15, 2018 (calendar year 2019).
• ASU 2015-14: deferral of effective date by one year (for both public and private)
• ASU 2016-08: principal vs agent considerations (implementation guidance)
• ASU 2016-10: identifying performance obligations and licensing (implementation guidance)
• ASU 2016-12: narrow-scope improvements and practical expedients (transition)
• ASU 2016-20: technical corrections and improvements to ASC 606
• ASU 2021-08: contract assets and contract liabilities acquired in business combinations — require acquirer to apply ASC 606 to measure contract assets/liabilities (not fair value); effective for public entities 2023, private entities 2024
• ASU 2024-13: disaggregation of income statement expenses — requires disaggregated disclosure of certain expenses (including cost of revenue); effective for public entities beginning after December 15, 2026 (large accelerated filers) and December 15, 2027 (all other public entities)

---

References

• FASB ASC 606, Revenue from Contracts with Customers
• FASB ASU 2014-09, Revenue from Contracts with Customers (Topic 606)
• FASB ASU 2021-08, Business Combinations — Accounting for Contract Assets and Liabilities
• AICPA Revenue Recognition Guide (industry-specific implementation guidance)
• Deloitte. "A Roadmap to Applying the New Revenue Recognition Standard." Deloitte Accounting Research Tool.
• PwC. "Revenue from Contracts with Customers — Global Edition." PwC Viewpoint.
• EY. "Financial Reporting Developments: Revenue from Contracts with Customers (ASC 606)."