ACC/422 Intermediate Financial Accounting II Week 1 guide
A source-bounded manual for the real registered Week: capture its identity, map its rubric, complete the permitted work, verify delivery, and carry feedback forward.
An official Phoenix program page establishes a 5-Week class context for this mapped code. It does not publish a universal topic or assessment for ACC/422 Week 1. The registered classroom is authoritative for the exact work.
Capture the live Week identity
Record the exact Week heading, assessment or discussion title, type, directions, point value or weight, rubric version, template, permitted sources and tools, deadline and time zone, file type, and submission location. Preserve any announcement that changes a requirement. Do not rely on a prior section or the public program duration for assignment identity.
Separate every obligation into its own row: initial discussion, peer replies, paper, case, calculation, quiz, presentation, project step, laboratory, simulation, group dependency, practicum document, clinical task, or exam-preparation block. One Week position can contain several distinct completion tests.
Mark prerequisite work before production begins. Required reading, data access, site or preceptor confirmation, group input, instructor approval, template download, or earlier project feedback can determine whether the Week is ready to draft.
Convert the rubric into acceptance tests
Rewrite every row as a yes-or-no test. Identify the action verb, required concept or decision, evidence, example or application, calculation or visual, destination, and top-band condition. Highlight all, each, compare, analyze, evaluate, and justify because each word changes what complete means.
Directions and rubric remain separate contracts. Directions control scenario, audience, length, format, source limits, tools, and submission. The rubric controls scoring. If they conflict, pause and obtain clarification rather than silently choosing the easier interpretation.
Build a criterion-to-section map before writing. Every rubric row needs a visible home. Every major paragraph, table, slide, calculation, or appendix should earn its space by satisfying a named requirement.
Reading the rubric row by row on a first submission
The first rubric of a term is the one most often skimmed, because nothing has gone wrong yet. Read it in three passes instead. The first pass is structural: count the rows, note how credit or weight is spread across them, and see which row carries the most. In accounting coursework that heavy row is usually analysis or application rather than computation, which means a page of flawless arithmetic can still land mid-band if the interpretation paragraph is thin.
The second pass is verbal. Underline the verb in each row and decide what artifact would satisfy it. Calculate asks for a number with a visible method. Compare asks for at least two objects and a stated basis of comparison. Justify asks for a reason tied to a standard or a stated criterion, not a preference. Evaluate asks for a judgment plus the evidence that produced it. If a row says analyze the effect and your draft only reports the effect, that row is incomplete no matter how correct the figure is.
The third pass is the band comparison. Put the top band and the band beneath it side by side and write down the single difference between them in your own words. Rubrics usually separate those two bands with one added demand: depth, a second example, a stated limitation, a link to authoritative literature, or a recommendation. Naming that difference in one sentence turns a vague quality target into a concrete thing to add.
Close the pass by giving every row an address in the draft: a heading, a paragraph, a table, or an appendix. A row with no address is the row you lose. Do this before writing, while the outline is still cheap to change, and keep the map beside the draft as you produce.
Produce the Week 1 work
Begin with the purpose, answer, or decision the prompt actually requires. Organize by rubric logic, not by the order ideas occurred. Connect claims to evidence and explain why that evidence matters in the specific scenario. Label assumptions and keep facts, interpretation, and recommendation distinct.
For discussions, answer the prompt directly, add permitted evidence, apply it, and end with a question or implication that supports substantive peer exchange. For papers and presentations, use headings or slide messages that expose the argument. For calculations, show inputs, units, method, intermediate result, final result, rounding rule, and interpretation.
Clinical, practicum, laboratory, simulation, group, and authenticated actions remain student-performed. Support can explain concepts, help plan de-identified written components, review calculations, rehearse a presentation, or prepare for a proctored exam. It cannot fabricate experience, signatures, attendance, patient facts, or assessment performance.
Working a measurement decision at the opening of the run
Week 1 sits at the front of a five-week run, so the reasoning goal is orientation rather than mastery. The catalog description for this course lists property, plant and equipment, intangible assets, current liabilities and contingencies, long-term liabilities, contributed capital, and retained earnings among its territories. Which of those the opening Week actually names is a registered-classroom fact, not something this page can supply. What does not change is the habit an opening Week rewards, and that habit is worth rehearsing now: every figure you report should be traceable to a recognition decision, a measurement basis, and a period.
Rehearse it on a capitalization question, the cleanest entry point this course's own territory offers. Suppose an entity buys equipment and, in the same set of invoices, pays freight, installation labor, a test run of the machine, and a separate one-year service contract. The work is not arithmetic first. It is an ordered set of questions: which outlays were necessary to bring the asset to the condition and location intended for use, which outlays purchase service in a future period, and which are simply costs of the period. Freight, installation, and testing generally attach to the asset. The service contract buys next year's maintenance and belongs elsewhere. Write the reasoning in that order and the number arrives last, already defended.
Then take the step that separates a passing paragraph from a strong one: say what the decision changes. Capitalizing rather than expensing moves cost off this period's income statement and onto the balance sheet, where it is released through depreciation across the asset's useful life. That single sentence about consequence is often the whole difference between reporting a treatment and analyzing it, and an opening Week is the cheapest place to build the reflex.
What counts as a source in intermediate accounting
Accounting has an unusually clear authority hierarchy, and using it correctly is what separates a sourced argument from an asserted one. At the top sits the authoritative literature itself, the FASB Accounting Standards Codification, which is what actually governs treatment under United States generally accepted accounting principles. Beneath that sit the standard setters' own explanatory materials and, where an assignment reaches internationally, IASB pronouncements. Company filings retrieved from EDGAR, especially the notes to audited financial statements, are primary evidence of how a real entity applied a rule. Peer-reviewed accounting journals supply research. Professional publications and firm guides are useful commentary but are not the standard, and your assigned intermediate accounting text explains the standard rather than being it.
Sources enter a draft in a fixed order. State the treatment, cite the authority that requires it, then apply it to the scenario in front of you. A paragraph that cites nothing is an opinion, and a paragraph that is only a citation is a copy. Keep a small ledger while you read, one line per source, recording the claim it supports, the exact locator, whether you quoted or paraphrased, and where it will land in the draft. The permitted list is set by the current directions, so confirm there before assuming any of these categories are allowed.
Verify quality and delivery
Run a requirement pass first: every direction and rubric row is present. Run a reasoning pass: evidence fits the claim, analysis fits the prompt, calculations reproduce, and recommendations follow. Run a consistency pass across prose, tables, figures, slides, appendices, citations, and references.
Finish with the delivery pass: current template, citation style, accessibility, filename, file type, export, links, and rendered upload. Open the final file after export. A correct source document can still fail when a chart clips, a table shifts, a font disappears, or the wrong version uploads.
After submission, record the posted result and feedback. Classify the miss, revise the smallest complete unit if revision is allowed, trace dependent changes, and write one prevention rule for Week 2. Reconcile the class grade and update the next action.
Three ways an opening Week goes wrong
The first pitfall is treating the syllabus as the assignment. A syllabus line names a deliverable; the classroom shell holds the directions, the rubric version, the template, and any announcement that has already amended one of them. Students who draft from the syllabus alone routinely produce work that answers a slightly older prompt. The fix costs five minutes: open the shell, copy the live directions and rubric into your working document, and date that copy so you can tell later whether anything changed.
The second pitfall is answering with definitions. An opening Week often invites a conceptual prompt, and it is tempting to explain what a term means and stop there. Definitions are the setup, not the answer. The fix is mechanical: after each definition paragraph, add a sentence that begins with the scenario in the prompt and shows the concept doing work inside it. If you cannot write that sentence, you have not yet answered.
The third pitfall is a formatting debt taken on in Week 1 and repaid every week after. Citation style, heading levels, table captions, and file naming get improvised under first-week pressure and then copied forward for the rest of the run. The fix is to build the template correctly once, now, with the required style, a heading skeleton, and a reference list already formatted, then reuse that file rather than the last draft for every remaining submission.