1. Transactions

The ‘Transactions’ functionality enables the process of bringing the accounting transactions onto the blockchain. It streamlines the process from a data source (ERP/accounting system) to blockchain publication, incorporating automated validation and multi-tiered approvals. This ensures data integrity, enhances auditability, and fosters trust through immutable, verifiable records. Transactions functionalities

1.1 Import

Reeve can integrate with the existing Enterprise Resource Planning (ERP) system and can import accounting transaction data, based on a set of parameters defined by the user. Parameters: Organization Accounting System Date Period (from - to) Transaction type Transactions number

1.2 Automated Validation and Conversion

Upon importing, Reeve automatically validates and converts the imported transactions based on a predefined set of rules. This ensures data consistency and compliance. Based on the validation and conversion rules, each transaction will be assigned a status: Ready to Approve: These transactions have passed all validation checks and are ready for review and approval. Pending: These transactions require further attention. They failed the conversion process and some information might be missing in the application. Reeve will indicate the reason for pending for the user to review and take action. Invalid: These transactions have failed the validation rules and cannot be processed as they are. Reeve will provide clear information on why they are invalid. The correction will need to be performed in the Accounting system and the transaction re-imported.

1.3 Review

Reeve is designed with a two-tier review process to enhance security and accuracy through multiple checks. The first review process allows users to meticulously review all transactions and approve them individually or in bulk. Once approved, the transactions are “Ready to publish”. In case the user detects any inaccuracy, the transaction can be rejected and a reason for rejection indicated. Based on the indicated reason the transaction will gain one of the failed status (Pending or Invalid).

1.4 Publish

Before publishing to the blockchain, a second and final review is required. This step can only be performed by users with higher level permissions, ensuring an additional layer of scrutiny and security. This user will verify the transaction details and give the final approval for publishing. In case the user detects any inaccuracy, the transaction can be rejected and a reason for rejection indicated. Based on the indicated reason the transaction will gain one of the failed status (Pending or Invalid). Once the approval is granted, the transactions are dispatched to be securely published to the Cardano Blockchain.

1.5 All Batches

Reeve provides a comprehensive overview of all imported transaction batches. This allows the user to monitor the status of each batch and the individual transactions within them at any given moment.

1.6 Reconciliation

The Reconciliation function in Reeve allows the user to verify the accuracy and consistency of data by comparing transactions in the ERP system with those published on the Cardano blockchain. This feature helps to identify discrepancies, ensuring data integrity.

To begin reconciliation, the user will need to specify the period for which wants to compare transactions. This involves selecting the start and end dates, and the system sourcing the data. Reeve automatically compares the transactions from your ERP for the specified period with the transactions published on the Cardano blockchain for the same period. The application then categorizes transactions as either ‘Reconciled’ or ‘Unreconciled’: Reconciled: These transactions match perfectly between your ERP and the blockchain, indicating data consistency. Unreconciled: These transactions show discrepancies between your ERP and the blockchain. Reeve provides detailed information on the nature of the discrepancy, including transaction details, the specific issue detected during the reconciliation and guidance on how to resolve the issue.