What AXIOTRA cannot do yet

Why this page exists

A reconciliation tool is only as useful as your understanding of what it did not look at. A clean findings list means no detector fired on the rows it received, not that nothing is wrong. This page collects, in one place, the things the current build does not do, so that you can decide which checks to keep doing by hand. Each item is true of the code as it runs today; when one ships, it comes off this list.

Data it does not bring in

No payouts file. The CSV importer accepts seven kinds: orders, payments, refunds, shipments, inventory, costs and fees. Payout rows arrive only through a Stripe connection whose restricted key can read payouts, so the payout comparison cannot run for Shopify Payments, Amazon or a CSV-only workspace.

No payments from a Shopify connection. The Shopify connection reads orders, refunds, fulfillments, inventory and unit costs. Captures come from a Stripe connection or from a payments CSV, such as the Shopify Payments transactions export. Until one of those is in, every Shopify order reads as an order with no captured payment.

No disputes or chargebacks. The Stripe connection reads charges, refunds and, when allowed, payouts. Dispute objects, dispute fees and their reversals are not read, and there is no CSV kind for them.

No currency conversion. Amounts are parsed into minor units and compared as numbers in the workspace's reporting currency. An order recorded in one currency and paid in another is compared without an exchange rate, and will read as an amount difference if the numbers differ.

No push from the platforms. Connections are polled on a schedule; there are no inbound webhooks. The Stripe connection re-reads charges and refunds created in the last 30 days on each run, so a later change to an older charge, such as a late capture, is not picked up.

Things the detectors do not check

Payment status. The payment detector matches payments to orders on the order reference and ignores the status on both sides: an authorized but uncaptured charge counts as payment, and a cancelled order with no payment is still raised. It compares each payment to the order total on its own, so it neither sums several partial captures nor flags two identical charges on one order as a double charge.

Refunds across systems. No detector matches a storefront refund to the processor refund for the same money, and a refund with no return received is not raised at all; the refund detector fires only on received but not restocked. Refunds from a Stripe or Amazon connection arrive with both return flags false.

Fulfillment on connected stores. The fulfillment detector looks for the literal status marked_shipped with no tracking. No connector produces that status, so the detector fires only from a shipments CSV.

Reversals and payout terms. The duplicate-fee detector cannot see a later credit, because the fees file has no reversal column. The payout detector compares Stripe captures minus fees with payouts and does not subtract refunds, disputes or reserves, so a large difference on its own is a prompt to reconcile, not an answer.

Automation, access and integration

Autopilot recommends and never acts. The workspace stores the autopilot mode and a kill switch, and marks some findings as eligible, but there is no executor: nothing is refunded, captured, restocked or edited in any connected system. Selecting the safe autopilot mode stores it as recommend.

One person per organization. Every account creates its own organization on first sign-in and becomes its owner. There is no invite screen, so two people cannot share a ledger today, even though roles exist in the schema.

Audit trail without a screen. Imports, connections, status changes, autopilot changes and billing events are written to the audit log, but no screen displays it yet.

No outbound webhooks and no API keys. The three read endpoints under /api/v1 require a signed-in browser session. The events endpoint reads a table that imports and connections do not write yet, so it returns an empty list for a real workspace; findings are available from the anomalies endpoint.

Short list screens. The Orders, Payments and Shipments screens show the first 40 rows, with no search or filter. For a full list, filter the file you imported, or read findings, which cover every row.

How to work around the gaps

Treat the findings list as the rows AXIOTRA can judge from evidence, and keep a short monthly checklist for the rest: uncaptured and expired authorizations, disputes, refunds without a return, and a full payout reconciliation that includes refunds and account-level charges. The problem pages linked from the library describe each of those checks field by field, including the parts that remain spreadsheet work today.