Connect with us

Accounting

EU AI Act likely not a hassle for most use cases

Published

on

While the EU AI Act—which officially went into force about a year ago—creates a number of new obligations regarding AI, its more stringent mandates apply only to the minority of organizations involved with high-risk use cases, with the rest able to mostly get by with what they already do to comply with the EU’s General Data Protection Regulation. 

This is according to Dr. Rafae Bhatti, chief information officer of Thunes Financial Services and a speaker at the Governance, Risk Management and Control conference in New York, hosted annually by the Institute of Internal Auditors and ISACA (formerly the Information Systems Audit and Control Association.) While navigating the EU AI Act might seem intimidating to people, he said that, for the majority of organizations, the things they’re expected to do are better thought of as extensions of current regulations with which many are already complying. 

“It is not completely a situation where you need to start from scratch. You may already have certain cybersecurity controls, certain data privacy controls, and that is one of the important pieces of guidance that I’d like to share with you so that you can feel a little bit more comfortable about not having to start from scratch as it relates to cybersecurity and data privacy,” he said. 

EU AI Act

tanaonte – stock.adobe.com

Before anything, he said, understand the scope of the regulations, which vary based on the AI in question as well as the specific use case toward which it is applied. Certain use cases, such as social scoring or real-time surveillance, are outright prohibited. Below that are high-risk use cases that involve industries such as health care, employment, education and other sectors with major societal implications. After this are those who fall in the limited risk category, which includes chatbots and image generators, followed by those deemed minimal risk, such as AI-enabled video games or spam filters. 

Another way to think of these various risk levels and their consequences, said Bhatti, is in terms of “career ending, sleepless nights, committee meetings or PowerPoints.” 

The good news, he said, is that very few organizations are involved in prohibited use cases, and even those involved in high-risk ones will be uncommon considering they’re restricted to specific sectors. 

“If you are a company that is only creating an application which is a game, you are probably not subject to most of the requirements. If you’re just a shopping website and not doing anything to do with employment or health care or education, there is going to be very minimal you’re required to do,” he said. 

Anything of a limited or minimal risk, he said, doesn’t trigger the AI-specific requirements of the EU AI Act, meaning entities should just continue doing what they’re already doing to comply with existing regulatory frameworks, “and if you’re doing it well you should be OK,” said Bhatti, adding that generally, “the only thing you still have to worry about is GDPR principles.” 

If something is considered high-risk, however, not only is it subject to greater GDPR scrutiny—meaning “if previously you were not taking it seriously, now is the time to take it seriously because there will be a requirement for a conformity assessment.” But some of the AI-specific measures also kick in. Part of this is more stringent security requirements, such as controlling for AI-specific attacks such as data poisoning and prompt injections (broadly referred to as ‘adversarial robustness’ controls.) 

Beyond this, those involved in high-risk use cases must also consider fairness and nondiscrimination controls; transparency and explainability controls; accountability and human oversight. What exactly counts within these categories, though, can be a matter of debate, starting with whether the use case is even high risk or not. 

“Is this AI high risk? The lawyer might say, ‘legally yes.’ The engineer might say, ‘technically no.’  They are both at medium risk of losing their careers. This is going to be a back and forth. Just be prepared to have that argument,” he said. 

Then there are the other controls that, themselves, can rest on slippery definitions. For instance, the fairness and nondiscrimination control requirement ostensibly is to mitigate the effect of bias in AI models. But the definition of these things can be tricky. An engineer might ask what exactly is the definition of fairness; a lawyer might answer, “whatever keeps us out of court,” which he conceded was an unhelpful answer, but one that some will likely use. 

Similarly, while explainability might seem like a simple enough concept at first glance, the detail and granularity of these explanations can be a point of contention. Some people may go into exhaustive detail about how their AI works while others might try to say, “It works in mysterious ways.” Such an answer is not necessarily in the spirit of the rule, but some try to use it anyway. However, he said such questions are only required to be addressed by those using high risk use cases. 

Transparency controls will be more common, as they are required for those involved in limited-risk use cases. Generally, he said, people need to know that they’re interacting with AI, such as through a privacy clause that tells users the system uses it to process their data, or even a note in the interface. However one does it, following this regulation needs documentation as well as a conformity assessment. 

The last bucket is accountability. Who is responsible for the AI? He cautioned against taking a cavalier approach to this question. There needs to be real accountability, along with the ability to escalate further up the chain. 

