StarTrack Shipping Invoice Reconciliation

Cointab helps finance and operations teams reconcile StarTrack shipping invoices against internal shipment records, ERP exports, and supporting masters. Instead of checking every line in Excel, users upload the required files, map the fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in an audit-ready report.

What StarTrack shipping invoice reconciliation covers

Shipping invoice reconciliation compares what your business expected to be charged with what appeared on the carrier invoice. For StarTrack billing review, that usually means comparing an internal shipment or order file on one side with the invoice or shipment statement on the other side.

Typical checks include:

• Shipment reference or order ID alignment
• Zone or postcode mapping
• Weight, volumetric weight, or weight slab validation
• Freight charge comparison
• Additional charges, surcharges, or adjustments
• Missing shipments or missing invoice lines
• Duplicate billing or repeated reference numbers

Cointab is built for this Side A and Side B model:

• Side A: your internal shipment, ERP, or order records
• Side B: StarTrack invoice or carrier statement data

This structure keeps the reconciliation process transparent for finance teams and easier to audit later.

Data commonly used in the workflow

Shipping invoice reconciliation is usually more accurate when finance teams combine the primary invoice files with supporting data. Cointab allows supporting files to be used for enrichment, lookup, merging, or calculation before reconciliation.

Common inputs include:

• ERP shipment or sales export
• Dispatch or order fulfilment report
• StarTrack invoice or billing statement
• SKU or product master
• Postcode or zone master
• Rate card or charge matrix
• Returns or reverse logistics report
• Customer, vendor, or store mapping file

These files help finance teams verify whether the billed charge matches the expected charge, not just whether a shipment ID appears on both sides.

How Cointab handles the reconciliation workflow

A typical reconciliation setup follows a structured flow:

1. Upload the StarTrack invoice data and the internal shipment data.
2. Map required fields such as date, amount, and identifier columns.
3. Add supporting files if you need lookups, enrichment, or calculations.
4. Create derived columns where needed, such as a cleaned reference field or a calculated freight amount.
5. Run the reconciliation manually or schedule it to run automatically.
6. Review the reconciliation report while the engine processes matching in the background.
7. Explore fully matched, partially matched, unmatched, and skipped transactions.
8. Download the Excel report for internal review, follow-up, or audit support.

Because the setup is reusable, the same StarTrack reconciliation can be used again for the next billing period without rebuilding the workflow.

The kinds of differences this process can reveal

Shipping invoice mismatches are often subtle. The invoice may be close to expected, but not exact. Cointab helps surface the difference clearly so finance teams can investigate the right records first.

Examples of issues the reconciliation can highlight include:

• A shipment billed under the wrong zone
• A weight slab that differs from the internal shipment record
• A dimensional weight calculation that increases the charge
• A freight fee that does not match the rate card
• A shipment that appears on the invoice but not in the internal system
• A shipment present internally but missing from the invoice
• A duplicate or partially duplicated charge
• A return shipment or adjustment that needs separate review
• A file that was missed and uploaded later under the same reconciliation

Open transactions can then be reviewed manually if the business context is clear but the system cannot confidently match them on its own.

Why finance teams use Cointab for shipping invoice verification

StarTrack invoice review is usually not a one-time task. It repeats every billing period, and the same checks are often done by different team members. Cointab brings consistency to that process.

Better control over invoice review

Reconciliation rules are configured once and reused. That reduces spreadsheet dependence and makes review steps more consistent across periods.

Faster exception handling

Instead of manually scanning every row, teams can focus on the exceptions that matter:

• Partially matched charges
• Unmatched shipment references
• Skipped records with missing or invalid data
• Billing differences that need investigation

Audit-ready reporting

Cointab produces downloadable reports that show what matched, what did not match, and what was skipped. That gives finance teams a clear record for month-end review, internal controls, and audit support.

Support for recurring workflows

Once a reconciliation is set up, it can be reused for future periods. Teams can run it manually, automate the data flow through email, SFTP, or API, and optionally push output back to internal systems.

When a custom shipping reconciliation is useful

Some businesses have a standard carrier invoice format and can use a reusable workflow as-is. Others need a custom reconciliation because the internal shipment file, rate card logic, or reference fields are specific to their operations.

A custom StarTrack workflow may be useful when you need to compare:

• ERP shipment data vs carrier billing
• Order report vs delivery invoice
• Shipment dispatch data vs freight statement
• Sales or fulfilment records vs carrier charges
• Internal expected freight vs billed freight after surcharges

Cointab supports this by letting finance teams define the reports on each side, map the fields, and reuse the setup for future runs.

What the report gives finance teams

After the reconciliation is complete, users can review a dashboard that shows:

• Total summary
• Fully matched transactions
• Partially matched transactions
• Unmatched transactions
• Skipped transactions
• Filters for deeper analysis
• Transaction-level detail for follow-up

This makes it easier to answer practical finance questions such as:

• Which shipments were billed exactly as expected?
• Which invoices need a correction or vendor follow-up?
• Which differences are due to weight, zone, or surcharge logic?
• Which rows were ignored because the source file was incomplete?

For recurring carrier invoice review, that level of visibility is often more useful than a simple total difference.