Enterprise payment infrastructure is moving faster than most finance teams realise. The gap that creates isn’t a technology problem but an operational one that shows up in the close, audit queries, and eventually the data room.

The PXP and Stable partnership is a good example of how quickly this is moving.

In April 2026, PXP, a global omnichannel payment platform processing more than €30 billion annually, announced a strategic stablecoin-focused partnership with Stable, a Layer 1 blockchain designed for financial transactions. The partnership brings stablecoin settlement directly into PXP's existing infrastructure, the same platform merchants are already using to process billions in revenue. Merchants can now settle in digital dollars without leaving the system they're already running. Stablecoin transaction volume grew 83% between July 2024 and July 2025, according to TRM Labs. This isn't a pilot anymore but core infrastructure.

Most growth-stage finance teams are running reporting, reconciliation, and close processes built around a specific set of assumptions: transactions settle through traditional banking rails, in fiat currency, through counterparties your bank already knows. When a platform like PXP adds stablecoin settlement, those assumptions quietly stop being true but without anyone in finance getting a memo about it. The technology isn’t the problem but operational readiness.

Why Stablecoin Settlement Changes the Accounting Workflow

When a merchant settles in USDC or USDT, the transaction hits a wallet first, not a bank account. There's a conversion step between wallet and fiat, which takes time and involves a new counterparty. This creates a gap in treasury visibility that most finance teams aren't set up to monitor. During that window, you have an asset that isn't cash, isn't in your bank feed, and probably isn't flowing into your ERP automatically.

Settlement timing differences compound the problem. Stablecoin transactions can settle in seconds, but the downstream reconciliation (matching wallet receipts to invoices, converting to fiat, recording in the ledger) often still runs on manual or semi-manual workflows. The payment moved faster than the process.

New counterparties enter the flow too. Custody providers, conversion platforms, and blockchain infrastructure none of these look like the bank relationships your existing controls were designed around. Your auditors will want to understand them but most finance teams don't have a clean answer ready.

The Gap Between Wallet Receipt and Ledger Entry 

ERP systems weren't built for this. They were designed around fiat, traditional banking rails, and counterparties with routing numbers. Stablecoin receipts don't map neatly into that structure. The result is usually a workaround: manual journal entries, spreadsheet-based reconciliation, or a lag between when cash effectively arrived and when the books reflect it. This lag is where the operational risk lives.

Stablecoins are the current example. But the underlying problem, payment rails outpacing the workflows built to account for them, isn't unique to crypto. It's what happens any time settlement infrastructure changes faster than ERP configuration, control design, or close processes do. Most finance teams have been here before with new payment types. The difference now is the pace.

The Accounting Questions New Payment Rails Introduce

Asset Classification The most immediate question is classification. Is USDT or USDC a cash equivalent, a financial asset, or an intangible asset? Most accounting frameworks don't have a dedicated category for assets that behave like currency but don't sit in a bank account. Under IFRS, stablecoins typically fall outside the definition of cash and cash equivalents, which means they sit on the balance sheet as something else, usually an intangible asset or a financial instrument, with different measurement and disclosure requirements.

Revenue Recognition Revenue recognition is the next problem. If a customer pays in a non-traditional settlement asset, when is revenue recognised: at the point of receipt, at the point of conversion to fiat, or somewhere in between? If the asset moves in value between those two points, even fractionally, that movement needs to be accounted for.

Unrealised Gain and Loss Unrealised gain and loss treatment follows. Stablecoins are designed to hold their peg, but they don't always. USDT has traded as low as $0.96 in periods of market stress. Any asset held on the balance sheet, even briefly, requires fair value movements to be assessed and potentially recognised.

The Receipt-to-Conversion Window The window between receipt and conversion is its own accounting period. What's the asset worth at period end if it hasn't converted yet? What rate do you use? Who signs off on that judgement? These questions apply to any settlement asset that isn't immediately fungible with cash.

Audit Evidence Blockchain transactions are publicly verifiable, but that doesn't make them automatically audit-ready. Your auditors will want to confirm wallet ownership, trace transactions to source documents, and understand the control environment around custody. For finance teams used to bank statements as the primary audit evidence, that's a different kind of conversation.

What Auditors and Investors Will Actually Look For

The data room question isn't whether you've adopted a new payment rail. It's whether your finance function kept up with the decision.

Auditors and investors doing diligence on a business processing non-traditional payment types will look for a specific set of things to determine whether the numbers can be trusted:

Documented Accounting Policy: The first is a documented accounting policy. How does the business classify the settlement asset on the balance sheet? When is revenue recognised? How are conversion gains and losses treated? These policies need to exist in writing, be applied consistently, and predate the audit. Policies written after the auditor asks the question aren't policies, they're responses.

Consistent Period Treatment: Consistent period treatment matters more than most finance teams expect. If a digital asset was treated as a cash equivalent in Q1 and an intangible asset in Q3, that inconsistency will surface. Auditors will want to understand why, and investors will want to understand what it means for the comparability of reported numbers.

Traceable Reconciliation Evidence: Traceable reconciliation evidence is the practical test. Can you show a clean, documented trail from transaction receipt to ledger entry to financial statement line? Each step needs to connect to the next. Gaps in that trail are audit findings, regardless of what payment rail created them.

Close Timing Metrics: Close timing metrics will also be scrutinised. If your close is taking longer quarter over quarter, that's a signal. It suggests your processes aren't keeping pace with transaction volume, which is exactly the operational risk this piece is about.

Internal Controls Around Non-Traditional Settlement Assets: Finally, internal controls around non-traditional settlement assets. Who has access to wallets or custody accounts? What's the authorisation process for conversion? How are access credentials managed and by whom?

A business that can answer all of these cleanly understood what it was taking on when it adopted a new payment type. Most can't answer them cleanly. That's the gap.

What Happens When Finance Doesn't Keep Up

When finance doesn't keep pace with a new payment type, the problems surface in familiar places: slower closes, fragmented audit trails, inconsistent accounting policies, and numbers that are harder to defend than they should be when the data room opens. 

This isn't unique to blockchain-based payment rails. It's what happens at every inflection point where settlement infrastructure moves faster than the finance function around it. The businesses that navigate it cleanly tend to have one thing in common: someone embedded in the finance function who has seen the transition before, knows which questions to ask early, and can build the right processes before volume forces the issue.

That's what PIF Advisory does. PIF works with growth-stage businesses as an embedded finance partner, not a periodic reviewer. That means being in the room when payment decisions are made, not called in afterwards to explain why the books don't close cleanly.

If your business is adopting new payment rails, expanding into new markets, or approaching a fundraise or diligence process, the time to get the finance function right is before you need it to be. 

Get in touch with PIF Advisory Today