Adyen

Automatic reports: Adyen can send a REPORT_AVAILABLE webhook whenever a batch-close Settlement details report is generated. n8n downloads that CSV using a saved Report Service API credential and imports it as a DRY RUN automatically.

Only Settled and Refunded rows enter the Odoo matcher. Fees, MerchantPayout, balance transfers and other report journal types are retained as payout activity for audit/reporting instead of becoming fake missing transactions.

Queue is for new uploads and batches currently being processed. History contains completed DRY RUN and LIVE batches.

1. Upload the Adyen CSV and enter the reconciliation batch number.
2. Run as DRY RUN to validate PSP references, invoice matches and amounts.
3. Review anything marked Warning, Needs review or Failed.
4. Promote an approved DRY RUN to LIVE.
5. LIVE appends the PSP and batch label to the Odoo invoice Payment Reference.

Amazon

Queue shows settlement files still matching or writing LIVE references. History contains the complete settlement workbench.

1. Upload the tab-separated Amazon settlement TXT.
2. The portal analyses sales, refunds, Amazon fees and settlement-level adjustments.
3. The background matcher joins Amazon order-id to Odoo sale.order.amazon_order_ref.
4. Accounts enters the Settlement reference used for Odoo matching.
5. Promote to LIVE only after the Odoo comparison is acceptable.
6. LIVE re-matches Odoo and appends the Accounts-supplied reference to matched customer invoices.

eBay POC

The first eBay implementation is read-only while the payout format and Odoo matching are validated.

1. Upload the eBay payout CSV from Seller Hub Payments.
2. The portal groups payout activity by eBay Order Number and keeps transaction IDs/fees.
3. Primary Odoo match: eBay Transaction ID → sale.order.woo_trans_id.
4. Fallback/cross-check: eBay Order Number → sale.order.woo_order_number.
5. The linked invoice ref is also checked against the eBay Order Number.
6. Review Odoo order/invoice values against eBay gross activity. No Odoo fields are written in this POC.

DRY RUN vs LIVE

DRY RUN

Read-only evidence run. Performs validation and matching but makes no Odoo write.

LIVE

Approved run allowed to update Odoo. LIVE evidence cannot be deleted.

Promote

Creates a separate LIVE batch from a completed DRY RUN; the original is retained for audit lineage.

Delete dry run

Available only for eligible, completed, unpromoted DRY RUNS.

Status definitions

Queued

Waiting for an on-demand worker.

Processing

A background worker is currently handling the batch.

Completed

Finished without unresolved processing issues.

Completed with issues

Finished, but one or more rows need review.

Warning

Processed, but Accounts should verify the result.

Needs review

The portal deliberately did not make an automatic decision.

Failed

The row or action could not be completed.

Resolved in Odoo

Accounts has manually dealt with the issue; the original audit result remains unchanged.

Amazon fee definitions

Principal

The product sale value reported by Amazon.

Commission

Amazon's sale-specific marketplace commission.

FBA fee

Fulfilment-by-Amazon charge tied directly to a sale.

Shared / batch fee

A settlement-level fee such as advertising, storage or subscription. The current allocation spreads these proportionally across positive principal sales.

Adjustment

A settlement movement such as reserve or reimbursement that stays separate instead of being treated as a normal sale fee.

MFN

Merchant Fulfilled Network — the merchant fulfils the order.

FBA / AFN

Fulfilment by Amazon / Amazon Fulfilled Network.

Amazon match definitions

Matched

Exactly one Odoo sale order contains the Amazon order ID in amazon_order_ref.

Invoice exact

The current Odoo customer invoice net agrees with the Amazon order gross used for comparison.

Invoice variance

The Odoo invoice net and Amazon order gross differ and should be reviewed.

Missing

No matching Odoo sale order was returned.

Ambiguous

More than one Odoo sale order matched the same Amazon order ID; the portal refuses to guess.

Already current

The LIVE reference is already present on the invoice, so no duplicate write is made.

Roles

Viewer

Can inspect reconciliation results but cannot perform Accounts write actions.

Accounts

Can upload, review, resolve, promote and perform supported LIVE reconciliation actions.

Admin

Accounts permissions plus user whitelist and access management.

Shopify Payments

Shopify is API-first, but payout-first: the payout remains the reconciliation batch boundary.

1. The portal wakes the on-demand Shopify collector and fetches current payouts.
2. Every balance transaction assigned to a payout is fetched, including additional API pages.
3. Scheduled payouts can be cached, but Odoo reconciliation starts only when Shopify marks the payout PAID.
4. Order activity is grouped by Shopify Order and hydrated with Shopify paymentId.
5. Primary Odoo match: the numeric tail of Shopify Order GID → sale.order.shopify_order_number.
6. Cross-checks: Shopify order name → Odoo sale-order name/reference fields; Shopify paymentId → payment.transaction.provider_reference; linked invoice ref → Shopify order name.
7. Statement descriptor, external trace ID and the Accounts-entered Bank statement reference are retained separately.
8. LIVE promotion locks the bank statement reference and appends that exact value to matched Odoo invoice/credit-note payment_reference fields. Refund credit notes are only included when the payout actually contains refund activity for that order.

Reports

Platform fees

Charges identifiable from reconciliation/settlement data. For Adyen this is inferred as gross credits less debits and net credits.

Platform contribution

Gross sales less refunds/debits and identified platform fees. It deliberately excludes COGS.

Fee burden

Identified platform fees as a percentage of gross sales.

Blended sales / ad spend

Total platform sales divided by identifiable advertising spend. Useful directionally, but it is not campaign-attributed ROAS.

Gross margin

Not calculated yet because product COGS has not been joined into the reporting layer.

Background processing

The portal uses on-demand workers. You do not need to leave the browser open while a batch runs.

Queue pages show current work; History pages are the long-term audit and review workbench. History lists are paginated at 10 batches/payouts per page so the selected detail stays close to the top.

eBay and Shopify are intentionally visible in the navigation, but disabled until their reconciliation rules are agreed.