ERP & financeAutomated detention and demurrage recovery for SAP S/4HANA
Hold disputed D&D supplier invoices in SAP until the audit clears them
- Sync
- Every 60 minutes, plus an on-demand pull before each scheduled payment run
- Authentication
- SAP communication arrangement with a technical user (OAuth 2.0 or basic authentication, as your Basis team configures)
- Data exchanged
- Supplier invoices · Invoice line items · Payment block · Recovery credits
How it connects
SAP S/4HANA is SAP's ERP suite. For large importers it is where carrier and terminal invoices become supplier invoices in accounts payable, are posted to cost centers, and are paid on a payment run.
ATAHSKIA reads supplier invoices and line items carrying your detention, demurrage, per diem and storage cost elements through the APIs SAP publishes for S/4HANA, matches them to the container and B/L, and runs the 20 element check of 46 CFR § 541.6 and the § 541.7 issuance test. If you enable write-back, invoices that fail are flagged with a payment block reason your AP team defines, and released when the dispute closes.
This matters because § 541.5 says a billed party has no obligation to pay a charge on an invoice missing required information. Paying first and disputing later turns a non-payment into a refund chase. A block in SAP keeps the money in place while the billing party has its 30 days under § 541.8 to answer.
Data flows
Supplier invoices
Reads
Invoice header, supplier, invoice date, reference and amounts for D&D cost elements.
Invoice line items
Reads
Line text and assignment fields carrying container and B/L references.
Payment block
Writes
Optional: set or clear a payment block reason on audited invoices.
Recovery credits
Reads
Credit memos from carriers, matched back to the disputed invoice for recovery reporting.
Field mapping
| ATAHSKIA | SAP S/4HANA | Note |
|---|---|---|
| Billing party | Supplier (business partner) on the supplier invoice | |
| Invoice number | Supplier invoice reference | |
| Invoice date | Invoice document date | |
| Charge amount | Line amount on the D&D cost element or G/L account | |
| Container number | Line item text or assignment field | The field your AP team uses is set during onboarding. |
| Bill of lading number | Reference or header text field | |
| Dispute hold | Payment block reason | Only written if you enable it. |
| Recovered amount | Credit memo matched to the original invoice |
Setup
Create a communication user
Your SAP Basis team sets up a communication arrangement and technical user with read access to supplier invoices, and block rights only if you want write-back.
Agree the cost elements
List the G/L accounts or cost elements used for D&D, per diem and storage so only those invoices are audited.
Define the block reason
AP picks or creates a payment block reason for disputed D&D, so blocked items are easy to report on.
Test in a quality system
Run the connection against your QA client first and review a sample of blocked and released invoices.
Go live
Switch to production and backfill 12 months of invoices for the retrospective audit.
What it recovers
Block before the payment run
A carrier invoice issued 41 days after the charge was last incurred is blocked automatically under § 541.7 before Friday's payment run.
Accrue only what holds up
Finance sees audited exposure next to billed exposure, so D&D accruals reflect charges that are actually owed.
Close the loop on credits
Carrier credit memos are matched to the blocked invoice and the recovery is reported against the original charge.
SAP S/4HANA integration FAQ
Do you support SAP ECC?
Yes, through file exports or the interfaces your ECC system exposes. The audit logic is the same.
Will ATAHSKIA post documents in SAP?
No. At most it sets and clears a payment block you define. Postings stay with your AP team.
Is this an SAP certified integration?
No certification is claimed. ATAHSKIA uses the APIs SAP makes available to S/4HANA customers.
Related connectors
Don't let your 30-day dispute window expire.
Send your recent D&D invoices for a free audit. We report what is recoverable within 48 hours.