Tell Us What You’re Connecting
Provide the systems, workflow and business requirements.
International shipping · Finance
Connect Sage Intacct + DHL
Automate shipment request, service and account mapping, label and tracking number, freight charge, dimension coding between Sage Intacct and DHL — with monitoring and managed support from APIWORX.
APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.
ERP + eCommerce Specialists
Managed & Monitored Integrations
Expert Integration Team
APIWORX Provides the Service
Yes. APIWORX connects Sage Intacct and DHL.
But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.
APIWORX automates that process end to end — the objects moving between Sage Intacct and DHL, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.
How it works
From requirements to a managed integration
We Design the Integration
APIWORX recommends the integration architecture, mappings and implementation approach.
We Build, Monitor & Support It
APIWORX implements the integration and provides ongoing monitoring and support as applicable.
Who this is for
This page is for finance and operations teams running Sage Intacct as the financial system of record while shipping internationally with DHL.
What needs to be in place
- Sage Intacct with API access and a service account permitted to read orders and post the entries your finance team agrees to.
- A DHL account with integration credentials available for the service you actually ship on.
- An agreed dimension structure — class, location, department, project — for freight posting.
- A named finance contact for charge treatment and variance decisions.
When you may not need this
Low international volume can be handled inside the DHL portal with manual entry into Intacct. Managed integration earns its place when shipment volume, dimension-aware freight posting or reconciliation between carrier charges and the ledger becomes a standing cost.
What is out of scope
- DHL is a group of businesses — DHL Express, eCommerce and Supply Chain each expose different interfaces. Which one applies to your account, and in which countries, is confirmed in scoping before any commitment.
- APIWORX does not negotiate your DHL rates, hold your carrier contract, or act as a freight broker.
- Rate shopping and landed-cost calculation are only in scope where your DHL account exposes them and the behaviour is agreed before build.
- Customs and commercial-invoice content stays owned by the system and team that produce it; we move the values those systems hold.
What actually moves, and who owns it
A representative scope. Exact records, DHL service and charge treatment are confirmed before build.
Sage IntacctAPIWORX (mapping, retries, exception queue)DHL
| Object | From | To | System of record | Trigger | If it fails | Owner |
|---|---|---|---|---|---|---|
| Shipment request | Sage Intacct or the order system | DHL | Agreed in scoping | Order reaches the agreed ready-to-ship state | Held in exception queue with the validation error | APIWORX |
| Service and account mapping | Agreed rule set | DHL | Rule set agreed in scoping | At shipment creation | Shipment held for an operations decision | APIWORX |
| Label and tracking number | DHL | Sage Intacct or the order system | DHL | Shipment confirmed | Retried, then queued for review | APIWORX |
| Freight charge | DHL | Sage Intacct | DHL | Charge published on your account | Queued with the shipment reference; nothing posted on a guess | APIWORX |
| Dimension coding | Agreed mapping | Sage Intacct | Finance mapping | At posting | Unmapped dimensions reported before posting | APIWORX |
| Delivery status | DHL | Order system | DHL | Status change | Last known status retained; gap reported | APIWORX |
Three decisions that make or break this integration
Freight cost never lines up with the ledger
Carrier charges arrive after the shipment, often adjusted. Charges are matched to the original shipment reference and posted with the dimensions your finance team agreed, so reconciliation is a review rather than a rebuild.
- Every posting carries the DHL shipment reference.
- Adjustments handled as their own entry against the same reference.
- Variances above an agreed threshold reported instead of posted quietly.
More than one DHL service is in play
Express, eCommerce and Supply Chain behave differently. Which service applies per lane, and therefore which interface is used, is decided once in scoping and applied consistently.
- Service selection expressed as configuration, not code you maintain.
- Ship-from location and account mapped per lane.
- Unsupported lanes held for a decision rather than defaulted.
Customs data is incomplete
International shipments fail on missing commodity detail more often than anything else. Required fields are validated before the request reaches DHL, so the gap is reported as a data task.
- Validation against the fields your DHL service requires.
- Specific missing values listed per shipment.
- APIWORX reprocesses the shipment once the data is corrected.
Reliability and ownership
The operating rules that apply to this workflow after go-live.
- Every run is logged with the source record reference so a shipment can be traced end to end.
- Failed messages are retried on a defined schedule; anything still failing lands in an exception queue rather than being dropped silently.
- Duplicate prevention keys on the source system's own identifier so a replayed message does not create a second shipment or a second posting.
- Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
- Mapping changes — new service levels, new ship-from locations, new accounts — are handled inside the ongoing engagement.
- Support windows and response commitments live in your agreement; this page does not state an SLA.
How a shipment is traced
Illustrative — not customer data
An illustrative reference trace from order to DHL shipment to the Sage Intacct posting.
| Order reference | DHL shipment reference |
|---|---|
| DHL tracking number | Order shipment record |
| DHL charge line | Sage Intacct entry |
| Agreed dimension set | Intacct class / location / project |
Scope and questions
- Which DHL service do you connect to?
- The one your account actually ships on. DHL Express, eCommerce and Supply Chain expose different interfaces, so the applicable service and credentials are confirmed in scoping before any commitment.
- Can freight charges post automatically to Sage Intacct?
- Where the charge data is available on your account, yes — with the dimension coding your finance team defines. Nothing is posted on an estimate.
- Do you handle customs documentation?
- We move the commodity and value data the source systems hold and validate the fields DHL requires. Determining what is declared stays with your team.
- Who works the exceptions?
- APIWORX works the queue and escalates to your named contacts when a business decision is needed.
Your integration plan
Get My Integration Plan
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Ready to map your integration?
Tell us what systems you need connected. We’ll recommend the architecture, implementation approach, timeline and estimated price range.
Next step
Scope your Sage Intacct + DHL integration
Tell us your systems and documents. A specialist confirms scope by email.