Which marketplaces does Dira Reconcile support?

Reconcile works on payout reports from the marketplaces connected through Dira. Uber Eats is live today; DoorDash and Grubhub adapters are in development and targeted next.

Does it replace our ERP or accounting system?

No. Reconcile prepares the reconciliation and a journal export for the finance process you already run. Account mapping is set up during deployment.

How are payouts matched to orders?

Each payout line is compared with the canonical order Dira recorded when the order came in, including its items, totals, status changes and store actions. Lines that agree are matched; the rest become exceptions with the difference shown.

What evidence comes with an exception?

The order's event timeline, relevant store actions such as rejections or manual POS entry, the payout line itself and, for commission issues, the contract rate on file. Finance can use it to prepare a dispute through the marketplace's own process.

Can we check commissions against our contracts?

Yes. Contract rates are stored per store group, and charged commissions are checked against them order by order. Differences appear as exceptions with expected and reported amounts side by side.

Who can resolve exceptions or export journals?

Access follows roles managed in Dira Command. Each resolution and each export is written to audit history with the person and the time.

Dira Reconcile · Marketplace finance

A complete picture of every payout.

Dira Reconcile imports marketplace payout reports and matches every line to the order behind it. Finance sees commissions, refunds and adjustments per order, works exceptions with the evidence attached, and exports a journal ready for the close.

Book a demo Finance and reconciliation

diraReconcile/ Uber Eats payout · week 44

3 exceptions

GROSS SALES

$12,480.20

COMMISSIONS

−$3,108.42

ADJUSTMENTS

−$96.10

NET PAYOUT

$9,275.68

Orders matched to payout lines412 of 415

Close checklist: import done · matching done · review exceptions · export journal

Commission above contract rate

DR-47790

Expected: Commission $6.12
Reported: Commission $7.34

EVIDENCE

Contract rate on file for this store group
Payout line 118 · order subtotal $24.48
Canonical order timeline

Prepare disputeAccept variance

Illustrative interface · sample data

Payouts arrive as totals. Finance needs orders.

A marketplace deposit nets sales, fees, refunds and adjustments into one number. Pulling it apart by hand is slow, and it still leaves gaps.

Deposits don't explain themselves

One payout covers a week of orders across many stores. Tying it back to sales means rebuilding the period in a spreadsheet every cycle.

Fees drift from the contract

Commission rates differ by store group and agreement. Without an order-level check, a charge above the agreed rate passes unnoticed.

Disputes start without evidence

Challenging a refund or a missing order means reconstructing what happened from POS, store and marketplace records, often under a deadline.

Every line of the payout, accounted for.

Reconcile works from the same canonical order history as the rest of Dira, so each payout line has a recorded order to compare against.

Payout report import

Import marketplace payout reports by channel and period. Each line is parsed into sales, commissions, refunds, credits and corrections.

Channel, period and store kept with every line

Order-level matching

Payout lines are matched to the canonical orders behind them. Matched, variance and unmatched orders separate before anyone opens a spreadsheet.

Matched · variance · unmatched

Commission and contract rate checks

Charged commissions are compared with the rate on file for each store group. Overcharges surface as exceptions with the expected amount beside them.

Refund and adjustment tracking

Refunds, missing-item credits and corrections are tied to the order's event history, so finance can see whether a cancellation or store issue was ever recorded.

Exceptions with evidence

Every exception carries the order timeline, store actions and the payout line. Finance prepares a dispute, accepts the variance or holds it for the next cycle.

Journal export and channel performance

Close the period with a journal export for your existing finance process, and compare financial performance by channel across stores.

Account mapping set per deployment

diraReconcile/ Payout breakdown · week 44

PAYOUT LINEAMOUNT

Commissions

Checked order by order against the contract rate on file for each store group.

At contract rate: 414 orders
Above contract rate: 1 order
Variance: −$1.22

Illustrative interface · sample data

Close a payout week without rebuilding it.

Import the report, match it to orders, work the exceptions, export the journal. The sample runs one Uber Eats payout week from start to finish.

Import

The payout report lands as structured lines, not a PDF to retype.

Match

Most orders reconcile on their own. Only the differences need a person.

Review

Each exception opens with the evidence already gathered.

Export

A balanced journal goes to the finance process you already run.

diraReconcile/ Uber Eats · Payout close · week 44

PAYOUT REPORTS · UBER EATS

Week 43 · Oct 20–26398 linesClosed
Week 44 · Oct 27–Nov 2415 lines
Week 45 · Nov 3–9Not yet issuedAwaiting report

Import the week 44 report to start matching.

Illustrative interface · sample data

What goes in. What comes out.

Reconcile sits on the canonical order model and event history that every Dira product shares.

Data in

Marketplace payout reports, imported per channel and period
Canonical orders and event history from Dira Connect
Store actions from Dira Store, including rejections and manual POS entry
Contract commission rates by store group

Matching and review

Order-level matching of every payout line
Contract rate checks on charged commissions
Exception queue with evidence and resolution history
Role-based access and audit history from Dira Command

Data out

Journal export for your existing finance process
Dispute evidence per exception, for the marketplace's own dispute process
Financial performance by channel and store
Data held in PostgreSQL alongside the canonical order model

Uber Eats is live today; DoorDash and Grubhub adapters are in development. Report handling and account mapping are confirmed for each deployment.

Architecture and APIs

Questions buyers ask

Give finance the same view operations has.

We'll walk a sample payout week from import to journal, exceptions included.

Book a demo Talk to the team

A complete picture of every payout.

Payouts arrive as totals. Finance needs orders.

Deposits don't explain themselves

Fees drift from the contract

Disputes start without evidence

Every line of the payout, accounted for.

Payout report import

Order-level matching

Commission and contract rate checks

Refund and adjustment tracking

Exceptions with evidence

Journal export and channel performance

Close a payout week without rebuilding it.

Import

Match

Review

Export

What goes in. What comes out.

Data in

Matching and review

Data out

Questions buyers ask

Which marketplaces does Dira Reconcile support?

Does it replace our ERP or accounting system?

How are payouts matched to orders?

What evidence comes with an exception?

Can we check commissions against our contracts?

Who can resolve exceptions or export journals?

Works with the rest of Dira

Give finance the same view operations has.