“Your answer shouldn’t be that it leads to a voicemail. A 1-800 number is not going to cut it, an email is not going to cut it,” he said, though noted that only high risk cases require documentation. Still, even if it’s not strictly required, he said it’s a good idea to consider this anyway. 

He stressed that most of the time organizations will only need to account for transparency. This does not, however, mean they should ignore all other controls. While it may not be specifically required to control for fairness and explainability, he said it is likely still a good idea for any organization dealing with AI. 

Bhatti said AI itself can be a valuable tool in complying with the EU AI Act, as it can do things like perform initial risk analyses and gap assessments, as well as monitor and retrieve vast stores of organizational data. However, he cautioned against letting AI agents perform actual remediation steps, as he felt there is still too much risk (noting, for example, how an agent accidentally deleted a company’s entire codebase by accident).

“If someone is trying to convince you that automatic remediation using [AI agents] is happening now, and that you should adopt it, proceed with caution,” he said. He noted that a few years from now “we can get to a point where we have enough confidence with what automatic remediation is doing. But not today.” 

Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Accounting

FASB plans changes in crypto accounting

Published

on

The Financial Accounting Standards Board met this week to discuss its projects on accounting for transfers of cryptocurrency assets and enhancing the disclosures around certain digital assets, such as stablecoins.

Processing Content

During Wednesday’s meeting, FASB’s board made certain tentative decisions, according to a summary posted to FASB’s website. FASB began deliberating the Accounting for transfers of crypto assets project and decided to expand the scope of its guidance in  Subtopic 350-60, Intangibles—Goodwill and Other—Crypto Assets, to address crypto assets that provide the holder with a right to receive another crypto asset. FASB decided to clarify the existing disclosure guidance by providing an example of a tabular disclosure illustrating that wrapped tokens, if they’re significant, would be disclosed separately from other significant crypto asset holdings.

At a future meeting, the board plans to consider clarifying the derecognition guidance for crypto transfer arrangements to assess whether the control of a crypto asset has been transferred.

FASB also began deliberations on the Cash equivalents—disclosure enhancement and classification of certain digital assets project and made a number of decisions.

The board decided to provide illustrative examples in Topic 230, Statement of Cash Flows, to clarify whether certain digital assets such as stablecoins can meet the definition of cash equivalents. It also decided to include the following concepts in the illustrative examples:

  1. Interpretive explanations that link to the current cash equivalents definition;
  2. The amount and composition of reserve assets; and,
  3. The nature of qualifying on-demand, contractual cash redemption rights directly with the issuer.

FASB plans to clarify that an entity should consider compliance with relevant laws and regulations when it’s creating a policy concerning which assets that satisfy the Master Glossary definition of the term “cash equivalents will be treated as cash equivalents.

“I agree with the staff suggestion to look at examples,” said FASB vice chair Hillary Salo. “From my perspective, I think that is going to help level the playing field. People have been making reasonable judgments. I agree with that. And I think that this is really going to help show those goalposts or guardrails of what types of stablecoins would be in the scope of cash equivalents, and which ones would not be in the scope of cash equivalents. I certainly appreciate that approach, and I think it has the least potential impact of unintended consequences, because I do agree with my fellow board members that we shouldn’t be changing the definition of cash equivalents, and it’s a high bar to get into the cash equivalent definition.”

“I’m definitely supportive of not changing the definition of cash equivalents,” said FASB chair Richard Jones. “I believe that’s settled GAAP in a way, and we’re not really seeing a call to change it for broader issues. I am supportive of the example-based approach. The challenge with examples, though, is everybody’s going to want their exact pattern, but that’s not what we’re doing.”

The examples will explain the rationale for how digital assets such as stablecoins do or do not qualify as cash equivalents and give a roadmap for other types of digital assets with varying fact patterns to be able to apply.

“We really don’t want to be as a board facing a situation where something was a cash equivalent and then no longer is at a later date,” said Jones. “That’s not good for anyone, so keeping it as a high bar with certain rigid criteria, I think, is fine.”

Stablecoins are supposed to be pegged to fiat currencies such as U.S. dollars and thus provide more stability to investors. “In my view, while a stablecoin may meet the accounting definition established for cash equivalents, not every one of those stablecoins in the cash equivalent classification represents the same level of risk,” said FASB member Joyce Joseph.

