A stablecoin issuer approaching its first attestation discovers that the process is not a simple year-end formality. The reserve attestation and audit function underpins the credibility of every redemption promise the issuer makes to holders and to the regulators watching the space. As European MiCA requirements take effect and other flagship regimes converge on disclosure-driven supervision, the attestation framework sits at the centre of the issuer's operational risk map. This guide walks through the construction of the attestation and audit function a stablecoin issuer needs – the scope, the frequency, the publication standard, and how findings interact with supervisory duties.
The reserve attestation obligation applies whenever a token issuer promises redemption at par or makes a value claim backed by underlying assets. The relevant regimes – MiCA for asset-referenced tokens and e-money tokens, the UAE's VARA for payment-token issuers, Singapore's MAS for digital payment tokens with reserve backing – impose periodic public disclosure of reserve composition and reconciliation. Each regime calibrates the frequency and the audit standard to the token's classification and the issuer's scale, but the underlying logic is the same: if you promise redemption, you must prove you can deliver. We regularly advise issuers structuring their attestation function across multiple jurisdictions and guide them through the transition from informal quarterly checks to formal published audits compliant with the applicable framework.
What is reserve attestation for stablecoins
Reserve attestation is the independent verification and public reporting of the assets an issuer holds to back the issued tokens at a defined moment. It answers three questions for holders and supervisors: does the reserve exist, does it cover the circulating supply, and is it held in the permitted asset classes. A proper attestation engagement produces a report signed by a qualified auditor or attestation provider, prepared to the applicable professional standard – typically the International Standards on Related Services (ISRS) 4400 for agreed-upon procedures or a higher assurance standard required under the relevant regime. The report is then published or filed with the regulator according to the prescribed timetable.
The attestation is distinct from a full financial-statement audit. It addresses a narrower, asset-specific question: at the snapshot date, did the issuer hold the stated reserve in the stated form. The process involves confirmation directly from custodians and banks, reconciliation of on-chain token supply to off-chain reserve positions, and verification that the asset classes and their proportions fall within the regulatory limits. In a well-designed system, the issuer runs internal reserve checks daily or in real time, and the external attestation provides independent periodic confirmation of the position the issuer has already disclosed. The frequency – monthly, quarterly or annually – depends on the jurisdiction and the token classification, with e-money tokens under MiCA and certain payment tokens under other regimes attracting the tightest reporting cadence.
The effect for issuers: a published attestation converts a marketing claim into a supervised fact. A clean report reinforces market confidence and keeps the regulator satisfied. A qualified opinion or a shortfall triggers immediate remediation duties and often accelerates the next review cycle. The regulator may require an additional ad-hoc attestation before the standard cycle completes. Issuers who wait until the eve of their first deadline to engage the auditor typically underestimate the lead time the auditor needs to establish procedures and secure custodian confirmations, and that delay creates a compliance gap the regulator sees on the filing date.
When does attestation become mandatory
Attestation becomes mandatory when the issuer's business model and token classification cross a regulatory threshold that triggers reserve-backed supervision. Under MiCA, the obligation attaches immediately for asset-referenced tokens and e-money tokens: the whitepaper must identify the auditor and set out the reporting frequency. For issuers outside the EU targeting ART or EMT classification – for instance, a BVI-incorporated issuer with a European distribution strategy – the MiCA disclosure and attestation standards apply at launch if the token is offered to European holders. The regime does not wait for scale: publication begins with the first issuance cycle.
In the UAE under VARA, payment tokens and other virtual assets that promise redemption or backing trigger reserve disclosure obligations calibrated to the activity licence the issuer holds. The issuer typically works with VARA to clarify the reporting standard and frequency during the application phase, and the final licence conditions specify the attestation requirement explicitly. Singapore's MAS imposes reserve-disclosure expectations on digital payment token service providers where the token incorporates a redemption or value-stabilisation mechanism; the precise threshold and standard are determined through the MAS approval process and documented in the licence conditions. Issuers targeting multiple hubs often find that the strictest regime – typically the EU under MiCA – sets the baseline, and the other jurisdictions accept the MiCA-compliant reports as sufficient for their own purposes, though filed separately.
For a utility token or a governance token with no redemption promise, attestation is not a regulatory requirement – the issuer's disclosure obligation, if any, relates to the development roadmap and treasury management, not to a reserve-backing claim. The classification boundary is strict: a token advertised as stable or pegged to fiat falls under reserve supervision even if the whitepaper never uses the word "stablecoin". The regulator reads the substance of the holder's expectation, not the label the issuer applies.
Who may conduct the attestation
The regulator's rules specify the category of professional the issuer may engage for the attestation function, and the permitted list varies by jurisdiction. Under MiCA, the auditor must be a statutory auditor or audit firm authorised in a member state under the EU's audit directive and must have no conflict of interest with the issuer. Dual appointments – where the same firm audits the issuer's financial statements and the reserve attestation – are generally allowed but face heightened independence scrutiny if a shortfall is found. Some national competent authorities recommend separate firms for the two functions to avoid any appearance of compromise.
Outside the EU, the acceptable auditor profile differs. VARA in Dubai specifies that the attestation must be performed by a firm registered with a recognised international audit standard-setter and with experience in digital-asset reserve verification; the practical effect is to limit the pool to a small number of firms active in the crypto-asset space. Singapore similarly expects the attestor to be a firm registered with the Accounting and Corporate Regulatory Authority and with demonstrated capacity to verify digital-asset custody arrangements. Offshore hubs – BVI, Cayman – typically defer to internationally recognised audit firms, but the issuer must ensure the engagement letter specifies the standard under which the report is prepared and that the standard meets the threshold the target-market regulator expects.
The qualification of the auditor is half the equation; the other half is the scope letter. The issuer and the auditor agree a terms-of-reference document setting out the asset classes to be verified, the cut-off date, the procedures the auditor will perform, and the form of the attestation report. The regulator may prescribe a template or a minimum set of required procedures; where the regime is silent, the ISRS 4400 standard (revised 2021) provides a widely accepted framework for agreed-upon-procedures engagements. An issuer who signs a scope letter that omits a material asset class – for instance, confirming only the fiat bank balance but not the tokenised money-market instruments that make up 40 per cent of the reserve – produces an attestation that is technically compliant with the engagement but substantively insufficient under the regulatory obligation. The supervisor notices the gap, and the issuer must commission a supplemental report to cover the missing tranche.
What the auditor verifies
The auditor's scope covers three core verification tasks: confirming that the reserve assets exist at the snapshot date, confirming that the total value meets or exceeds the circulating token supply, and confirming that the composition of the reserve complies with the regulatory asset-mix rules. The first task – existence – requires direct confirmation from custodians, banks and any other holder of the issuer's reserve assets. The auditor sends confirmation requests to each counterparty, asking them to state the balances held in the issuer's name as at the cut-off date. For tokenised reserves – for instance, short-dated Treasury tokens or tokenised deposits – the auditor must also verify on-chain balances and trace them back to the underlying custodian or issuer of the instrument.
The second task – coverage – involves reconciling the confirmed reserve total to the on-chain token supply. The auditor queries the relevant blockchain to obtain the total circulating supply of the stablecoin at the snapshot time, adjusts for any issuer-held tokens that are not yet in circulation, and compares the net supply figure to the reserve value. If the reserve is denominated in a currency different from the token's peg, the auditor applies the exchange rate prevailing at the cut-off to determine whether coverage holds. A reserve shortfall – even a small one – must be disclosed in the attestation report and triggers an immediate regulatory filing obligation in most regimes.
The third task – asset-mix compliance – verifies that the reserve composition falls within the limits the applicable regime sets. MiCA prescribes detailed rules for ART and EMT issuers on the proportion of the reserve that may be held in cash, in government securities, in reverse-repo arrangements and in other permitted instruments. The auditor checks each category and flags any position that breaches the limit. Outside the EU, the asset-mix rules are typically lighter – VARA and MAS require reserves to be held in highly liquid, low-risk instruments but do not specify percentage caps for each class – so the auditor's role is to confirm that the disclosed composition is accurate and that the instruments meet the general prudential standard. An issuer who shifts reserve composition between attestation dates without notice to the auditor or the regulator risks a supervisory breach even if the assets remain within the regulatory envelope, because the published disclosure is out of date the moment the shift occurs.
How attestation reports are published
The publication requirement converts the attestation from an internal compliance exercise into a market-facing disclosure. Under MiCA, the issuer must publish the auditor's report on its website within the prescribed timeline after the cut-off date – typically within a matter of weeks for quarterly reports and within a slightly longer window for annual audits. The report must remain accessible to the public for a minimum retention period, and the issuer must file it with the national competent authority that authorised the token. The publication standard is strict: a summary or a press release announcing "reserves confirmed" does not satisfy the obligation. The issuer must post the full attestation report, including the auditor's name, the scope of procedures, the findings, and any qualifications or emphasis-of-matter paragraphs.
Outside the EU, the publication expectation varies. VARA requires reserve attestation to be filed with the regulator and disclosed on the issuer's platform; the format and frequency are specified in the licence conditions. Singapore expects similar disclosure for digital payment tokens with reserve backing, aligned to the payment-institution's regular reporting cycle. Offshore hubs – BVI, Cayman – do not always mandate public publication, but an issuer marketing to retail holders or listing on a major exchange will find that the exchange's due-diligence requirements effectively create a publication obligation through the listing rules. The practical baseline across all regimes is that if the issuer has promised redemption and marketed the token as stable, the market expects periodic proof, and the absence of published attestation becomes a red flag for sophisticated holders and banking counterparties.
The publication cycle feeds the redemption window. Holders who see a qualified report or a coverage shortfall will accelerate redemption, and if the issuer's liquidity management is not designed for a surge, the redemption queue can spiral into a run. The issuer's operational playbook must therefore include a stress-test scenario in which a reserve attestation reveals a temporary shortfall – caused, for instance, by a sudden exchange-rate move or a delay in settlement of a Treasury instrument – and the communications and liquidity plan to manage the holder response. In our cross-border practice, we have seen issuers handle this scenario well by pre-filing a remediation plan with the regulator and by publishing a simultaneous statement explaining the cause of the shortfall and the timeline to cure. The key is speed: disclosure within hours, not days.
How attestation findings trigger regulatory action
A clean attestation report closes the cycle and resets the clock to the next reporting date. A qualified report or a shortfall finding opens a regulatory escalation path the issuer must manage under time pressure. Most regimes impose an immediate notification duty when the reserve coverage falls below 100 per cent or when the asset-mix breaches the prescribed limits. The issuer must notify the regulator within a short window – often 24 hours for a material shortfall – and must submit a remediation plan within a slightly longer period, typically a few business days. The plan must identify the cause of the breach, the steps to restore compliance, and the timeline for each step. The regulator may impose interim restrictions on new issuance or require additional liquidity buffers while the breach is open.
The attestation auditor has no direct reporting line to the regulator under most frameworks – the auditor's duty is to the issuer, and it is the issuer who files the report with the supervisor – but if the auditor forms a view that the issuer is withholding material information or misrepresenting the findings, professional standards and in some jurisdictions statutory whistle-blowing rules create an indirect pathway for the auditor to escalate. The practical effect is that the issuer cannot suppress a bad attestation result. The report goes to the regulator, and any attempt to delay or redact it compounds the breach. Issuers who have managed reserve deficits successfully in our experience are those who treat the attestation process as a live governance input, not a retrospective formality. When internal reserve monitoring flags a potential issue, they surface it to the auditor early and work the remediation plan before the formal attestation date arrives.
The second-order regulatory consequence of a qualified report is heightened supervision. The regulator may increase the attestation frequency – monthly reports where quarterly was the baseline – and may appoint a skilled-person review or an on-site inspection to assess the issuer's reserve-management systems. For an issuer marketing across multiple jurisdictions, the qualification in one hub can trigger scrutiny in others, because banking counterparties and exchange partners monitor the public filings and adjust their risk appetite accordingly. A payment-rail provider who sees a reserve shortfall in a published attestation may invoke force-majeure clauses to pause services or may increase collateral requirements for the issuer's fiat settlement account. That cascade is often more damaging to the business than the direct regulatory penalty, and it reinforces the operational imperative to maintain reserve coverage with a prudent buffer above the minimum threshold at all times.
Managing attestation across multiple jurisdictions
An issuer with users in the EU, banking in the UAE and token issuance in BVI faces a three-way attestation obligation. Each regime has its own reporting standard, but the asset pool is one. The issuer's legal structure determines where the attestation duty formally sits – typically with the issuer entity that mints and redeems the token – but the substance of the verification must satisfy the strictest regime. In practice, that means the issuer commissions a single comprehensive attestation prepared to the MiCA standard and files adapted versions of the same underlying report in the UAE and with any offshore regulators who require it. The auditor's engagement letter must specify all three target jurisdictions and confirm that the procedures meet each regime's expectations.
The cross-border complexity multiplies when the reserve itself is distributed. A common structure holds fiat in a UAE bank, short-dated Treasuries with a European custodian, and a liquidity buffer in a Singapore payment institution. The attestation auditor must confirm positions across all three locations, and each custodian or bank must cooperate with the confirmation process. In some cases, the custodian's own audit or reporting obligations create timing friction – for instance, if the custodian's year-end falls at a different date from the issuer's attestation cycle, the custodian may not have the internal systems ready to provide an off-cycle confirmation. The issuer mitigates that risk by agreeing in advance with each custodian that they will support quarterly or monthly confirmations aligned to the issuer's cycle and by building an extra week into the timeline to accommodate any delays.
For a scoped assessment of your reserve attestation build and how it maps across your licensing and banking stack, contact OBOLUS at info@oboluslaw.com. The process set out above frames the standard path. Your facts – the entity structure, the reserve composition, the user geography – determine which regime's disclosure rules control and which auditors can credibly deliver the report your regulators and your banking partners expect. If you have launched without a formal attestation function and the supervisor or a banking counterparty now requires one, a structured catch-up can bring you into line within a single reporting cycle.
How often attestation must occur
The attestation frequency depends on the token classification and the scale of issuance. Under MiCA, e-money token issuers face the tightest cycle: quarterly public attestation is the baseline, with annual full audits. Asset-referenced tokens also require quarterly reporting unless the issuer qualifies for a lighter regime based on issuance volume and holder count. Outside the EU, the frequency is typically calibrated to the issuer's payment-institution or VASP licence tier. A major payment institution in Singapore or a Category 1 VASP in certain hubs may face monthly or quarterly attestation duties, while smaller-scale operators report annually. The issuer's licensing application should explicitly address the proposed attestation frequency and identify the auditor the issuer intends to engage; that disclosure allows the regulator to confirm at the outset that the proposal meets their expectations.
Timing the attestation cycle to align with other reporting obligations reduces operational friction. An issuer whose financial year ends 31 December and whose quarterly attestation dates fall on calendar quarters can synchronise the reserve attestation with the entity's regular financial-statement audit, allowing the same auditor to perform both tasks in a coordinated window. If the cycles are misaligned – for instance, if the attestation date is mid-quarter – the issuer must run a separate cut-off and reconciliation exercise, and that adds cost and consumes finance-team capacity. In our experience advising issuers structuring their attestation function, the cleanest setup is to set the attestation dates at the end of each calendar quarter and to engage the auditor under a standing annual retainer that covers all four cycles, so that there is no negotiation or procurement delay when each reporting window opens.
What the attestation function costs
The cost of reserve attestation depends on the complexity of the reserve, the number of custodians and the frequency of reporting. A straightforward setup – one fiat bank account, one custodian, quarterly reporting – typically runs in the low five figures per attestation cycle. A multi-jurisdiction reserve with tokenised instruments, multiple custodians and monthly reporting can reach low to mid six figures annually. The issuer should budget for the attestation cost as a fixed operational expense from day one; it is not an optional enhancement. The regulator expects the attestation at the prescribed frequency regardless of the issuer's revenue or profitability.
Auditor selection turns on three factors: the firm's capacity to verify digital-asset custody arrangements, the firm's regulatory standing in the relevant jurisdiction, and the firm's willingness to work within the issuer's timeline. A small number of firms dominate the stablecoin-attestation market, and their capacity can become constrained around common year-end reporting windows, so issuers benefit from engaging the auditor months in advance of the first cut-off date. The engagement letter should specify the service-level agreement – typically the number of business days from the cut-off to the delivery of the draft report – and should provide for additional ad-hoc attestations if the regulator or a banking partner requires one outside the scheduled cycle. The issuer who waits until the compliance deadline to approach the auditor will struggle to secure a slot and may miss the filing window, triggering a reportable breach.
Building the internal reserve-monitoring function
The external attestation auditor verifies the position at a single snapshot. The issuer's internal function monitors reserve coverage continuously and flags emerging gaps before the next attestation cycle. Best practice is a daily end-of-day reconciliation of on-chain token supply to off-chain reserve balances, with automated alerts if the coverage ratio falls below a pre-set threshold – typically 102 to 105 per cent to provide a working buffer above the regulatory minimum of 100 per cent. The reconciliation process feeds into the issuer's treasury function, which manages the composition and liquidity of the reserve to ensure that redemption requests can be met without breaching coverage.
The monitoring system must integrate real-time or near-real-time data from the on-chain token contract, from each custodian's reporting portal, and from the issuer's banking dashboards. Building that integration requires technical investment – APIs to query blockchain balances, data feeds from custodians, reconciliation logic to handle timing differences between on-chain minting events and off-chain cash settlement – but it is the only way to maintain operational confidence in the reserve position between attestation dates. Issuers who rely on manual spreadsheet reconciliation find that the process is too slow to catch intraday breaches and that errors accumulate as the reserve structure scales. The cost of the monitoring system is an order of magnitude less than the reputational and regulatory cost of a surprise shortfall discovered only when the auditor performs the next attestation.
What happens if the auditor qualifies the report
A qualified opinion means the auditor could not confirm one or more material elements of the reserve verification or identified a shortfall or non-compliance. The qualification must be disclosed in the published report, and the issuer must notify the regulator immediately under the standard breach-reporting obligation. The immediate next step is to determine whether the issue is one of evidence – for instance, a custodian confirmation arrived late – or substance – the reserve genuinely fell short. If it is an evidence issue, the issuer works with the auditor and the custodian to secure the missing confirmation and to issue a supplemental attestation that lifts the qualification. If it is a substantive shortfall, the issuer must implement the remediation plan filed with the regulator: inject additional reserve assets, redeem tokens to bring supply into line with coverage, or both.
The market impact of a qualified report can be swift. Sophisticated holders monitor published attestations, and a qualification triggers redemption requests within hours. The issuer's liquidity buffers must be sized to handle a surge, and the fiat payment rails must be pre-cleared to process high volumes. Where the issuer holds part of the reserve in less-liquid instruments – for instance, three-month Treasury bills – it may need to monetise those instruments quickly at a discount to meet redemptions, crystallising a loss that compounds the shortfall. That dynamic is the reason most regimes impose composition limits on the reserve and require a minimum proportion in cash or overnight deposits. The issuer who structures the reserve solely for yield – holding long-dated instruments that offer a better return – creates a liquidity mismatch that a qualified attestation exposes.
If a reserve-attestation deadline is approaching and you have not yet engaged an auditor or structured the monitoring function, reach out to OBOLUS now at info@oboluslaw.com. The process runs on a fixed timeline from the cut-off date. Engaging late reduces the auditor's time to confirm balances and increases the risk of a delayed report or a qualification due to incomplete evidence. We work with issuers to triage the attestation build – identifying the right auditor, drafting the scope letter, coordinating custodian confirmations, and managing the filing with the regulator – so that the first attestation cycle runs clean and the function is embedded into operations for the cycles that follow.
Related at OBOLUS
- Banking, Payments & EMI Onboarding for Digital-Asset Businesses – securing payment rails and banking relationships that support stablecoin issuance and redemption flows.
- Crypto Promotions and Marketing Rules Across Major Regimes – managing the disclosure and approval obligations when marketing a stablecoin to holders in multiple jurisdictions.
- How to Safeguard Client Funds Compliantly – applying the safeguarding and segregation rules that intersect with reserve-management obligations for issuers holding user deposits.
FAQ
Can a crypto firm access banking under this regime?
Access to banking for a stablecoin issuer depends on the issuer's licence, the reserve-attestation function, and the banking counterparty's risk appetite. Payment institutions and e-money issuers under MiCA or equivalent regimes can typically open accounts with European banks once licensed. Outside the EU, an issuer with a VASP or payment-institution licence and a published attestation function has a stronger banking case than an unlicensed operator with no public disclosure. Banks assess the issuer's reserve-management systems and audit trail as core due-diligence points; a clean quarterly attestation record materially improves the onboarding outcome.
What safeguarding applies to client funds?
Safeguarding obligations depend on whether the issuer holds client fiat as part of the reserve or only holds the reserve to back issued tokens. An e-money issuer holding customer deposits pending token issuance must safeguard those funds under the applicable e-money or payment-institution rules, typically in a segregated account at an authorised credit institution. The reserve backing already-issued tokens is not client money in the traditional sense – it is the issuer's asset, held to satisfy the redemption obligation – but the reserve-composition and attestation rules serve a parallel protective function. If the issuer also operates an exchange or custodial wallet, client crypto-asset segregation rules apply separately and run alongside the reserve-attestation obligation.
Which payment licence is required?
The licence type depends on the issuer's activities and target market. In the EU under MiCA, an e-money token issuer needs e-money institution authorisation or a credit-institution licence; an asset-referenced token issuer needs CASP authorisation with the ART add-on. Outside the EU, a payment-token issuer typically applies for a payment-institution licence or the local equivalent – for instance, a major payment institution licence in Singapore or a payment-token issuer registration under VARA in Dubai. The licence must cover issuance and redemption activities; if the issuer also operates secondary-market trading or custody, additional licence categories apply. The attestation obligation attaches to the issuance licence and does not vary by the secondary activities.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70-plus jurisdictions, on disputes and on-chain asset recovery across 25-plus forums, and on the tax, banking and compliance that sit around them. Digital assets are the entirety of our practice. Stablecoin issuers turn to us to map the reserve-attestation build and to coordinate the licensing, auditor engagement and regulatory filing across multiple hubs, so that the first attestation cycle runs clean and the function embeds into operations for the cycles that follow. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in digital-asset licensing frameworks, reserve-attestation systems for stablecoin issuers, and cross-border regulatory coordination for token projects spanning the EU, UAE, Singapore and offshore hubs.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.