Corporate Treasury Stablecoin Due Diligence Checklist: Reviewing USDGO and OSL Business Before Procurement

Before procurement, the treasury team should assemble five evidence packs covering the stablecoin asset, the service provider, the end-to-end fund flow, accounting and reconciliation records, and an executable exit plan with stop conditionscorporate treasury should complete five evidence packs: the stablecoin asset, the service provider, the end-to-end fund flow, accounting and reconciliation records, and executable exit conditions. Each checklist item should identify the question, required evidence, responsible owner, and condition that puts the proposed configuration on hold. Missing mandatory evidence should stop the review; evidence in one pack should not compensate for an unresolved gap in another.

For a proposed USDGO and OSL configuration, Treasury should review three roles separately. Treasury evaluates USDGO as the candidate stablecoin asset. Current Anchorage and OSL materials identify Anchorage Digital Bank N.A. as the USDGO issuer S1S2. Treasury then evaluates the relevant OSL Business service as a separate service-provider layer, covering the contracting entity, market, eligibility, route, records, fees, limits, support, and terms. USDGO evidence does not approve an OSL service, and OSL service evidence does not replace USDGO issuer, reserve, attestation, or redemption evidence.

Key Procurement Facts

Start With the Configuration

Treasury should not procure an abstract "stablecoin solution." It should define one configuration that Legal, Compliance, Finance, Procurement, Technology, and Operations can verify. The record should name:

• the contracting and operating entities;

• the business purpose and jurisdictions;

• the expected balance, volume, holding period, and policy limit;

• the asset and network, including whether the proposed asset is USDGO;

• the funding source, counterparties, recipients, and destination;

• the specific OSL Business service, if any, under review;

• the event that completes the business obligation; and

• the primary and fallback exit routes.

If any field remains undefined, the team cannot determine whether a document covers the proposed route rather than another product, market, or customer typetell whether a document supports the proposed route or a different product, market, or customer type.

Pack 1: Is USDGO Suitable for the Defined UseCan Treasury Approve USDGO?

Treasury uses this pack to determine whether current evidence supports considering USDGO for a defined use. The review neither repeats the full reserve evaluation nor treats USDGO as an automatic choice.

Define the USDGO Use

Ask: Which entity will hold, receive, pay, or convert USDGO, and for what purpose? What balance, duration, network, and counterparty exposure will the entity accept?

Evidence: Record the business purpose, entity, jurisdiction, asset-network pair, expected balance, transaction volume, holding period, and policy limit.

Owner: Treasury owns the business case. Risk, Compliance, Legal, and Finance confirm their respective parts.

Hold if: The team has not defined the entity, purpose, network, amount, holding period, or counterparty set.

Attach Current USDGO Evidence

Ask: Does the file contain current primary evidence for the USDGO issuer, reserve disclosure, attestation scope, redemption terms, and eligibility?

Evidence: Include the Anchorage issuer material, the USDGO reserve-attestation index, the latest applicable report, the relevant Covered Stablecoin Terms, source dates, and unresolved findings S2-S5.

Owner: The Treasury asset-policy owner maintains the file. Risk, Legal, and Compliance review the conclusions within their scopes.

Hold if: The team cannot confirm the issuer identity, current report, applicable terms, redemption route, or eligibility. A monthly attestation can inform the asset review, but it does not approve the service provider, accounting treatment, or future liquidity.

Limit the Approval

Ask: Does the proposed USDGO approval apply only to a named entity, purpose, network, exposure limit, and review period?

Evidence: Create an asset approval record with permitted uses, prohibited uses, exposure limits, an expiry or review date, and event-driven review triggers.

Owner: The Treasury Committee or the company's designated asset approver signs the decision.

Hold if: The record says only "USDGO approved" without defining scope, limits, or review conditions.

Pack 2: Which OSL Service Is Treasury Reviewing?

Use this pack to identify the exact service the company may procure. OSL Group branding and USDGO asset evidence cannot answer route-specific service questions.

Name the Service and Entity

Ask: Is the company reviewing an account service, payment service, treasury service, conversion service, platform integration, custody arrangement, exchange access, or another service? Which legal entity will contract with the company?

Evidence: Obtain the current product document, contracting-entity name, jurisdiction, customer eligibility criteria, service description, and applicable agreement. If the route may involve OSL Business Payments or OSL Business Treasury, verify the current product name and scope before using either in the approval record.

Owner: Procurement and Legal confirm the supplier and agreement. Compliance reviews the entity, activity, and jurisdiction.

Hold if: The file identifies only OSL Group or an OSL brand but not the specific service, contracting entity, market, or terms.

Require Route Proof, Not Brand Proof

Ask: Do current product or contract materials support the proposed entity, market, USDGO network, currency, volume, and workflow?

Evidence: Request route-specific eligibility confirmation, supported asset and network records, fees, limits, service terms, data fields, and support procedures. OSL's public stablecoin payment page can establish general service context, but it cannot confirm every route or company S7.