She noted that the capital markets recognize the distinctions and have established a Stablecoin Stability Assessment Framework to evaluate a stablecoin’s ability to maintain its peg to a fiat currency. Such assessments look at the legal and regulatory framework associated with the stablecoin, and provide investors with information that could enable them to do forward-looking assessments about the stability of the stablecoin.

“However, for an investor to consider and utilize such information for a company analysis the financial statement disclosures would need to include information about the stablecoin itself,” Joseph added. “In outreach, the staff learned that investors supported classifying certain stablecoins as cash equivalents when transparent information is available about the entities at which the reserve assets are held. Therefore, in my view, taking all of this into consideration a relevant and informative company disclosure would include providing investors with the name of the stablecoin and the amount of the stablecoin that is classified as a cash equivalent, so investors can independently assess the liquidity risks more meaningfully and more comprehensively by utilizing broader information that is available in the capital markets and its emerging information.”

Such information could include the issuer, reserves, governance and management, she noted, so investors would get a more holistic look at the risks that holding the stablecoin would entail for a given company.

The board decided to require all entities to disclose the significant classes and related amounts of cash equivalents on an annual basis for each period that a statement of financial position is presented.

Entities should apply the amendments related to the classification of certain digital assets as cash equivalents on a modified prospective basis as of the beginning of the annual reporting period in the year of adoption.

FASB decided that entities should apply the amendments related to the disclosure of the significant classes and amounts of cash equivalents on a prospective basis as of the date of the most recent statement of financial position presented in the period of adoption.

The board will allow early adoption in both interim and annual reporting periods in which financial statements have not been issued or made available for issuance.

FASB also decided to permit entities to adopt the amendments to be illustrated in the examples related to the classification of certain digital assets as cash equivalents without the need to perform a preferability assessment as described in Topic 250, Accounting Changes and Error Corrections.

The board directed the staff to draft a proposed accounting standards update to be voted on by written ballot. The proposed update will have a 90-day comment period.

Continue Reading

Accounting

Lawmakers propose tax and IRS bills as filing season ends

Published

on

Senators introduced several pieces of tax-related legislation this week, including measures aimed at improving customer service at the Internal Revenue Service, cracking down on tax evasion and curbing the carried interest tax break, in addition to efforts in the House to repeal the Corporate Transparency Act.

Processing Content

Senators Bill Cassidy, R-Louisiana, and Mark Warner, D-Virginia, teamed up on introducing a bipartisan bill, the Improving IRS Customer Service Act, which would expand information on refunds available to taxpayers online and help taxpayers with payment plans if they need it.

The bill would establish a dashboard to inform taxpayers of backlogs and wait times; expand electronic access to information and refunds; expand callback technology and online accounts; and inform individuals facing economic hardship about collection alternatives.

“Taxpayers deserve a simple, stress-free experience when dealing with the IRS,” Cassidy said in a statement Wednesday. “This bill makes the process quicker and easier for taxpayers to get the information they need.”

He also mentioned the bill during a Senate Finance Committee hearing about tax season when questioning IRS CEO Frank Bisignano. During the hearing, Cassidy secured a commitment from Bisignano that the IRS would work with Congress to implement these reforms if the legislation were signed into law.

“I’m happy to meet with the team … and do all I can to make it as good as you want it to be,” said Bisignano.

“My bill would equip the IRS with the legislative mandate to create an online dashboard so that taxpayers can monitor average call wait time and budget time accordingly,” said Cassidy. He noted that the bill would allow a callback for taxpayers that might need to wait longer than five minutes to speak to a representative, and establish a program to identify and support taxpayers struggling to make ends meet by providing information about alternative payment methods, such as installments, partial payments and offers in compromise. 

“I know people are kind of desperate and don’t know where to turn for cash, so I think this could really ease anxiety,” he added. “This legislation is bipartisan and is likely to pass this Congress.”

Cassidy and Warner introduced the Improving IRS Customer Service Act in 2024. Last year, Warner wrote to National Taxpayer Advocate Erin Collins at the IRS regarding the underperforming Taxpayer Advocate Service office in Richmond, Virginia, and advocated against any harmful personnel decisions that would negatively impact taxpayers.

