When an FOB‑source order triggers an IPAC settlement, what’s really happening?
You’ve probably stared at a purchase order, saw “FOB Source” in the terms, and then later got a strange “IPAC Settlement” notice on your accounting screen. It feels like two different worlds colliding—shipping jargon on one side, finance acronyms on the other. In practice, the two are linked tighter than you’d think, and ignoring the connection can cost you time, money, and a lot of head‑scratching That's the whole idea..
Below is the full rundown: what the phrase actually means, why it matters to anyone who ships or pays for goods, the step‑by‑step flow that turns an FOB‑source order into an IPAC settlement, the pitfalls most people fall into, and a handful of tips that actually work in the real world.
What Is an FOB‑Source Order?
FOB stands for Free On Board, a trade term that tells you who owns the goods—and the risk—at which point in the shipping journey. Which means “FOB Source” (sometimes written “FOB Origin”) means the seller’s responsibility ends the moment the goods leave their dock. From that moment on, the buyer picks up the freight cost, insurance, and any customs duties Easy to understand, harder to ignore..
In plain English: you place the order, the supplier loads the pallets onto a carrier at their warehouse, and you are on the hook for everything that follows. It’s a common clause for manufacturers who want to keep their logistics footprint light That's the part that actually makes a difference..
Not the most exciting part, but easily the most useful Easy to understand, harder to ignore..
How FOB Source Differs From Other FOB Types
- FOB Destination – seller keeps risk until the goods reach your door.
- FOB Shipping Point – essentially the same as FOB Source; the moment the carrier takes possession, the buyer owns the shipment.
The key takeaway? With FOB Source, the buyer’s accounting system must be ready to record freight, duties, and any ancillary charges the moment the carrier’s bill of lading is issued.
Why It Matters / Why People Care
If you’ve ever gotten a surprise invoice for “carrier fees” months after you thought the transaction was closed, you already know why this matters. The moment an FOB‑source order is shipped, a cascade of financial events begins:
- Cash flow impact – you owe the carrier before you even receive the goods.
- Compliance risk – customs duties must be paid on time, or you face penalties.
- Reconciliation headaches – the purchase order, the freight invoice, and the customs entry all need to line up perfectly.
When the pieces don’t line up, the system that many ERP platforms call IPAC (Import/Export Processing and Accounting Consolidation) steps in. An IPAC settlement is the accounting engine’s way of saying, “Alright, let’s balance the books for this import transaction now that we have all the data.”
If you ignore the link between FOB Source and IPAC, you’ll see mismatched amounts, delayed payments, and a lot of “why is this showing as a variance?” emails.
How It Works (or How to Do It)
Below is the typical end‑to‑end flow that turns an FOB‑source purchase order into an IPAC settlement. The exact steps can vary by ERP, but the concepts stay the same.
1. Purchase Order Creation
- Buyer creates PO in the ERP, selects “FOB Source” as the shipping term.
- System automatically flags the order for post‑shipment cost capture (freight, insurance, duties).
2. Supplier Ships the Goods
- Supplier generates a Bill of Lading (B/L) and sends a shipping notice (ASN – Advance Shipping Notice) to the buyer.
- The B/L includes carrier name, container number, and estimated departure date.
3. Carrier Issues Freight Invoice
- Once the cargo is on board, the carrier bills the buyer for the freight charge.
- In many cases the invoice arrives before the goods hit customs, creating a timing gap.
4. Customs Entry & Duty Calculation
- The buyer (or a customs broker) files an entry with the importing country’s customs authority.
- Duties, taxes, and any anti‑dumping fees are calculated based on the HS code, value, and origin.
5. Data Feeds Into IPAC
- The ERP’s IPAC module pulls three streams of data: PO details, freight invoice, and customs entry.
- It matches them using key fields: PO number, container ID, and vendor code.
6. IPAC Settlement Generation
- Once all three streams are present, IPAC creates a settlement record that:
- Debits the freight expense account.
- Credits the accounts payable (carrier) and customs payable (duties).
- Adjusts the landed cost of the inventory item.
7. Final Posting & Reporting
- The settlement is posted to the general ledger.
- Inventory valuation now reflects the true cost of goods (purchase price + freight + duties).
- Management can run landed‑cost reports, margin analysis, and compliance dashboards.
That’s the whole loop. It feels like a lot, but each step has a purpose: making sure the money you owe matches the physical goods you own.
Common Mistakes / What Most People Get Wrong
Mistake #1: Forgetting to Flag FOB Source in the PO
If the PO defaults to “FOB Destination,” the system assumes the seller will pay freight. Because of that, later, the carrier invoice lands in a “unmatched” queue, and the IPAC settlement never fires. On top of that, the result? A phantom liability that sits in “unallocated expenses” forever Less friction, more output..
Not the most exciting part, but easily the most useful.
Mistake #2: Relying on Manual Data Entry
Copy‑pasting the carrier invoice number into the ERP seems harmless, but a single typo breaks the matching algorithm. IPAC then throws a “no match found” error, and the settlement stalls Still holds up..
Mistake #3: Ignoring the ASN Timing
The ASN is the glue that holds the PO and the freight invoice together. Still, if the supplier doesn’t send it, or you don’t import it, the system can’t tie the container to the PO. The settlement ends up with an “orphaned freight” flag Worth keeping that in mind..
Mistake #4: Not Updating HS Codes Promptly
Customs duties are calculated on the HS code you have on file. If you change the product description but forget to update the HS code, the duty amount will be off, and the IPAC settlement will show a variance that needs manual adjustment It's one of those things that adds up..
Not the most exciting part, but easily the most useful Worth keeping that in mind..
Mistake #5: Overlooking Currency Conversions
Freight invoices often come in the carrier’s local currency, while your PO is in USD. If you don’t let the ERP apply the correct exchange rate at the time of settlement, you’ll see a mismatch between the freight expense and the payable balance.
It sounds simple, but the gap is usually here Simple, but easy to overlook..
Practical Tips / What Actually Works
-
Standardize the “FOB Source” flag
- Create a mandatory field in the PO template that forces the user to select a shipping term.
- Use a validation rule that throws an error if the term is left blank.
-
Automate ASN ingestion
- Set up an EDI bridge or a simple API that pulls the supplier’s ASN directly into the ERP.
- Map the ASN container ID to the PO number automatically.
-
Use a three‑way match engine
- Many ERP systems let you configure a match on PO, invoice, and customs entry.
- Enable “auto‑release” for matches that meet 100 % criteria; anything less should trigger a workflow for review.
-
Maintain a master HS‑code list
- Keep a centralized table that links product SKUs to HS codes.
- Schedule a quarterly audit to ensure the list reflects any tariff changes.
-
make use of real‑time exchange rates
- Integrate a currency service (e.g., OANDA, XE) so the ERP pulls the rate on the day the freight invoice is posted.
- Store the rate in the settlement record for audit trails.
-
Run a “pre‑settlement” report
- Before closing the month, generate a report that shows all FOB‑source orders with pending freight or customs entries.
- Flag any that are older than 7 days for immediate follow‑up.
-
Train the finance‑logistics liaison
- Appoint a “settlement champion” who knows both shipping terminology and accounting rules.
- This person can troubleshoot mismatches before they become month‑end headaches.
FAQ
Q: Does “FOB Source” mean I’m responsible for insurance too?
A: Yes. Under FOB Source, the buyer must arrange and pay for cargo insurance unless the contract says otherwise Most people skip this — try not to..
Q: What if the carrier invoice arrives after the customs entry is already posted?
A: Most IPAC modules can handle out‑of‑order data. The freight expense will post as a separate journal entry, and you can run an adjustment to update the landed cost.
Q: Can I switch an order from FOB Destination to FOB Source after it’s already shipped?
A: Technically you can, but you’ll need to reverse any seller‑paid freight entries and create new buyer‑paid entries. It’s a messy process; better to decide the term before the ship‑date Surprisingly effective..
Q: Is IPAC the same as a “settlement run” in my ERP?
A: In many systems, the IPAC settlement is the automated “settlement run” that consolidates import‑related costs. The terminology varies, but the function is identical That's the part that actually makes a difference..
Q: How do I know if a settlement has been posted correctly?
A: Look for a single journal entry that debits freight, duties, and landed‑cost inventory, and credits the appropriate payables. The entry should reference the PO number, B/L, and customs entry number.
When an FOB‑source order creates an IPAC settlement, it’s not magic—it’s a chain of data points that, when aligned, give you a true picture of what you actually paid for each imported item. Miss one link and the whole chain wobbles, leading to delayed payments, compliance headaches, and skewed profit margins.
This changes depending on context. Keep that in mind.
By flagging the shipping term, automating ASN intake, and keeping your HS codes and currency rates fresh, you can turn that chain into a smooth, predictable process. The next time you see “IPAC Settlement” pop up in your ledger, you’ll know exactly why it’s there—and, more importantly, that you’ve done the work to make sure it’s right The details matter here. Took long enough..
Not obvious, but once you see it — you'll see it everywhere.
Happy shipping, and may your settlements always balance.
