Intro to Business Procedures FBLA Practice Test

Q: How should I answer segregation-of-duties questions when the scenario is a small office with few employees?

Show you understand the three incompatible roles : authorization, custody, and recording. In a small office, you may not fully separate duties, so strong answers propose compensating controls such as owner/manager review, documented reconciliations, locked blank check stock, system permissions, or periodic independent spot checks.

10 – 59 Questions 13 min

This practice test focuses on the document trails and internal controls expected in office workflows—procure-to-pay, cash handling, and records retention—using COSO’s Internal Control—Integrated Framework as the control lens. Weak authorization, filing, or reconciliation can become audit findings and, if records are altered during an inquiry, exposure under 18 U.S.C. §1519 carries fines and up to 20 years’ imprisonment.

Start

Choose quiz length

1Which document is the buyer’s authorization to purchase goods from a vendor?

2A journal records transactions in chronological order.

True / False

3In a basic flowchart, which symbol represents a decision point (yes/no)?

4An employee needs supplies and submits an internal request that triggers approval to buy. What is this document called?

5Which filing system is typically best when records are retrieved by customer account number?

6Which record is commonly called the “book of original entry” because transactions are first recorded there in date order?

7Which item best demonstrates that a purchase was authorized?

8A records retention schedule means keeping every record indefinitely unless a lawsuit occurs.

True / False

9Accounts Payable receives a vendor invoice, but it doesn’t match the purchase order or the receiving report. What is the best next step?

10Select all that apply. Which three categories are the core of segregation of duties?

Select all that apply

11A process map uses swimlanes labeled Sales, Shipping, and Accounting. What do the swimlanes indicate?

12Which task is most commonly processed in a batch rather than in real time?

13Arrange the procure-to-pay documents/steps in the typical order.

Put in order

1Receiving report

23-way match/approval

3Purchase order (PO)

4Invoice

5Requisition

6Payment + remittance advice

14After learning of a likely federal investigation, which action creates the greatest risk of record-tampering exposure under 18 U.S.C. §1519?

15Select all that apply. A company sets a $5,000 approval threshold for purchases. Which controls best ensure the threshold is enforced?

Select all that apply

16A warehouse team needs to prove what quantities arrived on a specific date. Which document provides that evidence?

17Select all that apply. Which practices align with a strong records retention program?

Select all that apply

18A clerk can add new vendors and also enter invoices for payment. Which control best reduces the risk of fake vendors and fraudulent payments?

19Arrange the typical steps of a monthly bank reconciliation.

Put in order

1Compare cleared checks/withdrawals to the books

2Obtain the bank statement

3Identify outstanding items and errors

4Have a supervisor review and sign off

5Compare deposits to the books

6Prepare the reconciliation and any adjusting entries

20Select all that apply. In a standard 3-way match, which documents are compared?

Select all that apply

21Select all that apply. After receiving notice of a likely investigation, which actions are appropriate to reduce record-tampering risk?

Select all that apply

22An auditor asks for evidence that the purchase-approval control operated last month. Which package of evidence is strongest?

23In many flowcharts, a parallelogram is used to represent data input or output (such as entering or printing information).

True / False

24Which option is an internal control (not just a policy statement)?

25In a basic flowchart, which symbol typically represents the start or end of a process?

26A store allows cashiers to issue refunds. Which control best reduces the risk of improper refunds?

Disclaimer

This quiz is for educational and training purposes only. It does not constitute professional certification or legal compliance verification.

Frequent FBLA Business Procedures Errors: Documents, Flowcharts, and Controls

Confusing which document does what (and who creates it)

Purchase order vs. invoice: Students treat both as “a bill.” A PO is the buyer’s authorization and terms; an invoice is the seller’s request for payment.
Requisition vs. PO: A requisition is an internal request to buy; it typically triggers approval and then a PO to the vendor.
Receipt vs. receiving report: A receipt is proof of payment; a receiving report documents what arrived and supports the match to the PO/invoice.

Missing the control objective behind the step

Three-way match misunderstood: It’s not “extra paperwork”—it’s a preventive control to stop paying for goods not ordered or not received.
Approvals without evidence: If an answer choice describes a “policy” but no signature, log, timestamp, or system approval trail, it’s usually not the best control.
Segregation of duties ignored: One person authorizes, has custody (cash/asset), and records the transaction—this is a classic control weakness.

Workflow/flowchart reading mistakes

Skipping decision points: Diamonds are rules. If the invoice doesn’t match PO/receiving, the correct path is an exception process, not “pay anyway.”
Symbol confusion: Document vs. process vs. stored file. Before answering, label each symbol in your head: “document created,” “process performed,” “record filed.”

