| Approval (four eyes) |
A second person must agree before something takes effect: a version going live, a break resolution, a journal. With four eyes, the person who proposed it cannot approve it. |
| Audit log |
The permanent record of who changed what, and when. See Audit log. |
| Break |
A record that needs a person: unmatched, matched with a difference, or duplicated. See Breaks. |
| Break cause |
Why a record broke, such as Amount differs or No counterpart. |
| Certification |
Signing off that an account’s balance is right and supported, by a preparer, reviewer and approver. See The close. |
| Check |
A proof that a reconciliation’s result can be trusted, such as balances agree. See Checks. |
| Condition |
A rule that is true or false. |
| Connection |
A signed-in account or saved credentials, reused by data sources. See Connections. |
| Connector |
A kind of system RefinePoint reads from directly. See Connectors. |
| Data source |
A table of records that reconciliations read. See Data sources. |
| Designer |
Where a reconciliation is set up, in ten steps. See The designer. |
| Difference / variance |
How far two amounts are apart. |
| Duplicate |
A record that appears more than once on the same side. |
| Field |
A common name (reference, date, amount) that every side’s columns are mapped onto. See Fields. |
| File routing |
Receiving files by upload, API, SFTP or watched folders and sending each to the right side. See File routing. |
| Flux |
Explaining how much an account’s balance moved since the last period. |
| Function |
A named calculation used in rules, written in square brackets: [round] amount to 2. See the function reference. |
| Journal |
An accounting entry raised to fix a break, approved and posted to your accounting system. See Journals. |
| Key |
The field (or fields) that must agree for two records to be paired, usually a reference. |
| Live version |
The version of a reconciliation that runs use. |
| Lookup table |
A table of reference data that rules look values up in. See Lookup tables. |
| Match rate |
The share of records that matched in a run. |
| Matched / partly matched / unmatched |
The result for a record: paired and agreeing; paired with a difference; no partner found. |
| Matching pass |
One way of pairing records across sides, tried in order. See Matching. |
| Open item |
A record left open by a run and followed into later runs, such as an uncleared cheque. See Open items. |
| Period |
A month or quarter of the close. |
| Plugin |
A Java library that adds functions or connectors. See Plugins. |
| Process |
Another name for a reconciliation’s saved set-up. |
| Reason code |
A label that explains a known kind of break, and can clear it automatically. See Reason codes. |
| Reconciliation |
Checking that two or more records of the same money agree; in RefinePoint, the saved set-up that does it. See Reconciliations. |
| Resolved |
A break that has been dealt with: matched by hand, explained, or adjusted. |
| Role |
What a person may do. See Members, groups and roles. |
| Rule |
A short English sentence that decides something. See Writing rules. |
| Run |
One execution of a reconciliation on the latest data. |
| Side |
One of the datasets a reconciliation compares. See Sides. |
| Staging version |
A draft change to a reconciliation, prepared without touching the live version. See Versions and approval. |
| Template |
A ready-made reconciliation set-up to start from. See Templates. |
| Tolerance |
How far apart two amounts or dates may be and still match. |
| Workflow state |
Where a break stands: open, investigating, resolved… |
| Workspace |
Your organisation’s space in RefinePoint. See Workspaces. |
