Monetary Instrument Sales Log

This template is for cash sales of monetary instruments such as cashier's checks, money orders, and traveler's checks when the transaction falls within the BSA reporting threshold described in the template. It is meant to capture the details needed at the point of sale, not to replace your broader AML program. If your institution sells other products or accepts non-cash payment, those transactions should be handled under separate procedures.

It should be completed at the time of each qualifying sale, not reconstructed later from memory or end-of-day totals. Immediate entry reduces missing fields, improves validation of ID details, and supports a cleaner audit trail. If your branch batches paperwork, the log should still reflect the original transaction time and teller handling the sale.

The teller or frontline employee who completes the sale should enter the transaction details and purchaser information, then complete the verification fields. A supervisor should review any transaction that triggers the form's review logic or appears unusual. This division of labor helps keep the record accurate and makes accountability clear.

Yes, if your policy and the transaction rules require identity verification for the sale, the form includes fields for DOB, ID type, ID number, issuing jurisdiction, and expiration date. Keep the collection limited to what you actually use for compliance and verification, following data minimization principles. Do not add extra PII fields unless your procedure requires them.

Supervisor review should be triggered by the template's suspicious activity indicators, incomplete identity details, third-party involvement, or any unusual behavior noted by the teller. It can also be required for edge cases such as multiple purchases that may indicate structuring. The goal is to route only the exceptions that need escalation, not every routine sale.

Ad-hoc notes usually miss required fields, use inconsistent wording, and make it hard to prove who verified what and when. A dedicated log standardizes field labels, validation, and review steps so the same information is captured every time. That consistency is especially important when the record may be reviewed later in an audit or examination.

Yes, the branch location field, employee identifiers, and notes section can be adapted to your operating model while keeping the required data intact. Many teams connect the form to teller systems, case management, or document storage so the submission creates a searchable record and audit trail. If you customize it, preserve the required-versus-optional structure and any conditional logic tied to suspicious activity.

Common mistakes include leaving the cash amount, instrument serial number, or ID fields incomplete, and collecting free-text notes instead of structured values. Another frequent issue is showing every field to every user instead of using progressive disclosure for optional or conditional fields like third-party details. The form should also make clear what happens after submission so the record does not disappear into an untracked workflow.