Get in touch

A short message with the following gets a far more useful answer:

• What you were doing — importing, mapping columns, reviewing suggestions, allocating a payment, or exporting.
• What you expected and what happened instead.
• Your browser and operating system, and whether you were on desktop or mobile.
• The shape of your CSV: the header row and a couple of made-up sample rows.

Please do not send real invoice or bank files. They are not needed to diagnose a problem, and SettlePair is built specifically so your financial data never reaches us. Replace names and amounts with fabricated values before sharing an example.

Because reconciliation files are parsed in your browser and never uploaded, there is no stored copy of your financial data for us to look up, correct or delete. If you have a question about the limited technical data involved in serving the website, or want to exercise a privacy right, write to support@settlepair.com with "Privacy request" in the subject line. The Privacy Notice explains what does and does not exist.

Use the subject line "Security report" and follow the guidance on the Security and Data Handling page. Report privately rather than publicly. SettlePair does not run a bug bounty and does not offer safe harbour for testing.

SettlePair is a small, early-stage product, so support is best-effort and there is no guaranteed response time or service-level commitment. We aim to read every message and reply to those that need one, and we prioritise security reports and reports of incorrect reconciliation behaviour. If you have not heard back and the issue is still live, it is fine to send a follow-up.

Many questions about CSV formats, bank exports, partial and grouped payments, scoring and storage are already answered in the FAQ and the workflow walkthrough.