<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IEEPA tariffs &#8211; Sharretts, Paley, Carter &amp; Blauvelt, P.C.</title>
	<atom:link href="https://spcblaw.com/tag/ieepa-tariffs/feed/" rel="self" type="application/rss+xml" />
	<link>https://spcblaw.com</link>
	<description></description>
	<lastBuildDate>Wed, 09 Sep 2026 19:02:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1</generator>

<image>
	<url>https://spcblaw.com/wp-content/uploads/2025/10/cropped-SPCB-logo-plain-SVG-icon-32x32.png</url>
	<title>IEEPA tariffs &#8211; Sharretts, Paley, Carter &amp; Blauvelt, P.C.</title>
	<link>https://spcblaw.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>CBP Expands CAPE to Entries Flagged for Reconciliation</title>
		<link>https://spcblaw.com/2026/06/24/cbp-expands-cape-reconciliation/</link>
		
		<dc:creator><![CDATA[Geraldine Tourny]]></dc:creator>
		<pubDate>Wed, 24 Jun 2026 18:54:53 +0000</pubDate>
				<category><![CDATA[Client Alerts]]></category>
		<category><![CDATA[CAPE declaration]]></category>
		<category><![CDATA[CAPE refund]]></category>
		<category><![CDATA[customs tariffs]]></category>
		<category><![CDATA[IEEPA duties]]></category>
		<category><![CDATA[IEEPA refunds]]></category>
		<category><![CDATA[IEEPA tariffs]]></category>
		<guid isPermaLink="false">https://spcblaw.com/?p=4118</guid>

					<description><![CDATA[U.S. Customs and Border Protection has announced that effective June 29, 2026, CAPE will accept entries flagged for reconciliation (entry types 01, 02, and 06) for which the related reconciliation entry (entry type 09) has not yet been filed. CBP confirmed that all filing and processing requirements from the first phase of CAPE remain in...]]></description>
										<content:encoded><![CDATA[<p align="justify">U.S. Customs and Border Protection has <a href="https://content.govdelivery.com/accounts/USDHSCBP/bulletins/41d65dd" target="_blank" rel="noopener">announced</a> that effective June 29, 2026, CAPE will accept entries flagged for reconciliation (entry types 01, 02, and 06) for which the related reconciliation entry (entry type 09) has not yet been filed.</p>
<p align="justify">CBP confirmed that all filing and processing requirements from the first phase of CAPE remain in effect; notably, acceptance remains limited to unliquidated entries and entries within 80 days of liquidation.</p>
<p align="justify">Once an entry flagged for reconciliation is accepted on a CAPE declaration, the corresponding reconciliation entry may then be filed.</p>
<p align="justify">However, CBP cautioned that if the reconciliation filing deadline is approaching (e.g. where fewer than 30 days remain), priority should be given to filing the reconciliation entry to avoid missing the deadline.</p>
<p align="justify">CBP also noted that while entries flagged for reconciliation for which a reconciliation entry is already on file are not yet covered by this functionality, those entries are expected to be addressed in a future phase of CAPE development.</p>
<p align="justify">Please <a href="https://spcblaw.com/about-us/contact/">contact us</a> with any additional questions.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Government Announces Intent to Appeal CIT Order on IEEPA Duty Refunds</title>
		<link>https://spcblaw.com/2026/05/31/appeal-ieepa-refund-order/</link>
		
		<dc:creator><![CDATA[Geraldine Tourny]]></dc:creator>
		<pubDate>Sun, 31 May 2026 19:33:58 +0000</pubDate>
				<category><![CDATA[Client Alerts]]></category>
		<category><![CDATA[Court of International Trade]]></category>
		<category><![CDATA[customs tariffs]]></category>
		<category><![CDATA[IEEPA duties]]></category>
		<category><![CDATA[IEEPA litigation]]></category>
		<category><![CDATA[IEEPA refunds]]></category>
		<category><![CDATA[IEEPA tariffs]]></category>
		<guid isPermaLink="false">https://spcblaw.com/?p=4101</guid>

					<description><![CDATA[The Government has now formally announced its intention to appeal the U.S. Court of International Trade’s order requiring refunds of IEEPA duties on finally liquidated entries. Specifically, the Government intends to challenge the Court’s authority to order refunds for importers that are not parties to the litigation and whose entries have become final. Accordingly, companies...]]></description>
										<content:encoded><![CDATA[<p align="justify">The Government has now formally announced its intention to appeal the U.S. Court of International Trade’s order requiring refunds of IEEPA duties on finally liquidated entries. Specifically, the Government <a href="https://insidetrade.com/daily-news/trump-administration-will-appeal-universal-tariff-refund-order" target="_blank" rel="noopener">intends</a> to challenge the Court’s authority to order refunds for importers that are not parties to the litigation and whose entries have become final.</p>
<p align="justify">Accordingly, companies that have not yet joined the litigation, but have potential refunds associated with entries that liquidated more than 90 days ago, should consider filing their own protective pleading with the CIT as soon as possible.</p>
<p align="justify">In this regard, given the Government’s position, it is increasingly likely that a company-specific court order will be required to recover refunds on finally liquidated entries.</p>
<p align="justify">Please <a href="https://spcblaw.com/2026/05/08/section-122-tariffs-unlawful/#:~:text=Follow%20us%3A-,CONTACT%20US,-Home">contact us</a> if you are interested in filing. We will continue to keep you apprised of further developments.</p>
<p>&nbsp;</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
