Square US: identify the location behind a bank transfer
Updated · 3 min read
When several Square US locations use the same bank account, identify the location and transfer before matching a deposit. A bank amount alone cannot establish which location’s card payments it contains. Square’s Dashboard transfer history is the useful starting point; the POS app does not export this CSV.
The desktop apps export date, description, and amount as CSV. Open CSV in Excel to save an XLSX workbook. Statement support varies: verify the result against your own PDF.
Open location-specific transfer history
- In Square Dashboard → Banking, choose the location before reviewing the transfer list.
- Open View all transfers and select the relevant dates.
- Open the particular transfer. Inspect its included card payments, transfer mechanism and destination’s last three digits.
- If a working transaction list is needed, export CSV from Dashboard. Retain the chosen location and transfer context with the file before combining it with another location’s export.
Square’s US transfer-to-sales instructions describe this Dashboard investigation; the POS app does not export this CSV.
Square documents location tags for locations sharing a bank account. These tags are unavailable for instant and same-day transfers, so their absence does not prove a different location. Setting up a tag is an owner-authorized configuration change, not a prerequisite that an analyst should silently perform. Use existing detail and available transfer trace information when a tag is absent.
Separate cutoff from deposit date
Payments after the daily cutoff can belong to the following transfer. Check the actual location context, including the location used to sign into POS, before assuming a day’s displayed sales belong to the bank’s same-day credit. For restaurant modes without the Banking or Balance view, use Dashboard rather than inventing a missing POS menu.
The synthetic location exercise stipulates transfers of 90 and 140 from two different locations to one destination. A 140 bank credit is a candidate for the second location, but the destination and actual transfer references must also agree. A late 30 payment is assigned to the next transfer by the exercise’s explicit cutoff evidence, not by the bank date. The checks reject treating the two transfers as one pooled 230 deposit.
| Invented source assignment | Transfer identity | Destination | Amount | Meaning for observed bank credit |
|---|---|---|---|---|
| Location L1 | T1 | D | 90 | Different transfer |
| Location L2 | T2 | D | 140 | Matches stipulated T2 bank identity and destination |
| Late payment | T3 by explicit cutoff evidence | Not stipulated | 30 | Outside T1 and T2; do not infer destination |
The observed bank record is T2, amount 140, destination D. Sharing D does not turn T1 and T2 into one deposit, and the case does not supply a bank receipt for T3. These are invented identities in one unspecified currency, not promised Square CSV columns.
Close the evidence gap, not just the amount gap
Retain location, transfer identity, destination, included payments, dates and available trace alongside the bank observation. Missing trace or uncertain location stays unresolved. Do not alter an account link or create another transfer to repair a reporting mismatch. The example is an identity and arithmetic check, not a Square export or payment execution.
For a PDF-only bank source, download LocalExtract. It processes one PDF locally to date,description,amount CSV; it does not access platform accounts or synchronize accounting records.
Official sources and scope
Documentation checked October 16, 2026. Official reference 1 — square
LocalExtract Team
We build LocalExtract, a desktop bank statement converter. Questions or corrections? Contact · Editorial policy