ERPClimb logoERPClimb

SAP TM Freight Settlement Interview Questions

In SAP TM rounds, freight settlement questions are where configuration knowledge meets day-to-day behaviour — what a setting does, and what breaks in a live system when it is wrong.

Freight Settlement in SAP Transportation Management (TM) covers the end-to-end process of calculating, agreeing, and paying (or invoicing) transportation charges for freight orders and freight bookings, using calculation sheets, agreements, and settlement documents that integrate with MM/FI (Embedded TM, Decentralized TM) or native S/4HANA charge management, enabling accurate carrier cost accrual, customer billing, and dispute resolution.

This page carries 59 reviewed SAP TM freight settlement interview questions, each with a complete written answer and no sign-in required. The set breaks down into 8 foundational, 28 mid-level and 23 advanced questions, so you can start at the top for a first interview or skip ahead to the scenario-based items for a senior round.

Rehearse these out loud rather than reading them. If you can explain each answer in your own words, including one realistic way it goes wrong on a project, you are covering what a normal SAP TM round on freight settlement expects.

59 Freight Settlement questions with answers

easyFreight Settlement

1. In S/4HANA TM, which settings on the freight order type determine whether a completed freight order becomes relevant for FI settlement, and how do these interact with item category and cost distribution settings?

The freight order type carries a settlement-relevant indicator that, combined with the freight unit's item category and the assigned charge/settlement profile, determines whether a freight settlement document is created. If the order type is not flagged for settlement or lacks a linked settlement profile, no FI-relevant document is generated even after execution completes. Cost distribution settings on the order type also determine how charges split across cost objects during posting.
easyFreight Settlement

2. What is the purpose of dispute management in SAP TM freight settlement, and how does the freight order type influence which settlement documents can be disputed?

Dispute management in freight settlement lets planners or AP flag a freight settlement document (FSD) line item as contested when the carrier invoice amount deviates from the system-calculated charge, preventing automatic release to FI. The freight order type determines the settlement document type, charge calculation sheet, and whether self-billing or carrier-invoice-based settlement applies, which in turn governs whether and how disputes can be raised and tracked against that settlement.
easyFreight Settlement

3. What role does the freight order type play in determining whether a freight order is relevant for FI settlement, and which settings on the freight order type control this?

The freight order type carries a settlement profile assignment that determines whether the freight order is relevant for freight settlement (self-billing or invoice verification) and ultimately FI posting. Key settings include the item category determining charge-relevant items, the settlement control fields governing whether cost distribution documents are created, and links to the purchasing organization/company code data needed for the FI document. Without correct settlement profile assignment, no settlement document or FI posting occurs.
easyFreight Settlement

4. In SAP TM freight settlement, how are tax-related disputes on a carrier invoice typically handled when the calculated tax code in the Freight Settlement Document does not match the vendor's physical invoice?

The FSD is blocked from posting via the settlement status (e.g., 'Blocked' or dispute status), and the discrepancy is resolved by correcting the tax code on the Charge Item or Agreement rate before re-triggering settlement. Disputes on tax amounts typically require manual review since TM derives tax code from the Organizational Data/Account Determination rather than reading the vendor invoice directly.
easyFreight Settlement

5. What analytics or reporting mechanisms are typically used to reconcile freight costs calculated in SAP TM against actual postings in Finance during month-end close?

Reconciliation typically relies on comparing TM freight order/settlement document values against ACDOCA line items posted via the FI/CO integration, often using embedded analytics (Fiori apps) or custom CDS views joining TM charge tables with ACDOCA. Freight Settlement Document status and accrual postings are checked against actual invoice postings to identify variances before period close.
easyFreight Settlement

6. In S/4HANA TM, why are freight accruals posted before the carrier invoice is received in MM-LIV, and what triggers the reversal of that accrual?

Accruals are posted from the Freight Settlement Document so estimated transportation costs hit the correct period and cost object even though the vendor invoice hasn't arrived. This supports accurate period-end expense recognition. When the actual supplier invoice is posted in MM-LIV against the referenced purchase order or service entry sheet, the accrual reversal is triggered automatically, and any variance between estimate and actual is posted separately.
easyFreight Settlement

7. In S/4HANA TM, what is the purpose of the accrual posting generated from a Freight Settlement Document, and how does it relate to the eventual MM-LIV supplier invoice?

The accrual posting recognizes estimated freight cost in FI/CO at the time the Freight Settlement Document is created, before the carrier invoice arrives, ensuring costs are matched to the correct period. It typically debits a freight expense account and credits an accrual/provision account. When the actual vendor invoice is verified via MM-LIV, the accrual is reversed and the actual liability posted, with any variance flowing to a variance or price difference account.
easyFreight Settlement

