Stablecoin acceptance now has a timetable, and the redemption right is where the ledger design starts.

Two dates, and about two years to design for them.

The GENIUS Act was approved on 18 July 2025 as Public Law 119-27. Section 20 sets its effective date at the earlier of eighteen months after enactment or one hundred and twenty days after the primary federal regulators issue final implementing regulations, and Treasury states in its own rulemaking that the effective date is expected to be 18 January 2027. A second date sits further out. From 18 July 2028, three years after enactment, a digital asset service provider may only offer or sell a payment stablecoin to a person in the United States if it was issued by a permitted payment stablecoin issuer, or by a foreign issuer that meets the conditions in section 18(a).

On 18 August 2026 Treasury opened the first rulemaking on that section, proposing a new 12 CFR part 1523 and asking for comments by 19 October 2026. It is a proposal rather than a final rule, and it is worth reading precisely because it is still open. Almost a quarter of the document is questions, including whether Treasury should create de minimis safe harbours at all, and whether such a safe harbour should be time based or capped by transaction volume, with a million dollars a year floated as an example.

For a finance team the useful observation is about who these prohibitions actually bind. They bind issuers and they bind digital asset service providers. A company that takes a stablecoin in settlement of an invoice is generally neither. What the framework gives that company instead is something it has rarely had when a new payment instrument appears: a defined set of facts about the instrument, published on a schedule, examined by an accounting firm, and certified by named officers.

That is a good position to design from. The work ahead is mostly master data and policy, the sort of thing a finance systems team does well when it has time. The two dates supply the time, and the rest of this piece is about what to build with it.

Who the rules bind, and what each one means from your side.

Reading the prohibitions as a table of counterparties rather than as a compliance checklist makes the shape of the thing obvious. Each row is somebody else obligation, and each one resolves into a question you can ask that party and record the answer to.

The definition doing the work is in section 2(7). A digital asset service provider is a person, and the statute gives a digital asset exchange as its example, who for compensation or profit engages in the business of exchanging digital assets for monetary value or for other digital assets, transferring them to a third party, acting as a custodian, or participating in financial services relating to their issuance. Everything in that list is somebody providing a service in the transaction. Accepting money for a shipment is not on it.

One caution is worth stating plainly, because it is the kind of thing that gets assumed in the wrong direction. Section 3(h) contains three rules of construction that exempt certain transactions from section 3 entirely: direct transfers between two individuals acting on their own behalf without an intermediary, movements between an account an individual owns in the United States and one they own abroad offered by the same parent company, and transactions through software or hardware wallets that facilitate an individual own custody. All three are written around individuals. A company reading any of them as cover for its own arrangements is reading something that is not there.

What becomes knowable about an issuer, on a monthly rhythm.

Here is the part that repays attention. Section 4(a)(1) requires a permitted payment stablecoin issuer to hold identifiable reserves backing its outstanding stablecoins on an at least one to one basis, and the instruments those reserves may consist of are a closed list rather than a principle. Reading the list tells you what the promise behind a coin is made of.

Around that list sit three obligations that together make an issuer unusually legible. The issuer has to publish its redemption policy, with clear and conspicuous procedures for timely redemption and plain language fee disclosure, and fees can only change on at least seven days notice. It has to publish the monthly composition of its reserves on its own website, giving the total number of outstanding stablecoins and the amount and composition of reserves including the average tenor and the geographic location of custody of each category. And under section 4(a)(3) the previous month end report is examined every month by a registered public accounting firm, with the chief executive officer and chief financial officer certifying its accuracy, a certification that carries the criminal penalties in section 1350(c) of title 18 if knowingly false.

Compare that to what a treasury team can usually learn about a payment instrument between reporting seasons, and the asymmetry runs the right way for once. There is also a quieter layer above it. The OCC has proposed two supervisory returns in Bulletin 2026-24: Form PS-01, a weekly report of payment stablecoin activity and reserves filed for each stablecoin an issuer issues, and Form PS-02, a quarterly report of condition and income. The weekly return is confidential to the regulator, so it is not a source you can build a control on. The monthly website disclosure is, and that is the one to diary.

Two further facts belong in a counterparty file. Reserves may not be pledged, rehypothecated or reused, with narrow exceptions for margin on permitted repurchase transactions, standard custodial obligations, and creating liquidity to meet reasonable expectations of redemption. And section 11 gives holders a claim in an insolvency proceeding that ranks ratably with other holders and ahead of other claimants with respect to the required reserves, limited to claims arising directly from holding. That is a credit position with a defined place in the queue, which is more than can be said for most new payment rails at this stage.

