GlowRoad Marketplace Reconciliation Automation

Cointab helps finance teams reconcile GlowRoad marketplace data with internal records, payout statements, settlements, and bank entries in a structured and reusable workflow. Instead of comparing files in Excel every period, teams can upload the required reports, map fields once, run reconciliation, and review matched, partially matched, unmatched, and skipped records in one report.

What GlowRoad marketplace reconciliation typically compares

GlowRoad reconciliation usually involves matching your internal business records against the reports you receive from the marketplace and your bank.

Side A: your records

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

• Internal order or sales report
• ERP or ledger export
• Refund or return working file
• Customer or order master data
• Any supporting file used for lookups or calculations

Side B: external records

Side B contains the records received from GlowRoad or related external sources. These may include:

• Order detail report
• Payout report
• Settlement report
• Bank statement
• Deduction or adjustment report
• Supporting files used by the marketplace or finance team

This side-by-side model helps teams compare what should have happened with what actually happened.

Common GlowRoad reconciliation workflows

Order to payout matching

A common workflow is to compare internal order data with GlowRoad payout records. This helps teams confirm whether orders were paid, partially paid, overpaid, deducted, or still open.

Settlement to bank statement matching

Many teams also reconcile GlowRoad settlement reports against bank deposits. This helps identify whether the expected settlement amount was received, delayed, short-paid, or recorded differently in the bank.

Returns, cancellations, and deductions

Marketplace reconciliation often includes returns, cancellations, reversals, and deductions. Cointab helps users see whether these items were reflected in the external reports and whether the net amount aligns with internal records.

Supporting report checks

If your workflow uses additional files for lookups, mapping, or calculations, those files can be added as supporting data. Supporting data is used to enrich the primary reports before reconciliation.

How the reconciliation workflow works

Cointab follows a clear workflow so finance teams can understand exactly what is being matched.

1. Upload the required Side A and Side B files.
2. Map the required columns, such as date, amount, and reference fields.
3. Add supporting data if lookup, merge, or enrichment is needed.
4. Create derived columns when a cleaned or calculated field is required.
5. Run reconciliation manually or schedule it for recurring runs.
6. Review the reconciliation report and investigate open items.
7. Download the Excel report for internal review, audit, or follow-up.

Users can work with common identifiers such as order ID, transaction reference, payout reference, settlement ID, or bank UTR, depending on the format of the source files.

How Cointab classifies the results

Cointab separates transactions into clear result buckets so teams can focus on exceptions instead of reviewing every row manually.

Fully matched

These are transactions where the identifiers and amounts match according to the configured reconciliation logic.

Partially matched

These are transactions where the records are related, but the amounts do not fully align. Partial matches are useful for spotting underpayments, overpayments, deductions, or rounding differences.

Unmatched

These are transactions that appear on one side but cannot be found on the other side. Unmatched records often indicate missing files, open settlements, timing differences, or data issues that need review.

Skipped

Skipped records are rows that were excluded from reconciliation because they were incomplete, invalid, duplicated, or did not meet the required format.

Manual match

If the system cannot confidently match a transaction, users can manually match it when the totals tally and the business context is clear. Manual matches remain visible for auditability.

Why this matters for finance teams

GlowRoad reconciliation is not only about confirming payments. It is also about making month-end close, reporting, and follow-up work more controlled.

• Reduce repetitive Excel-based comparison work
• Keep matching logic consistent across periods
• Separate exceptions from clean transactions
• See why a record is unmatched or partially matched
• Reuse the same reconciliation setup in future periods
• Maintain an audit-ready record of what was matched and what was not

For finance teams managing marketplace revenue, settlements, and bank movement, a structured workflow makes the review process easier to explain and easier to repeat.

Reuse and automation for recurring runs

Once the GlowRoad reconciliation is set up, the same workflow can be reused for future periods. Teams do not need to rebuild the logic every month.

Cointab also supports recurring automation through email, SFTP, or API-based data flow where needed. That makes it possible to receive files, validate them, run reconciliation, and prepare reports on a scheduled basis.

If a report file is received late or missed entirely, it can be uploaded later under the same reconciliation and the report can be refreshed.

What the report includes

After reconciliation is complete, users can review a dashboard with transaction-level detail and summary views.

Typical report outputs include:

• Total summary
• Fully matched summary
• Partially matched summary
• Unmatched summary
• Skipped summary
• Filters for deeper analysis
• Detailed matched transaction view
• Downloadable Excel output

This gives finance teams a clear view of what was reconciled, what needs follow-up, and what is ready for internal review.

FAQs

What can be reconciled for GlowRoad?

Common GlowRoad workflows include order to payout matching, settlement to bank reconciliation, and review of returns, cancellations, and deductions. Teams can also use supporting files when lookup or enrichment is needed.

Can the same GlowRoad workflow be reused each month?

Yes. Once the reconciliation is configured, the same setup can be reused for future periods. Users only need to upload the current files, run reconciliation, and review the report.

What if a GlowRoad file is received late?

If a file is missed or arrives later, it can be uploaded under the same reconciliation and the report can be refreshed so the latest data is included.

How does Cointab handle items it cannot match confidently?

Cointab leaves uncertain items open rather than forcing a weak match. Users can review unmatched and partially matched records, then apply manual match where the business context supports it.