8. In S/4HANA TM, what role does the freight order type configuration play in determining whether and how FI-relevant settlement documents are generated during freight execution?

The freight order type carries settings that control whether the order is settlement-relevant, which settlement document type and item category are used, and which cost distribution/accrual logic applies. It links to the freight settlement document type and controls integration with FI postings such as service entry sheets or invoices. Misconfigured order types can prevent settlement documents from generating or post costs to the wrong FI account assignment.
mediumFreight Settlement

9. A freight agreement's rate scale was updated mid-quarter, and several already-processed supplier invoices now show cost variances when compared against Group Reporting figures for the same shipments. As the architect, how would you approach root cause analysis and remediation?

First confirm whether the rate change was applied retroactively or only prospectively in the agreement, and identify which freight settlement documents were calculated before versus after the change. Compare settlement amounts against the corresponding supplier invoices posted in MM-LIV to isolate genuine variances from timing differences. For amounts already consolidated in Group Reporting, determine if a correcting entry or restated allocation is needed, and implement rate change approval and effective-dating controls to prevent uncontrolled retroactive updates going forward.
mediumFreight Settlement

10. When freight settlement disputes can be raised based on data discrepancies received through SAP Business Network for Logistics, what configuration must align between the TM charge profile and dispute case handling to ensure discrepancies are captured before settlement posts?

The charge profile must define calculation bases (e.g., weight, distance) that are traceable back to the specific execution attribute source, so that when BN4L delivers a conflicting actual value, the variance can be flagged. Dispute case creation typically relies on tolerance thresholds configured on the settlement document type or profile; if BN4L data updates arrive after settlement release, no automatic dispute case is triggered unless a reconciliation step or exception handler compares planned versus BN4L-confirmed values before final posting.
mediumFreight Settlement

11. During production support, a client reports that freight costs settled in TM are not flowing correctly to the correct cost center in CO. What configuration areas would you check first?

I would first check the account assignment determination in TM (settlement/cost distribution rules) mapping to CO objects, then verify the cost center derivation logic in the Charge Calculation profile and the FI/CO account assignment in the Transportation Charge Management settings. I would also confirm the cost center master data validity and check whether the CO substitution or derivation rules in FI-CO are overriding TM-provided account assignments.
mediumFreight Settlement

12. During transportation financial close, how does invoice verification (MM-LIV) for carrier invoices integrate with CO-relevant accrual postings created earlier through freight settlement, and what design ensures accurate CO postings when actual invoice amounts differ from accruals?

Freight settlement posts an accrual to a cost object (cost center, WBS or internal order) via a provisional FI/CO document; when the vendor invoice is verified in MM-LIV, the accrual is reversed and the actual cost hits the same cost object using the account assignment carried from the purchase order/service entry. Design ensures consistency by keeping account assignment logic identical between accrual and invoice verification postings, using clearing accounts for variance tracking, and running periodic variance reports to catch mismatches before close.
mediumFreight Settlement

13. How do pricing conditions maintained in SAP TM transportation charge management integrate with FI to ensure accurate G/L account determination during freight settlement posting?

TM pricing conditions determine calculated freight charges per charge type, which are then passed to settlement documents that trigger account determination through condition-based mapping, typically referencing charge type, cost center, and vendor account assignment groups defined in customizing shared with FI. The account determination logic must align charge types consistently with G/L accounts to avoid postings landing in suspense or default accounts. Any mismatch between TM charge type configuration and FI account determination tables results in settlement documents failing accounting release or posting incorrectly.
mediumFreight Settlement

14. During transportation cost allocation, a Freight Settlement Document posts successfully to FI but the corresponding CO cost center or internal order remains unassigned, causing the postings to fall into a default cost object. What are the likely root causes and how would you resolve this?

Root causes typically include missing or incomplete cost object derivation rules in account determination, a Transportation Charge Item not linked to a valid Freight Order/Cost Distribution rule, or missing CO-relevant fields (cost center/internal order) on the GL account master. Resolution involves reviewing the cost distribution configuration on the Freight Order, verifying account assignment derivation logic, and correcting the CO object substitution/validation rules so future settlements derive the correct cost object.
mediumFreight Settlement

15. When configuring carrier master data governance in SAP TM S/4HANA, what steps ensure that a business partner created as a carrier is correctly integrated with FI for freight settlement?

The carrier must be created as a Business Partner with the Carrier role (TM) and an FI vendor role (or equivalent) linked via the BP-vendor integration. Company code data, payment terms, and reconciliation account assignment must be maintained on the vendor side. In TM, the carrier's transportation-relevant attributes (e.g., contract types, texts) are maintained separately, but settlement documents (freight settlement to invoice) rely on the vendor role for FI posting, so both roles must be synchronized and active.
mediumFreight Settlement