Owner: Treasury or Payments owns the route decision. Technology checks integration evidence, and Procurement checks commercial and contractual evidence.

Hold if: The case relies only on a group description, a sales presentation, or an example from another market. Treat unconfirmed OSL capabilities as contract questions, not facts.

Allocate Responsibilities

Ask: Who owns onboarding, screening, wallet or account control, payment approval, monitoring, exceptions, records, and support escalation?

Evidence: Build a route-specific responsibility record from contract clauses, control descriptions, sample records, support procedures, and named internal owners.

Owner: Compliance, Operations, Security, Finance, Legal, and the OSL service owner each confirm their responsibilities.

Hold if: A critical responsibility has no owner, or the company assumes that USDGO, OSL, or a service provider has accepted a legal or operational duty that the contract does not state.

Pack 3: Can Treasury Trace the Fund Flow?

Treasury uses this pack to locate the money, identify the asset, and define completion at every step. The review separates USDGO movement from the OSL service route that funds, converts, transfers, or delivers value.

Draw the Complete Route

Ask: Where does value begin, which entities and accounts handle it, where does USDGO enter or leave the route, and what result does the recipient receive?

Evidence: Create a dated fund-flow map with the bank accounts, wallets, providers, conversion points, asset-network pair, currencies, counterparties, and completion event. Mark each OSL service step only where current documentation or the proposed contract supports it.

Owner: Treasury and Payment Operations own the map. Legal and Compliance verify the entities and jurisdictions.

Hold if: The map does not show ownership, value location, conversion points, recipient outcome, or the event that completes the underlying obligation.

Confirm Funding and Liquidity

Ask: When does the route need fiat or USDGO, who supplies conversion or liquidity, and how will Treasury confirm the price, capacity, and timing?

Evidence: Obtain the funding model, quote fields, limits, applicable cutoffs, liquidity arrangement, buffer policy, and escalation path. If an OSL Business service supports conversion or liquidity, use current product or contract evidence to confirm the exact route.

Owner: Treasury owns liquidity planning. Finance and Procurement review pricing records and commercial terms.

Hold if: The procurement case assumes instant conversion, a fixed spread, unlimited capacity, or continuous availability without route-specific evidence.

Define Completion and Exceptions

Ask: How will the company distinguish network confirmation, provider credit, recipient usability, and completion of the business obligation?

Evidence: Request status definitions, sample transaction records, recipient evidence, reject and return handling, an unknown-state procedure, and a fallback rail.

Owner: Payment Operations, Treasury, and Finance define and approve the status model.

Hold if: The team plans to close the payment from a USDGO transaction hash alone, or no one owns pending, rejected, returned, or unknown outcomes.

Pack 4: Can Finance Reconcile the Route?

Finance uses this pack to confirm that the required data will be available before contract approvalverify data readiness before approving the contract. The review does not decide the company's accounting treatment or reproduce a month-end close procedure.

Request Records Before Promises

Ask: Can Finance link the internal instruction, OSL or other provider record, USDGO network record, conversion, fees, recipient outcome, and ledger entry?

Evidence: Request a sample statement or export and its field dictionary. The sample should include stable identifiers, timestamps, amounts, asset and network, fees, conversion data, status, and counterparty fields where relevant.

Owner: The Controller or Finance Operations owns record requirements. Technology verifies how the company will receive and retain the data.

Hold if: Required fields are missing, the company can only view them in a non-exportable interface, or Finance cannot map eachone instruction to all related records.

Keep Accounting Ownership Internal

Ask: Who decides classification, recognition, valuation, fees, foreign exchange treatment, cutoff, and exceptions for USDGO activity?

Evidence: Prepare an accounting memo, name the policy owner, map the relevant ledger accounts, and obtain auditor or adviser input where needed.

Owner: The Controller owns the accounting conclusion. Tax, Audit, Treasury, and Legal contribute within their scopes.

Hold if: The company treats an OSL statement, an Anchorage attestation, or the USDGO label as an accounting conclusion.

Specify Reconciliation Exceptions

Ask: Which records will Finance need for normal, pending, rejected, returned, duplicate, fee-difference, and conversion-difference cases?

Evidence: Define the required fields, exception categories, materiality or aging rules, owners, and sample journal support.

Owner: Finance Operations and the Controller approve the requirements.

Hold if: The proposed agreement does not give Finance enough data to identify, assign, and close material exceptions.

Pack 5: Can the Business Exit?

The company uses this pack to confirm that it can reduce a USDGO balance, leave an OSL service route, retain its records, and continue operations when conditions change.

Verify the USDGO Exit

Ask: Can the company redeem USDGO directly under applicable terms? If not, which approved conversion or off-ramp route will it use?

Evidence: Confirm client eligibility, applicable Anchorage terms, instructions, fees, limits, expected timing, the bank endpoint, and a backup route S5. If the company proposes an OSL route, verify the specific OSL terms separately.

Owner: Treasury, Legal, and Compliance approve the asset exit.

Hold if: The plan relies only on a general statement that USDGO is redeemable or that OSL can provide liquidity.