The ledger question turns on the redemption right.

Regulatory status tells you whether a coin will still be offered to you in 2029. It does not tell you which line of the balance sheet it belongs on. That question has its own answer, and the encouraging thing is how narrow the hinge is.

The elegant part is that the two frameworks meet at the same document. Section 4(a)(1)(B) of the GENIUS Act obliges an issuer to publish a redemption policy with clear procedures for timely redemption. ASC 350-60-15-1(b) asks whether the asset provides the holder with enforceable rights to or claims on underlying goods, services or other assets. The published policy is the primary evidence for the accounting conclusion, which means the regulatory regime is quietly generating the exact artefact the technical accounting file needs.

The Board was candid about the difficulty in the basis for its conclusions. It included the enforceable rights criterion so that ordinary arrangements such as contracts with customers, guarantees and insurance contracts would not be swept into the Subtopic merely because they exist in digital form. It also acknowledged that enforceability is a notion used throughout GAAP, that determining it may require judgement, and that in many though not necessarily all cases the answer will be clear. A published redemption policy makes more of those cases clear than would otherwise be true.

One structural point is easy to miss and expensive to miss twice. ASC 350-60-05-2 states that the Subtopic covers subsequent measurement, presentation and disclosure, and that initial measurement, recognition and derecognition come from other GAAP. Even where a holding falls inside Subtopic 350-60, the entry that books the receipt against an invoice has to be reasoned separately. A design that treats the classification memo as covering the whole lifecycle will have a gap exactly where the transaction volume is.

It is worth noting what section 17 does and does not settle. It amends the Securities Act, the Exchange Act, the Investment Advisers Act, the Investment Company Act, the Securities Investor Protection Act and the Commodity Exchange Act so that a payment stablecoin issued by a permitted payment stablecoin issuer falls outside the definitions of security and commodity in each. That is a statutory conclusion about those regimes. The Codification reaches its own definitions independently, which the Board noted when it observed that assets treated as securities for regulatory purposes may not be securities as defined in the Master Glossary. Both facts belong in the memo, and neither substitutes for the other.

The artefact: an instrument record, and a receipt that stays separate from it.

Nearly every question above resolves to a field. Which issuer, what status, checked when, redeemable on what terms, backed by what, classified how, accepted up to what limit. None of that fits on a customer record or a payment method, which is why the object worth creating is an instrument master with one row per stablecoin you are willing to touch.

# Instrument master: one record per stablecoin you will accept

instrument:
  code: PSC-USD-EXAMPLE
  display_name: "Example payment stablecoin (placeholder)"
  ticker_as_marketed: "USDX"          # marketing string, never the key
  issuer:
    legal_name: "Example Issuer, LLC (placeholder)"
    lei: "0000000000EXAMPLE00"
    domicile: US
    category: permitted_payment_stablecoin_issuer
    regulator: OCC
    status_as_at: 2026-08-23
    status_source: "https://example.invalid/register-entry"
  foreign_issuer_checks:                # only where domicile is not US
    occ_registration: not_applicable
    comparability_determination: not_applicable
  redemption:
    right_to_redeem_for_cash: yes
    policy_url: "https://example.invalid/redemption-policy"
    policy_captured_at: 2026-08-23
    fee_change_notice_days: 7
    pays_holder_interest: no            # prohibited by section 4(a)(11)
  reserve_reporting:
    monthly_composition_url: "https://example.invalid/reserves"
    last_reviewed: 2026-08-01
    last_reviewed_by: treasury.analyst
    accountant_examined: yes
  accounting:
    classification: financial_asset_receivable
    guidance_applied: "ASC 310, per memo TA-2026-014"
    gl_account: 1185
    memo_ref: TA-2026-014
    concluded_on: 2026-08-14
  policy:
    accepted: yes
    max_single_receipt: 250000
    max_balance_held: 500000
    hold_rule: convert_within_2_business_days
    approved_by: group.treasurer
    review_due: 2027-02-01

# Receipt: a separate record, because a receipt is not a holding
receipt:
  reference: SCR-2026-000118
  instrument: PSC-USD-EXAMPLE
  customer: CUST-40218
  applied_to_invoice: INV-2026-09912
  units_received: 48750.00
  network_fee_units: 1.85
  rate_used: 1.0000
  rate_source: "contracted redemption rate, per agreement CA-2026-31"
  settled_at: 2026-08-23T09:14:22Z
  wallet_credited: WLT-TREAS-02
  status: applied