16. A customer complains that the freight cost shown in the Forwarding Settlement Document does not reconcile with the revenue recognized in the corresponding SD billing document, even though both reference the same Forwarding Order. How would you approach reconciliation?

I would compare the Charge Item breakdown in the Forwarding Settlement Document against the billing-relevant conditions transferred to SD, checking whether all charge types (e.g., surcharges, accessorials) were mapped to billing item categories. Common gaps include charges calculated after billing was released, manual charge adjustments not re-triggering billing update, or currency/exchange rate differences between settlement and billing dates. I'd trace both documents back to the Forwarding Order's charge calculation results to isolate the mismatched line.
mediumFreight Settlement

17. An Event Management milestone flags a delivery discrepancy (short delivery) on a freight order, which should trigger a dispute on the linked settlement document and hold the corresponding MM goods receipt for review, but neither action occurs automatically. How would you troubleshoot this?

Check whether the event rule for the short-delivery milestone is actually configured to raise a follow-up action against the settlement document and MM goods receipt, since Event Management milestones by default only log status and alerts unless explicitly linked to downstream workflow triggers. Validate the event-to-exception mapping, confirm the settlement document dispute workflow is activated for that freight order type, and check whether MM goods receipt tolerance settings would have blocked posting anyway, independent of the TM event.
mediumFreight Settlement

18. When configuring the Freight-to-Settle process for a freight agreement, what configuration steps ensure that the CO account assignment (cost center, WBS, or internal order) defined on the agreement is correctly propagated through charge calculation to the final settlement document posting?

The freight agreement's business share or cost distribution settings must reference the correct account assignment category, and the calculation sheet's cost distribution categories must map consistently to those objects. The settlement profile and FI posting configuration must not override account assignment defaults. Any discrepancy between agreement-level defaults and calculation sheet mapping causes postings to fall back to default cost objects rather than the agreement-specified one.
mediumFreight Settlement

19. A customer disputes a portion of a forwarding settlement document charge after it has already been transferred to billing. Walk through the configuration and process steps needed to support a partial dispute without reversing the entire settlement.

Enable dispute case management or manual blocking on the settlement document line item level so only the disputed charge line is held while undisputed lines proceed to billing. Configure a settlement status that allows partial release, use charge line-level blocking reasons in the agreement/rate table, and route disputed items through a manual review workflow. Once resolved, the disputed line is corrected via credit/debit adjustment and re-released, avoiding full document cancellation and preserving already-billed undisputed charges.
mediumFreight Settlement

20. An internal audit flags that several carrier agreements had rate changes applied retroactively, affecting already-settled freight settlement documents without a visible approval trail. What controls would you recommend to prevent and detect this going forward?

Implement change history logging on agreement/rate master data with mandatory approval workflow for retroactive validity date changes, and restrict authorization so rate changes affecting already-settled periods require a separate approval role from routine rate maintenance. Add a periodic report comparing rate master change dates against validity start dates to flag retroactive changes, and require that any retroactive correction be processed through a formal re-settlement or adjustment document rather than silently updating the agreement, preserving an auditable link between the rate change and any resulting financial correction.
mediumFreight Settlement

21. A carrier invoice received through SAP Business Network for Logistics shows charges that don't match the amounts calculated on the corresponding freight order, causing settlement exceptions. How would you design the integration to auto-reconcile these before settlement posts?

I would configure a tolerance-based matching step within the settlement process that compares the BN4L-submitted invoice charge lines against the freight order's calculated charge items by charge type and quantity basis. Discrepancies within defined tolerances auto-approve; those outside tolerance route to an exception workflow for manual review before settlement document creation. The charge profile must expose charge type mapping between the carrier's invoice format and TM's internal charge types to ensure comparable line items.
mediumFreight Settlement

22. When integrating SAP TM with MM purchasing for freight procurement, how is the purchasing organization data relevant to carrier business partners and freight settlement configured?

Carrier business partners in TM are extended with vendor master data via the BP transaction, linking them to a purchasing organization and purchasing group in ERP/MM. This enables freight order/settlement documents to generate purchase orders or service entry sheets against the carrier vendor, respecting purchasing org assignments, pricing conditions, and release strategies. Correct purchasing org assignment ensures freight costs flow to the right company code and controlling objects during settlement via SAP TM's Freight Settlement Document.
mediumFreight Settlement

23. At month-end, the freight cost accrual generated from unsettled freight orders needs to reconcile with revenue already recognized through SD billing for the same shipments. How would you design the cost distribution and accrual process to keep these aligned?

Design the accrual calculation to run at the same shipment/order granularity as SD billing revenue recognition, using consistent cost object assignment (sales order, WBS, or cost center) so accrued freight cost and recognized revenue post to matching CO objects. Schedule accrual runs after billing has posted so cost distribution reflects billed quantities/values, and build a reconciliation report comparing accrued freight cost against billed revenue per shipment to flag mismatches before period close, allowing correction before financial statements are finalized.
mediumFreight Settlement

