Before export
Preview the sales summary or invoice output and check mappings before Xero is changed.
Bookkeepers are often the first people to see the practical mess: gateway deposits that do not equal sales, refunds in the wrong period, thousands of retail invoices and BACS orders that look paid when they are not.
Preview the sales summary or invoice output and check mappings before Xero is changed.
Use separate payment clearing mappings so Stripe, PayPal and manual methods do not become one unexplained balance.
Read the sync history, correct the problem and retry without building a second copy of the same accounting record.
Trace refunds and source references without rebuilding the ecommerce sales calculation in a spreadsheet.
Why is the bank payout lower than sales? The gateway clearing account separates gross captured money from fees and later settlements.
Why is this order in Tuesday's sales? The export profile shows whether the store groups by paid date, created date or another configured basis.
Why is this BACS invoice still outstanding? Its payment mapping can deliberately leave it unpaid until the transfer arrives.
Was this refund exported already? Source and Xero references remain in the history so the answer does not depend on memory.
Access can be scoped so a bookkeeper reviews mappings, exports and clearing balances without needing to alter connector settings.
Daily summaries and mapped clearing accounts are designed to leave a shorter, more explainable list of items to check at month end rather than eliminating review entirely.
Yes. Each client remains a separate company with its own stores, mappings and Xero connection.
We will use that task as the demo scenario instead of walking through generic slides.