“Taxpayers shouldn’t have to jump through hoops to get basic answers from the IRS — and in the last year, those challenges have only gotten worse,” Warner said in a statement. “I am glad to reintroduce this bipartisan legislation on Tax Day to ease some of this frustration by increasing clear communication and making IRS resources more readily available.”

Stop CHEATERS Act

Also on Tax Day, a group of Senate Democrats and an independent who usually caucuses with Democrats teamed up to introduce the Stop Corporations and High Earners from Avoiding Taxes and Enforce the Rules Strictly (Stop CHEATERS) Act.

Senate Finance Committee ranking member Ron Wyden, D-Oregon, joined with Senators Angus King, I-Maine, Elizabeth Warren, D-Massachusetts, Tim Kaine, D-Virginia, and Sheldon Whitehouse, D-Rhode Island. The bill would provide additional funding for the IRS to strengthen and expand tax collection services and systems and crack down on tax cheating by the wealthy.

“Wealthy tax cheats and scofflaw corporations are stealing billions and billions from the American people by refusing to pay what they legally owe, and far too many of them are getting a free pass because Republicans gutted the enforcement capacity of the IRS,” Wyden said in a statement. “A rich tax cheat who shelters mountains of cash among a web of shell companies and passthroughs is likelier to be struck by lightning than face an IRS audit, and Republicans want to keep it that way. This bill is about making sure the IRS has the resources it needs to go after wealthy tax cheats while improving customer service for the vast majority of American taxpayers who follow the law every year.”

Earlier this week. Wyden also introduced two other pieces of legislation aimed at cracking down on the use of grantor retained annuity trusts and private placement life insurance contracts to avoid or minimize taxes.

The Stop CHEATERS Act would provide the IRS with additional funding for tax enforcement focused upon high-income tax evasion, technology operations support, systems modernization, and taxpayer services like free tax-payer assistance.

“As Congress seeks ways to fund much-needed policy priorities and address our growing national debt, there is one common sense solution that should have unanimous bipartisan support: let’s enforce the tax laws already on the books,” said King in a statement. “Our legislation will make sure the IRS has the resources it needs to confront the gap between taxes owed and taxes paid – while ensuring that our tax enforcement professionals are focused on the high-income earners who account for the most tax evasion. This is a serious problem with an easy solution; let’s pass this legislation and make sure every American pays what they owe in taxes.”

Carried interest

Wyden, King and Whitehouse also teamed up on another bill Thursday to close the carried interest tax break for hedge fund managers that Democrats as well as President Trump have pledged for years to curtail. The tax break mainly benefits hedge fund managers, private equity firm partners and venture capitalists, who have lobbied heavily to defeat attempts to end the lucrative tax break. The tax break was scaled back somewhat under the Tax Cuts and Jobs Act of 2017.

Carried interest is a form of compensation received by a fund manager in exchange for investment management services, according to a summary of the bill. A carried interest entitles a fund manager to future profits of a partnership, also known as a “profits interest.” Under current law, a fund manager is generally not taxed when a profits interest is issued and only pays tax when income is realized by the partnership, often in connection with  the sale of an investment that happens years down the road. Not only does this allow a fund manager to defer paying tax, but the eventual income from the partnership almost always takes the form of capital gain income, taxed at a preferential rate of 23.8% compared to the top rate of 40.8% for wage-like income.  

Under the bill, the Ending the Carried Interest Loophole Act, fund managers would be required to recognize deemed compensation income each year and to pay annual tax on that amount, preventing them from deferring payment of taxes on wage-like income. A fund manager’s compensation income would be taxed similar to wages on an employee’s W-2, subject to ordinary income rates and self-employment taxes.   

“Our tax code is rigged to favor ultra-wealthy investors who know how to game the system to dodge paying a fair share, and there is no better example of how it works in practice than the carried interest loophole,” Wyden said in a statement. “For several decades now we’ve had a tax system that rewards the accumulation of wealth by the rich while punishing middle-class wage earners, and the effect of that system has been the strangulation of prosperity and opportunity for everybody but the ultra-wealthy. There are a lot of problems to fix to restore fairness and common sense to our tax code, and closing the carried interest loophole is a great place to start.”

Repealing Corporate Transparency Act

The House Financial Services Committee is also planning to markup a bill next Tuesday that would fully repeal the Corporate Transparency Act, which has already been significantly scaled back under the Trump administration to only require beneficial ownership information reporting by foreign companies to FinCEN, the Treasury Department’s Financial Crimes Enforcement Network. 

