BUSACT 702 Accounting Information Systems
BUSACT 702 Overview
- University of Auckland
- Quarter
- 11 chapters
- Accounting
BUSACT 702 Accounting Information Systems is a postgraduate (Level 9, 15 points) course in the University of Auckland Business School, taken inside the Master of Professional Accounting.
- Assessed by Secure Test (systems flowcharting) Confirm on Canvas (a ~45% figure is unconfirmed) + 2 more
- Key terms Accounting Information System (AIS), Systems flowchart, Data flow diagram (DFD), Activity -> risk -> control analysis
- Assessment move Treat the weekly rhythm as the whole game: watch the lecture, then use the team-based-learning and computer-lab sessions to draw the case flowcharts…
What you get in the full BUSACT 702 Study & Assessment Guide
- 11 chapters, 107 pages — every assessed topic, week by week
- 8 original practice questions
- 11 worked examples, solved the way BUSACT 702 marks
- 31 computed figures, redrawn from the course’s own numbers
- Before-you-submit checklist for the Secure Test — what markers reward, what costs marks
Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full study & assessment guide.
How BUSACT 702 is assessed
| Component | Weight | Format |
|---|---|---|
| Secure Test (systems flowcharting) | Confirm on Canvas (a ~45% figure is unconfirmed) | On-campus, closed-book, under examination conditions; read a business-process narrative and draw/critique a systems flowchart |
| Robotic Process Automation Assignment | Part of the coursework (weight on Canvas) | Build a Power Automate flow (triggers, actions, conditions, connectors, error handling) — an individual business report of about 1,500-2,000 words designing an automation for one of the given scenarios |
| Coursework & Data Analytics | The remaining coursework (weights on Canvas) | Systems-documentation and internal-control analyses plus Power BI data-analytics work; at least 70% of the grade is individual |
What other students are asking about BUSACT 702
- Where can I find lecture notes or study guides for BUSACT 702 at Auckland?
- The BUSACT 702 study guide in AskSia Library covers Accounting Information Systems in 11 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
- Is there a final exam in BUSACT 702?
- No final exam is listed in the offering this AskSia Library guide is built from; BUSACT 702 is assessed by Secure Test (systems flowcharting) Confirm on Canvas (a ~45% figure is unconfirmed), Robotic Process Automation Assignment Part of the coursework (weight on Canvas), Coursework & Data Analytics The remaining coursework (.
- What does BUSACT 702 cover on systems flowcharts: symbols & rules?
- In AskSia Library's BUSACT 702 guide, the Systems Flowcharts: Symbols & Rules chapter explains the flowchart symbols · the drawing rules · columns/swim-lanes · reading a process narrative.
- What does BUSACT 702 cover on data flow diagrams?
- In AskSia Library's BUSACT 702 guide, the Data Flow Diagrams chapter explains logical vs physical DFDs · the context diagram · Level-0 and Level-1 decomposition · balancing.
- What does BUSACT 702 cover on internal controls: activity -> risk -> control?
- In AskSia Library's BUSACT 702 guide, the Internal Controls: Activity -> Risk -> Control chapter explains preventive/detective/corrective controls · the activity-risk-control analysis technique · segregation of duties.
What BUSACT 702 covers
The whole course → one map for the way it is actually assessed. BUSACT 702 has no traditional final exam: the University of Auckland Master of Professional Accounting programme grades this course through coursework plus a secure, on-campus, closed-book test held under examination conditions.
The high-stakes event is a systems-flowcharting test — you read a business-process narrative and draw or critique a systems flowchart under time pressure — while a Robotic Process Automation (Power Automate) report and Power BI data-analytics work carry the coursework. Each chapter links to its free guide.
Introduction to AIS & Systems Documentation
What an AIS is · why we document systems · process maps, DFDs and flowcharts as documentation toolsWeek 1 of University of Auckland BUSACT 702 Accounting Information Systems sets the foundations: what an accounting information system is, how a business process moves data across the organisation, and the three documentation tools you will use all quarter — process maps, data-flow diagrams and systems flowcharts.
- AIS = the intersection of accounting and information systems: people, processes, data, hardware and software supporting a business process
- Business process = the activities that work together to achieve business objectives, often spanning several information systems (sales, purchasing, finance)
- Three documentation forms in increasing detail: process map (swim-lanes) -> data-flow diagram (logical then physical) -> systems flowchart (combines both)
- Why we document: preserve process knowledge, enable business-process redesign (BPR), and let the auditor understand data handling, steps, controls and misstatement risk
- The 'balanced set' of systems documentation — using the tools together so the picture is complete
- Auditing context: ISA (NZ) 315 requires understanding the entity's processes; narrative, questionnaire, checklist and flowchart are recognised techniques
Systems Flowcharts: Symbols & Rules
The flowchart symbols · the drawing rules · columns/swim-lanes · reading a process narrativeThis is the engine room of University of Auckland BUSACT 702: the systems-flowchart symbol set and the nine drawing rules, laid out in columns (swim-lanes) by entity, and the craft of turning a business-process narrative into a correct flowchart.
- The symbol set: external entity / start-stop, single document, multiple (three) documents, manual input, manual process, computer process, on-screen display
- Data-store symbols: magnetic disk storage; a paper file filed N (numerically), A (alphabetically) or C (chronologically); the general journal / general ledger symbol
- Connectors and flows: on-page connector (labelled A), off-page connector, document flow, data/information flow, telecommunications link, batch total (BT), annotation
- Columns / swim-lanes: one column per entity; every symbol sits in the column of whoever performs it
- The nine drawing rules (e.g. show where a document ends up; number copies; filing needs no process symbol; every process has an input and an output)
- Manual process vs computer process — the distinction markers watch for (an automatic journal posting is a computer process)
Data Flow Diagrams
Logical vs physical DFDs · the context diagram · Level-0 and Level-1 decomposition · balancingData-flow diagrams (DFDs) are the logical backbone underneath a systems flowchart in University of Auckland BUSACT 702.
- Logical vs physical DFD: logical = the process activities plus the data needed and generated; physical = the people, functional areas and physical resources
- The context diagram: the whole system as one process, with the external entities and the net data flows in and out
- Level-0 decomposition: the major processes (numbered 1.0, 2.0, ...) with data flows to external entities and data stores
- Level-1 decomposition: exploding one Level-0 process into its sub-processes (1.1, 1.2, ...)
- Balancing: the data flows into and out of a process must match between the parent level and the exploded child level
- Data stores, external entities and processes as the three building blocks; numbered data flows connect them
Internal Controls: Activity -> Risk -> Control
Preventive/detective/corrective controls · the activity-risk-control analysis technique · segregation of dutiesThis chapter is the second core skill of University of Auckland BUSACT 702: evaluating a process for control.
- Purpose of internal control: safeguard assets, ensure reliable records, promote efficiency and compliance
- Control types: preventive (stop it happening), detective (find it after), corrective (fix it and prevent recurrence)
- The activity -> risk -> control technique: for each activity, name the risk/weakness, then the control that corrects it (a three-column table)
- Segregation of duties: separate authorisation, recording and custody so no one person controls a whole transaction
- Recurring controls: independent authorisation, sequential (pre-)numbering of documents, exception reporting, blind purchase orders, three-way match
- More controls: credit checks and limits, periodic stocktakes, independent master-data maintenance, dual signatories, regular bank reconciliations, edit/validity checks, barcodes/RFID
Databases & Data Modelling
Entity-relationship diagrams · cardinalities · relationship sentences · the relational modelUniversity of Auckland BUSACT 702 turns from process pictures to the data underneath them: the relational database model, entity-relationship (ER) diagrams, reading cardinalities and writing relationship sentences in both directions.
- The relational model: data held in related tables (entities) rather than in one flat file; keys link them
- Entity-relationship (ER) diagram: entities (e.g. Customer, Sales order, Stock picking, Shipment, Sales invoice) connected by relationships
- Cardinality: whether a relationship is one-to-one, one-to-many (1:N) or many-to-many, in each direction
- Relationship sentences: stating a relationship in both directions ('one customer places many orders; an order relates to one customer')
- Translating cardinalities into business rules: partial picks allowed vs partial shipments not allowed vs invoiced in full
- Why a good data model supports the AIS: consistent, non-redundant data that controls and analytics can rely on
The Revenue (Sales) Cycle
Order -> deliver -> bill -> collect · the risks at each step · the internal controls that address themThe revenue cycle is the first full transaction cycle in University of Auckland BUSACT 702: order, deliver, bill, collect.
- The activities in sequence: 1.1 check inventory levels -> 1.2 credit check -> 1.3 create sales order -> 2.1 pick the goods -> 2.2 prepare for shipping -> 2.3 deliver the goods
- Selling unavailable goods -> perpetual inventory records plus physical checks
- Selling to customers who won't pay -> independent credit limits, pre-billing, accounts-receivable ageing
- Fictitious sales -> a signed/authorised order before goods move
- Goods not picked / picking errors -> sequentially numbered picking tickets and exception reports
- Theft in transit and on delivery -> secure conveyance, restricted access, valid customer signature per delivery
The Expenditure Cycle
Demand -> order -> receive -> pay · source documents · ERP/EDI · risks & controlsThe expenditure cycle in University of Auckland BUSACT 702 mirrors the revenue cycle from the buying side: determine demand, order, receive, pay.
- The four processes: 1.0 Determine demand (collect requests, create purchase requisition) -> 2.0 Order (choose supplier, create purchase order) -> 3.0 Receive (accept delivery, record goods received) -> 4.0 Pay (approve payment, make payment)
- The seven source documents: purchase requisition, purchase order, vendor/supplier list, purchase invoice, goods packing slip, receiving report, remittance advice
- Enabling technologies: ERP (enterprise-wide data integration) and EDI (electronic data exchange between two computer systems)
- Ordering risks and controls: unauthorised suppliers -> pre-approved supplier list + independent master-data maintenance; paying too much -> price lists, competitive tendering, budgets
- Receiving risks and controls: unordered goods -> check the PO before accepting; miscount -> blind purchase orders, double-checking, barcodes/RFID
- Payment risks and controls: paying twice -> mark paid invoices and restrict duplicate transaction numbers; misappropriation -> dual signatories, segregation of duties, regular bank reconciliations
General Ledger & Financial Reporting Cycle
Posting & the GL · report controls · bank reconciliation · budgeting & timelinessThe general-ledger and financial-reporting cycle in University of Auckland BUSACT 702 is where the transaction cycles come together: posting to the general ledger, the controls over report generation, bank reconciliation and budgeting.
- Posting from the subsidiary ledgers to the general ledger, and the risk of stale GL data
- Controls over report generation when reporting devolves from IT to finance: restrict to trained staff, senior review and approval of new reports
- Timeliness: daily subsidiary data vs a weekly GL update -> risk of decisions on incomplete data; embed cautions in report screens
- Balances affected when GL data is stale: Inventory, Cash at Bank, Accounts Receivable, Accounts Payable
- Bank reconciliation controls: independent approval of adjusting journals; separate cash handling from reconciliation; check postings from subsidiary ledgers
- Budget process controls: consultative vs top-down budgeting; performance metrics such as budget variances and error complaints
Systems Development & Risk Frameworks: COSO & COBIT
The systems development life cycle · the COSO internal-control framework · COBIT for IT governanceThis chapter of University of Auckland BUSACT 702 steps up to how systems are built and governed: the systems development life cycle (SDLC), the COSO internal-control framework and COBIT for IT governance.
- The systems development life cycle (SDLC): the phased approach to building or acquiring an information system (broadly: planning/analysis -> design -> build -> implement -> operate and maintain)
- Why the SDLC matters for accountants: controls and documentation must be designed in, not bolted on after
- COSO as an internal-control framework: a structured way to think about the components of internal control across an organisation
- The standard COSO components (control environment, risk assessment, control activities, information & communication, monitoring activities) — confirm the exact treatment on Canvas
- COBIT as an IT-governance framework: aligning IT with business objectives, with governance separated from management
- How the frameworks relate: COSO frames internal control broadly; COBIT focuses on governing and managing enterprise IT
Robotic Process Automation & Power Automate
What RPA is · triggers, actions, conditions & connectors · error handling · where RPA fits in the AISThis chapter of University of Auckland BUSACT 702 is where the AIS meets automation: what robotic process automation (RPA) is, where it fits in accounting, and how to design a flow in Microsoft Power Automate — triggers, actions, conditions, connectors and error handling.
- What RPA is: software that automates routine, rule-based business processes; why the profession is adopting it
- Trigger: the event that starts the automation (an email received, a file uploaded, a form submitted)
- Actions: the steps the flow performs (send an email, update SharePoint, request an approval)
- Conditions and loops: if/then branching and repetition to handle different cases and batches
- Connectors: the services a flow reaches into (SharePoint, Outlook, Teams, Excel, Forms, Dataverse)
- Data handling: what data is captured, where it is stored and how it moves through the flow
Data Analytics with Power BI
The analytics workflow · connecting & modelling data · visualising for decisions · analytics in the AISThe final chapter of University of Auckland BUSACT 702 turns accounting data into insight with Microsoft Power BI: the analytics workflow, connecting and modelling data, and building visualisations for decisions.
- The analytics workflow: connect -> model (relate tables) -> build measures -> visualise -> share for decisions
- Connecting data: importing from the accounting data sources into Power BI
- Modelling: relating tables (the ER model from the databases chapter) so measures compute correctly across entities
- Visualising for decisions: choosing charts and dashboards that answer a business question, not just decorate
- Analytics in the AIS: how data analytics complements the transaction cycles and their controls
- Data quality and controls: reliable analytics depends on a sound, controlled data model — garbage in, garbage out
It runs over the ten teaching weeks of a single quarter (confirm the exact quarter and dates on Canvas), with a weekly rhythm of lectures, team-based learning and computer-lab tutorials.
The course sits at the intersection of accounting and information systems: you learn to read how data flows through a business, document it with process maps, data-flow diagrams and systems flowcharts, evaluate the internal controls in each transaction cycle (revenue, expenditure, general ledger), model accounting data with entity-relationship diagrams, and use modern tools — Robotic Process Automation in Power Automate and analytics in Power BI.
There is no traditional invigilated final examination. Instead the programme assesses by coursework plus a secure, on-campus, closed-book test held under University examination conditions; attendance on campus is required for the test.
The examinable high-stakes event is a systems-flowcharting test — you read a business-process narrative and draw or critique a systems flowchart under timed conditions — and the marker ticks each correctly placed symbol and flow.
Programme policy caps any single assessment at 50% of the course grade and requires at least 70% of the grade to be individual work; the exact weights are set in the course outline, so confirm them on Canvas rather than relying on any single figure.
Worked example · free
Turning a sales narrative into a systems flowchart — how the secure test is ticked
- +1Set up the entity columns (swim-lanes) first: Customer · Sales department · Computer · Warehouse · Dispatch. One column per participant, and every symbol lives in the column of whoever performs it — a marker ticks a clean column layout before looking at any symbol.
- +1Show the incoming document where it ends up (rule 2): the emailed customer order enters Sales, is used for the credit check, then the hard copy is FILED in Sales by customer name — draw a data-store symbol labelled A (filed alphabetically). Filing needs no manual-process box (rule 5), so do not draw a process symbol for the act of filing.
- +1Distinguish manual from computer processing: 'check credit' and 'key the order' are manual input/process by the clerk and sit in the Sales column; 'record the sale in the sales journal' is an automatic COMPUTER process — draw it in the Computer column feeding the general-journal / general-ledger symbol. Mixing these up is the classic lost mark.
- +1Route the copies (rule 3 / data flows): the system sends the digital order to Warehouse and Dispatch — draw a data-flow (telecommunications) link from the Computer column to each; the printed picking copy is a document produced in the Warehouse column, not in Computer.
- +1Add the decision symbol: 'goods available?' — yes -> pick the goods; no -> the order awaits stock. Every process has an input and an output (rule 6), so the 'awaiting stock' branch must lead somewhere, not dead-end.
- +1Close every flow and annotate: the stock-release note and dispatch note are each shown flowing to where they are used (rule 2); no flow crosses several entities without passing through their columns (rule 1); add a short annotation (rule 8) wherever the narrative is ambiguous. Each correctly placed symbol and flow earns a tick.
Key terms
- Accounting Information System (AIS)
- The intersection of accounting and information systems: the people, processes, data, hardware and software that capture, store, process and report the accounting data of a business process. BUSACT 702 studies how to document, control and improve it.
- Systems flowchart
- The most detailed documentation tool taught in the course — a combination of the logical and physical views that shows inputs, processes, outputs, documents, data stores and who performs each step, laid out in columns (swim-lanes) by entity. Drawing one correctly from a narrative is the core secure-test skill.
- Data flow diagram (DFD)
- A logical picture of how data moves between external entities, processes and data stores. It decomposes from a single-bubble context diagram to a Level-0 and then Level-1 diagram; a logical DFD shows what activities and data, a physical DFD shows who and where.
- Activity -> risk -> control analysis
- The core control-evaluation technique: for each activity in a process, name the risk or weakness, then the internal control that corrects it. Delivered as a three-column table across a transaction cycle.
- Segregation of duties
- The control principle that no single person should both authorise, record and have custody over the same transaction — e.g. the person who raises a purchase requisition should not also select the supplier and approve the payment. Its absence is the weakness these cases are designed to expose.
- Robotic Process Automation (RPA)
- Software that automates routine, rule-based accounting work. In this course you build an RPA solution in Microsoft Power Automate — a trigger starts the flow, then actions, conditions and connectors carry it out, with error handling for exceptions — which is the basis of the individual coursework report.
BUSACT 702 FAQ
Is BUSACT702 hard?
It is more about a new way of thinking than heavy calculation — there is no math-heavy content. The difficulty is precision and speed: the secure test asks you to turn a business-process narrative into a correct systems flowchart in a short, closed-book window, and it is marked element by element, so a mis-typed symbol or a flow that doesn't close loses a tick.
Students who draw flowcharts by hand every week from the case narratives, and who can recite the symbol set and the drawing rules cold, generally find it very manageable. The coursework (the Power Automate report and Power BI work) rewards steady effort rather than exam nerve.
Can AI help me with BUSACT702?
Yes, as a study aid, not as a way to complete graded work.
Sia is an AI tutor trained on how BUSACT 702 is actually taught and assessed at the University of Auckland: it can walk a narrative-to-flowchart conversion step by step, check which symbol belongs to a manual versus a computer process, drill the activity -> risk -> control technique on fresh scenarios, read cardinalities off an ER diagram with you, and quiz you before the secure test.
It explains and checks your reasoning; it does not do your graded assessment for you, and University of Auckland academic-integrity rules apply — the AI-tool policy differs by assessment (the RPA report, for example, only permits generative AI if you reference it with an appendix of prompts), so confirm what is allowed for each task on Canvas.
How is BUSACT702 assessed?
By coursework plus a secure, on-campus, closed-book test held under University examination conditions — there is no traditional invigilated final exam and no past exam papers to grind.
The high-stakes examinable event is a systems-flowcharting test (read a narrative, draw or critique a systems flowchart, timed), delivered via Inspera or on paper; alongside it sit an individual Robotic Process Automation (Power Automate) report and Power BI data-analytics coursework. Attendance on campus is required for the test.
The exact weights are set in the course outline — confirm them on Canvas rather than relying on any single figure.
What are the assessment rules and is there a hurdle?
Two programme-wide rules are firm: no single assessment counts for more than 50% of the course grade, and at least 70% of the grade must be individual work (no more than 30% group). Late written work attracts a minimum penalty of 5% per day.
A separate minimum secure-test hurdle is plausible for an accredited Master of Professional Accounting course but is not confirmed for BUSACT 702 specifically — check the course outline on Canvas. The exact per-assessment weights (including any figure quoted for the systems test) live behind the Canvas / course-outline login, so confirm them there and don't treat a rumoured number as fact.
Which textbook and tools does BUSACT702 use?
The prescribed text is an ANZ accounting-information-systems textbook (an e-copy is provided via Canvas — confirm the exact edition on the course outline); the systems-documentation material draws on its chapter on process maps, DFDs and flowcharts, and the auditing context references ISA (NZ) 315 for understanding an entity's processes, with Sarbanes-Oxley section 404 as comparative context.
The two software tools you actually build in are Microsoft Power Automate (for the RPA report) and Microsoft Power BI (for the data-analytics work); a set of tool guides is provided on Canvas.
Questions students ask in each BUSACT 702 chapter
- What is an accounting information system, exactly?
- It is the people, processes, data and technology that turn business events into accounting information — where accounting meets information systems. In BUSACT 702 you study how data flows through it, how to document that flow, and how to control it so the reported numbers can be trusted. Chapter 01 · Introduction to AIS & Systems Documentation
- What is the single most important skill in this course?
- Turning a narrative into a correct systems flowchart, at speed, closed book. The secure test is exactly this and it is marked element by element, so the symbol set and the nine rules must be automatic. Chapter 02 · Systems Flowcharts: Symbols & Rules
- What is the difference between a logical and a physical DFD?
- A logical DFD shows what activities happen and what data flows, independent of who or where; a physical DFD adds the people, functional areas and physical resources. A systems flowchart is essentially the two merged. Chapter 03 · Data Flow Diagrams
- What is the activity -> risk -> control technique?
- It is the course's method for evaluating a process: take each activity in turn, name the risk or weakness at that step, then state the internal control that corrects it. You present it as a three-column table across the whole transaction cycle. Chapter 04 · Internal Controls: Activity -> Risk -> Control
- What is an ER diagram and why does the course use it?
- It models the data behind a process — the entities (Customer, Order, Shipment...) and how they relate, with cardinalities. It matters because the cardinalities encode business rules, and a clean data model is what the AIS and its analytics rely on. Chapter 05 · Databases & Data Modelling
- What are the steps of the revenue cycle?
- Check inventory, credit-check the customer, create the sales order, pick the goods, prepare for shipping and deliver — then bill and collect. Each step carries its own risk and control. Chapter 06 · The Revenue (Sales) Cycle
- What are the four processes of the expenditure cycle?
- Determine demand (requisition), order (choose supplier, raise the PO), receive (accept and record the goods), and pay (approve and make the payment). Each has its own risks and controls. Chapter 07 · The Expenditure Cycle
- What are the main control themes in the reporting cycle?
- Who is allowed to build and approve reports, how timely the underlying data is, the integrity of bank reconciliations (especially independent approval of adjusting journals), and how budgets are set. These are the angles the short-answer cases test. Chapter 08 · General Ledger & Financial Reporting Cycle
- What is the SDLC and why do accountants study it?
- It is the phased life cycle for building or acquiring a system. Accountants care because controls and documentation must be designed in during development, not retrofitted — a system built without them is expensive to control later. Chapter 09 · Systems Development & Risk Frameworks: COSO & COBIT
- What is RPA and why is it in an accounting course?
- RPA is software that automates routine, rule-based work. Accountants study it because the profession is automating high-volume tasks (like invoice processing), and accountants must be able to design, evaluate and control these automations — which is exactly what the RPA coursework asks. Chapter 10 · Robotic Process Automation & Power Automate
- What is the Power BI analytics workflow?
- Connect to the data, model it by relating the tables, build measures, visualise for the business question, and share for decisions. Following the workflow keeps the analysis structured and reliable. Chapter 11 · Data Analytics with Power BI
How to prepare for the assessments
Treat the weekly rhythm as the whole game: watch the lecture, then use the team-based-learning and computer-lab sessions to draw the case flowcharts by hand — Summise, XYZ Restaurant, Semantics, Metro — because the secure test rewards the drawing skill, not recognition.
Build two memory sheets early and keep adding to them: (1) the systems-flowchart symbol set (document, multiple documents, manual input, manual vs computer process, data store filed N/A/C, connectors, decision, data and document flows) and the nine drawing rules; (2) the recurring internal controls (segregation of duties, sequential numbering, three-way match, blind purchase orders, independent authorisation, bank reconciliation, exception reporting) so you can run an activity -> risk -> control table on any narrative fast.
For the secure test, rehearse the exact routine — set columns, place every document where it ends up, split manual from computer processing, add the decision, close every flow — under a timer, closed book. Start the Power Automate report early (it is worth a real slice of the coursework and rewards a working prototype and clear referencing) and do the Power BI work in the labs while support is on hand.
Because this is a quarter course with a secure test rather than an exam, confirm the quarter, the test date and the assessment weights on Canvas / the course outline, and prepare as if the test is strictly closed book — because it is.
Your AI Accounting tutor for BUSACT 702
Stuck on a hard BUSACT 702 question? Sia is AskSia’s AI Accounting tutor — ask any BUSACT 702 Accounting Information Systems question and get a clear, step-by-step explanation grounded in how the course is actually taught and assessed. Read this whole study guide free, then take your hardest questions to Sia.