{"id":28525,"date":"2026-06-04T00:15:48","date_gmt":"2026-06-04T00:15:48","guid":{"rendered":"https:\/\/synder.com\/help\/per-transaction-how-to-use-transaction-reconciliation-with-xero\/"},"modified":"2026-10-07T15:17:35","modified_gmt":"2026-10-07T15:17:35","slug":"per-transaction-how-to-use-transaction-reconciliation-with-xero","status":"publish","type":"post","link":"https:\/\/synder.com\/help\/per-transaction-how-to-use-transaction-reconciliation-with-xero\/","title":{"rendered":"How to Reconcile Xero with Synder \u2014 Transaction Reconciliation Guide (Per-Transaction)"},"content":{"rendered":"\n
This guide shows you how to reconcile Xero with Synder<\/strong> using Synder’s Transaction Reconciliation<\/strong> feature in Manual mode. You’ll export an Account Transactions<\/em> report from Xero, upload it into Synder, and match it against your payment platform data so every payment, fee, and refund posted by Synder lines up with what’s in your Xero clearing account.<\/p>\n\n\n\n\n For the full explanation of how Transaction Reconciliation works \u2014 what each result bucket means, and which integrations support Automated or Assisted modes \u2014 see Transaction Reconciliation for Per Transaction Sync<\/a>. To get Xero connected to Synder in the first place, see How to Connect QuickBooks Online and Xero to Synder<\/a>.<\/p>\n\n\n\n Try Assisted mode first.<\/strong> If your integration supports it, Assisted mode<\/strong> is the recommended path for Xero Per-Transaction users. You export a single Account Transactions<\/em> report, upload it, and Synder normalizes and maps everything automatically \u2014 no manual column mapping<\/strong>, so there is no risk of a mismapped ID sending every row to Missing source. Assisted mode also recovers original source-currency amounts, which Manual mode cannot do for multi-currency or FX transactions. See Assisted Transaction Reconciliation for Xero<\/a>. Use the guide below if Assisted is not available for your integration, or if you prefer to map the columns yourself.<\/p>\n\n\n\n Use this guide when your payment integration is in Manual reconciliation mode (for example Square, WooCommerce, or another platform without a built-in Synder reconciliation connector) and your accounting platform is Xero<\/strong>. You’ll export an Account Transactions<\/em> report from Xero, clean it up, and upload it into Synder alongside your payment-platform file.<\/p>\n\n\n\n Xero adds a few header rows to the top of the export (report title, account name, date range). Synder expects column headers on row 1, so open the file and:<\/p>\n\n\n\n Sample file:<\/strong> Download an example Xero Account Transactions export<\/a> to see the raw layout (4 metadata rows on top, headers on row 5) and what it should look like after cleanup.<\/p>\n\n\n\n Once Synder finishes comparing the two files, your results are organized into four tabs.<\/p>\n\n\n\n These transactions appear in both sources with matching IDs and amounts. They are fully reconciled \u2014 no action needed<\/strong>. Expand any matched row to see the individual Accounting rows<\/strong> and Integration rows<\/strong> that make up the match, along with their Primary ID, Secondary ID, Transaction type, and Amount. The Match type<\/strong> column shows whether Synder matched the row automatically (Auto<\/strong>) or you paired it yourself (Manual<\/strong>).<\/p>\n\n\n\n These transactions matched by ID, but the amounts differ<\/strong>. Review them to understand the cause \u2014 common reasons include partial payments, currency differences, or fee adjustments.<\/p>\n\n\n\n In Manual mode, a discrepancy often points back to your column mapping rather than to a real accounting problem. Before investigating the transaction itself, check that you mapped Amount<\/strong> to the same basis on both sides \u2014 Gross<\/strong> against gross, or Net<\/strong> against net. Mixing the two produces discrepancies on every fee-bearing transaction.<\/p>\n\n\n\n Synder could not find these transactions in the opposite source. The tab splits into two sections:<\/p>\n\n\n\n Each section has its own search<\/strong>, date range<\/strong>, currency<\/strong>, and amount<\/strong> filters, and each keeps its own separate selection. If you know a transaction in one source corresponds to an entry in the other, you can pair them yourself and keep a full audit trail \u2014 see How to Use Manual Matching in Transaction Reconciliation<\/a>.<\/p>\n\n\n\n Transactions you manually marked as ignored. Use this tab for known or non-material discrepancies. To move items here, tick the rows you want on the Discrepancy<\/strong> or Missing source<\/strong> tab, then click Ignore<\/strong> in the selection bar that appears. The bar shows how many rows you selected and their combined total; click Clear all<\/strong> to start over. You can un-ignore transactions at any time and they return to their original category.<\/p>\n\n\n\n Understanding the matching logic matters more in Manual mode than anywhere else, because you<\/strong> chose which Xero columns feed Synder’s ID fields. Synder runs a three-pass comparison based on transaction IDs:<\/p>\n\n\n\n When Synder finds a match, it groups all related rows by that ID and compares the total amounts<\/strong>. If the totals match, the group goes to Matched<\/strong>. If the totals differ, it goes to Discrepancy<\/strong>. If no match is found after all three passes, the transaction goes to Missing source<\/strong>.<\/p>\n\n\n\n Important:<\/strong> transaction dates are not used for matching. Matching is based on IDs and amounts only. If you mapped Xero’s Reference<\/strong> column to Primary ID but your payment platform writes its ID somewhere else, every row will land in Missing source \u2014 remap and run again rather than working through the list.<\/p>\n\n\n\n Manual mode depends on two files you prepared yourself, so most failures happen while Synder is reading them. Click Process log<\/strong> to see how far each side got: Download source files<\/strong>, Normalize and map<\/strong>, then Match transactions<\/strong>.<\/p>\n\n\n\n If a step fails, the reconciliation stops there and the log explains why. The error names the file<\/strong>, the row<\/strong>, the column<\/strong>, the value<\/strong> it could not read and the reason<\/strong> \u2014 plus how many other rows have the same problem, so you know the size of the fix before you start. The most common cause in Xero exports is leaving the metadata rows at the top of the file; see Step 2.<\/p>\n\n\n\n Click Export<\/strong> on the results page to download your data. You can export each tab separately \u2014 Export matched<\/strong>, Export discrepancy<\/strong>, Export missing source<\/strong>, or Export ignored<\/strong> \u2014 or use Export all<\/strong> for a 4-tab Excel file with every category. You can also download the normalized and mapped source files from the Process log, which is the fastest way to see exactly how Synder read your Xero export.<\/p>\n\n\n\n Your reconciliation is complete when the Discrepancy<\/strong> and Missing source<\/strong> tabs both show zero transactions and the status changes to Reconciled<\/strong>. Ignored transactions count as resolved and no longer hold the reconciliation open.<\/p>\n\n\n\n For everything else \u2014 managing and cloning reconciliations, status filters, and sharing results with your team \u2014 see the main Transaction Reconciliation guide<\/a>.<\/p>\n\n\n\n Reconcile Xero with Synder in 4 steps: export the Xero Account Transactions report, clean up the first 4 rows, upload to Synder’s Transaction Reconciliation in Manual mode, and review matches. Includes sample XLSX and screenshots.<\/p>\n","protected":false},"author":2318,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":"","_ppma_block_editor_authors":""},"categories":[473,384,461,56],"tags":[17,23,469,470],"ppma_author":[351],"class_list":["post-28525","post","type-post","status-publish","format-standard","hentry","category-transaction-reconciliation-module","category-useful-reconciliation-features","category-xero-accounting-integration","category-reconciliation","tag-reconciliation","tag-xero","tag-transaction-reconciliation","tag-per-transaction"],"yoast_head":"\nWhen to use this guide<\/h2>\n\n\n\n
Step 1 \u2014 Export the Account Transactions report from Xero<\/h2>\n\n\n\n
Step 2 \u2014 Clean up the XLSX file<\/h2>\n\n\n\n
<\/figure>\n\n\n\nStep 3 \u2014 Upload the file into Synder<\/h2>\n\n\n\n
Primary ID \u2192 Reference (Xero stores the transaction reference, e.g. INV-0013, here). Secondary ID \u2192 Reference (use the same column if Synder asks for both IDs). Amount \u2192 Gross (or Net, depending on what you’re matching). Date \u2192 Date. Description \u2192 Description.<\/em><\/li>\n
<\/figure>\n\n\n\nStep 4 \u2014 Review your results<\/h2>\n\n\n\n
Matched<\/h3>\n\n\n\n
<\/figure>\n\n\n\nDiscrepancy<\/h3>\n\n\n\n
Missing source<\/h3>\n\n\n\n
\n
<\/figure>\n\n\n\nIgnored<\/h3>\n\n\n\n
How Synder matches your transactions<\/h2>\n\n\n\n
\n
If the reconciliation stops before you see results<\/h2>\n\n\n\n
Exporting your results<\/h2>\n\n\n\n
When your reconciliation is complete<\/h2>\n\n\n\n
Tips and tricks<\/h2>\n\n\n\n
Related guides<\/h2>\n\n\n\n