ACC/421 Intermediate Financial Accounting I Week 2 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/421 Week 2. 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 against your first feedback
By the second position there is one graded artifact behind you and one set of instructor comments, and that changes how a rubric should be read. Print the current rubric, set the earlier feedback beside it, and draw a line from each comment to the row it would strike this time. Remarks about support, organization, or mechanics almost always map onto a standing row, and closing them is the least expensive improvement available to you.
Then read each row for its hidden second test. Rows in a business class frequently bundle two obligations into one sentence: accuracy and interpretation, breadth and depth, or content and format. Split any bundled row into two lines in your own checklist and mark them separately, because a draft that lands the calculation and skips the meaning has still answered half of that row. Where the rubric names a quantity, such as a count of examples or of statement items, record the quantity as a number and count the draft against it at the end rather than trusting a visual scan.
Close the pass by pricing the rows. Multiply each row's weight by the effort it will take you, rank the results, and sequence the week so the heaviest rows get your first working session rather than your last. Where two rows overlap heavily, decide in advance which section carries the evidence and which one refers back to it, so you are not writing the same analysis twice under two headings and losing space you need elsewhere.
Produce the Week 2 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 the reasoning as the statements start to connect
Once the opening orientation is behind you, the reasoning that pays off next is the one that stops treating the income statement and the balance sheet as two separate documents and starts treating them as one articulated system. It is worth rehearsing deliberately, because every later measurement topic in this catalog description eventually lands on both statements at the same time.
Set the drill up with a trial balance from the assigned reading and a single adjustment you choose yourself, such as wages earned but unpaid at period end. Trace it in four moves. Move one: name the expense and the period it belongs to, and say which principle put it there. Move two: name the obligation that appears in the same instant and confirm the accounting equation still holds. Move three: carry the income effect into retained earnings and check that the balance sheet you produce is the one your income statement implies. Move four: say in a sentence how a lender reading both statements sees the company differently before and after the adjustment. If move four is hard to write, the adjustment was recorded but not understood.
Layer a classification question on top once the arithmetic settles. Ask whether an item belongs in operating or non-operating results, whether an asset or obligation is current or non-current, and whether the presentation you chose helps or hides a reader's view of what is likely to persist. Classification choices are scored as reasoning rather than as formatting, so write the reason beside the choice. Where a posted item leaves presentation to your discretion, saying plainly why you arranged it one way instead of another usually matters more than the arrangement itself.
Bringing real financial statements into the draft
Once the statements are connected in your head, the strongest evidence available in this subject is a published set of financial statements and the notes that travel with them. A public company's annual report supplies a balance sheet, an income statement, and a significant accounting policies note written by people who had to defend every choice, which is exactly the sort of evidence a business rubric prefers to a restatement of the textbook.
Use them carefully. A filing is a primary document, so cite the company, the report, the fiscal year, and the note or statement line you actually read rather than the document as a whole. Keep three roles separate: authoritative guidance says what is required, the filing shows one company applying it, and the course text explains the mechanics. Blending all three into one undifferentiated citation is the common source error at this stage and it makes an otherwise sound paragraph look secondhand. Peer-reviewed accounting research belongs in the mix when an item asks about effects or disagreement rather than about mechanics.
A paragraph changes shape when a filing is involved. State the requirement first, show the company's disclosure second, then explain what a specific reader gains from that disclosure, whether that reader is a lender, an investor, or a manager inside the business. Name the reader. Business rubrics reward analysis addressed to a decision maker over analysis addressed to nobody. Before committing to a company, check the posted directions for limits on selection, industry, or report age, since those constraints are set per item and are easy to skip past.
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 3. Reconcile the class grade and update the next action.
Three traps in the second position and how to clear them
The first trap is the unreconciled table. A figure appears one way in a schedule and another way in the paragraph discussing it, usually because the schedule was rebuilt and the prose was not. The fix is to write figures into prose only after the schedule is final, then run a dedicated number pass in which you read only the numbers, in order, and match each one back to its source cell.
The second trap is analysis with no reader. A paragraph explains that a balance moved without ever saying who cares or what they would do differently. The fix is a two-line habit: after each analytical claim, add a sentence naming the decision maker and a sentence naming the decision. It costs almost no length and it converts description into the applied reasoning that most rows are really scoring.
The third trap is inherited feedback treated as history rather than as instruction, so the same deduction repeats. The fix is to turn each comment into a checklist line written in your own words, park that checklist at the top of your working file, and clear it before the draft goes out. Where a comment was unclear, ask the instructor for a specific example instead of guessing, because one misread comment repeated across a whole class costs far more than one question.