Procedure

The direct answer is B: damaged goods may also be accepted. A goods-receiving procedure should normally verify at least the quantity, the condition or quality, and the supporting documents. Quantity matching answers ‘How many items arrived?’ It does not answer ‘Are the items usable and undamaged?’ If quality inspection is missing, broken, expired, defective or inferior goods may pass into stock and the organisation may pay for goods that do not meet specifications. Option B is correct because it identifies the direct control risk created by the missing check. Option A is less correct: supplier selection usually happens earlier, during purchasing and vendor evaluation; a missing receiving-quality check does not necessarily choose the wrong supplier. Option C is wrong because a missing inspection does not automatically reduce the budget. Option D is wrong because an objective does not become a policy merely because a procedure is incomplete. The exam cue is simple: quantity check confirms number; quality check confirms condition and specification.

Supporting documents should be matched before payment. In exams treat document matching as a control point.

The direct answer is C: action is being taken before the basic record is created. A complaint procedure needs an initial record so that the organisation knows the complainant, date, issue, evidence and required follow-up. Step by step: receive the complaint; register it and assign a number; examine the facts; decide and communicate the solution; close the record. Writing a solution before registration reverses the prerequisite order and may produce an unsupported or wrong decision. Option A is wrong because a solution should not always come first; registration normally comes first. Option B is wrong because budget preparation is not the central procedural issue. Option C is correct because the action occurs before the complaint has been formally recorded. Option D is wrong because policy rigidity does not explain this sequence error. Exam cue: record first, investigate next, resolve after that.

Late eligibility check can waste time and effort. In exams keep screening steps in logical order.

Risk reduces when another person reviews cash work. In exams remember the maker checker system.

Customer confirmation before closure is a useful control. In exams treat final confirmation as service procedure control.

A backup owner gives procedure continuity. In exams connect absence risk with procedure planning.

Payment status check is needed before starting refund. In exams understand financial check as procedure control.

Procedure states order and method states specific way. In exams keep sequence and technique separate.

Time limits control procedure completion. In exams treat deadline as an effective procedure feature.

The direct answer is A, review may remain only nominal. A final review is useful only when the reviewer has clear criteria: what must be checked, what counts as acceptable, who decides and what action follows a failure. Without criteria, two reviewers may judge the same work differently, and a review may become a formality without meaningful control. Option A is correct. Option B is unrelated because a budget becomes accurate through reliable estimates and records, not merely through an undefined review. Option C is wrong because the absence of review criteria does not end a policy; it creates a weakness in implementation or control. Option D is also wrong because an objective is strengthened by clear targets and suitable action, not by a vague final check. Exam cue: a step without standards is weak because it cannot produce consistent decisions.

Escalation moves unresolved complaints forward. In exams treat escalation as a procedure control point.

Authorization slip is proof of stock control. In exams understand authorization as store procedure control.

Duplicate steps for the same purpose reduce efficiency. In exams treat unnecessary duplication as a procedural defect.

Validation is a control step to stop wrong data. In exams always check validation in data procedure.

The direct answer is A: the record trail is weak. A procedure is a predetermined sequence of steps used to perform work consistently. When approvals happen through email but no archive is preserved, the organisation may know that an approval was sent, yet it may not be able to retrieve the message, identify the approver, check the date, or prove what exactly was approved. Step by step: an approval is requested; an approver responds; the response should be stored safely; later, an auditor or manager checks the evidence. The missing archive breaks the evidence chain and weakens accountability and audit control. Option A is correct because it directly describes this missing evidence. Option B, weak market positioning, concerns how a business is placed against competitors and has nothing to do with approval records. Option C, a budget surplus, means income or available funds exceed spending; it does not follow from email storage. Option D, a policy being too broad, concerns general guidance, whereas the problem is a missing procedure record. Memory cue: approvals need proof—think “approve, archive, audit.”

Early information is necessary in safety cases. In exams check the logic of placing time critical step early.

Status update is communication control in customer-facing procedure. In exams check communication step in service procedure.

If exception is unclear it can be misused. In exams treat defined exceptions as part of effective procedure.

In a good procedure steps and controls are clearly documented. In exams treat complete documentation as effective procedure.

Cutoff date helps complete payroll steps on time. In exams treat deadline clarity as procedure quality.

Feedback is useful only when analysed. In exams connect feedback loop with procedure improvement.

The correct answer is lack of independent verification. When the person who performed the work also conducts the final review, errors, bias, or irregularities may not be detected objectively. Review by an independent person makes a control procedure more reliable. Lack of a time limit can be a different procedural weakness, but it is not the problem created specifically by self-review. Exam tip: Strong controls usually separate the responsibility for doing work from the responsibility for checking it.

Benefit of procedure comes from same steps. In exams treat branch variation as communication or design issue.

Reason recording with urgent route improves control. In exams check documentation in exception handling.