Three choices in that shape are deliberate. The ticker is stored but never used as the key, because a ticker is a marketing string and the issuer legal entity is the fact. Statuses carry an as at date and a source, so the record answers what was known on a given day rather than only what is true now. And the receipt is a separate object from the instrument and from the holding, because a receipt settles an invoice on a date at a rate while a holding sits on the balance sheet until it is redeemed, converted or spent.

The record above is a worked example of the shape being described. It is not an extract from any customer system, and the entity name, addresses, references and figures in it are placeholders.

An implementation checklist for the next few quarters.

The comment window on the Treasury proposal closes on 19 October 2026, and any company with a real view on how a de minimis safe harbour should work has an open invitation to say so. Everything below that is internal, and none of it depends on the final rule landing first.

• Write the acceptance policy before the first request arrives. A named list of stablecoins you will take, the wallet or provider each one may arrive through, a size limit, and a person who owns changes to the list. This is a short document, and drafting it under time pressure while a customer waits is how exceptions become precedent.
• Create an instrument master record per stablecoin rather than a single flag on the customer. The issuer, its legal name, its status, whether it is domestic or foreign, the redemption policy URL, the published reserve report URL, and the date each was last reviewed. One field on a customer record cannot answer any of the questions that follow.
• Diary the monthly reserve report as a control, not a curiosity. Section 4(a)(1)(C) requires the composition to be published on the issuer website every month, with the total outstanding, the amount and composition of reserves, and the average tenor and geographic location of custody of each category. A monthly obligation on their side deserves a monthly review on yours.
• Ask your custodian and your exchange the section 10 question in writing. Custody of reserves, collateral and issuing keys is limited to supervised or regulated persons. Getting the answer on paper now is cheaper than reconstructing it during a due diligence request later.
• Ask providers what happens to their coin list on 18 July 2028. From that date a digital asset service provider may only offer or sell a payment stablecoin issued by a permitted payment stablecoin issuer, or by a foreign issuer meeting the section 18(a) conditions. Providers will be planning this now, and their answer tells you which of your accepted coins have a long life.
• Settle the classification question once, in a memo, before volume builds. The redemption right is the fork. Getting a documented answer while there are three transactions to look at costs a fraction of what it costs after a quarter of activity, and it lets the chart of accounts be set up correctly the first time.
• Decide the holding period rule and automate it. Section 4(a)(11) forbids the issuer from paying holders any interest or yield for holding, using or retaining the stablecoin. An idle balance therefore earns nothing, which makes a sweep rule to cash or to a permitted investment a straightforward treasury policy with a real number behind it.
• Model the reconciliation before you model the revenue. On chain settlement and your cash application run on different clocks and different identifiers. Decide up front which field carries the invoice reference, how a partial payment is matched, and what happens to the small differences that network fees create.

A team that does the first three of those has already moved the topic out of the category of things that get decided in a hurry by whoever happens to be on the call. That alone is worth the afternoon.

Failure modes, and what each one looks like from inside.

• Treating the balance as cash on the balance sheet by default. Cash and cash equivalents is a conclusion that has to be reached, and a claim on a private issuer redeemable through that issuer is a different fact pattern from a bank deposit. Reaching for the familiar line first and documenting later is how a restatement conversation starts.
• Reading the July 2028 date as a deadline for your own compliance. It is the date a prohibition begins to apply to digital asset service providers. The consequence for a corporate holder is commercial rather than legal, and it arrives through the provider, which is why the provider conversation matters more than a compliance project.
• Assuming the individual carve outs help a company. Section 3(h) exempts direct transfers between two individuals acting on their own behalf, movements between two accounts owned by the same individual at the same parent company, and transactions through a wallet that facilitates an individual self custody. All three are framed around individuals, and a company relying on any of them by analogy is relying on nothing.
• Letting the wallet be the record. A wallet address holds a balance, not an accounting position. Which invoice it settled, at what rate, on what date, with what fee, and against which customer are all facts that live in the ledger, and a chain explorer will never produce them in a form anyone can review.
• Trusting the ticker instead of the issuer. Section 4(a)(9) prohibits deceptive names, including any combination of terms relating to the United States Government in the name of a payment stablecoin, and marketing that would lead a reasonable person to think the coin is legal tender, issued by the United States, or government guaranteed. It expressly allows abbreviations relating to the pegged currency, such as USD. A ticker is a marketing string, and the master data field you need is the issuer.
• Skipping the foreign issuer question. Section 18(a) requires a Treasury determination that the issuer home regime is comparable, and registration with the OCC. Those are two verifiable facts about a specific legal entity, and they belong on the instrument record with a review date rather than in somebody memory.
• Assuming the weekly supervisory data is available to you. Bulletin 2026-24 proposes Form PS-01 as a weekly confidential report to the OCC for each stablecoin issued, and Form PS-02 as a quarterly report of condition and income. The report a corporate holder can actually read on a schedule is the monthly website disclosure under section 4(a)(1)(C).
• Building the integration before writing the policy. It is genuinely easy to accept one of these payments and genuinely hard to unwind a series of them booked on an approach nobody agreed. The policy is a page and the integration is a project, and doing them in that order saves the project from being rebuilt.