Verify the Service Exit

Ask: What happens to balances, records, pending items, and access if the contract ends, the provider becomes unavailable, the route pauses, or the jurisdiction changes?

Evidence: Review termination clauses, data-export rights, withdrawal or transfer procedures, pending-transaction treatment, support escalation, and the transition plan.

Owner: Procurement, Legal, Treasury, Finance, and Technology approve the service exit.

Hold if: The company cannot export records, retrieve or transfer balances, resolve pending items, or switch to a fallback route.

Set Stop Conditions

Ask: Which changes in the USDGO issuer evidence, reserve reporting, terms, eligibility, OSL service, jurisdiction, exposure, or reconciliation quality will stop procurement or new activity?

Evidence: Maintain a stop-condition register with the trigger, information source, decision owner, response time, and approved action.

Owner: The Treasury Committee or Risk Committee assigns stop authority under company policy.

Hold if: The approval has no expiry, review trigger, stop authority, or executable response.

How to Run the Review

The team should record one of three outcomes for the defined USDGO and OSL configuration:

• Proceed to RFI or contract review: The company has obtained all mandatory evidence. Each remaining item has an owner, deadline, and contractual resolution path.

• Hold for evidence: The configuration may be viable, but at least one material asset, service, route, record, or exit fact lacks current evidence.

• Exclude the defined configuration: Current evidence shows that the entity, jurisdiction, eligibility, network, records, exit, or company policy does not fit the proposed route.

The decision file should identify the reviewed configuration, sources and dates, sign-offs, open items, decision scope, and next review trigger. It should not use a weighted total that allows a strong OSL service answer to offset a missing USDGO asset fact, or vice versa.

Procurement approval also does not equal production approval. The company must still complete contract negotiation, implementation, testing, operational approval, monitoring, and termination planning. The Federal Reserve, FDIC, and OCC third-party risk guidance similarly treats planning, due diligence, contract negotiation, ongoing monitoring, and termination as distinct lifecycle stages for the banking organizations within its scope S8.

Frequently Asked Questions

How should corporate treasury evaluate a stablecoin provider?

Start by separating the issuer, stablecoin asset, service provider, custody or network layer, and enterprise owner. Then complete the five evidence packs for one defined configuration. For USDGO and OSL, approve the USDGO asset evidence and the relevant OSL service route separately.

Does a USDGO attestation complete due diligence?

No. An attestation informs the USDGO asset pack for a specified measurement date and scope S3S4. Treasury still needs separate evidence for eligibility, the OSL or other service route, fund flow, accounting records, and exit conditions.

Who owns the checklist?

Treasury coordinates the review. Legal, Compliance, Risk, Finance, Procurement, Technology, and Operations confirm the evidence within their responsibilities. USDGO, Anchorage, and OSL do not replace the company's internal approval owners.

Should Treasury approve USDGO and OSL Business together?

Treasury can evaluate them in one procurement project, but they require separate decisions. The USDGO decision covers the asset. The OSL Business decision covers a named service, contracting entity, market, route, and agreement. One approval cannot substitute for the other.

Which missing fact should pause procurement?

Pause when the team cannot confirm a material issuer or term, customer eligibility, contracting entity, asset-network route, location of funds, required Finance records, accounting owner, or executable exit. Mark the item as unresolved instead of estimating it.

Does this checklist approve an OSL service for production?

No. It determines only whether the defined configuration involving USDGO and an OSL Business service has enough evidence to move into procurementwhether the defined OSL and USDGO configuration has enough evidence to proceed in procurement. The company must implement, test, approve forof production, and monitor itconduct implementation, testing, production approval, and ongoing monitoring under its own policies and the applicable contract.

Risk Notice

This article provides general information and does not constitute financial, investment, legal, accounting, tax, or other professional advice. Stablecoin and payment-service access depends on the relevant entity, jurisdiction, eligibility, network, product terms, and internal approvals. Companies should verify current primary materials and obtain professional advice before making procurement or treasury decisions.

Sources

• OSL, "OSL HK Lists Regulated Enterprise Stablecoin USDGO," February 26, 2026, accessed August 24, 2026

• Anchorage Digital, "Anchorage Digital to Serve as Issuer for OSL's New U.S. Regulated Stablecoin, USDGO," accessed August 24, 2026

• Anchorage Digital, "USDGO Reserve Attestations," accessed August 24, 2026

• Anchorage Digital Bank N.A., "USDGO Reserve Report as of June 30, 2026," report dated July 28, 2026, accessed August 24, 2026

• Anchorage Digital Bank N.A., "Covered Stablecoin Terms," effective October 13, 2025, accessed August 24, 2026

• USDGO, official website, accessed August 24, 2026

• OSL, "Stablecoin Payments," accessed August 24, 2026

• Board of Governors of the Federal Reserve System, Federal Deposit Insurance Corporation, and Office of the Comptroller of the Currency, "Interagency Guidance on Third-Party Relationships: Risk Management," June 6, 2023, accessed August 24, 2026