24. A global logistics provider settles forwarding charges under multiple freight agreements with different rate structures across subsidiaries, and Group Reporting shows inconsistent freight cost totals per legal entity after consolidation. How would you approach resolving this as part of the forwarding settlement design?

I would first verify that freight agreements and rate tables are consistently maintained per company code/legal entity, with currency and rate validity aligned to the reporting period. Next, confirm that forwarding settlement documents post to the correct company code and that intercompany freight charges (if any) are properly eliminated in consolidation rather than double-counted. I'd reconcile TM settlement totals against ACDOCA postings per entity, checking for agreement-level rate discrepancies or missing currency translation before the figures reach Group Reporting.
mediumFreight Settlement

25. How would you configure cost distribution on a Freight Settlement Document so that transportation charges reconcile correctly with revenue recognized in SD-Billing during transportation financial close?

Align the cost distribution basis on the calculation sheet with the same reference document structure used by SD-Billing, typically the forwarding order or freight order item, so charges map to the same billing unit. Use consistent settlement and billing document date logic and ensure account assignment categories match between TM cost distribution and SD revenue recognition. Reconciliation reports comparing settlement totals against billing totals per reference document help validate the mapping before close.
mediumFreight Settlement

26. A shipper subcontracts a long-haul lane to an external carrier, and freight settlement for that carrier must not be released until the shipment has cleared a GTS compliance screening tied to the destination country. How would you design the integration between subcontracting settlement and GTS compliance checks in this scenario?

Configure the freight order/settlement document to hold a compliance-relevant block status until GTS confirms the sanctioned-party and embargo screening for the carrier and route is complete. Use the GTS plug-in interface to trigger screening at booking or tender confirmation, and propagate a block on the freight settlement document (via status or blocking reason) until screening passes. Settlement release should be conditioned on both freight order completion and a cleared compliance status, validated through periodic reconciliation between TM and GTS logs.
mediumFreight Settlement

27. Your team discovers that accrual postings for carrier freight costs are being duplicated each period, inflating cost center expenses. What is your troubleshooting approach?

I'd first check whether the accrual run is being executed multiple times per period without proper reversal of prior accruals, which is a common root cause. Next, I'd verify the accrual reversal logic tied to invoice receipt in MM-LIV is functioning—if invoices are matched but the original accrual isn't reversed, both accrual and actual cost post simultaneously. I'd also review whether freight settlement documents are being reprocessed or reset without clearing previously accrued amounts, and correct the accrual run scheduling or reversal automation accordingly.
mediumFreight Settlement

28. Describe the end-to-end process flow when a carrier invoice is received and processed in S/4HANA TM, including how accruals are reversed and how the process integrates with SD-Billing for customer-side freight cost recovery.

The carrier invoice triggers a Freight Settlement Document (FSD) creation or supplier invoice verification against the freight order. Prior accruals posted during periodic accrual runs are automatically reversed once the actual cost is confirmed. Simultaneously, TM can generate a debit charge to the customer via an SD billing document (or resource-related billing) reflecting the same freight charge, ensuring cost and revenue recognition are aligned in the same period, supporting margin visibility per shipment.
mediumFreight Settlement

29. When a carrier invoice is processed via MM-LIV, cost objects such as internal orders assigned during freight settlement must carry through to the resulting FI/CO postings. What integration points must be validated to ensure the cost object flows correctly from the Freight Settlement Document into the vendor invoice posting?

Verify the account assignment category on the service purchase order generated from the freight agreement carries the cost object (cost center, internal order, or WBS) from the settlement document's calculation sheet output. Confirm the GR/IR clearing account setup and that ML81N service entry sheets reference the same account assignment. Check that the settlement-to-PO mapping in charge calculation profile isn't overwritten by default account assignment on the purchasing info record.
mediumFreight Settlement

30. During month-end financial close, transportation charges for in-transit freight orders need to be reflected in CO reporting before the freight settlement document is finalized. How would you design the settlement profile and process to support this requirement?

Configure the settlement profile to trigger periodic accrual calculation for freight orders not yet settled, posting estimated charges to a cost center or internal order via a preliminary CO posting distinct from the final settlement document. Use a dedicated accrual calculation run tied to the charge calculation profile so estimated values sync with CO at period-end, then reverse and replace with actual settlement postings once the freight settlement document is created and transferred to FI, ensuring CO reporting reflects both estimate and final costs without double counting.
mediumFreight Settlement

31. When configuring credit memo processing for over-billed freight charges in SAP TM, what settlement document type and agreement configuration are typically required to allow a negative settlement (credit) to be generated against the carrier?

