These rules are applied immediately after transactions are imported from the ERP system or data source. Their purpose is to identify any discrepancies or issues that would prevent a transaction from being accurately processed, recorded and published.

Mandatory field presence

• Rule: mandatory fields must not be empty.

Mandatory fields: transaction type, transaction date, transaction ID, document number, debit account, credit account, amount FCY, amount LCY, Currency and FX rate.

• Impact: Transactions missing mandatory information will be flagged as ‘Invalid’, prompting the user to verify and reimport transactions, including the missing data.
• Code 

Balance Integrity (Double-Entry principle)

• Rule: For each transaction, the total debits must equal the total credits.
• Impact: Transactions that do not balance will be flagged as ‘Invalid’, requiring investigation and correction.
• Code foreign currency 
• Code local currency 

Transaction Uniqueness Check

• Rule: When a transaction is imported, Reeve checks if a transaction with the same unique identifier (e.g., transaction ID) already exists within the application. It will be replaced if not published, if published the transaction within this batch will end up in ‘INVALID’.
• Purpose: To prevent duplicate entries, maintain data integrity, and ensure that only the most current, un-published version of a transaction is available for review and approval, while upholding the immutability of published records.
• Code