How to Reconcile Revenue with Cointab

Revenue reconciliation helps finance teams confirm that internal revenue records align with external data such as payment gateway reports, settlement files, bank statements, marketplace reports, or vendor statements. When this work is done manually in spreadsheets, it can become slow, repetitive, and difficult to audit.

Cointab gives finance teams a structured way to reconcile revenue by uploading data, mapping fields once, running matching logic, reviewing exceptions, and downloading audit-ready reports. The same setup can be reused for future periods, which is especially useful for recurring month-end, quarter-end, or daily reconciliation workflows.

Why revenue reconciliation matters

Revenue reconciliation is not just about finding differences. It helps teams maintain control over reported revenue, spot missing receipts, identify settlement deductions, and understand why transactions do not fully match.

For finance teams, this typically means comparing Side A and Side B data:

• Side A: your internal records, such as sales reports, ERP exports, invoices, or revenue ledgers
• Side B: external records, such as payment gateway files, bank statements, marketplace settlements, or partner reports

This comparison helps teams identify:

• fully matched revenue records
• partial matches where the identifiers align but the amounts differ
• unmatched items present on only one side
• skipped rows that were excluded because of missing or invalid data

Common revenue reconciliation workflows

Cointab is flexible enough to support many revenue-related workflows, including:

• sales vs payment gateway reconciliation
• marketplace sales vs settlement reconciliation
• bank vs books reconciliation
• invoice vs receipt reconciliation
• customer or vendor statement reconciliation
• custom revenue workflows built around internal and external reports

If your revenue process uses a standard partner report format, you can use a popular reconciliation. If your business has a unique data structure, you can create a custom reconciliation and reuse it every period.

Step 1: Choose the right reconciliation setup

Start by selecting the reconciliation that matches your workflow.

Popular reconciliation

Use this when Cointab already supports a standard report structure, such as a payment gateway, marketplace, or bank-style workflow. The required logic and file format are already defined, so the setup is faster.

Custom reconciliation

Use this when you need to reconcile business-specific revenue data. You can define both sides of the workflow, upload multiple reports, and configure the fields that matter to your business.

This is useful for cases like:

• internal sales report vs multiple payment processors
• ERP revenue data vs marketplace settlement files
• invoice register vs received payment data
• revenue ledger vs bank statement

Step 2: Upload Side A and Side B files

Once the reconciliation is selected, upload the required files.

Cointab supports common file formats such as CSV, XLS, and XLSX. For each primary report, you map the key fields that the engine needs to understand the data, such as:

• transaction date
• amount
• order ID
• invoice number
• payment reference
• bank UTR
• settlement ID
• customer code
• any other business identifier

If a file does not match the configured format, Cointab can reject it with a clear error so the issue is visible before reconciliation runs.

Step 3: Map fields once

Field mapping is one of the most important parts of a revenue reconciliation workflow.

After upload, define which columns represent:

• the date field
• the amount field
• the identifier field or fields
• any additional fields needed for matching or review

This makes future runs easier because the same structure can be reused. Finance teams do not need to rebuild the setup every time a new period is reconciled.

Step 4: Add supporting data if needed

Revenue reconciliation often needs more than just the main reports. Cointab lets you upload supporting data to enrich or prepare the primary records before matching.

Examples include:

• product master files
• fee rate files
• return reports
• order metadata
• GST or tax mapping files
• SKU mapping files
• customer or vendor master files
• delivery partner reference data

Supporting data is useful when you need to:

• add missing order details
• combine sales and returns
• look up fee or tax values
• normalize identifiers
• prepare data for reconciliation without relying on manual Excel formulas

Step 5: Create derived columns when required

Sometimes revenue reconciliation requires calculated fields.

Cointab supports derived columns, which are calculated from existing columns and can be used for amounts, identifiers, lookups, or matching logic.

Examples include:

• clean order ID
• net amount
• delivered payment amount
• amount after fee
• refund amount as negative
• combined reference field
• normalized transaction ID

You can also use AI to help generate Excel-style formulas from simple natural-language instructions. This is especially helpful when a finance user knows the business rule but does not want to write the formula manually.

Step 6: Run reconciliation

After the files and fields are configured, run the reconciliation.

Cointab applies structured matching logic to compare records across both sides. It can support common matching scenarios such as:

• one-to-one matching
• one-to-many matching
• many-to-one matching
• many-to-many matching
• net-to-net matching
• partial matching
• contra matching

During the run, users can see progress clearly so they know the process is active and not stalled.

