Questions
Frequently asked questions
Practical answers about file formats, exceptions and data handling in this CSV reconciliation tool.
What CSV format does SettlePair need?
- Any comma, semicolon or tab separated export with a header row. The invoice file needs invoice number, customer, amount and issue date, with due date optional. The bank file needs transaction date, description or reference, and amount. Column names are auto-mapped and you can correct the mapping before reconciling.
Which bank statement exports work?
- Standard CSV downloads from online banking work, including exports that use quoted fields, a byte order mark, or a single signed amount column. Restrict the export to the statement period you are reconciling, and to deposits where your bank allows it, so outgoing payments do not compete with customer receipts.
How does SettlePair handle partial payments?
- A part payment is allocated against the invoice and the invoice keeps its remaining balance. It is labelled Partially paid, never settled. Allocations are stored in integer cents and cannot exceed the invoice's remaining balance or the payment's unapplied balance.
Can one deposit be split across several invoices?
- Yes. In the allocation sheet you can apply one bank payment to several invoices, apply several payments to one invoice, or leave part of a deposit unapplied. Automatic matching stays one-to-one; grouped allocations are always created by you, so the audit trail reflects a human decision.
What does the confidence score mean?
- It is a deterministic 0-100 total of named signals: invoice number in the bank description, amount agreement, customer name overlap, and a plausible payment date, less a penalty when other transactions could match equally well. Scores of 80 and above open as approved, 45 to 79 enter the review queue, and lower scores are not suggested. The evidence panel shows which signals fired.
Is this AI, and does it learn from my data?
- No. Matching is rule-based with fixed weights, so the same two files always produce the same scores. There is no model, no training, and no external service involved.
Where is my data stored?
- Nowhere. Files are parsed in your browser tab and held in memory for the session only. There is no upload, no database, no account, and no localStorage of financial data. Refreshing the page clears everything.
Does SettlePair connect to my bank or accounting software?
- No. It reads CSV exports you download yourself and produces a CSV you post to your books. It holds no credentials and makes no connection to a bank or ledger.
Is the output accounting-accurate?
- SettlePair is a review aid, not an accounting system, and makes no claim of accounting accuracy. Confirm every match before updating your books; the export exists so a person can check and record the decisions.
What does the export contain?
- One CSV named settlepair-reconciliation.csv with a row per record: record type, invoice number, customer, invoice amount, payment date, bank description, payment amount, allocated amount, remaining invoice balance, unapplied payment balance, confidence, decision, evidence summary, and whether the match was automatic or manual.
Which browsers are supported?
- Current versions of Chrome, Edge, Firefox and Safari on desktop, and the same engines on mobile. JavaScript must be enabled because all processing is client-side. Very large files are limited by your device's available memory.
How much does it cost?
- SettlePair is free to use in the browser during the beta. There is no sign-up, no payment step and no usage limit imposed by the app.
Still unsure how a case should be handled? The reconciliation guide works through the common exceptions.