DTDC Shipping Invoice Reconciliation
Cointab helps finance teams perform DTDC shipping invoice reconciliation with a structured workflow that compares internal shipment records with courier invoices, rate cards, and supporting master data. Instead of checking charges manually in Excel, teams can map fields once, run reconciliation, review exceptions, and export audit-ready reports.
This use case is useful when shipping costs depend on factors such as zone, weight slab, pincode, service type, volumetric weight, and surcharge rules. Cointab helps teams spot mismatches across these inputs so they can review overcharges, undercharges, missing shipments, and unsupported invoice lines in one place.
What DTDC shipping invoice reconciliation helps you check
DTDC invoice verification usually involves more than matching an order number to an invoice line. Finance teams often need to compare multiple business records before they can confirm whether the charge is correct.
Typical checks include:
- Order or shipment reference against the DTDC invoice
- AWB or tracking number against the internal shipment report
- Delivery zone against the pincode master or serviceability map
- Actual weight or volumetric weight against the rate card
- Forward charge, RTO charge, and tax components against expected values
- Missing, duplicated, or partially billed shipments
- Charges applied outside the expected date range or rate slab
Cointab keeps the reconciliation transparent so users can see what matched, what did not match, and why an item was flagged.
Side A and Side B in a DTDC reconciliation workflow
Cointab uses a Side A and Side B model for shipping invoice reconciliation.
Side A - your internal records
Side A contains the records your business expects to be correct. For DTDC reconciliation, this may include:
- ERP shipment data
- Sales or order reports
- Dispatch or fulfillment reports
- SKU master data
- Pincode master data
- Internal rate assumptions
- Supporting lookups for weight, dimensions, or service type
Side B - external courier records
Side B contains the records received from DTDC or the shipping partner. This may include:
- DTDC invoice files
- Shipment summaries
- AWB-level charge reports
- RTO or return charge data
- Billing details with zone, slab, and amount charged
This structure helps finance teams compare internal expectations with external billing in a repeatable way.
How the reconciliation is set up
A typical DTDC shipping invoice reconciliation in Cointab follows a simple workflow:
- Start a reusable DTDC or custom shipping reconciliation.
- Upload the required files for Side A and Side B, or configure automated data input.
- Map the required fields such as date, amount, and identifiers.
- Upload supporting files if they are needed for lookups or calculations.
- Create derived columns when a clean identifier or calculated amount is needed.
- Run reconciliation manually or on a schedule.
- Review matched, partially matched, unmatched, and skipped records.
- Download the Excel report for review, follow-up, or audit.
If a file was missed earlier, users can upload the missing file under the same reconciliation and refresh the report.
Common fields used in the setup
For shipping invoice checks, finance teams often map fields such as:
- Order ID
- AWB number
- Invoice number
- Billing date
- Shipping date
- Zone
- Courier service
- Actual weight
- Volumetric weight
- Charge amount
Derived columns can also help normalize identifiers or calculate expected values from supporting data.
Structured matching for shipping charges
Cointab applies structured matching logic so teams can compare records consistently across periods. The engine can handle common reconciliation patterns such as:
- One-to-one matching
- One-to-many matching
- Many-to-one matching
- Many-to-many matching
- Partial matching
- Contra or grouped matching where needed
For DTDC invoice reconciliation, this is useful when a shipment is billed differently from the internal dispatch record, or when multiple shipment lines need to be grouped before comparison.
The platform first applies deterministic matching rules. Remaining open items can then be reviewed with AI-assisted analysis, while keeping the process conservative and audit-friendly.
Common discrepancy scenarios in DTDC invoice verification
Shipping invoice discrepancies often come from rate, zone, or weight differences rather than a simple missing invoice line. Cointab helps separate these cases so finance teams can focus on the right exception.
| Scenario | What it may indicate |
|---|---|
| Zone matches, weight matches, amount differs | Possible overcharge, tax difference, or surcharge variation |
| Zone matches, weight differs | Weight slab may have been applied differently than expected |
| Zone differs, weight matches | Pincode or routing logic may need review |
| AWB or order reference missing | Shipment may be absent from one side or keyed differently |
| Charge line not found in rate card | Rate setup may be incomplete or outside the valid period |
| Amount present but record skipped | File format, missing data, or invalid value may need correction |
Because shipping invoices often combine freight, returns, and service-level charges, a clear exception view is important for finance review.
What the reconciliation report shows
Once reconciliation is complete, users can review a report dashboard with transaction-level detail and summary totals.
The report typically includes:
- Total summary
- Fully matched records
- Partially matched records
- Unmatched records
- Skipped records
- Filters for deeper review
- Detailed matched transaction view
- Downloadable Excel output
This makes it easier to separate clean billings from items that need follow-up with operations, logistics, or the courier partner.
Why matched, partially matched, unmatched, and skipped records matter
- Fully matched records support clean closure and reporting.
- Partially matched records often show a related shipment with a value difference.
- Unmatched records may indicate a missing shipment, missing invoice line, or reference mismatch.
- Skipped records explain which rows were not included and why.
For finance teams, this visibility is as important as the final totals.
Reuse and automation for recurring shipping reconciliation
DTDC invoice checks are often recurring. A team may need the same workflow every week or month with only a new period of files. Cointab is built for reuse, so once the setup is configured, the team can run the same reconciliation again without rebuilding it.
Cointab also supports recurring automation through email, SFTP, or API-based data input. That means shipping reports can be received automatically, validated, reconciled, and prepared for review on a regular schedule.
This helps teams reduce repetitive work in logistics finance, accounts payable, and month-end close.
AI assistance in shipping invoice reconciliation
AI supports the workflow in practical, reviewable ways:
- It can help build Excel-style formulas for derived columns.
- It can analyze difficult open items after rule-based matching is complete.
- It can suggest likely reasons for an unmatched or partially matched record.
- It can help identify whether a file may be missing or whether a charge difference may be due to a fee, return, or weight adjustment.
If the evidence is weak, the item remains unmatched rather than being forced into a low-confidence match.
Manual review and audit readiness
When the system and AI cannot confidently match a transaction, users can manually match records if the totals and business context support it. Manual matches remain visible and auditable.
Teams can also review reconciliation history in the dashboard, which helps with internal audit, vendor follow-up, and period-end reporting.
For finance teams that manage shipping costs closely, this makes DTDC shipping invoice reconciliation more controlled than spreadsheet-based review.