A separate Freight Settlement Document type configured for credit memos (or the same FSD type with a negative charge line) is used, and the underlying Charge Agreement must permit manual adjustment/correction of charge items. The FSD is settled to FI as a credit memo document type, and the vendor's payment terms and tax code must be correctly propagated to avoid duplicate liability postings.
mediumFreight Settlement

32. After go-live, a subset of freight orders fail during charge calculation with cost postings not reaching CO despite successful settlement document creation. How would you troubleshoot this?

I would check the settlement document's account assignment status for errors, review the CO account assignment derivation logs for missing or invalid cost objects, and verify whether the cost center or WBS element referenced was locked, closed, or inactive at posting date. I would also check if a batch job for periodic settlement processing failed silently, and review application logs or the settlement error queue for specific rejection reasons tied to CO validation.
mediumFreight Settlement

33. When freight bookings are settled based on carrier confirmations received through SAP Business Network for Logistics, what configuration components must be aligned in the charge profile to ensure automatic settlement triggers correctly?

The charge profile must reference calculation sheets tied to the freight agreement, with calculation base values sourced from confirmed execution data (weight, distance, or transit events) fed back via BN4L. Settlement triggering rules need to be configured to fire on receipt of a specific network confirmation status, and the freight agreement must have matching charge types and validity aligned with the carrier's contract. Without this alignment, settlement either fails to trigger or uses stale planned values instead of confirmed execution data.
mediumFreight Settlement

34. A client wants freight costs for road carriers settled through FI using purchase orders generated from freight orders. How does the purchasing organization assignment on the carrier affect this settlement flow and account determination?

The carrier vendor must be assigned to the purchasing organization referenced by the freight order's organizational data so that a valid purchasing info record or source of supply exists when the freight order generates a purchase order for settlement. If the purchasing organization on the carrier does not match the one on the transportation document, PO creation fails or defaults incorrectly, breaking the link between freight settlement and FI account determination, which relies on the resulting PO and goods/service entry for cost posting.
mediumFreight Settlement

35. A carrier connected via SAP Business Network for Logistics disputes a settled freight charge, claiming the delivered weight differs from what TM used for calculation. How would you design the dispute handling process integrating charge profiles and BN4L data exchange?

Design the charge profile to retain a clear audit trail of the calculation base (planned vs. actual weight/quantity) used at settlement time, referencing the source event or milestone data received via BN4L. On dispute, enable a process to compare the BN4L-reported delivery data against the freight order's settlement snapshot, and if a discrepancy is confirmed, trigger a settlement correction/reversal using the standard settlement document adjustment process rather than manual FI correction. Establish a dispute status on the freight order to track resolution and prevent re-settlement until resolved.
mediumFreight Settlement

36. A freight order settled in the carrier's local currency is later reflected in the customer's SD billing document in a different currency, and finance reports cost distribution variances tied to exchange rate differences between the settlement date and the billing date. How would you troubleshoot and resolve this?

Check which exchange rate type and date (settlement posting date vs billing document date) each process uses for currency translation; TM freight settlement typically converts at the settlement document's posting date rate while SD billing may use the billing date rate, causing timing-driven variances. Confirm rate type consistency in both configurations, and if business requires alignment, standardize on a shared exchange rate type or fix rate reference date. Document the variance as expected FX timing difference rather than a data error if full alignment isn't feasible, and route it through a currency translation variance account for finance visibility.
hardFreight Settlement

37. At month-end, freight accruals posted via the Freight-to-Settle process are not matching the actual MM-LIV invoice amounts received in the following period, resulting in variance postings that finance is questioning. As the architect, how would you investigate and design a sustainable fix?

I would first trace whether accruals were generated from planned/estimated charges versus actual rate agreements, since estimation-based accruals inherently create variances against actual LIV postings. I'd review the accrual calculation basis (tariff vs actual charge), confirm reversal timing aligns with LIV posting cycles, and assess whether a percentage-based tolerance or automated variance clearing account is needed. Long-term, I'd recommend refining rate agreement accuracy and possibly triggering settlement closer to actual charge confirmation to reduce reliance on estimates.
hardFreight Settlement

38. Walk through the end-to-end dispute resolution process when a carrier disputes a freight settlement amount that was derived from SD-integrated sales order freight terms, and where in the process the settlement profile controls dispute handling.

Disputed freight documents are typically blocked or flagged during settlement document review before FI posting release; the settlement profile determines whether disputed charges can be partially released or must be fully held. The dispute is investigated against the originating SD condition records and freight agreement to confirm expected charges versus carrier-submitted charges. Once resolved, a correction is applied either via manual charge adjustment on the freight order or by reprocessing the settlement document, and the settlement profile's release strategy governs re-submission to FI.
hardFreight Settlement

