These rules define how imported transaction data from your ERP system is transformed and standardized by Reeve to ensure consistency, and readiness for blockchain publication and subsequent reporting. This automated process ensures that even if your ERP has unique configurations, the data is properly prepared for Reeve’s internal structure and is compatible with applicable regulations (e.g.GDPR)

Transaction Type Mapping

• Rule: ERP-specific transaction types are mapped and converted to Reeve’s internal standard transaction type categories. Refer to the Annex I, Transactions Type table.
• Purpose: To standardize financial event categorization for consistent reporting and analysis.
• Code 
• Unkown Project Type Code 

Cost Center and Project Code Mapping

• Rule: Detailed cost center codes and project codes imported from the ERP are automatically mapped to their corresponding ‘parent’ or higher-level codes within Reeve. This aggregation happens during the import and conversion process.
• Purpose: Transactions will reflect the aggregated ‘parent’ codes for cost centers and projects within Reeve, ensuring consistent high-level analysis and reporting across all imported data, regardless of the granular coding used in the source ERP. This mapping is fundamental for providing the appropriate level of granularity for analysis and for efficiency.
• Cost Center conversion 
• Project Conversion 

Account Code Combination to Event Code Mapping

• Rule: Specific combinations of debit and credit account codes are mapped to predefined ‘Event Codes’ within Reeve. These Event Codes categorize the underlying business activity or financial event that the transaction represents (e.g., ‘Expense Payment’, ‘Revenue Recognition’, ‘Asset Purchase’).
• Purpose: Each imported transaction will be assigned a standardized ‘Event Code’ based on its debit and credit accounts. This simplifies analysis and high-level understanding of the transaction’s purpose, rather than relying solely on granular account codes and movements.
• Code 

VAT Code to Rate Mapping

• Rule: The VAT (Value Added Tax) code included in the imported transaction is mapped to its corresponding numerical VAT rate (percentage) as defined and configured within Reeve’s internal setup.
• Purpose: The transaction will carry the standardized VAT rate, allowing for accurate calculation of tax liabilities and consistent reporting of tax-related financial data within Reeve and on the blockchain.
• Code 

Undefined Code Handling

• Rule: If any cost center, project, or account code present in an imported transaction is not yet defined or mapped in Reeve’s internal setup, the transaction’s validation will result in a ‘Pending’ status.
• Purpose: The transaction will be flagged with a specific reason indicating the undefined code. This allows the user to update Reeve’s internal mapping or setup without needing to re-import the entire transaction batch. Once the setup is corrected and updated, the transaction can be reprocessed directly within Reeve to achieve a ‘Ready to Approve’ status.