Compliance book
Every firearm has a line. Every line has a name.
One acquisition and disposition book per license. Receipts, manufacture, imports, transfers and releases all land in the same book, with the person who wrote each one.
- Acquire
- Dispose
- Hold
- Correct
- Exceptions
- FastBound queue
Names and serials are illustrative.
Inside the product
What you can do on the book
Acquisitions
Six kinds of acquisition.
Receive from another FFL, record a manufacture, enter an import, log a found firearm, assemble a receiver into a firearm, or disassemble a firearm back to a receiver. Type 07 and Type 10 makers can record a manufacture; Type 08 and Type 11 importers can record an import. Assembly and disassembly use their own routes.
A refused request leaves no line behind.
Dispositions
A release is as detailed as the receipt.
Record an FFL transfer, a retail 4473, an exempt transfer, a return to source, a theft or loss, a destruction, or an NFA transfer. Attach the 4473 and NFA references the transfer type requires. Store the NICS status when it is supplied.
- Transfer type selectedFFL, retail, exempt or NFA
- Recipient recordedName, license or address
- Form referenceRequired by type
- Recorded byName stored with entry
The book does not invent a missing reference.
Holds
A pending hold is visible, not buried.
Put a transfer that can be held on hold and the firearm stays open on the book. A pending transfer older than 25 days appears in exceptions as a stale hold, so an old hold stays visible.
Stale holds appear in exceptions.
Corrections
A correction adds a version. It does not erase one.
Correct a manufacturer, importer, model, serial, type or caliber. The book keeps both versions and asks for a reason. Every entry names the person who recorded it, including the correction.
v2 18 Feb 2026 serial corrected
reason: engraver transposed 8 and 3
recorded_by: j.reyes
v1 17 Feb 2026 original entry
recorded_by: j.reyes
The first line remains readable.
Exceptions
The audit starts with the exceptions.
The exceptions view names late entries, stale holds, changes still not in FastBound after 24 hours, look-alike serials and a firearm that is open on two licenses at once. Each group lists the entries behind it.
- Late entryOne receipt recorded after the deadline
- Stale holdOne pending hold older than 25 days
- Sync overdueFour entries not in FastBound after 24 hours
- Look-alike serialTwo serials differ by one character
- Open on two licensesOne firearm has two open lines
Counts are examples, not a live account.
FastBound
FastBound stays the legal record until the license switches.
By default, FastBound is the legal system of record. On a FastBound license, every committed change waits in a sync queue. The adapter that drains that queue and acknowledges each entry is built. It is off until the FastBound account number, API key and audit user are set, along with a RollStamp API key; no live account is connected in this build. Switching the legal record to RollStamp needs a recorded counsel sign-off and no change still waiting to sync.
The queue, ack endpoints and adapter are built. Live credentials are not configured here.
The boundaries
What the book does, and what it does not do yet.
One book per license
Each license has its own A&D book. A firearm open on two licenses is flagged as an exception, not merged away.
Names on every write
Acquisitions, dispositions, holds and corrections all store recorded_by. There is no anonymous book write.
Deadlines from a table
Recording rules and deadlines come from a data table with a citation. A rule marked (verify) is waiting on a legal review.
No silent switch
FastBound remains the legal record until a license is switched with a recorded counsel sign-off. The sync queue is explicit at every step.
Questions, answered plainly.
Can RollStamp replace FastBound today?
The book, queue, acknowledgement endpoints and adapter are built. The adapter runs only with the FastBound account number, API key and audit user, plus a RollStamp API key; those settings are not configured in this build. Until a license is switched, FastBound remains its legal system of record by default.
What happens to an entry that fails validation?
Nothing is written. The request reports what was refused, and the entry stays out of the book. A failed sync does not remove a committed line.
Are the deadlines legal advice?
No. Each rule points at a citation in a data table. Items marked (verify) are still under review. Check the citation before you rely on a deadline.
Put the book in front of us.
Bring a sample of your current records. We will show the acquisition, hold and exception paths, and show how the adapter is configured.