39. After go-live, freight settlement documents are being created for subcontracted freight orders, but no corresponding FI accounting document is posted, and finance reports missing accruals. As solution architect, how would you diagnose and resolve this?

Start by checking the settlement document status—if it's stuck in a released-but-not-transferred state, the issue is likely in the FI transfer step (e.g., account determination or company code assignment failure). Review the freight order type's settlement profile for correct company code and account determination settings, and check for missing or incorrect GL account assignments in the automatic account determination configuration. Also verify no direct postings to reconciliation accounts are being attempted, which would block the transfer. Reprocess failed documents after correcting configuration, and add monitoring for future settlement-to-FI transfer failures.
hardFreight Settlement

40. Explain the end-to-end process flow from freight order settlement through accrual posting to final invoice verification in an integrated TM-MM/LIV scenario.

Freight order costs are calculated and a Freight Settlement Document is created, which posts an accrual to FI (typically a provision/accrual account) via automatic account determination. When the carrier invoice arrives, it is processed through MM Logistics Invoice Verification (MIRO or supplier invoice app) referencing the freight order/PO, which reverses the accrual and posts the actual liability. Variances between accrued and actual amounts are analyzed and cleared, often triggering follow-up postings if thresholds are exceeded.
hardFreight Settlement

41. Design a settlement profile architecture for a global shipper that must support both carrier payable settlement and customer freight cost recovery through SD billing across road, ocean, and air freight order types with differing cost structures. What key architectural decisions must be made?

Define separate settlement profiles per transportation mode reflecting distinct charge calculation sheets and cost element mapping, while standardizing the cost distribution logic that feeds SD so customer billing remains consistent regardless of mode. Decide whether carrier settlement and customer recovery run as parallel processes tied to the same freight order or are decoupled via intercompany cost objects, establish account determination rules per mode/company code, and ensure settlement document types align with freight order types to avoid cross-mode posting errors and reconciliation gaps.
hardFreight Settlement

42. Freight charges calculated on a freight order are correct in TM but the resulting FI posting shows a materially different amount than expected, and finance is disputing the accrual. As solution architect, how would you diagnose and resolve this discrepancy?

I would compare the calculation sheet output on the freight order against the settlement document's charge items to isolate whether the discrepancy occurs during calculation, settlement document creation, or FI transfer. Common causes include currency conversion timing differences, tax code determination differences between TM and FI, or account assignment splitting rules in the freight order type causing cost distribution across cost centers or profit centers differently than expected. I would validate exchange rate type consistency and reconcile the account determination configuration before adjusting.
hardFreight Settlement

43. Walk through how settlement profile configuration governs the timing and cost-object linkage between freight costing on a freight order and the corresponding SD billing document for customer freight pass-through, and what architectural decisions must be resolved.

Freight costing on the order calculates planned or actual charges, which the settlement profile routes into either a supplier settlement document or, for pass-through, a linkage into the SD sales order/billing plan via freight cost distribution. Key decisions include whether billing timing follows execution milestone completion or a periodic batch cycle, how cost objects (cost center, WBS, profit center) are derived on the freight order versus the SD document, and whether discrepancies between TM-calculated cost and SD-billed amount are reconciled automatically or require manual intervention before invoice release.
hardFreight Settlement

44. Explain the end-to-end process and controls required when a carrier issues a credit memo against a previously settled and posted freight settlement document, ensuring accurate FI reversal and no duplicate accrual release.

The credit memo is matched to the original freight settlement document via reference, creating a settlement correction document that generates a reversing FI posting against the original vendor/GR-IR or accrual account. Controls include validating the credit memo against the original charge lines to prevent over-crediting, ensuring the accrual that was already relieved at initial settlement is not released a second time, and confirming the correction flows through the same cost center/WBS assignment as the original posting for CO consistency. Tolerance and duplicate-check rules in charge management prevent erroneous double corrections.
hardFreight Settlement

45. A shipper needs a formal dispute management process where freight settlement disputes surfaced during SD billing reconciliation can hold settlement, trigger investigation, and resume without corrupting the freight costing history. As enterprise architect, how would you design this?

I would introduce a dispute status flag on the settlement document that blocks further settlement posting while preserving the original costing document as an immutable audit trail; a correction/adjustment costing document would be created rather than modifying history. The dispute workflow would integrate with SD billing block reason codes so disputed items are held from invoicing until resolution, and resolution actions (approve, adjust, reject) would generate clearly traceable settlement corrections tied back to the original freight order and costing document.
hardFreight Settlement

46. A freight booking for an ocean shipment settles successfully and posts an accrual to FI, but when the final carrier invoice arrives at a different rate, the corresponding FI adjustment posting never occurs, leaving a permanent variance in the GL. As solution architect, how would you diagnose and redesign this?