If enacted, the repeal would eliminate beneficial ownership reporting requirements, removing a transparency measure designed to help law enforcement and national security officials identify who is behind U.S. companies. 

“This repeal would turn the United States back into one of the easiest places in the world to set up anonymous shell companies, something Congress worked for years to fix,” said Erica Hanichak, deputy director of the FACT Coalition, in a statement. “These entities are routinely used to facilitate corruption, financial crime, and abuse. Rolling back the CTA doesn’t just weaken transparency, it signals to bad actors around the world that the U.S. is once again open for illicit business.”

Continue Reading

Accounting

IRS struggles against nonfilers with large foreign bank accounts

Published

on

The Internal Revenue Service rarely penalizes taxpayers who have high balances in foreign bank accounts and fail to file the proper forms, according to a new report.

Processing Content

The report, released Tuesday by the Treasury Inspector General for Tax Administration, examined Foreign Account Tax Compliance Act, also known as FATCA, which was included as part of a 2010 law in an effort to tax income held by U.S. citizens in foreign bank accounts by requiring financial institutions abroad to share information with the tax authorities. 

Taxpayers with specified foreign financial assets that meet a certain dollar threshold are also required to report the information to the IRS by filing Form 8938. Failure to file the form can result in penalties of up to $60,000. However, TIGTA’s previous reports have demonstrated that the IRS rarely enforces these penalties. 

The IRS created an Offshore Private Banking Campaign initiative to address tax noncompliance related to taxpayers’ failure to file Form 8938 and information reporting associated with offshore banking accounts, but it’s had limited success.

Even though the initiative identified hundreds of individual taxpayers with significant foreign bank account deposits who failed to file Forms 8938, the campaign only resulted in relatively few taxpayer examinations and a small number of nonfiling penalties. The campaign identified 405 taxpayers with significant foreign account balances who appeared to be noncompliant with their FATCA reporting requirements.

The IRS used two ways to address the 405 noncompliant taxpayers: referral for examinations and the issuance of letters to them.

  • 164 taxpayers (who had an average unreported foreign account balance of $1.3 billion) were referred for possible examination, but only 12 of the 164 were examined, with five having $39.7 million in additional tax and $80,000 in penalties assessed.
  • 241 noncompliant taxpayers (who had an average unreported account balance of $377 million) received a combination of 225 educational letters (requiring no response from the taxpayers) and 16 soft letters (requiring taxpayers to respond). None of the 241 taxpayers were assessed the initial $10,000 FATCA nonfiling penalty.

“While taxpayers can hold offshore banking accounts for a number of legitimate reasons, some taxpayers have also used them to hide income and evade taxes,” said the report. 

Significant assets and income are factors considered by the IRS when assessing whether taxpayers intentionally evaded their tax responsibilities, the report noted. Given the large size of the average unreported foreign account balances, these taxpayers probably have higher levels of sophistication and an awareness of their obligation to comply with the law. 

TIGTA believes the IRS needs to establish specific performance measures to determine the effectiveness of the FATCA program. “If the IRS does not plan to enforce the FATCA provisions even where obvious noncompliance is identified, it should at least quantify the enforcement impact of its efforts,” said the report. “This will ensure that IRS decision makers have the information they need to determine if the FATCA program is worth the investment and improves taxpayer compliance. 

TIGTA made three recommendations in the report, including revising Campaign 896 processes to include assessing FATCA failure to file penalties; assessing the viability of using Form 1099 data to identify Form 8938 nonfilers; and implementing additional performance measures to give decision makers comprehensive information about the effectiveness of the FATCA program. The IRS disagreed with two of TIGTA’s recommendations and partially agreed with the remaining recommendation. IRS officials didn’t agree to assess penalties in Campaign 896 or with implementing performance measures to assess the effectiveness of the FATCA program. 

“From our perspective, TIGTA’s conclusions regarding IRS Campaign 896 are based, in part, on a misguided premise and overgeneralizations, including the treatment of ‘potential noncompliance’ as tantamount to ‘egregious noncompliance’ that warrants a monetary penalty without contemplating the variety of justifications that may exempt a taxpayer from having to file Form 8938,” wrote Mabeline Baldwin, acting commissioner of the IRS’s Large Business and International Division, in response to the report. 

Continue Reading

Trending