Guides & Resources
Shiprocket Invoice Reconciliation for Shipping Partner Charges
Cointab helps ecommerce and finance teams reconcile Shiprocket shipping partner invoices against internal order data, SKU data, pin code masters, and rate card rules. Instead of checking every shipment manually in Excel, teams can upload the relevant files, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped transactions in a structured report.
This is useful when shipping costs need to be verified across multiple reports and billing dimensions, such as billed weight, zone, shipment date, service type, and applicable rate slabs. Cointab makes the workflow easier to repeat for each period and keeps the review trail clear for finance, audit, and partner follow-up.
What Shiprocket reconciliation helps finance teams verify
Shipping partner invoices often contain many line items and rule-based charges. Finance teams usually want to confirm that each shipment was billed correctly and that the invoice matches the business records.
With Cointab, teams can compare:
- Internal order or shipment data on Side A
- Shiprocket invoice or billing data on Side B
- SKU masters with gross or dimensional weight
- Pin code or zone masters
- Rate card or charge-rule files
- Optional returns, COD, or supporting reports
This helps teams identify differences such as:
- Incorrect billed weight
- Zone mismatches
- Rate card mismatches
- Missing shipments
- Duplicate or unusable rows
- Amount differences that need review
Typical Side A and Side B setup for Shiprocket
Cointab uses a clear reconciliation model.
Side A: your internal records
Side A usually contains the data your business expects to be correct, such as:
- OMS or order export
- ERP shipment export
- Internal delivery or dispatch report
- SKU master
- Weight or product master
- Internal settlement working file
Side B: Shiprocket and related partner records
Side B usually contains the external records received from the shipping partner, such as:
- Shiprocket invoice
- Shipment billing report
- Zone or pin code reference file
- Courier or rate card file
- Exception or adjustment report
If additional supporting reports are needed, they can be uploaded alongside the primary files and used for lookup, enrichment, or calculation before reconciliation runs.
How the reconciliation workflow works
A Shiprocket shipping partner reconciliation in Cointab follows a simple workflow:
- Upload the required files for Side A and Side B.
- Map the key fields such as shipment date, amount, order ID, AWB, reference number, or pin code.
- Upload supporting files if you need lookups or calculations.
- Create derived columns if needed, such as a cleaned shipment reference or calculated weight field.
- Run reconciliation manually or on a scheduled basis.
- Review the report dashboard once processing is complete.
- Open the matched, partially matched, unmatched, and skipped views to investigate exceptions.
- Download the Excel report for review, follow-up, or audit use.
If a file was missed earlier, it can be uploaded under the same reconciliation and the report can be refreshed.
What gets checked in a Shiprocket invoice review
The exact logic depends on how the customer’s shipping workflow is structured, but common checks include:
- Shipment reference matching between internal data and Shiprocket data
- Expected versus billed weight
- Pin code or zone mapping
- Rate card applicability for the shipment date
- Forward, return, or COD-related charge differences
- Invoice amount versus expected amount
- Shipments present on one side but missing on the other
For many finance teams, the goal is not only to confirm that an invoice total is correct, but also to understand why a line item differs and whether the issue is a data problem, a billing issue, or a legitimate operational charge.
Common mismatch scenarios
Cointab separates exceptions clearly so teams can focus on what needs attention.
| Scenario | What it means | Typical review action |
|---|---|---|
| Fully matched | Internal data and Shiprocket data match according to the configured rules | Mark as verified |
| Partially matched | Shipment is linked, but one or more fields such as amount or weight differ | Review the difference and confirm the reason |
| Unmatched | Record appears on one side but not the other | Check for a missing file, missing shipment, or data issue |
| Skipped | Record could not be included in reconciliation | Review missing columns, invalid values, or unusable rows |
Common causes of differences include zone mapping issues, weight calculation differences, rate card changes, shipment corrections, or missing order records.
Reporting for audit and review
After reconciliation runs, users can review a clear report dashboard with transaction-level detail. The report helps finance teams see what was matched, what remains open, and what should be escalated.
Useful report views include:
- Total summary
- Fully matched summary
- Partially matched summary
- Unmatched summary
- Skipped summary
- Filters for deeper investigation
- Transaction-level tables
- Downloadable Excel output
This format is useful for period-end close, internal review, partner follow-up, and audit preparation because the logic and outcomes remain visible.
Why teams use Cointab for recurring shipping partner reconciliation
Shiprocket reconciliation is rarely a one-time task. Most ecommerce teams need the same review every month, every settlement cycle, or every time a new invoice arrives.
Cointab supports that recurring workflow by allowing teams to:
- Reuse the same reconciliation setup for future periods
- Map fields once and run the same process again
- Use manual match when the system needs a finance-side override
- Add supporting data for enrichment or calculation
- Automate file input through email, SFTP, or API where needed
- Push output back to internal systems through email, SFTP, or API
This helps reduce repeat Excel work and makes the shipping invoice review process more consistent across periods.
When a custom Shiprocket workflow is useful
Some teams use standard shipment and invoice formats, while others need a more specific workflow based on their internal data structure. Cointab supports both.
A custom Shiprocket reconciliation is useful when your business needs to compare:
- OMS shipment data versus Shiprocket invoices
- Internal shipping working files versus partner billing reports
- Order, SKU, and zone reference data together
- Additional supporting files for lookups or derived fields
This is especially helpful when the same reconciliation has to be repeated across multiple periods and the finance team wants a structured process instead of rebuilding spreadsheets each time.
How Cointab supports finance teams beyond matching
Shipping reconciliation is not only about finding differences. It is also about making those differences easier to investigate and report.
Cointab helps teams:
- Keep the reconciliation logic reusable
- Review only open items that need attention
- Separate matched, partially matched, unmatched, and skipped records
- Work in a shared team workspace
- Maintain a clearer audit trail for review and handoffs
For finance teams handling shipping charges at scale, that structure matters as much as the final amount itself.