GingerOSTrade compliance for Finance
Know what a tariff costs.
When a notice lands, you get the cost by SKU, plant and line, with the basis behind every number.
- Know what a new tariff costs
2 to 3 weeksSame dayIllustrative - Show the basis for every duty line
Days of diggingMinutesIllustrative - Test a plant or supplier first
2 to 3 weeksSame dayIllustrative
A window listing the three Finance jobs on this page: pricing a new tariff, showing the basis for every duty line and testing a plant or supplier. Each row has a small picture of today’s spreadsheet and the number that changes, today’s value struck through next to the GingerOS value, marked Illustrative because these are not measured results.
Price a tariff the day it lands.
The notice is matched to your SKUs and priced by line and plant.
Illustration with sample data: an old-style spreadsheet runs VLOOKUP on five sample parts from three systems against a Section 232 annex, and three rows return #N/A or #VALUE!. A pinned comment says one ERP stores the code as free text, and a CFO note asks whether the assumed 25% is right.
Illustration with sample data: a GingerOS window for a sample Section 232 notice shows 38 sample SKUs as tiles sized by the duty each adds a year, with 2 unclear SKUs held for compliance and left out of the total. After the card turns, the tiles regroup into one column per product line, and a toggle regroups them by plant.
Each ERP is exported and run through VLOOKUP. FP&A fills the gaps by hand.
Days from notice to a number by SKU
Illustrative
Illustrative comparison, not a measured result: days from a notice to a number by SKU, 2 to 3 weeks today against the same day with GingerOS.
Show the basis for every line.
Every duty line opens its classification record, approver and date.
Illustration with sample data: an old-style spreadsheet of an auditor’s request list, where the support for one duty line’s code is only an email saying “per John”, and a pinned comment says the reason left with John. Other rows show 6 of 20 duty-line bases found, an unreconciled AP statement and an open tax request.
Illustration with sample data: a GingerOS table of three duty lines on a sample entry, each tagged with its basis. Line 4 opens its classification record: the code and its earlier code, four reasons, the approver, the date, how long it is kept and an Export audit pack button.
When audit asks why a line is 8708, the answer sits in one person’s inbox.
Time to show the basis for one duty line
Illustrative
Illustrative comparison, not a measured result: the time to show the basis for one duty line, days of digging today against minutes with GingerOS.
Test a site before you commit.
Run each option on your own parts: origin, duty and missing papers.
Illustration with sample data: an old-style spreadsheet compares three sample site options, Monterrey, Rayong and a target company, by origin, duty and evidence. Rayong’s duty is typed in by hand as 2.5% plus an assumed 25%, a pinned comment says nobody marks the guess, and the target company’s origin and duty are unknown.
Illustration with sample data: a GingerOS scenario compares one sample part made in Monterrey, Mexico or Rayong, Thailand, row by row, from origin result and duty to the net. Rayong has no trade agreement and ends at a net loss, with 2 assumptions marked Estimated.
Each site gets a consultant memo, and duty is one line in the capex model.
Time to rerun one scenario
Illustrative
Illustrative comparison, not a measured result: the time to rerun one scenario, 2 to 3 weeks today against the same day with GingerOS.
Numbers marked Illustrative are not measured results. Your own baseline is set with you before the build.
Questions you’ll probably ask
Is this a refund service?
No. Refunds are a byproduct of good records, won entry by entry. When you ask, we prepare the IEEPA refund file for the 2025 emergency tariffs and our licensed IEEPA refund partner files it, with no guaranteed amount. We never file entries.
Will old errors all land in one quarter?
Not as a surprise. When a code changes, GingerOS lists the past entries it affects and the duty difference in both directions, so you see the size before anything is filed. When to correct, disclose or accrue is decided by you, your counsel and your auditors. Nothing here is legal advice.
How is it priced?
Quoted per project by how complex it is, never per SKU. You get the quote after the Prototype Week and pay a deposit at kickoff, refundable until MVP acceptance. The balance is due on final acceptance.
How do we know it paid off?
Agree the baselines before the build, for example days from notice to exposure or the share of SKUs with written reasoning, and measure them again after go-live.
Do you need our cost or transfer-pricing data?
Not to classify. Origin rules that use regional value content need value inputs; which ones, and who can see them, is agreed up front and limited by role.
Will you guarantee the number?
No one can guarantee a classification. You get a number where every line shows its basis and its approver, so you can document your own reasonable care.