Step 7: Review matched, partially matched, unmatched, and skipped records

Once the reconciliation is complete, the report shows the outcome in a finance-friendly format.

Fully matched

These are records where identifiers and amounts align according to the reconciliation logic.

Partially matched

These are records where the identifier matches, but the amount is different. Partial matches are important because they usually point to a settlement difference, fee deduction, refund, short payment, or timing issue.

Unmatched

These are records that appear on one side but not the other. For example, a sale may exist in your internal report but not in the payment gateway file, or a bank credit may appear without a matching book entry.

Skipped

These are rows that were excluded from reconciliation because of issues such as incomplete data, invalid amounts, duplicates, or missing required fields. Skipped records are visible so finance teams understand what was not processed.

Step 8: Investigate open items with AI and manual review

After structured matching, Cointab can help analyze remaining open transactions.

AI can assist with difficult cases such as:

• slightly different descriptions
• missing or partial identifiers
• unstructured references
• exception items that require business context
• open items where the correct match is not obvious

If the evidence is not strong enough, the item remains unmatched rather than being forced into a weak match. That keeps the reconciliation process conservative and reviewable.

When needed, users can also manually match transactions. Manual matches are useful for one-off exceptions or cases where a finance user has the context that the system cannot infer.

Step 9: Download the reconciliation report

After review, finance teams can download an Excel reconciliation report that includes the matched, partially matched, unmatched, and skipped records.

This supports:

• internal review
• month-end close
• partner follow-up
• audit preparation
• exception tracking
• management reporting

Because the report is structured, it is easier to share across finance, operations, and audit teams than a spreadsheet built from scratch.

Step 10: Reuse the setup for future periods

One of the most useful parts of Cointab is reuse.

Once a revenue reconciliation is configured, the same workflow can be used again for future periods. For recurring monthly or daily work, the process becomes much simpler:

1. select the reconciliation
2. choose the period
3. upload the files or receive them automatically
4. run reconciliation
5. review the report

This reduces repeated setup and makes the process more consistent across periods.

Automating recurring revenue reconciliation

For teams that reconcile revenue frequently, Cointab can support automated data input through email, SFTP, or API integrations. That means data can be received or pulled on a schedule, validated, loaded into the correct workflow, and reconciled automatically.

Cointab can also push reconciliation output back to internal systems through email, SFTP, or API. This helps teams keep accounting, ERP, analytics, or BI workflows updated without repeating manual file handling.

What finance teams gain from a structured process

A structured revenue reconciliation workflow helps teams:

• reduce repetitive Excel work
• keep matching logic consistent across periods
• isolate exceptions faster
• maintain clearer audit trails
• handle large or multi-source datasets more reliably
• reuse the same configuration for recurring revenue checks

For finance leaders, the key benefit is visibility. You can see what matched, what did not match, what was skipped, and what needs review in one place.

Revenue reconciliation questions finance teams usually ask

Before closing a period, finance teams often want to know:

• Did every sale or invoice receive the expected payment or settlement?
• Are there deductions, refunds, or fees that explain the difference?
• Are any files missing from a partner, bank, or marketplace?
• Which items need manual review before the books are finalized?
• Can the same setup be reused next month without rebuilding it?

Cointab is built to make those questions easier to answer through a repeatable reconciliation workflow.

Practical example of revenue reconciliation

A D2C brand may upload its internal sales report on Side A and payment gateway data on Side B. Cointab matches order IDs and amounts, shows fully matched transactions, flags partial matches where fees or refunds created a difference, and isolates unmatched records for review.

The same approach can be used for:

• marketplace sales vs settlement
• bank vs books
• customer receivables vs receipts
• vendor statements vs internal ledgers

FAQ

What is revenue reconciliation in Cointab?

Revenue reconciliation in Cointab is the process of comparing internal revenue records with external reports, matching transactions, identifying differences, and downloading an audit-ready report.

Can Cointab handle custom revenue workflows?

Yes. You can build custom reconciliations for business-specific workflows where the reports, identifiers, or matching logic are unique to your process.

What file types can be uploaded?

Cointab supports common spreadsheet and CSV file formats such as CSV, XLS, and XLSX for primary reconciliation files.

What happens to unmatched revenue items?

Unmatched items remain visible in the report so finance teams can investigate them, apply manual review where needed, and determine the appropriate follow-up action.

Can the same revenue reconciliation be reused later?

Yes. Once a reconciliation is configured, it can be reused for future periods instead of being rebuilt from scratch.