Introduction

RefinePoint is a workspace for reconciliation and month-end close. It takes data from your banks, ledgers, ERPs, vendors and files, matches records across them, explains the differences, and gives your team a governed place to resolve what is left: who is working on which break, by when, approved by whom.

The dashboard of a workspace, with the main navigation on the left.

Who it is for

• Finance and operations teams reconciling bank statements, vendor ledgers, payments, card settlements, tax returns such as GSTR-2B, or anything else that has to agree with something else.
• Controllers running the month-end close: certifying account balances, explaining movements, posting adjustments.
• Administrators and auditors who need to know that set-ups are controlled, access is limited, and every change is recorded.

The ideas you will meet everywhere

Idea	What it is
Workspace	Your organisation’s space in RefinePoint. Everything (data, reconciliations, rules, members) belongs to one workspace. You can belong to several and switch between them.
Data source	Where data comes from: an uploaded file, a connected system (Tally, Xero, QuickBooks, a database, a warehouse) or files arriving by SFTP or the API.
Reconciliation	A saved set-up (also called a process) that compares one to four sides, each read from a data source, and says what matches.
Fields	The common names each side’s columns are mapped onto (reference, date, amount, party…), so different files can be compared.
Matching pass	One way of pairing records across sides, tried in order: an exact reference first, then amount and date within a tolerance, and so on.
Run	One execution of a reconciliation on the latest data. Each run produces records: matched, partly matched, unmatched or duplicate.
Break	A record that needs attention: something did not match, or matched with a difference. Breaks are assigned, investigated and resolved.
Reason code	A label that explains a known kind of break, such as bank charges, and can clear it automatically.
Rule	A short English sentence that decides something: narration contains 'SMS' and amount is less than 500. Rules are used for filters, fields, reason codes, checks and workflow.
Version	Every change to a live reconciliation is prepared as a staging version and, where approval is on, approved before it goes live.

How the pieces fit

1. Bring data in. Upload files or connect a source. See Data sources.
2. Design a reconciliation. Start from a template, describe it to the AI, or build it step by step in the designer.
3. Run it. By hand, on a schedule, or whenever a new file arrives.
4. Review the results. See what matched and why the rest did not, in Results.
5. Work the breaks. Assign them, comment, match by hand and resolve them in Breaks.
6. Close and report. Certify accounts, post journals, and build the reports and dashboards your team needs.

New here?

The quick start takes you through a first reconciliation with sample files in about ten minutes. You can also try a plain two-file comparison, without signing up, at refinepoint.com/try.

What makes it different

Rules your team can read

Conditions are written as sentences, not code, and checked as you type. See Writing rules.

Changes are controlled

Live set-ups change only through approved versions. See Versions and approval.

Built for volume

Data is prepared and matched in an embedded analytical engine that handles files larger than memory.

Extensible

Your own functions and connectors can be added without waiting for a release. See Plugins.