Shopify with Increff Reconciliation
Shopify with Increff reconciliation is a common eCommerce finance workflow for comparing order and fulfillment records across two systems that often serve different business teams. Shopify usually reflects customer order activity, while Increff is used for order management and downstream operational reporting. Finance teams use reconciliation to confirm that records match, identify exceptions, and keep order, payment, and settlement data aligned.
With Cointab, this becomes a reusable custom reconciliation setup. Teams upload the required reports, map the fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in a structured report. The same setup can be reused for future periods instead of rebuilding spreadsheets every month.
Why finance teams reconcile Shopify with Increff
In eCommerce operations, the same order can appear in multiple systems with slightly different identifiers, statuses, or amounts. A Shopify order may be marked one way, while Increff may show a fulfilled, canceled, returned, or adjusted version of the same business transaction.
Finance teams usually reconcile these reports to:
- confirm that orders captured in Shopify are reflected correctly in Increff
- identify fulfilled orders, cancellations, and returns that need review
- check whether operational records support payment and settlement tracking
- detect missing, duplicate, or incorrectly mapped transactions
- prepare cleaner month-end and audit-ready reports
This is especially important when the reconciliation expands beyond the two core systems and includes payment gateway, COD remittance, or bank statement data.
Typical data used in this reconciliation
A Shopify with Increff reconciliation usually compares Side A and Side B records, with optional supporting files for enrichment or validation.
| Side | Typical data | Why it matters |
|---|---|---|
| Side A | Shopify order report | Acts as the customer order record and order source of truth |
| Side B | Increff order report | Shows fulfillment, operational status, and related order details |
| Supporting data | SKU master, mapping file, tax file, fee file, return file | Helps enrich records before matching |
| Optional external reports | Payment gateway, COD remittance, bank statement | Helps extend the workflow into payment and settlement reconciliation |
Cointab lets teams map key columns such as date, amount, order ID, transaction reference, invoice number, shipment reference, or other business identifiers. If a report has a different structure in a later period, the setup can be reused and refreshed with the new files.
How the reconciliation workflow works in Cointab
A Shopify with Increff setup follows the same structured reconciliation flow used across Cointab.
- The user creates a new reconciliation in a team workspace.
- The user selects a custom reconciliation workflow.
- Shopify and Increff reports are uploaded on Side A and Side B.
- Required fields are mapped once, such as date, amount, and order identifier.
- Optional supporting data can be uploaded for lookup, merge, or calculation.
- Derived columns can be created when a cleaned or calculated field is needed.
- The user runs reconciliation manually or schedules it automatically.
- Cointab applies structured matching logic.
- Open transactions are reviewed with AI-assisted analysis where needed.
- The report is displayed with matched, partially matched, unmatched, and skipped records.
- The Excel report can be downloaded for review, follow-up, and audit support.
This approach reduces repeated spreadsheet work and gives finance teams a consistent reconciliation process across periods.
Common matching scenarios
Shopify and Increff records may not always line up perfectly on the first pass. Cointab supports structured matching across several real-world scenarios, including:
- one-to-one matches where order ID and amount align
- one-to-many matches where a single record needs to be grouped with multiple records
- many-to-one matches where multiple entries settle against one business record
- partial matches where the identifiers align but the amounts differ
- contra or netting scenarios where records need to be compared after adjustments
This is useful when finance teams need to handle returns, canceled orders, split fulfillment, fee deductions, or other operational differences that affect the final reconciliation view.
What finance teams review in the report
Once reconciliation is complete, the report dashboard shows the key outcomes in a format that is easier to review than a spreadsheet full of formulas.
Fully matched records
These are records where the relevant identifiers and values match according to the configured logic. For example, an order recorded in Shopify appears in Increff with the expected identifier and amount.
Partially matched records
These are records where a match is likely, but the values do not fully agree. This often highlights a price change, fee difference, quantity issue, return adjustment, or another exception that needs review.
Unmatched records
These are transactions present on one side but missing on the other. For example, an order may exist in Shopify but not in Increff, or the operational record may exist without a matching source order.
Skipped records
These are rows excluded from reconciliation because they were incomplete, invalid, duplicated, or did not meet the configured file requirements. Skipped records remain visible so the team understands what was not processed and why.
How supporting files help the reconciliation
Shopify with Increff reconciliation is often more effective when finance teams include supporting reports.
Supporting files are not reconciled directly. They are used to enrich or prepare the main reports before matching. Common examples include:
- SKU master files
- product or store mapping files
- return reports
- tax reports
- payment gateway settlement files
- COD remittance files
- bank statements
- fee or rate card files
These files help teams add missing details, calculate adjusted values, normalize reference fields, and reduce manual VLOOKUP-style work.
Using derived columns for cleaner matching
Sometimes the raw columns in Shopify and Increff are not enough for a clean comparison. Cointab lets teams create derived columns using formulas, including AI-assisted formula generation.
Examples of derived columns include:
- cleaned order ID
- normalized reference number
- net amount after adjustments
- refunded amount as a negative value
- delivery-status-based amount
- combined reference for matching
Derived columns are recalculated every time the reconciliation runs, which helps keep the workflow consistent and reusable.
Why this is better than manual spreadsheet reconciliation
Manual reconciliation in Excel can work for small files, but it becomes difficult to audit and repeat when reports grow or when the workflow expands across multiple sources.
A structured Shopify with Increff reconciliation helps teams:
- reduce copy-paste and formula errors
- keep matching logic consistent across periods
- review only the open items that need attention
- preserve an auditable history of the run
- reuse the same setup instead of recreating it each month
- work in a shared finance workspace instead of passing files around
Cointab also makes it easier to track who ran a reconciliation, which files were used, and how the results were generated.
Extending the workflow into payments and settlements
Many teams use Shopify and Increff reconciliation as the operational base layer, then extend it to payment and settlement checks.
That can include comparisons such as:
- Shopify and Increff versus payment gateway records
- payment gateway settlement versus bank statement
- COD remittance versus bank statement
- order-level data versus refund or return reports
This gives finance teams a fuller view of what happened from order creation to settlement and helps them investigate differences earlier.
Reconciliation automation for recurring runs
Once the Shopify with Increff workflow is configured, Cointab can support recurring reconciliation through scheduled runs and automated data movement.
Teams can use:
- email-based file intake
- SFTP-based file transfer
- API-based data integration
- scheduled reconciliation runs on a daily, weekly, or monthly basis
This is useful for finance operations that need regular reporting and do not want to upload the same reports manually every time. The same reconciliation can remain on the dashboard for future reference, and missed files can be added later before refreshing the report.
AI support for open items and formulas
Cointab uses AI in practical ways that support finance teams without replacing review controls.
AI can help with:
- generating Excel-style formulas for derived columns
- analyzing difficult open items after structured matching
- suggesting likely reasons for differences
- identifying whether a file may be missing
- helping teams review unresolved transactions more efficiently
If evidence is not strong enough, the item remains unmatched rather than being forced into a weak match.
FAQ
Is Shopify with Increff reconciliation a standard or custom setup?
It is usually configured as a custom reconciliation because each business may use different report formats, identifiers, and matching logic. The setup can be reused once configured.
Can the workflow include payment gateway, COD, or bank reports?
Yes. Many finance teams extend the core Shopify and Increff workflow with payment gateway, COD remittance, and bank statement files to review the full order-to-settlement chain.
What if the Shopify or Increff file format changes later?
Cointab validates the uploaded file against the configured structure. If a file does not match, the system can reject it with a clear message so the team can correct the issue before running reconciliation.
Can partially matched and unmatched records be reviewed separately?
Yes. The report separates fully matched, partially matched, unmatched, and skipped records so finance teams can focus on exceptions instead of reviewing every line item manually.
Can the same reconciliation be reused every month?
Yes. Once the setup is created, the same workflow can be reused for future periods by uploading the new files and running the reconciliation again.