How to Bridge Business and Finance: A Practical Guide to Business‑Finance Integration

1. Introduction to Business‑Finance Integration

Most enterprises face a monthly closing nightmare: hundreds of data reports are generated per department, per system, and each report must be manually verified and submitted to finance, causing a half‑month delay. The question "Can we generate vouchers automatically at month‑end?" reveals the deeper need for business‑finance integration, a topic that can be broken down into manageable pieces.

2. Three Key Insights

Business processes are highly variable, while finance follows strict accounting standards. Integration means linking the two at the data layer, turning business‑specific records into standardized financial entries.

2.1 Connector from Business to Finance

Think of business outputs as plugs of various shapes (round, flat, irregular) and finance as a standardized socket. The integration model acts as a converter that maps any business plug to the financial socket.

2.2 Five‑Point Model for Implementation

Companies need integration to support IPO disclosures.

Executives seek transparent data to attract investors.

Finance wants to reduce manual bookkeeping.

Business units desire faster data flow and reduced constraints.

R&D requires unified data definitions to avoid silos.

Implementation typically follows a reference path that starts with identifying data sources, designing conversion rules, and then deploying the accounting engine.

2.3 Choosing the Right Data Cut‑off

Data can be routed directly to a financial module, or a custom conversion layer (the accounting engine) can be built to translate business data into voucher data before pushing to systems like Kingdee or SAP.

3. From Business to Accounting Engine

Before integration, monthly closing required exporting over 200 reports, manually reconciling them, and then feeding the data to finance for voucher creation. The finance team later asked whether Kingdee’s voucher API could be used to automate this step.

3.1 What Is an Accounting Engine?

An accounting engine is a translation tool that converts business data into pre‑defined accounting vouchers using a set of mapping rules.

3.2 Business Processes and Data

Typical enterprise processes that generate accounting data include procurement, sales, expense reimbursement, and payroll. Each process produces detailed records (e.g., purchase orders, invoices, payment vouchers) that serve as the raw material for accounting entries.

Sales, procurement, expense, and payroll processes each map to specific voucher types, illustrating why a unified accounting engine is essential for automated conversion.

4. Accounting Engine Details

The engine must pre‑define conversion rules, then apply them to incoming business data to generate vouchers automatically.

4.1 Building the Engine

Key steps include analyzing the target voucher format (different ERP systems such as Kingdee, Yonyou, SAP, Oracle have distinct structures) and extracting the fields that cannot be derived directly from business data.

The engine’s core functions are:

Direct mapping of business fields to voucher fields when a one‑to‑one relationship exists.

Computation and transformation of business data when no direct mapping is possible.

4.2 Engine Rules

Each rule consists of condition statements (based on business data) and result statements (producing financial data). Example rule components include ledger selection, posting date, accounting period, debit/credit direction, summary generation, account code generation, and auxiliary accounting items.

Complex rules can combine multiple conditions with logical AND, producing a single result when all conditions are satisfied.

4.3 Rule Configuration UI

Although rule content varies by company, the configuration interface follows a common pattern: a rule‑type management page defines the applicable organization, condition factors, and result factors; a rule‑management page lets users create individual rules by selecting a rule type and adding multiple condition/result pairs.

5. Conclusion

Business‑finance integration is a vast subject that requires deep business analysis, precise rule design, and strong execution. The real difficulty lies not in technology but in mapping complex business processes to accounting logic and driving organizational change.