Key points
- At its core are accounting rules that map business events to accounts, amounts and analysis dimensions; the rules are configurable and versioned.
- Accounting is triggered when a business event is confirmed, not by finance staff ticking off documents for a batch transfer at month end.
- Business and finance need variance reconciliation and two-way enquiry: from a business document to its entry, and from an entry back to the business.
In practice
For trading companies, the difficulty lies in the complexity of the business itself. A single lot may go through provisional pricing, final price adjustment, several pricing events, cost allocation, FX revaluation and transfer of non-refundable VAT to cost, each of which affects cost and profit. If finance only catches up with entries from business reports at month end, amounts and period attribution easily go wrong, and the source of differences cannot be explained.
Finance-business integration requires the operational system to emit a clear accounting event at each key step – goods receipt, goods issue, invoice confirmation, receipt and payment, expense recognition, pricing settlement – so that a rules engine generates the entry immediately and pushes it to the general ledger. When a push fails or an account mapping is missing, the item goes to a manual queue instead of being silently dropped. At month-end close, unposted business and business-finance differences are checked to ensure the books match reality before the period is locked.
How Tranexio supports it
Tranexio generates accounting events and journal entries when business is confirmed, mapping accounts by trade model; there is no month-end tick-and-transfer option. It provides inventory costing, period locking at month-end close, business-finance variance reconciliation and drill-back from entries. Entries are pushed to the external general ledger via the integration hub, with connectors available for mainstream finance systems such as Yonyou. See Finance-business integration.