ACC/290 Principles of Accounting I Week 4 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/290 Week 4. 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 late-term deliverable
Late rubric rows tend to bundle. One criterion can quietly hold three separate tests, such as whether the required schedules are all present, whether items are classified correctly inside each of them, and whether the results are interpreted for a reader. Split every bundled row into its component tests on paper before drafting and treat each component as its own line to satisfy, since partial credit inside a bundled row is normally awarded on exactly those components.
Look for cumulative language. A criterion referring to the project, to earlier work, or to consistency with previous submissions is instructing the grader to open a prior file, which turns agreement across Weeks into a scored property rather than a courtesy. Reconcile both the figures and the framing between the pieces before submitting, and where something changed for a defensible reason, say so in one line rather than letting the difference read as an error nobody caught.
Then sort the remaining rows by what they demand. Rows worded around accuracy are answered by recomputation, so book time to rebuild the numbers independently instead of re-reading them and recognizing them. Rows worded around explanation are answered by prose, and prose has to live somewhere specific rather than being distributed as tone. Rows covering headings, currency notation, table titles, and file format are answered in a final mechanical pass. The posted rubric stays the only authority on which of these actually apply.
Produce the Week 4 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.
Assembling and reading a statement set late in the term
When a late-term deliverable calls for a full set of financial statements, the order of assembly is not a preference. Each statement feeds the next, and most breakages come from building them in parallel. Work from an adjusted trial balance. Suppose it shows service revenue of $42,000 against wages expense of $18,500, rent expense of $7,200, supplies expense of $1,300, and depreciation expense of $2,000. Expenses total $29,000, so income for the period is $13,000. Carry that into the equity statement: beginning capital of $25,000, plus the $13,000 earned, less $4,000 of owner withdrawals, produces ending capital of $34,000.
Only now build the balance sheet, and lift the equity figure from the statement just finished rather than from the trial balance. Cash of $12,400, receivables of $9,600, supplies of $700, and equipment of $26,000 shown net of $6,000 accumulated depreciation give total assets of $42,700. Accounts payable of $3,700, wages payable of $1,200, and a note payable of $3,800 give total liabilities of $8,700. Add the $34,000 of ending capital and the statement closes at $42,700 on both sides.
Interpretation is a separate act of work, not a restatement of the arithmetic. Income of $13,000 on revenue of $42,000 is a margin near 31 percent, which speaks to pricing and cost control at the same time. Current assets of $22,700 against current obligations of $4,900 cover the near-term claims several times over, which sounds comfortable until the composition gets examined: receivables of $9,600 make up more than two fifths of that cushion, so a share of the comfort depends on collection rather than on money already in hand. Writing the second sentence, the one about composition instead of size, is what a late-term row means when it asks for financial data to be used in a decision.
Source work when the deliverable interprets results
Interpretation needs a benchmark, and a benchmark needs an origin. A ratio described as healthy, strong, or concerning without a reference point is an opinion, and it gets graded as one. Three benchmarks are usually defensible: the same enterprise in a prior period taken from the same filing, a published industry or sector figure from an identified data source, or a threshold the assigned text states outright. Whichever is used, put its origin in the same sentence that uses it so nobody has to guess where a comparison came from.
Scale discipline matters more here than anywhere else in the term. Filings report in full dollars, in thousands, and in millions, and the notation is easy to drop when figures are transcribed into a comparison table. Record the scale beside every borrowed number and state the fiscal year and the statement it came from, because a comparison built across mismatched periods or mismatched units is wrong in a way that invalidates the whole paragraph rather than a single line of it.
Build the comparison table before writing any prose, with a column recording the source of every borrowed figure, then write each sentence from a row of that table. If the required format leaves no room for a source column, move those citations into the text while drafting rather than afterwards. Check the permitted list first, since a section restricted to the course text expects benchmarks drawn from the ranges that text supplies, and an outside industry figure can cost a source row even when the analysis wrapped around it is sound.
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 5. Reconcile the class grade and update the next action.
Three late-term traps and how to clear them
The first trap is carrying the wrong equity figure. The trial balance shows beginning capital, the balance sheet needs ending capital, and the two sit close enough together that the older number gets copied under deadline pressure. The result is a balance sheet out by exactly the period's income less withdrawals, which is a distinctive and very visible failure. The fix is procedural rather than clever: assemble in order, and copy the ending figure from the completed equity statement instead of retyping anything from the trial balance.
The second trap is a mismatched statement header. An income statement and an equity statement cover a span of time, while a balance sheet reports a single instant, so a balance sheet headed for the period ended is describing something that cannot exist. The fix is a short header pass across the whole set, confirming the enterprise name, the statement name, and the date line on each one. Headers are read first and they are the cheapest points in the entire deliverable to protect.
The third trap is computing ratios from unadjusted figures, or reporting them with no arithmetic shown. Either version leaves a grader unable to verify a number that is driving the conclusion. The fix is to compute only after every adjustment is posted, present the numerator and denominator by their statement line names rather than as bare figures, and attach one sourced point of comparison to each ratio that carries weight in the recommendation.