DX Express Shipping Invoice Verification with Cointab

Cointab helps finance teams verify DX Express shipping invoices by comparing internal shipment and order records against courier billing data, rate cards, pincode masters, and other supporting files. Instead of checking every line manually in Excel, teams can map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a structured report.

What DX Express invoice verification covers

Shipping invoice verification is not only about checking the final billed amount. Finance teams usually need to confirm whether the courier has applied the correct zone, weight slab, delivery type, and additional charges for each shipment.

A typical DX Express reconciliation workflow can help teams review:

• Order and shipment references
• Billing zone and pincode mapping
• Forward freight charges
• RTO charges
• COD charges
• GST or tax treatment
• Weight differences and volumetric weight logic
• Missing, duplicate, or incomplete invoice lines

This makes the process more transparent for finance, AP, and logistics operations teams that need a clear audit trail.

How Cointab structures the reconciliation

Cointab uses a Side A and Side B model for shipping invoice verification.

Side A: your records

Side A contains the records your business expects to be correct. For this workflow, that may include:

• ERP shipment or order exports
• Internal sales or dispatch reports
• SKU master data
• Product weight and dimension files
• Internal billing or courier accrual workings
• Pincode master or serviceability mapping

Side B: DX Express records

Side B contains the external records received from DX Express, such as:

• Shipping invoice files
• Courier billing statements
• Rate card or tariff references
• Shipment-level charge summaries
• COD or return charge lines

Supporting data

Supporting data is optional, but it is often useful in courier invoice verification. It can help enrich the primary data before reconciliation.

Examples include:

• Rate card files
• Pincode zone masters
• SKU and dimension masters
• Order metadata
• Weight calculation references
• Return or reverse pickup reports

Typical verification flow

A logistics finance team can use Cointab to run the workflow in a consistent order.

1. Upload the DX Express invoice file and internal source files.
2. Map fields such as order ID, shipment reference, date, amount, and identifiers.
3. Add supporting data like pincode master or rate card files.
4. Create derived columns if the team needs clean identifiers or calculated weights.
5. Run reconciliation manually or on a schedule.
6. Review matched, partially matched, unmatched, and skipped records.
7. Download the Excel reconciliation report for review and follow-up.

If a file was missed, it can be uploaded later under the same reconciliation and the report can be refreshed.

What gets checked in a shipping invoice review

Cointab helps teams compare the charges on the invoice with what should have been billed based on the agreed logic.

Forward charges

Forward charges are usually verified against the shipment's zone, billable weight, and rate card slab. Cointab can help teams compare whether the applied charge matches the expected charge based on the configured data.

RTO charges

For returned shipments, teams often need to verify whether the return-to-origin amount follows the correct slab and rate card rules.

COD charges

If cash-on-delivery charges apply, Cointab can help compare the fixed fee or percentage-based charge against the agreed rate.

Weight and volumetric weight checks

Shipping invoices can differ from internal records when a courier uses a different billable weight than the one stored in ERP. Supporting SKU or dimension data can be used to calculate or validate the expected weight before comparison.

Pincode and zone checks

A pincode master helps teams verify whether the shipment has been billed under the correct zone. This is especially useful when the tariff varies by origin and destination mapping.

GST and additional charges

Teams can also review tax and surcharge components to understand whether the final billed amount aligns with the expected calculation.

How exceptions are handled

Not every shipment will match perfectly. Cointab separates exceptions so finance teams can focus on the items that need review.

Fully matched

These are transactions where the shipment reference, charge logic, and amount align with the expected records.

Partially matched

These are transactions where the shipment is identified correctly, but the amount differs. This can happen because of weight changes, zone changes, returns, or extra charges.

Unmatched

These are records found on one side but not the other. For example, a DX Express invoice line may not appear in the ERP shipment file, or an internal shipment may be missing from the courier invoice.

Skipped

Skipped records are rows that could not be used because of missing required fields, invalid amounts, duplicates, or file-format issues.

Why finance teams use Cointab for courier invoice verification

Courier invoice checks often repeat every week or month, and the same logic is rebuilt again and again in spreadsheets. Cointab helps finance teams turn that work into a reusable workflow.

Key benefits include:

• Reusable reconciliation setup for future billing periods
• Consistent matching logic across runs
• Clear exception visibility for AP and finance teams
• Audit-ready Excel reports for internal review
• Manual match support for one-off cases
• Team workspace support with shared reconciliation history

This is useful when courier billing needs to be reviewed alongside month-end close, accrual checks, or vendor settlement review.

When automation is a better fit than spreadsheets

Manual invoice verification can become slow when the invoice file is large or when the team needs to compare multiple references such as order IDs, consignment numbers, AWB numbers, zone codes, and weight slabs.

Cointab is designed to reduce that manual work by letting teams:

• Upload data in CSV, XLS, or XLSX format
• Map date, amount, and identifier fields once
• Use derived columns for clean references or calculated values
• Reconcile multiple files on each side when needed
• Schedule recurring runs through email, SFTP, or API-based automation

This makes shipping invoice verification more repeatable and easier to audit.

Reconciliation reports for review and follow-up

After the run completes, the reconciliation report shows the outcome in a structured format. Finance teams can review the overall summary and then drill into the transaction-level detail.

The report typically includes:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper analysis
• Transaction-level tables
• Downloadable Excel output

This helps teams investigate overcharges, undercharges, missing invoices, and differences caused by weight, zone, or charge setup.

A practical workflow for DX Express invoice control

For teams managing shipping costs, the most useful workflow is the one they can reuse every period. Once the DX Express reconciliation is configured, future runs can follow the same pattern:

• Select the reconciliation
• Select the period
• Upload or receive the files
• Run reconciliation
• Review the report
• Carry forward unresolved items if needed

That approach keeps shipping invoice verification organized, transparent, and easier to manage across finance and operations teams.