Records handling and retention missteps

Over-retention as “safety”: Keeping everything forever increases search burden and legal exposure; good practice is a documented retention schedule and consistent disposition.
Informal corrections: “Fixing” a record by deleting/overwriting instead of using a documented correction trail (initials, date, adjusting entry, or approved edit log) is a common red-flag pattern in controls questions.

One-Page Review: Procure-to-Pay, Filing, and Internal Controls (FBLA Intro to Business Procedures)

Printable note: Save/print this section as a PDF for a one-page review before practice sessions.

Procure-to-Pay mini-map (what each step proves)

Requisition (internal) — request to purchase; establishes need and begins approval.
Purchase Order (PO) (buyer → vendor) — authorization + terms; establishes approved commitment.
Receiving Report (receiving/warehouse) — quantity/condition/date received; establishes custody and receipt.
Invoice (vendor → buyer) — request for payment; establishes amount claimed.
Three-way match (PO + receiving + invoice) — approve payment or route to exception; establishes validity/accuracy.
Payment + remittance advice — evidence of settlement; supports posting and vendor communication.

Accounting records (the “where it goes” logic)

Source document: original evidence (invoice, receipt, timecard).
Journal: chronological “book of original entry.”
General ledger: account-by-account totals (Cash, A/P, Supplies Expense).

Internal control quick checks (COSO thinking without memorizing COSO)

Authorization: Who can approve purchases, discounts, voids, refunds?
Custody: Who touches cash, checks, inventory, or blank forms?
Recording: Who posts to the journal/ledger or edits vendor master data?
Review/monitoring: Who reconciles bank statements, reviews exception reports, and signs off?

Filing and retention (what good answers usually include)

Consistent naming + indexing: vendor/date/document number so retrieval is repeatable.
Retention schedule mindset: classify → retain for set period → dispose → document disposition.
Audit trail: corrections via adjusting entries or logged edits, not silent overwrites.

Flowchart “sanity step” for test questions

Before choosing an option, restate the workflow in one sentence: “If X doesn’t match Y, the process stops and routes to Z for review.” If your answer doesn’t include the decision rule, it’s usually incomplete.

Mini Case Drills: Authorization, Matching, and Records Handling Decisions

Use these short prompts to practice the same decisions the objective test targets. For each scenario, state (1) the correct document, (2) the next workflow step, and (3) the control that prevents or detects error/fraud.

Invoice arrives first: Accounts payable receives an invoice, but the PO isn’t in the file. What should happen before any payment approval?
Quantity mismatch: PO shows 50 units, receiving report shows 45, invoice bills 50. Where should this route, and what documentation resolves it?
Single-employee risk: One clerk orders supplies, receives deliveries, and posts bills to A/P. Identify the segregation-of-duties issue and propose one practical fix in a small office.
Cash handling closeout: A front-desk employee collects payments and prepares the deposit. What independent check should exist before the deposit is recorded in the ledger?
Filing breakdown: Vendor files are alphabetized, but invoices are missing randomly and duplicates appear. What filing/indexing change creates a better audit trail?
Correcting an error: A posted amount is wrong in the journal. Choose the best correction method that preserves traceability (and explain why deleting is risky).
Master data change: A vendor’s bank info is updated based on an emailed request. What verification step prevents payment diversion?
Retention decision: A supervisor says “keep everything forever just in case.” What is the compliant, business-sensible alternative process?

Self-check rubric (fast)

Best answers mention evidence: approvals, timestamps, checklists, reconciliation sign-offs, exception queues.
Weak answers rely on intent: “be careful,” “follow policy,” or “double-check” with no accountable step.

Authoritative References for FBLA Business Procedures, Internal Control, and Recordkeeping

FBLA Competitive Event: Introduction to Business Procedures — Official event overview describing the objective-test focus areas and expectations.
FBLA 2025–2026 Introduction to Business Procedures Guidelines (PDF) — Current guideline document for the event, including topics and competitive-event specifics.
COSO: Internal Control—Integrated Framework (overview) — The standard reference for thinking about control objectives, components, and evidence.
SEC: Sarbanes-Oxley Section 404—A Guide for Small Business (PDF) — Practical explanation of documenting and evaluating internal controls and maintaining support for assessments.
National Archives (NARA): Scheduling Records — Authoritative guidance on retention periods and disposition concepts that map to real-world records programs.

FBLA Intro to Business Procedures FAQ: Documents, Controls, and Audit-Ready Workflows

