ReconciliationManagerProcess

This component runs the Reconciliation Manager (RCM) function and is used to match and reconcile transactions in the SunSystems ledgers.

It is set up as a Process component. Unlike the ReconciliationManager component, it allows reconciliation between two account codes.

Note: SSC is limited to using the AutoReconcile action. For greater control, the Reconciliation Manager function, accessible via Navigator Manager, should be used.

Reconciliation Manager allows you to reconcile transactions on different accounts. For example, to reconcile transactions that appear on two corresponding inter-company accounts.

Because of its flexibility Reconciliation Manager has a number of uses including:

  • bank reconciliation
  • inter-company reconciliation
  • debtor/creditor payment matching.

Reconciliation Manager matches and then reconciles two sets of transactions according to a set of predefined match criteria. The two sets of transactions are defined as separate reconciliation accounts. The selection and matching criteria are defined in a reconciliation profile.

Reconciliation Manager can reconcile the transactions automatically using the match criteria and also allows you to manually reconcile the transactions. This is particularly useful if you are reconciling a large number of transactions because you can automatically reconcile all of the obvious matches.

For example, if you use Reconciliation Manager to perform a bank reconciliation, you can automatically reconcile the bank account postings to the bank statement details by matching on the amount and reference number.

Before running a reconciliation:

  • the transaction selection criteria and matching criteria for the reconciliation must have been defined in a reconciliation profile, using the SunSystems Reconciliation Profiles (RCP) function, or the ReconciliationProfiles component.

  • the source of each set of transactions must have been identified using Reconciliation Accounts (RCA), or the ReconciliationAccountsSetup component.

  • the transactions you wish to reconcile must have been imported or loaded into SunSystems before you run the reconciliation. For example, if you are running a bank reconciliation, the bank statement details must have been posted as budget transactions to the ledger.

Methods

Process
Driver Type: SASI
You can use this method to run the reconciliation process, using the reconciliation profile to match and reconcile the transactions.
Either or both account codes to be reconciled may be defined beforehand via the ReconciliationAccountsSetup component, or they can be specified at runtime. An account can be reconciled with itself to allow the reconciliation of debits and credits. To do this, specify the same value in payload elements <AccountCode1> and <AccountCode2> or set the same Account Code on both Reconciliation Accounts records.
Some values can be preset, depending on how the Reconciliation Profile and Reconciliation Accounts have been set up. If this occurs, the preset fields are populated automatically at runtime, and are set to read only; SSC cannot override these settings and any values provided by the user will be ignored.
Note: Whereas SunSystems prompts you for the reporting option (whether to Print, Store or View), SSC only allows Print or Store to be used. The SSC default is Store.

Mandatory fields

When running the component, the following must be supplied:

  • Business Unit (payload element <BusinessUnit>)
  • Reconciliation Profile Code (payload element <ProfileCode>)
  • Account Codes (payload elements <AccountCode1>, <AccountCode2>) must either be provided via SSC or pre-defined on the Reconciliation Accounts records.
Note: At runtime the component validates the payload contents to ensure that the values supplied are correct. Various combinations of values may require other elements in the payload to be specified before the payload can be processed successfully.

Related data

None.