I would first confirm whether the freight order type and settlement profile are configured for two-step settlement (self-billing accrual followed by invoice reconciliation) or a single-step process, since a single-step design has no natural trigger point for a later adjustment. I'd check whether invoice receipt is being matched against the original settlement document or treated as a standalone document, and verify tolerance settings that might be silently absorbing or rejecting the variance. The fix typically involves enabling a reconciliation step in the settlement profile so late invoice variances generate a corrective FI posting automatically.
hardFreight Settlement

47. Walk through the end-to-end process of how a Settlement Profile controls the transition from Charge Calculation to FI posting during month-end financial close for transportation costs, including the key configuration nodes involved.

The Settlement Profile, assigned at the Transportation Charge Management level, determines which settlement document type is created, the account determination logic, and whether settlement happens automatically or manually after charge calculation completes. During month-end close, it governs how accrued (not-yet-invoiced) charges are transferred to FI/CO via the Freight Settlement Document, controlling GL account assignment, cost object derivation, and timing of the accrual reversal in the next period.
hardFreight Settlement

48. Walk through the end-to-end process from freight booking to customer billing when a settlement profile is configured to pass freight costs from a TM booking into an SD billing document.

A booking is created and charges are calculated using the assigned charge calculation sheet; upon confirmation, the settlement profile determines how internal freight costs are captured (e.g., via a freight settlement document for carrier payables and a separate cost distribution to the sales order for customer billing). Freight costs relevant for customer billing are transferred to SD as billing-relevant conditions or debit memo requests, often via cost distribution to the business document, then invoiced through standard SD billing, while the settlement profile ensures no double-posting between carrier settlement and customer billing.
hardFreight Settlement

49. During month-end financial close, a multinational shipper finds that Freight Settlement Documents for cross-border shipments are posting incorrect tax amounts because the tax jurisdiction determined at settlement differs from the one expected at shipment creation. As the solution architect, how would you diagnose and resolve this?

I would first verify tax determination inputs on the FSD—ship-from/ship-to locations, service provider tax classification, and the tax code derivation logic pulled from the underlying freight order versus what's redetermined at settlement time. Common root causes include location master data changes between order creation and settlement, or condition-based tax code determination in pricing procedures using outdated org data. Resolution involves aligning tax determination timing (freezing at order creation vs. redetermining at settlement) and validating tax condition records and jurisdiction codes in the settlement pricing procedure.
hardFreight Settlement

50. Walk through the end-to-end settlement process for a subcontracted freight order integrated with SD billing, from Event Management milestone confirmation through settlement profile application to invoice creation.

Event Management captures execution milestones (e.g., POD) that update the freight order's transportation status. This status change, if configured, triggers charge calculation and freight settlement document creation based on the settlement profile attached to the freight order type. Simultaneously, on the SD side, the delivery-related billing document release depends on the freight order reaching a completed status. Once settlement documents post, FI accounting entries are generated, and if SD billing is linked (e.g., freight passed through to customer), the settlement cost feeds into cost distribution for downstream billing accuracy.
hardFreight Settlement

51. Walk through the end-to-end accrual process in forwarding settlement where calculation sheet charges representing subcontracted carrier costs must accrue before the actual carrier invoice arrives via MM-LIV, ensuring the accrual reverses correctly once the invoice posts.

Charges flagged in the calculation sheet for accrual generate a periodic accrual posting to a freight accrual account and matching CO object based on the forwarding order's cost distribution. When the actual carrier invoice arrives and is processed through MM-LIV against the linked purchase order or service entry, the system reverses the accrual and posts the actual liability. Reconciliation reports should compare accrued versus actual amounts by settlement document and PO to catch mismatches before close.
hardFreight Settlement

52. Walk through how tax determination flows from a Service Purchase Order generated for freight settlement through to the final FI posting, and where tax mismatches typically originate.

The Service Purchase Order created from the freight agreement inherits tax classification from the vendor master, purchasing info record, and plant/tax jurisdiction data, which the tax calculation procedure then uses to determine the tax code applied during MM-LIV invoice verification. Mismatches typically arise when the freight settlement document calculates tax using shipment-level jurisdiction data that differs from the PO's tax code, especially for cross-border or drop-ship scenarios where the ship-from/ship-to combination changes the applicable tax logic.
hardFreight Settlement

53. A freight order type is configured such that the freight settlement document is only created after execution status reaches 'Completed', but production incidents show settlement documents being created and posted to FI while the freight order's execution status still shows 'In Transit'. As solution architect, how would you diagnose and correct this inconsistency?