In FBLA business procedures questions, what’s the fastest way to distinguish a requisition, PO, receiving report, and invoice?

Use the “who created it + what decision it triggers” test: a requisition is internal and triggers approval to buy; a PO is the buyer’s authorization sent to the vendor; a receiving report is created when goods arrive and supports acceptance; an invoice comes from the vendor and triggers the payables review/match.

What does a three-way match actually control for (and what’s the typical exception path)?

The three-way match (PO + receiving report + invoice) is a preventive control for validity and accuracy—you pay only for items authorized and received at the correct price/quantity. If any element disagrees, the best workflow routes to an exception queue for investigation (short shipment, backorder, price dispute, duplicate invoice) before approval.

How should I answer segregation-of-duties questions when the scenario is a small office with few employees?

Show you understand the three incompatible roles: authorization, custody, and recording. In a small office, you may not fully separate duties, so strong answers propose compensating controls such as owner/manager review, documented reconciliations, locked blank check stock, system permissions, or periodic independent spot checks.

Why do questions emphasize filing, retention, and “audit trail” instead of just efficiency?

Because documentation is evidence. Good filing supports retrieval, approvals, and reconciliations; poor documentation creates audit findings and can look like concealment when records can’t be produced. For broader context on how organizations treat evidence and controls in regulated environments, see the Banking Compliance Quiz - Free Risk Assessment Practice.

Where does 18 U.S.C. §1519 fit into a business procedures mindset?

It’s a federal obstruction statute that can apply when someone destroys, alters, or falsifies records with intent to impede an investigation. In business-procedure terms, this reinforces why corrections should be traceable (adjusting entries, logged edits, documented voids) and why retention/disposition should follow an approved schedule. This is general educational information, not legal advice.

What’s the most reliable way to improve on workflow diagram questions?

Practice converting each diagram into “if/then” rules: for every decision diamond, write the condition and the action (e.g., “If invoice ≠ PO/receiving, route to exceptions; otherwise approve payment”). Then verify the diagram shows who creates the document, where it’s filed, and which step provides review or reconciliation.

Five High-Impact Skills for the FBLA Introduction to Business Procedures Objective Test

Identify documents by decision: Always tie each form to the decision it authorizes (requisition → request, PO → authorization, invoice → pay request, receiving report → acceptance evidence).
State the control objective: When picking a “best control,” name what it prevents/detects (duplicate payment, unauthorized purchase, missing assets, misstatement).
Use the 3-role lens: Spot segregation-of-duties issues by checking who authorizes, who has custody, and who records—then add a review/reconciliation step.
Treat mismatches as exceptions: In procure-to-pay, mismatched documents should stop the normal path and trigger documented investigation, not “override and proceed.”
Preserve traceability in corrections: Prefer adjusting entries, logged edits, and approved voids over deletion/overwrite so the audit trail remains intact.

Glossary: Core Documents and Controls for Intro to Business Procedures

Requisition: An internal request to purchase goods/services that starts the approval workflow. Example: “IT submits a requisition for two monitors before a PO is created.”
Purchase Order (PO): A buyer-issued document authorizing a vendor to supply specified items at stated terms. Example: “A PO number must appear on the vendor invoice to pass matching.”
Receiving Report: A record created at delivery that documents what was received (quantity, condition, date). Example: “Payment is held until the receiving report confirms delivery.”
Invoice: A vendor-issued request for payment that should be validated against authorization and receipt evidence. Example: “An invoice without a matching PO routes to exceptions.”
Three-way match: A control comparing PO, receiving report, and invoice before approving payment. Example: “Invoice quantity exceeds receiving quantity, so the match fails.”
Source document: Original evidence supporting a transaction (e.g., invoice, receipt, timecard). Example: “The invoice is the source document for the A/P entry.”
Journal: A chronological record of transactions (book of original entry). Example: “Record the purchase in the journal on the transaction date.”
General ledger: The account-by-account record where journal entries are posted and summarized. Example: “Posting moves the amount from the journal to Accounts Payable.”
Segregation of duties: Separating authorization, custody, and recording responsibilities to reduce error/fraud risk. Example: “The person preparing deposits should not post cash receipts.”
Reconciliation: An independent comparison of two records to confirm completeness/accuracy. Example: “Bank reconciliation compares the bank statement to the cash ledger.”
Retention schedule: A rule set defining how long records are kept and how they are disposed of, by record type. Example: “Invoices are retained for the specified period, then disposed and logged.”
Exception queue: A controlled workflow path for transactions that fail validation (mismatch, missing approval, duplicate). Example: “A price discrepancy sends the invoice to the exception queue for review.”