Monetary Instrument Sales Log

Use this log for cash sales of monetary instruments such as cashier's checks, money orders, traveler's checks, and bank drafts when the sale falls within the covered dollar range. It is meant for recordkeeping on qualifying cash purchases, not for every deposit or non-cash sale. If your institution has a broader internal policy, keep the template aligned to the exact transactions you need to document.

The issuing teller or branch staff member should complete the transaction fields at the time of sale, with supervisor review when required by policy or when a suspicious pattern appears. The purchaser identity section should be captured from the customer and verified against acceptable identification. If your workflow uses a second reviewer, keep that role separate from the person entering the original transaction.

Use it every time a covered cash sale occurs, not as a periodic summary after the fact. Real-time completion reduces missing fields, improves audit trail quality, and makes it easier to spot structuring indicators. If a branch handles these sales frequently, the template can be used as a daily operational log with end-of-day review.

The template includes an established-customer field, but that does not replace the need to record the required transaction details. If your policy allows reduced identity collection for established customers, make sure the rule is explicit and consistently applied. Avoid assuming prior familiarity is enough without a documented verification path.

Yes. The suspicious activity screening section is designed to capture structuring indicators, a short description of concerns, and whether a SAR referral was made. That keeps the log useful for escalation and internal review without turning it into a full investigation file. If no concern is identified, record that the screening was completed rather than leaving the section blank.

Common mistakes include leaving the instrument serial number blank, using free text where a structured field should be selected, and collecting more PII than the log actually needs. Another frequent issue is failing to note whether a supervisor was notified when a suspicious pattern appears. The form works best when required fields are clear and optional notes stay focused on the transaction.

Yes. You can add branch-specific routing, internal approval fields, or conditional logic for different instrument types. Keep the data-minimization principle in mind and avoid adding fields that do not support recordkeeping, review, or audit trail needs. If you serve multiple locations, standardize the core fields and only localize the branch information.

Ad-hoc notes often miss required fields, use inconsistent labels, and make review harder when a transaction is questioned later. This template gives you a repeatable structure for identity capture, transaction details, and escalation notes, which improves usability and audit trail quality. It also makes it easier to train staff on exactly what must be collected each time.