Transaction logs

Transaction logs are the line-by-line financial records of your Mirakl account. Every fee, commission, refund and payout the operator books against you shows up as one row. Invoices aggregate them — transaction logs are the source data those totals come from.

Where to find it

Open Mirakl Dashboard → Quick Start → Transaction Logs. The page title is Transaction Logs and it has two cards:

• Seller Payment Transactions (TL02) — the actual transactions.
• Export jobs — bulk-export jobs you started.

Seller Payment Transactions card

Columns: Connection, Type, Amount, Currency, Order, Transaction date, Created.

Sidebar filters: Connection, Transaction type.

Toolbar:

• Refresh — refreshes the list from the local database.
• Sync — opens the Sync transaction logs dialog, where you pick one of your connections and the plugin fetches new transactions from that operator.
• Export history — opens the Export transaction history dialog (see below).

Per-row action: Show details — opens a dialog with the operator’s full data for the transaction (raw fields).

Recognised transaction types include Order amount, Commission fee, Refund order amount, Refund commission fee, Shipping amount, Refund shipping amount, Payout, Manual credit and Manual invoice. Each operator may add more.

Export jobs card

Lists the bulk-export jobs you started, with their status (Pending, Running, Completed, Error). When a job is complete, the Download action appears on the row.

What gets stored

For each transaction the plugin keeps:

• the operator’s transaction ID,
• the Type (a free-text label the operator uses — the recognised codes are shown in the Transaction type filter),
• the transaction date,
• the amount and currency,
• the linked Mirakl order (empty for transactions that are not tied to a specific order, e.g. monthly fees),
• the full operator data, available through Show details.

Background sync

The plugin pulls new transactions from each connection on a schedule. The default interval is once every 24 hours. Mirakl publishes a soft limit of around 20 calls per day for this endpoint, so it is best not to go below 6 hours.

A second scheduled task runs every minute and checks on running bulk-export jobs you started — once they finish, Download becomes available on the Export jobs card.

Initial import

The first time you turn on order import for a connection, the plugin backfills every transaction within the initial-import window. For accounts with years of history, pick a recent date in the wizard’s initial-import step to avoid pulling millions of legacy rows.

Bulk export

When you need more history than the regular sync would cover (for example all commission fees from a particular quarter for a year-end review), use the Export history action:

1. Click Export history on the Transaction Logs page. The Export transaction history dialog opens.
2. Pick a Connection, a From date and a To date.
3. Optionally type a value into Transaction type filter (for example a specific type code) — leave it empty for all types.
4. Click Start export.

The job is added to the Export jobs card with status Pending. The plugin polls the operator in the background and the Download action appears on the row when the export is ready. The result is a single CSV the operator generated on its side.

Configuration

Open Mirakl → Settings → Sync tab, Invoicing & Transaction Logs Sync card:

• Enable Transaction Log Sync (TL02) — default off.
• Transaction Log Sync Interval — how often to pull new transactions. Presets 6 / 12 / 24 hours. Default 24 hours.
• Transaction Log Export Poll Interval — how often to check on bulk-export jobs. Presets 30 seconds / 1 minute / 5 minutes. Default 1 minute.

Tips & gotchas

Tip

Cross-check the transaction log with the invoice list. Transactions that are not yet linked to an invoice are fees the operator has booked but not billed yet — useful for cash-flow forecasting.

Caution

Mirakl rate-limits this endpoint to about 20 calls per day per connection. Do not lower the Transaction Log Sync Interval below 6 hours unless you really need to — the default of 24 hours already approaches the limit if you have many connections.

Note

The transaction table can be very large on busy accounts. The list is paginated on the server and the sidebar filters are pushed down to the database, so filtering big result sets is fast. Use the sidebar filter inputs rather than scrolling.

Tip

For one-shot historical reports (for example “all commission fees for Q3 2024”), use Export history rather than scrolling the regular list — you get a single CSV the operator generated on its side.

Related

• Invoices — the aggregated view of these transactions
• Order import
• Sync logs
• Background tasks