D561 Information Systems for Accounting and Control, catalog number ACCT 6345, is a three-CU graduate course giving an overview of the information systems and technology used in accounting, including networks, hardware and data. Where a transaction cycles course looks at how a business process flows, this one looks underneath it at the infrastructure the process runs on, and at the controls that live at that layer rather than in the workflow.
The stack an accounting system actually sits on
Accountants tend to experience a system as a screen. Underneath that screen is a stack of components, each with its own failure modes and its own controls, and a graduate course expects you to be able to talk about them without either hand-waving or pretending to be an engineer.
At the bottom is infrastructure: servers or cloud capacity, storage, and the networks connecting them. These determine availability, which is an accounting concern the moment a period-end close depends on a system being up. Above that sits the database, which is where the data actually lives and where integrity constraints either exist or do not. Above that is the application, with its own access controls and its configured business rules. Around all of it sits identity management, which decides who can do what, and backup and recovery, which decides what happens when something fails.
The accountant's stake in each layer is specific. Data integrity is an accounting concern because a report is only as good as the records behind it. Access control is an accounting concern because segregation of duties is enforced at the identity layer in any modern system. Availability is an accounting concern because reporting obligations have dates attached. Change management is an accounting concern because an undocumented change to a configured business rule silently changes the numbers.
Cloud arrangements shift where those controls live without removing any of them. Responsibility is shared between provider and customer, and the boundary is set by the service model, so the first question about any hosted system is which controls the organization still owns.
Planning a technology evaluation for an accounting audience
Aspects in your Course of Study are scored independently and each needs a 2. Technology aspects in an accounting course have a particular risk: writing at the wrong altitude, either too vague to demonstrate understanding or so detailed that the accounting relevance disappears.
Worked example with an altitude rule. Suppose your rubric lists five scored aspects and the directions ask for roughly 2,000 words. Reserve 140 for the system description, leaving 1,860, or 372 per aspect. Now impose the altitude rule: within each aspect, spend no more than 120 words on how the technology works and at least 250 on what it means for accounting records, controls or reporting. That ratio keeps a technology discussion anchored to the reason an accountant is being asked about it.
Where an aspect concerns security or data governance, expect to need the full 372 and take the difference from a hardware or network aspect, where the accounting consequence is usually stated more briefly.
Evaluating the technology layer by layer
This layout works for tasks asking you to assess a system's technology environment. Task directions take precedence where they specify a format.
| Layer | What to establish | The accounting consequence |
|---|---|---|
| Network | Connectivity, segmentation, remote access arrangements | Whether transaction data can be intercepted or altered in transit |
| Hardware and hosting | On premises, hosted or cloud, and who operates it | Which controls the organization still owns and which the provider holds |
| Database | Structure, integrity constraints, direct access privileges | Whether records can be changed outside the application's audit trail |
| Application | Configured rules, interfaces, automated postings | Whether the numbers a report shows follow the rules management believes are set |
| Identity and access | Provisioning, privileged accounts, review of entitlements | Where segregation of duties is actually enforced in practice |
| Change management | How changes are requested, tested, approved and released | Whether a change to a posting rule could reach production unreviewed |
| Backup and recovery | Frequency, retention, restoration testing | Whether the accounting records survive an incident and can be produced |
| Logging and monitoring | What is recorded and who reviews it | Whether an unauthorized change would ever be noticed |
Privileged access is the item to examine hardest in any scenario. An administrator who can modify data directly in the database bypasses every control designed in the application above it, and a system evaluation that describes application controls without asking who can go around them has assessed the wrong layer.
Writing precisely about technology and its controls
Precision matters here because vague technology writing is easy to produce and impossible to evaluate.
- Name what a control actually does rather than the category it belongs to. Encryption in transit and encryption at rest protect against different threats.
- State whether a control is preventive, detective or corrective, and whether it is automated or manual, since both change the assurance it provides.
- Identify the responsible party for every control in a hosted arrangement, since shared responsibility means some controls are not yours to test.
- Where you rely on a provider's assurance report, say what it covered and what period, because such reports are scoped and dated.
- Cite standards, frameworks and course material in APA paraphrase, keeping quotation minimal because submissions are similarity-checked.
Interfaces between systems are the place where accounting data most often goes missing, and they are underexamined in student submissions because they are invisible from any single screen. When a subsidiary ledger feeds a general ledger, or a payroll platform feeds an accounting system, something has to guarantee that everything sent arrived, that nothing arrived twice, and that a failed transfer is detected rather than silently dropped. Ask what reconciliation runs after each transfer, who reviews the exception report and what happens when the counts disagree. An interface with no reconciliation is a gap in the accounting records regardless of how well controlled either system is on its own.
Data governance deserves its own treatment in a graduate answer. Who owns a data element, who may change it, how master data is maintained and how records are retained and disposed of are all accounting questions in systems terms, and they are where reporting inconsistencies usually originate. A customer record maintained in two systems with no authoritative source produces reports that disagree, and no amount of application control fixes a governance gap.
What a Competent systems evaluation demonstrates
Each aspect is scored on its own against the competency standard, and the standard is whether an accountant could use the evaluation to decide how much to trust the numbers.
- Each technology layer is addressed with its accounting consequence stated, not just its technical description.
- Privileged access and the ability to bypass application controls are examined explicitly.
- Controls are classified by type and by whether they are automated or manual.
- Responsibility boundaries in hosted arrangements are identified.
- Recommendations are proportionate to the risk and account for what they cost.
WGU records Competent or Not Competent, with no letter grade and no ordinary grade point average, and performance assessment work can be revised and resubmitted with no penalty. The cost of a return is calendar time inside a six-month flat-rate term. Where a proctored objective assessment is part of this course, our support is preparation only: control classification drills, architecture review and an honest readiness verdict. We never sit assessments and never ask for portal credentials.
Six mistakes in an accounting systems course
- Writing a technology essay with no accounting consequence. The reason an accountant is asked is what the aspect is scoring.
- Ignoring privileged access. Application controls are irrelevant to someone who can edit the database directly.
- Assuming a cloud provider handles everything. Responsibility is shared and the boundary depends on the service model.
- Treating backups as recovery. An untested backup is a hope, and restoration testing is the control that matters.
- Naming control categories instead of controls. Access control is a category; quarterly review of privileged accounts by the process owner is a control.
- Overlooking change management. A configured posting rule changed without review alters reported numbers with no visible trail.
Support that keeps the accounting question in view
Send the rubric, the directions and the system or scenario. The evaluation comes back layer by layer with the accounting consequence stated for each, privileged access examined explicitly, controls classified by type and automation, responsibility boundaries identified for anything hosted, data governance addressed and recommendations proportionate to the risk they reduce. The walkthrough covers how to interrogate a system you have not seen before, which is the transferable skill.
D561 sits above D217 Accounting Information Systems, which covers the process layer, and connects to D552 Data Analytics for Accountants I, where the quality of the data these systems produce becomes the working material.
Questions students ask about D561
Is D561 the same as ACCT 6345?
Do I need a technical background?
How is this different from the accounting information systems course?
System evaluation due?
Send the scenario and the rubric. The evaluation runs layer by layer, with the accounting consequence stated for every technical point.
Where D561 sits in WGU's programs
The July 2026 catalog places this code in 2 current WGU programs. Open a program page for the complete standard path and term positions. The live Degree Plan remains authoritative after transfer credit, substitutions, and mentor planning.
The assessments, one by one
The public catalog does not publish this course's PA/OA identity or task count. WGU Tutors publishes at most one PA manual per course and only from a WGU-controlled public rubric. Until that source exists, PA help begins from the student's real Course of Study and OA support remains preparation only.