Unlocking Business‑Finance Integration: A Practical Guide to Accounting Engines

1. Introduction to Business‑Finance Integration

Business‑finance integration (业财一体化) merges a company's operational activities with its financial processes, turning fragmented, paper‑based workflows into seamless digital ones.

1.1 Business Activities

Businesses generate revenue through procurement, production, sales, marketing, and other processes, each involving distinct personnel, workflows, and data.

1.2 Financial Activities

Financial data records the monetary outcomes of every business activity; finance participates in budgeting, approval, and accounting for each operation.

1.3 Integration (Fusion)

Integration means connecting business and finance data, moving from offline documents to online systems such as ERP, e‑commerce, and digital vouchers.

2. Three Key Insights for Integration

Business processes are highly non‑standardized, while finance follows strict accounting standards. The integration acts as a connector that translates diverse business data into standardized financial entries.

2.1 Connector Between Business and Finance

Rules map business events to financial vouchers, answering questions like “which business data become which accounting entry?”

2.2 Five‑Point Model for Implementation

Why implement integration (e.g., IPO preparation, investor attraction, efficiency gains).

How to start – choose a data‑exchange point and align business data with financial requirements.

Select the appropriate integration touch‑point (order, payment, reimbursement, etc.).

Directly connect business systems to the finance module, converting data into accounting vouchers.

Build an accounting engine to handle the conversion logic.

3. From Business Data to Accounting Engine

The accounting engine acts as a translator, converting granular business data into pre‑defined accounting vouchers based on mapping rules.

3.1 What Is an Accounting Engine?

It applies a set of transformation rules to map business fields (e.g., product category) to accounting fields (e.g., expense account).

3.2 Typical Business Processes

Key processes that generate data for accounting include procurement/payment, sales/receipts, expense reimbursement, and payroll.

Procurement: purchase orders, invoices, receipt records become payable vouchers.

Sales: order, payment, delivery, and invoice data become revenue vouchers.

Expense reimbursement: travel requests, tickets, and receipts become expense vouchers.

4. Building the Accounting Engine

An accounting engine must pre‑define rules that specify how to extract values for voucher fields such as ledger, date, period, debit/credit direction, summary, account code, and auxiliary accounting.

4.1 Core Functions

Direct mapping: when a business field directly corresponds to a voucher field.

Calculated mapping: when the voucher value requires computation from multiple business fields.

Rule configuration typically includes a condition part (business data) and a result part (financial data), combined with logical operators (AND/OR).

4.2 Example Rule Syntax

Condition → Product Category = "Women’s Tops" Result → Expense Account = "Apparel/Women"

4.3 Rule Management UI

Rules are organized by “rule type” to limit selectable condition and result factors, simplifying configuration for large rule sets.

By defining rule types, conditions, and results, enterprises can tailor the accounting engine to their specific processes while maintaining consistency.