HarborWorks begins by separating the eight kinds of record involved in NP-2026-04 and assigning each decision to its qualified owner. The output is a source-and-owner map that every later reconciliation uses.
Separate the records before reconciling them
Revenue is recognized when or as promised goods or services transfer to a customer in an amount reflecting the consideration to which the entity expects to be entitled. Signature, billing, and cash receipt do not by themselves create recognized revenue (FASB, 2014; IASB, 2014).
Each record changes only when the applicable evidence, policy criteria, owner, and effective date are present. This is an operating rule, not an accounting conclusion or a claim that balances move through one universal sequence. A contract can simultaneously have partly satisfied obligations, a receivable, and a contract liability.
HarborWorks shows why. The company may admit the $120,000 contract to its bookings register on April 1 under its written management policy. The accounting owner separately identifies the performance obligation and recognition method. Billing creates the $120,000 payment request. Payment on April 15 settles the receivable, while the remaining obligation continues to be accounted for under the approved policy. The booking, revenue, invoice, receivable, contract liability, and cash application are linked statements about one arrangement.
Assign each record to its qualified owner
Bookings are commitments admitted under a management policy; they are not a journal entry or an accounting-revenue category defined by ASC 606 or IFRS 15. The chief executive officer (CEO) or chief financial officer (CFO) should approve the policy. It should state the qualifying agreement, approvals, term, cancellations, options, modifications, taxes, currency treatment, and handling of variable amounts. Each register line links the customer, contract, approved amount, dates, policy version, and later changes.
The controller or qualified accounting owner maintains the performance-obligation and recognition schedule. For each obligation, it identifies the allocated amount, satisfaction pattern, method used to measure progress for over-time recognition when applicable, accepted transfer evidence, estimates, review owner, and conclusion. An operational milestone is relevant only to the extent the accounting policy and facts make it relevant.
Link Billing, Balances, and Cash to the Contract
The billing owner translates approved rights and terms into invoices or other payment requests. The record needs the contract, schedule or trigger, source quantity, price rule, tax treatment, customer details, purchase-order requirement, and dispute route. Billing remains separate from recognition. A conditional right after performance may be a contract asset; an unconditional right apart from the passage of time is a receivable (FASB, 2014; IASB, 2014).
A contract liability relates to consideration received or due before the related transfer under the accounting policy. Deferred revenue and unearned revenue are common labels that must map to the entity's applicable presentation. Reconcile contract assets and liabilities by contract and obligation. Interpret movements with the underlying promises, billing terms, performance, modifications, refunds, and collectability rather than treating growth as a universal demand or backlog signal (Prakash & Sinha, 2013).
Cash application links a bank settlement to the correct receivable, contract liability, tax, refund, or other purpose. It records the bank reference, customer, invoice or balance, date, amount, currency, resolver, and any unapplied remainder. Cash is not “collected revenue.”
Receivable aging and days sales outstanding (DSO) can monitor collection behavior, but both are management measures whose formulas and populations must be published. Working-capital research supports a trade-off rather than a universal DSO target (Baños-Caballero et al., 2014).
Conclusion
The map now separates contract, performance obligation, invoice, receivable, payment, cost transaction, forecast, and close period, with a source, owner, effective time, and correction route for each.
Chapter glossary
- Revenue: Income recognized from transferring promised goods or services to customers in ordinary activities under the applicable reporting framework.
- Bookings: Customer commitments admitted under the company's written management policy; they are neither recognized revenue nor an accounting-revenue category defined by ASC 606 or IFRS 15.
- Contract asset: A conditional right to consideration arising from performance that occurred before the right became unconditional.
- Receivable: An unconditional right to consideration for which only the passage of time is required before payment is due; the related balance is commonly called accounts receivable.
- Contract liability: An obligation to transfer goods or services for which consideration has been received or is due before the related transfer.
- Cash application: Assignment of a bank settlement to the correct receivable, contract liability, tax, refund, deposit, or other purpose.
- Days sales outstanding (DSO): A management measure of receivable collection timing whose formula and eligible population must be published.