Data and interface considerations.

• The missing object is an instrument master, sitting between the payment method and the general ledger account. Most finance architectures have a place for a bank account and a place for a payment method, and no place at all for the thing that says who owes you the dollar behind this balance. That record is small, it changes rarely, and everything downstream keys off it.
• Status is a dated attribute, never a boolean. Permitted issuer status, OCC registration for a foreign issuer, and any comparability determination all have effective dates and can change. Storing them with an as at date and a source URL lets you answer what you knew and when, which is the only version of the question an auditor asks.
• Keep the receipt and the holding as two records. The receipt settles an invoice on a date at a rate. The holding sits on the balance sheet until it is redeemed, converted or spent. Collapsing them into one entry works for the first transaction and stops working the moment a balance survives a period end.
• Network fees need an owner in the data model before they need one in the policy. A transfer arrives net of a fee that neither party controls precisely. Deciding in advance whether that difference is a deduction from revenue, a bank charge equivalent, or a customer receivable saves a recurring judgement call at every close.
• Rate capture is an audit fact, not a display preference. Record the rate used, its source, and the timestamp on the receipt itself. A rate looked up later from a different source is a different number, and the difference will be small and persistent, which is the worst combination for a reconciliation.
• The chart of accounts should carry the classification, not hide it. If the memo concludes a receivable under ASC 310, the account should say so. Parking the balance in an other assets bucket makes the disclosure work harder every quarter and makes the original judgement invisible to whoever inherits it.
• Treat the issuer as a counterparty in the same register as your banks. Section 11 gives holders a claim that ranks ratably with other holders and ahead of other creditors with respect to required reserves, and that priority covers only claims arising directly from holding. That is a genuine credit fact and it belongs where your other counterparty exposures live.

The integration pattern here is familiar, which is the reassuring part. A settlement arrives from an external network with its own identifiers and its own timing, and it has to be matched to an open item, valued, posted, and reconciled. Finance systems have solved that shape repeatedly for card acquirers, for payment service providers and for instant payment schemes. The new elements are the instrument master and the classification field, and both are small.

Audit evidence worth capturing from the first transaction.

• The acceptance policy as approved, with its version history and the person who owns it. The interesting question later is never whether a policy existed. It is which version was in force on the day a specific payment was taken.
• The instrument master record as at the transaction date, showing issuer, status, and when each was last verified. This is the record that turns a judgement into a checkable statement.
• The issuer published redemption policy captured at the time, not a link followed a year later. Terms change on notice, so the version that supports your classification memo is the version that was live when you formed the conclusion.
• The monthly reserve composition report for the periods you held a balance, with the total outstanding, the composition, the average tenor and the custody locations. Section 4(a)(3) has the previous month end report examined by a registered public accounting firm and certified by the chief executive and chief financial officer, so this is evidence with real weight behind it.
• The technical accounting memo, dated, naming the criteria it applied. Whether the conclusion is a receivable, another financial asset, or an intangible, the file should show the redemption analysis and cite the criteria at ASC 350-60-15-1 that were tested.
• The rate source and timestamp for every receipt, held on the transaction. Reconstructing rates after the fact is the single most common gap in this area and the easiest one to close in advance.
• The reconciliation between on chain settlement and the cash application, at each period end, including the unmatched items and how long they stayed unmatched. Ageing is what turns a reconciliation from a snapshot into a control.