D217: Accounting Information Systems

D217, often shortened to "AIS" by students and faculty alike, is where the Accounting major meets information technology. It's built around the reality that modern accountants don't just record numbers — they operate, control, and audit the systems that generate those numbers.

What D217 covers

The course covers transaction cycles (how a sale, purchase, or payroll event flows through a company's systems) and the IT controls attached to each cycle, data management practices, and how enterprise resource planning (ERP) and e-commerce systems have reshaped financial reporting.

It also addresses systems development and acquisition — how a company selects or builds an accounting system — documentation standards for accounting processes, and IT auditing, which previews the systems-focused portion of the later Auditing course.

The D217 performance assessment

D217's performance assessment typically asks you to map a transaction cycle for a given company, identify the IT controls that should exist at each step (and any gaps), and document the system using standard flowcharting or narrative documentation techniques — sometimes paired with a short IT-audit risk assessment.

Key topics in D217

• Transaction cycles and their associated IT controls
• Data management in accounting systems
• ERP and e-commerce systems
• Systems development and acquisition
• Documentation standards
• IT auditing fundamentals

Writing tips for D217

Follow the task instructions and rubric line by line

WGU performance assessments for D217 are graded against a fixed rubric, not classroom "vibes" — every rubric line has to be visibly addressed, usually with a labeled heading that mirrors the rubric language. Skipping a rubric point because it seems minor is the single most common reason a competent task submission comes back "Not Yet Competent" for revision.

Use real, specific numbers and named scenarios, not generalities

WGU evaluators are trained to distinguish genuine analysis from a paraphrased textbook summary. Ground your submission in the specific company, dataset, or scenario the task provides (or that you're asked to select), and show your work — calculations, journal entries, or supporting schedules — rather than only stating a conclusion.

Because WGU is self-paced, don't let "no deadline pressure" become no submission

There's no weekly due date forcing progress, which means procrastination costs more at WGU than at a traditional term-based school — a stalled task can quietly eat weeks of a term. Treat your own target date for each D217 assessment as a real deadline.

Why students seek help with D217

Students without an IT background often underestimate how much of AIS is genuinely systems-thinking rather than accounting — mapping a transaction cycle correctly requires understanding data flow, not just debits and credits, and documentation-standard formatting is graded specifically, not just the underlying analysis.

How GradeEssays helps with D217

Share your company scenario and rubric, and your writer will map the transaction cycle accurately, identify the right IT controls for each step, and produce documentation in the standard format your task expects — flowchart, narrative, or both.

Prerequisites and program context

D217 requires Intermediate Accounting I (D103) and Intermediate Accounting II (D104) as prerequisites, and itself feeds into Auditing (D215).

Related courses