Website Orders with Payment Gateway Reconciliation

Reconcile website orders with payment gateway transactions, settlement reports, and bank statements in one structured workflow. Cointab helps finance teams match internal order data with external payment records, identify differences early, and review audit-ready reports without rebuilding the process every month.

This is especially useful for eCommerce, D2C, retail, and other payment-heavy businesses that process a large number of prepaid orders. Instead of comparing exports in Excel, teams can map fields once, run reconciliation, and focus on the exceptions that need review.

What gets reconciled

Website order reconciliation usually compares your internal business records against external payment and settlement records.

Side A contains the records your business expects to be correct. Side B contains the records received from the payment gateway, bank, or other external source.

Why payment gateway reconciliation matters

When website orders are paid online, the order value on your system does not always match the amount ultimately settled in the bank. Common differences include:

• underpayments or short collections
• overpayments or duplicate payments
• refunds and reversals
• cancelled orders that were paid before cancellation
• fee deductions and service charges
• tax differences where applicable
• settlement delays or missing bank entries
• partial matches where the order reference is correct but the amount is not

If these items are not tracked clearly, finance teams can miss settlement differences, delay month-end close, or spend too much time investigating payment issues one by one.

How Cointab handles website order reconciliation

Cointab provides a reusable reconciliation workflow for comparing website order data with payment gateway and bank records.

1. Upload the required files

Users can upload CSV, XLS, or XLSX files for the reconciliation.

Typical inputs include:

• internal website order report
• payment gateway transaction report
• settlement report
• bank statement
• optional supporting files such as fee or mapping data

2. Map the required fields

For each primary report, users map the relevant columns such as:

• order date or transaction date
• amount
• order ID
• transaction ID
• payment reference
• settlement ID
• bank UTR

If a file does not match the configured format, Cointab can reject it with a clear error so the team knows what needs to be corrected.

3. Add supporting data when needed

Supporting data is optional, but useful when order reconciliation requires enrichment or lookup logic.

Examples include:

• product master data
• order metadata
• fee rate files
• refund files
• tax mapping data
• delivery or status reference files

Supporting data is not reconciled directly. It helps prepare the primary records before matching.

4. Create derived columns if needed

Finance users can create derived columns for cleaning or combining data before reconciliation.

Examples include:

• clean order ID
• net amount
• delivered payment amount
• amount after fee
• refund amount as negative
• normalized reference number

Cointab can also help generate Excel-style formulas from natural-language prompts.

5. Run reconciliation

Users can run the reconciliation manually or schedule it to run automatically. The engine performs structured matching across the uploaded records and then analyzes any remaining open items.

What the reconciliation report shows

Once the run is complete, finance teams can review the report dashboard and drill into individual transactions.

Fully matched

These are records where the website order, payment gateway record, and settlement logic align as expected.

Partially matched

These are records where the reference matches but the amount does not. Partial matches are useful because they often point to underpayments, deductions, rounding differences, or settlement adjustments.

Unmatched

These are records present on one side but not found on the other side. For example, an order may exist in the website report but not in the payment gateway report, or a gateway transaction may appear without a corresponding internal order.

Skipped

These are rows that were not included in reconciliation because they were excluded by a rule, incomplete, invalid, or otherwise unusable.

Cointab keeps skipped items visible so finance users understand what was ignored and why.

Common exception types in website order reconciliation

A good payment reconciliation process does more than match order IDs. It helps teams understand why exceptions occurred.

Common exception buckets include:

• order recorded in the website report but missing in the gateway report
• gateway transaction present but missing in internal order data
• amount difference between order value and received value
• fees charged differently from expected values
• tax or deduction differences
• settlement amount mismatch
• settlement present in gateway data but missing in the bank statement
• bank credit present but not linked to a gateway settlement
• cancelled orders that require separate treatment

These exception buckets help finance teams focus on open items rather than reviewing every transaction manually.

Payment gateway fee, tax, and settlement review

Website order reconciliation often involves more than payment matching.

Teams may also need to review:

• gateway fees charged per transaction
• taxes charged on those fees where applicable
• settlement values after fees and deductions
• bank receipt against expected settlement amount

This makes it easier to identify whether the amount collected from the customer, the amount retained as charges, and the amount deposited into the bank all line up correctly.

Manual match for unresolved items

Some transactions need human review.

Cointab includes manual match options for records that the system or AI cannot confidently match. This is useful when:

• partner data is incomplete
• identifiers are missing
• a one-off exception needs context
• the business wants to confirm a match before closing the item

Manual matches are clearly marked so the audit trail remains visible.

Reuse the same reconciliation every period

Website order and payment gateway reconciliation is usually a recurring process.

Cointab is designed so finance teams do not need to recreate the workflow every month. Once the reconciliation is configured, users can reuse it for future periods by selecting the workflow, uploading the latest files, and running the report again.

That helps teams standardize review steps across month-end close, daily settlement checks, and periodic audit work.

Automation for recurring payment reconciliation

For teams that reconcile the same reports repeatedly, Cointab can support automated data flow through email, SFTP, or API integrations.

That means:

• payment gateway reports can be received automatically
• bank or settlement data can be pulled on a schedule
• reconciliation can run after files are received
• output can be delivered back to internal systems

This is especially useful for daily or high-volume order-to-payment reconciliation workflows.

Why finance teams use Cointab for this use case

Cointab helps finance teams replace manual spreadsheet checks with a structured, auditable workflow.

Key benefits include:

• faster matching of website orders and payment gateway records
• clearer visibility into matched, partial, unmatched, and skipped transactions
• reusable reconciliation logic for recurring periods
• support for supporting data and derived columns
• audit-ready Excel report downloads
• team workspace visibility with roles and history
• easier review of fees, deductions, and settlement differences

FAQs

What files are needed for website order payment reconciliation?

The most common files are the internal website order report, the payment gateway transaction report, and the bank statement or settlement report. Supporting files can be added when enrichment or lookup is needed.

Can Cointab handle partial matches and amount differences?

Yes. Cointab supports partial matches where the identifier matches but the amount differs, which is useful for underpayments, deductions, fees, or settlement adjustments.

Can missed files be added later?

Yes. If a required file arrives late, users can upload it under the same reconciliation and refresh the report.

Can this reconciliation be automated for recurring runs?

Yes. Once configured, the workflow can be reused and automated with scheduled data intake and recurring reconciliation runs.

Are skipped records visible in the report?

Yes. Skipped records remain visible so finance teams can see what was excluded and why.