WGU D561: Information Systems for Accounting and Control

What D561 is and where it fits in your accounting degree

WGU D561: Information Systems for Accounting and Control is a graduate course in the School of Business, part of Western Governors University's Master of Science in Accounting. It sits at the intersection of two skills employers keep asking for at once: understanding how accounting data actually moves through modern software, and knowing how to protect that data with sound internal controls. If your background is heavier on debits and credits than on databases and IT risk, this is the course that closes that gap.

Direct answer: To pass D561, learn how each transaction cycle flows through an accounting information system, master the vocabulary of general and application controls, and practice applying control frameworks to realistic business scenarios rather than memorizing definitions in isolation. Work steadily through the course material, use the pre-assessment to find weak spots, and you will be ready.

Most students meet D561 as working professionals: staff accountants, auditors, and analysts who already know financial reporting but want the systems-and-controls depth that graduate accounting and the CPA path expect. The course matters because accounting no longer happens in ledgers by hand. It happens inside enterprise systems, and the accountant is increasingly the person who designs, evaluates, and audits the controls around those systems. That is exactly the skill this course builds.

Because it is a business systems course rather than a computational one, D561 rewards conceptual clarity over calculation. You are not solving long math problems. You are explaining how a process works, spotting where it could fail, and recommending the control that fixes it.

What the D561 assessment covers

The course centers on how accounting data is captured, processed, stored, and controlled. Always confirm the current competencies on your official course page, since WGU updates courses over time; the subject matter of an accounting information systems and control course consistently spans these areas:

• Transaction cycles — how the revenue, expenditure, and general ledger/financial reporting cycles capture and process economic events.
• Internal control concepts — control objectives, and widely used frameworks such as COSO's internal control and enterprise risk models.
• IT general controls vs. application controls — access controls, change management, and controls built into the software that processes each transaction.
• Data management and databases — how relational data is stored, related, and retrieved, and why data integrity matters to reporting.
• Enterprise systems — the role of ERP platforms and integrated systems in unifying accounting data.
• Systems documentation — reading and interpreting flowcharts and data flow diagrams that map a process.
• Risk, security, and IT auditing — identifying threats to financial data and evaluating whether controls are designed and operating effectively.

How hard is D561, and how long will it take?

Difficulty here depends heavily on your starting point. Students who come in with auditing, internal control, or IT experience often find the material familiar and move quickly. Students whose experience is purely in bookkeeping or financial statement preparation usually need more time to get comfortable with control terminology and systems diagrams, because the vocabulary is dense and the frameworks are new.

The honest takeaway many students share about courses like this is that the concepts are not intellectually brutal, but they are broad. Success comes less from raw difficulty and more from covering the full breadth of terms and being able to apply them to a scenario. Give yourself a few focused weeks rather than a single cramming weekend, and treat the pre-assessment as your progress gauge: when you can pass it comfortably and explain your wrong answers, you are ready to schedule the real thing. If accounting systems concepts are new to you, building the underlying financial base first through a course like D196 Principles of Financial and Managerial Accounting makes D561 noticeably smoother.

A study plan that works for accounting information systems

Passive reading is the slowest path through a terminology-heavy course. These tactics move faster:

• Active recall over rereading. After each module, close the material and write out, from memory, what a control does, where it lives in a process, and what risk it addresses. Check, correct, repeat. Retrieving the answer is what makes it stick.
• Spaced repetition for the vocabulary. D561 has a lot of terms: preventive vs. detective vs. corrective controls, general vs. application controls, segregation of duties, and more. Put these on a flashcard system you review on a spacing schedule so they stay fresh through exam day rather than fading after one session.
• Practice testing with scenarios. The most valuable practice is not "define X" but "here is a process; what could go wrong and which control prevents it?" Turn every concept into a mini case. Objective assessments often present scenario questions, so rehearse the reasoning, not just the label.
• Draw the cycles. Sketch the revenue and expenditure cycles by hand and mark where each control sits. If you can redraw the flow from memory and narrate the risks at each step, you understand it at the level the exam expects.
• Connect it to security. Because IT controls overlap with information security fundamentals, students find that reinforcing that side of the material pays off; a security-focused guide like D430 Fundamentals of Information Security covers the access-control and threat concepts D561 leans on.

Mistakes that trip students up in D561

• Memorizing definitions without application. Knowing that "segregation of duties" means splitting responsibilities is not enough; you need to say which duties, in which cycle, and why combining them creates risk.
• Blurring the control categories. Confusing general controls with application controls, or preventive with detective controls, is one of the most common ways points slip away. Keep those buckets crisp.
• Skipping the diagrams. Flowcharts and data flow diagrams feel optional until a question hands you one and asks what a symbol represents. Learn to read them early.
• Underestimating breadth. Because no single topic is hard, students sometimes study narrowly and get surprised by how much ground the assessment covers. Survey everything, then deepen.
• Rushing to schedule. Sitting the assessment before you can pass the pre-assessment cleanly is the fastest way to earn an avoidable retake.

D561 readiness checklist

Before you schedule, work through this self-check. You are ready when you can honestly answer yes to most of these:

• Can you trace the revenue, expenditure, and general ledger cycles from start to finish and name the key documents in each?
• Can you distinguish IT general controls from application controls with an example of each?
• Can you classify a control as preventive, detective, or corrective and justify the label?
• Can you explain segregation of duties and identify a scenario where it is violated?
• Can you describe how a control framework such as COSO organizes internal control?
• Can you read a basic flowchart or data flow diagram and explain what the process does?
• Can you name common threats to financial data and the controls that mitigate them?
• Can you explain the accountant's role in evaluating or auditing an accounting information system?
• Are you consistently passing the pre-assessment and able to explain why the wrong choices are wrong?

D561 questions students ask most

Is D561 an objective assessment or a performance task?

D561 is assessed through a proctored objective assessment, an exam you schedule once you and your course instructor agree you are prepared. Always confirm the current format on your official course page, since WGU updates courses over time. Whichever format applies, the study approach is the same: understand the concepts well enough to apply them.

How many attempts do I get?

WGU limits objective assessments to a set number of attempts, and a required pre-assessment gates your first sitting. The practical rule is simple: do not schedule until the pre-assessment score and your own confidence both say you are ready, so your first attempt is your best attempt.

Do I need a technical or IT background to pass?

No. D561 is written for accountants, not programmers. You will learn systems and control concepts from the ground up. A background in auditing or IT can speed things along, but it is not a prerequisite for success.

How does D561 relate to my other accounting courses?

It complements the financial and tax side of your program. A strong grasp of transactions from courses like C237 Taxation I and core accounting helps, because you already understand the data these systems process; D561 adds the controls-and-systems layer on top.

What is the single best way to study for it?

Turn every concept into a scenario. For each control or process, ask what could go wrong and what fixes it, then rehearse that reasoning out loud. Scenario-based active recall consistently beats rereading for a course built on application.

Where can I find more WGU study guides?

Browse the full School of Business guide hub for related accounting and business courses, or see every subject in the complete WGU course guide index. For the official program details, check the WGU Master of Accounting program page.