This guide is for importer-side users who need a practical walkthrough of onboarding, agreement state, claim creation, claim detail pages, representative access, and email-delivery confirmation inside the importer portal.
Main workspace /dashboard17 screenshot-backed walkthroughs
At a glance
Use the importer workspace to onboard the company, create claims, manage documents, and coordinate with brokers or attorneys from one portal.
Set up the importer account and company profile first
Everything in the importer portal hangs off company onboarding. This flow creates the importer record, sets the contact baseline, and unlocks the claims workspace.
Start on Company Registration to create the importer record and primary contact context.
Complete Import Profile so the platform has the business details, entry posture, and contact data that later claims, broker relationships, and attorney access depend on.
Use Eligibility to confirm whether the current importer and entry pattern fit the workflow before expecting claim creation or downstream invite flows to behave normally.
If a broker invited you, sign in with the invited email so the broker relationship attaches to the same importer record instead of creating parallel identities.
Onboarding is not a cosmetic checklist; it establishes the company object the rest of the portal reads from.
When onboarding is complete, the importer landing area becomes the dashboard at /dashboard.
Company Registration is the importer starting point. It creates the account context every later claim, document, broker, and attorney workflow depends on.Import Profile captures the importer-side business and contact details the claims workspace uses later.Eligibility is where the importer confirms the current business and entry posture match the supported refund workflow.
Complete the agreement flow or use the existing-protester branch
After the importer profile is in place, DutyClaims makes the agreement state explicit and keeps the alternate existing-protester path separate from the standard new-claim journey.
Use Agreement to review the participation terms before downstream claim activity depends on them.
After signature, confirm the completion state instead of assuming the agreement persisted silently.
If the importer already filed a protest outside the normal new-claim flow, use the existing-protester branch rather than repeating brand-new onboarding logic.
Agreement completion affects what the importer and broker can do next.
The existing-protester route is a deliberate alternate entry path, not a hidden workaround.
Agreement review is its own step so the importer can see when portal access is blocked by signature state rather than by a product error.The completion page makes agreement persistence visible before the importer moves into claim work.Importers who already filed a protest use a different path so the product can adapt to that posture instead of pretending it is a brand-new claim.
Run daily work from Overview, My Claims, and claim details
The importer dashboard is the daily command center. It surfaces next actions, claim inventory, and the record-level detail needed to answer status questions quickly.
/dashboard/dashboard/claims/dashboard/claims/[id]
Start on Overview each day to see open offer activity, unfinished setup, and the fastest route back into active claim work.
Use My Claims as the long-running system of record for search, saved views, and status filtering across the claim portfolio.
Open a claim detail page when the question is about one record's calculation state, results, or whether additional upload work is still required.
Overview is for next actions.
My Claims is for queue management.
Claim detail is for one-record troubleshooting or review.
Overview is the importer control room. It shows offer status, guided next steps, and the quickest routes back into claim work.My Claims keeps saved views, filters, and claim status in one queue so the importer does not need an off-platform spreadsheet.Claim detail is where one record stops being abstract. Use it to understand whether results exist yet and what the next record-level action should be.
Create new claims and manage source documents from claim-level screens
New claims and supporting documents stay attached to the importer's working record. Claim creation starts on the upload route, then document handling moves to the claim-specific page.
/dashboard/upload/dashboard/claims/[id]/documents
Use New Claim to upload an ACE CSV or start manual data entry for a fresh claim.
After the claim exists, move to the claim document page to upload Form 7501s, ACE-derived CSVs, and supporting evidence tied to that specific record.
Use the claim document surface rather than email threads as the source of truth for what has actually been uploaded.
Claim creation starts on /dashboard/upload.
Document management happens on the claim record, not in account settings.
New Claim is the intake surface for ACE CSV uploads and new importer claim work.Claim documents keep source files attached to the record itself so document readiness does not get lost in inbox history.
Manage broker delegation and attorney access without leaving the importer portal
Importers do not need separate trackers for representatives. Broker and attorney relationships each have dedicated, auditable pages inside the importer workspace.
/dashboard/broker/dashboard/attorneys
Open My Broker to confirm who is assigned, whether delegation is active, and what the broker is currently allowed to do on the importer's behalf.
Open Attorney Access to invite counsel, review pending representation changes, and verify which legal relationships are active before sharing sensitive case context.
Use these pages before escalating a permissions question, because most access-state answers are already visible here.
Broker delegation and attorney representation are separate permission tracks.
DutyClaims keeps them explicit so authority changes remain auditable.
My Broker makes delegation state visible so the importer can tell whether the broker is attached and what still needs approval.Attorney Access is the importer-side authority surface for invitations, pending representation changes, and active legal relationships.
Use Preferences to confirm delivery settings and recent email behavior
Preferences is the importer-side maintenance layer for notification settings and outbound email history when someone needs to confirm what was sent.
/dashboard/preferences
Use Preferences to review importer-facing email settings and recent outbound delivery activity.
Check this page when someone asks whether a reminder, agreement, or status email was actually sent before assuming a provider or product failure.
Treat email as a notification layer; claim state and document state still live on the portal pages themselves.
Preferences is the delivery-debugging layer for importers.
The portal remains the system of record for claims and documents.
Preferences is where importer-side notification settings and recent outbound email behavior stay visible.
Use the IEEPA refund estimator to project your refund before creating a claim
The public tariff calculator at /results gives any importer a fast, private estimate of IEEPA refund exposure before they create an account or engage a broker. Upload an ACE CSV or use sample data to see a refund projection, entry-level breakdown, and deadline calendar in seconds.
//results
Go to the homepage and upload an ACE CSV export from your CBP ACE portal, or click Try it to load sample data.
Click Calculate My Refund to run the estimator. The page redirects to /results with your data encoded in the URL.
Review the Summary tab first for the headline refund estimate, pathway breakdown, and top impacted entries.
Switch to the By Entry tab to inspect each entry's calculated refund amount, pathway, and urgency tier.
Switch to the Deadline Calendar to see all estimated liquidation deadlines and protest windows laid out month by month.
Use these results to decide whether to create an account and start a formal claim.
No account is required. The estimator is public and runs entirely in the browser.
Your data stays in the URL — nothing is sent to DutyClaims servers during the calculation.
Results include pathway-level breakdowns (PSC vs. protest) and statutory deadline windows.
The estimate is based on your uploaded entries; accuracy improves with a complete ACE export.
The Summary tab shows the headline IEEPA refund estimate, refund pathway breakdown, and the entries with the highest recovery potential.By Entry breaks the estimate down to the individual shipment level so importers can see which entries drive the most recovery and what filing pathway applies to each.Deadline Calendar maps all estimated liquidation dates, PSC windows, and protest deadlines so importers can judge urgency before engaging a broker or attorney.