What “ATF-compliant” means for electronic A&D books

Every bound book product page says “ATF-compliant.” Almost none of them explain what the phrase points to. If you’re an FFL evaluating electronic bound book software, it’s worth knowing exactly which rules matter — so you can tell a real compliance claim from marketing.

There are really just two documents that govern an electronic Acquisition & Disposition record: 27 CFR § 478.125 (what the record must contain) and ATF Ruling 2016-1 (permission to keep it electronically). Here’s what each one actually requires.

27 CFR § 478.125 — what the record must contain

This is the federal regulation that defines the Acquisition & Disposition record itself. It predates computers entirely — it’s the rule behind the paper “bound book.” For software, the practical takeaway is that the electronic record has to capture the same information, in the same structure:

• Manufacturer and/or importer
• Model
• Serial number
• Type
• Caliber or gauge
• Date and source of acquisition
• Date and details of disposition (including the transferee and the 4473 reference)

Two details trip up a lot of systems. First, line numbers must be preserved — your record is a continuous, numbered ledger, not a spreadsheet you can freely re-sort and lose your place in. Second, corrections are logged, not erased. If you fix an entry, the original and the change both have to remain visible. A tool that lets you silently overwrite a row is not helping you stay compliant.

ATF Ruling 2016-1 — permission to go electronic

Section 478.125 tells you what to record. It doesn’t, on its own, say you can keep that record in the cloud. ATF Ruling 2016-1 is the guidance that authorizes an FFL to maintain the A&D record in an electronic system instead of a physical book — provided the system meets specific conditions around integrity, availability, and inspection.

In practice, a compliant electronic bound book needs to demonstrate:

• Integrity — the record is tamper-evident, so an inspector can trust that entries haven’t been quietly altered.
• Availability — you can produce the complete record on demand, at the licensed premises, in a usable format.
• Retention — records are kept for the required period (and 4473s for at least 20 years).
• Access for inspection — an ATF investigator can review the record without you exporting it to some proprietary format they can’t read.

How that maps to real software

When BoundPro says it’s built for compliance, this is what we mean concretely:

• The ledger columns mirror § 478.125 exactly, with line numbers preserved and corrections tracked rather than overwritten.
• Every entry and edit is hash-chained and timestamped, so the record carries its own proof of integrity for Ruling 2016-1.
• Hosting is US-based, encrypted in transit and at rest, with nightly backups.
• Audit mode produces a one-click compliance pack — the ledger, the 4473s, NICS records, and any 3310.4 and 3310.12 reports — as a single timestamped file for inspection.
• Records are retained well beyond the 20-year 4473 archive requirement, and you can export the full book as CSV or PDF at any time.

A note on “ATF-approved”

You’ll see products claim to be “ATF-approved” or “ATF-certified.” Be a little skeptical: the ATF does not approve, certify, or endorse individual software products. What it does is authorize electronic recordkeeping that meets the regulation and Ruling 2016-1. Any vendor implying they hold a special ATF certification is, at best, being loose with language.

What software cannot do for you

Even with the best electronic bound book, the FFL holder remains the responsible party for the accuracy and completeness of the record. Good software catches deadlines, enforces structure, and makes inspection painless — but it doesn’t replace judgment at the counter, and it doesn’t transfer legal responsibility away from the licensee.

That’s the honest version of “ATF-compliant”: not a badge, but a record that contains what § 478.125 requires, kept in a way Ruling 2016-1 permits, that you can hand to an inspector without a scramble.

If you want the product view of how we implement this, see ATF compliance in Features and Audit mode — or read why we built ATF bound book software around the regulation in the first place.