Service terms
A plain-language pre-launch structure for conversion rules, credits, output review, and service use.
Pre-launch document
This concept is not a final legal notice. Replace every operational placeholder, identify the correct legal entity, and obtain South African legal review before production use.
Concept updated: 21 July 2026
ReconReady converts supported PDF bank-statement pages into structured transaction rows for review and CSV export. It does not provide banking, bookkeeping, accounting, tax, audit, or legal advice and does not perform reconciliation unless that functionality is explicitly released later.
Output can contain errors. Users must compare the result with the source statement before relying on, importing, or reconciling it.
The final terms should define account eligibility, email verification, credential protection, authorised users, acceptable document ownership, prohibited content, misuse, automated access, service interference, and the handling of suspected fraud or abuse.
Users should confirm that they are authorised to upload and process the relevant statement data.
One credit is intended to equal one successfully processed PDF page. The final terms must define when page count is shown, when a credit is deducted, how failed or unreadable pages are handled, whether free credits expire, whether paid credits expire, and what happens when a balance is insufficient.
Displayed launch prices, VAT treatment, invoices, payment methods, refunds, and unused-credit treatment require final commercial confirmation.
Users remain responsible for reviewing dates, descriptions, debit and credit direction, amounts, balances, duplicates, omitted rows, and destination mappings. A generic CSV is not automatically a valid direct-import file for Sage, Pastel, Xero, QuickBooks, or another accounting product.
No bank, accounting-product partnership, certification, or endorsement is implied unless explicitly stated.
The final terms should link to the Privacy Notice, Security & Data page, and any business data-processing terms. It should state customer instructions, service access, support access, confidentiality, subprocessors, deletion, export, account closure, and the parties’ POPIA roles after legal review.
Define maintenance, updates, bank-layout changes, unsupported files, processing limits, support scope, incident communication, and the right to change or discontinue features. Avoid absolute uptime, speed, accuracy, or compatibility promises unless backed by a measured service commitment.
South African counsel should draft the warranties, exclusions, liability caps, indemnities, consumer-law treatment, and remedies. These clauses must reflect the actual contracting party, buyer types, pricing, insurance, and risk allocation rather than copied software boilerplate.
The final terms should address suspension, account closure, remaining credits, data retrieval and deletion, breach, notices, assignment, severability, governing law, jurisdiction or dispute process, and the complete agreement.
Insert the verified legal entity, physical and electronic notice addresses, and effective date before acceptance is collected.