Check whether the freight order type's settlement relevance is tied to a status that isn't actually being enforced at document creation—settlement can be manually or batch-triggered independent of execution status if no explicit status check is configured. Review the status profile and any custom BAdI/workflow gating settlement creation, verify FBI (freight order integration) event dependencies, and check if manual settlement runs (via background job or app) bypass the intended status gate. Fix by embedding a hard status check in settlement creation logic, not just a UI hint.
hardFreight Settlement

54. A freight order type configured for a specific carrier lane triggers an Event Management milestone on delivery confirmation that is supposed to release the freight settlement document for FI posting, but postings are silently failing in production while the settlement document shows as released. As the architect, how would you diagnose and resolve this?

Start by checking whether the settlement document is genuinely released or stuck in an intermediate status misreported by the UI, then review the FI posting interface (accounting document creation) for errors such as blocked vendor master data, missing cost center or GL account derivation, or posting period closure. Validate the freight order type's account determination and settlement profile settings, check application log/monitoring for background job failures, and confirm the event rule isn't firing multiple times causing duplicate or conflicting posting attempts.
hardFreight Settlement

55. Design an event-to-settlement architecture where Event Management milestones on a freight order must gate freight costing calculation, and the resulting settlement document must align with SD billing timing for a customer-facing freight charge pass-through. What architectural decisions would you make?

I would design Event Management to raise a specific milestone (e.g., proof of delivery) that sets a settlement-relevant execution status, which only then allows charge calculation to finalize using actual execution data rather than planned estimates. The settlement profile would be configured to hold settlement document creation until this status is reached, preventing premature costing. On the SD side, I'd align billing block release logic to the same milestone so that customer freight pass-through billing and internal carrier settlement stay synchronized, avoiding scenarios where a customer is billed before carrier costs are finalized.
hardFreight Settlement

56. Design the settlement profile and freight order type architecture for a shipper that needs both self-billing settlement for core carriers and standard invoice-verification settlement for spot carriers, with both flowing through the same SD billing process for customer freight pass-through.

Define separate freight order types for core-carrier and spot-carrier lanes, each with a distinct settlement profile: one configured for self-billing (system-generated settlement documents with automatic release) and one for invoice verification (settlement documents awaiting carrier invoice match). Both freight order types should map to charge calculation sheets producing consistent cost elements so that downstream cost distribution to the SD sales order/billing document is uniform regardless of settlement path. Ensure a common cost distribution profile bridges both settlement flows into the same SD billing-relevant condition types for customer pass-through.
hardFreight Settlement

57. Describe the end-to-end process of how rate table-driven charges on a carrier freight order flow through accrual posting and eventually reconcile against a supplier invoice in MM-LIV.

Charges are calculated from rate tables in the freight agreement at freight order creation or confirmation, generating a freight settlement document. Before the actual invoice arrives, an accrual (provisional cost) is posted to FI/CO based on calculated charges, often via periodic accrual runs. When the carrier invoice is received, it's matched in MM-LIV against the freight order/settlement document, and any variance between accrued amount and invoiced amount is posted as a difference, with the original accrual reversed or adjusted.
hardFreight Settlement

58. At financial close, freight orders accrued in the prior period get invoiced via MM-LIV in the current period, but the accrual reversal timing doesn't align with the invoice posting date, causing double-counted freight expense in one period and understated expense in the next. As the architect, how would you redesign the accrual reversal and invoice verification process to prevent this?

Align the accrual reversal trigger to the invoice verification posting date rather than a fixed calendar cutoff, using automatic reversal linked to goods/service receipt or invoice receipt events instead of period-end batch jobs. Introduce a reconciliation report comparing outstanding accruals against MM-LIV postings by freight order to catch timing mismatches before close. Consider staggering reversal runs to run after the invoice verification batch completes each period.
hardFreight Settlement

59. During an internal audit of carrier invoice processing, auditors flag that several Freight Settlement Documents were posted with manually overridden tax codes that don't match the standard tax determination logic, with no visible approval trail. What controls would you recommend to close this gap?

I would recommend restricting manual tax code override authorization via role-based access control, enforcing a workflow approval step for any FSD where the derived tax code is manually changed, and enabling change document logging on the Charge Item/tax fields for audit traceability. Additionally, I'd introduce a periodic reconciliation report comparing system-derived tax codes against posted tax codes to flag discrepancies for review, and tighten segregation of duties between charge calculation setup and settlement release.

Related lesson

Configuring Freight Settlement: Calculation Sheets, Agreements, and Settlement Document Types

Related topics

Integration with EWMCharge CalculationTransportation PlanningTenderingTransportation Master DataFreight UnitsIntegration with SDEmbedded TM, EWM Integration, Migration and SupportExecutionCarrier CollaborationEmbedded/Decentralized TM, EWM Integration, Migration and ArchitectureFreight Orders

Next practice step

Practice with Interview AITake a mock test