D217 Accounting Information Systems (AIS) is the Western Governors University course that shows how accounting data is captured, processed, controlled and reported by information systems.
WGU's program guide emphasizes the accountant's role in management and financial reporting systems. Topics include transaction cycles and related IT controls, data management, enterprise resource planning (ERP) and e-commerce systems, systems development and acquisition, documentation and IT auditing.
The course carries three competency units in the B.S. Accounting. Its prerequisites are D103 Intermediate Accounting I and D104 Intermediate Accounting II, and it is itself a prerequisite for D215 Auditing.
Course at a Glance
| Item | Details |
|---|---|
| University | Western Governors University (WGU) |
| Course code | D217 |
| Level | Undergraduate (B.S. Accounting) |
| Competency units | 3 |
| Prerequisites | D103 Intermediate Accounting I, D104 Intermediate Accounting II |
| Typical work | Questions on cycles and controls; documentation such as flowcharts |
What D217 Covers
| Competency (summarized) | What it means in practice |
|---|---|
| Analyze system components and transaction processes | How inputs, processing, storage and outputs fit together |
| Explain revenue, expenditure and general ledger cycles | The steps, documents and controls in each cycle |
| Explain databases, ERP and e-commerce systems | How integrated systems support planning and operations |
| Describe the accountant's role in systems development | Requirements, testing and controls when systems are built or bought |
| Explain computer controls and IT auditing | General and application controls that protect reporting integrity |
Key Concepts Explained
Transaction Cycles
Most business events fall into a few cycles. The revenue cycle runs from customer order to cash receipt; the expenditure cycle from purchase requisition to payment; the general ledger cycle collects everything into the financial statements.
Example, revenue cycle: sales order entry, credit approval, picking and shipping, billing, then cash collection. Each step has a document (sales order, packing slip, invoice, remittance advice) and a risk, such as shipping to a customer who cannot pay. Credit approval before shipping is the matching control.
Segregation of Duties
No single person should authorize a transaction, record it and hold the related asset. If the same clerk can approve new suppliers and process payments, fictitious supplier fraud becomes easy.
General Versus Application Controls
General controls cover the IT environment as a whole: access security, change management, backups. Application controls work inside a specific process: input validation, batch totals, sequence checks.
Typical Assignments and How to Approach Them
| Task type | What it tests | How to approach it |
|---|---|---|
| Cycle scenario | Steps, documents and risks | Walk through the cycle in order and note one risk per step |
| Control weakness question | Matching controls to risks | Name the risk, then the preventive or detective control |
| Documentation | Flowcharts or diagrams | Use standard symbols and keep one process per chart |
| ERP or database question | Integrated systems | Explain the benefit and the control concern together |
Preventive, Detective and Corrective Controls
Controls are often classified by when they act. Questions frequently ask you to suggest one of each type for a given risk.
| Type | Purpose | Example in purchasing |
|---|---|---|
| Preventive | Stop errors before they happen | Only approved suppliers can be paid |
| Detective | Find errors after they happen | Three-way match of order, receipt and invoice |
| Corrective | Fix errors and prevent repeats | Recover duplicate payments and update the supplier file |
Linking each control to the specific risk it addresses is what turns a list into an answer.
Where Students Get Stuck
- Cycle steps out of order. Learn each cycle as a sequence with its documents.
- Vague controls. "Better security" is not a control; "role-based access to the supplier file" is.
- Flowchart symbols. Practice a few simple charts before tackling complex ones.
- Forgetting the accountant's role. Many questions ask what the accountant contributes, not the IT team.
Study Tips for D217
- Draw each cycle on one page with steps, documents, risks and controls.
- Think of a business you know and trace one sale and one purchase through its systems.
- Keep your control examples; you will reuse them in D215 Auditing.
- Learn segregation of duties as authorize, record, custody, and test it on every scenario.
How We Help with D217
Send the task instructions, rubric and any feedback. An accounting tutor explains cycles and controls, prepares a model flowchart or control matrix on a sample case, or reviews your work for accuracy and clarity.
GradeEssays is independent of Western Governors University. Our material is written from scratch as study and reference support; complete and submit your own work under WGU's academic integrity policy. Revisions within the scope of your original request are free.
Understand the Systems Behind the Numbers
Share your D217 instructions or practice questions. A tutor explains cycles and controls with worked examples.
Start My D217 HelpFree revisions · Full refund if late · Written from scratch for your order
Frequently Asked Questions
The program guide lists D103 Intermediate Accounting I and D104 Intermediate Accounting II.
Accounting Information Systems: the people, procedures, data and technology used to capture, process and report accounting information.
The competencies name the revenue, expenditure and general ledger cycles, along with their processes and controls.
No. It focuses on how systems support accounting, the controls around them and the accountant's role, not on writing code.
Auditors rely on understanding a client's systems and IT controls, so AIS is a listed prerequisite for D215 Auditing.
No. We tutor, explain and review so you can complete it yourself.