YonSuite Finance-to-Business Reconciliation: Build a Daily Pre-Close
Move differences among sales, purchasing, inventory, expenses and the ledger into daily checks instead of concentrating every issue at month end.
Learning objective
Create source-document, business-date and owner-based reconciliation and close procedures.
Roles
Cost accountants, finance leads, production, engineering, purchasing, warehouse, IT, key users and consultants
Prerequisites
- Confirm organisations, periods, currencies, items, routings, resources and access ownership.
- Prepare approved masters plus representative normal, exception and reversal test data.
- Define business cut-off, interface boundaries, approvals and change control.
Completion checks
- Results trace from cost detail to business source and accountable role.
- Quantity, amount, period and status reconcile across business and finance views.
- Exceptions retain cause, approval, correction and repeatable closure evidence.
Common errors
- Masking business-source errors with ledger adjustments.
- Failing to freeze versions and periods, making recalculation irreproducible.
- Testing only the happy path without late, reversal and cross-period cases.
Thailand project note
Thai implementations should confirm Thai/English master data, THB and foreign currencies, Asia/Bangkok time, segregation of duties, approval evidence and local document retention. This tutorial covers ERP controls and reconciliation only; VAT, WHT, BOI, customs and statutory-accounting conclusions require current review by qualified Thai professionals.
Related modules
Steps
- 01
Define reconciliation links from sales to receivables, purchasing to payables, inventory to ledger and expenses to vouchers.
- 02
For each link define quantity, amount, currency, business date, posting date and status fields.
- 03
Daily, identify missing generation, failed generation, unapproved, cross-period and reversed-without-counterentry records.
- 04
Trace differences by source number and separate interface delay, master data, exchange rate, price and process errors.
- 05
Operate a close timetable; business teams confirm document completeness before finance closes.
- 06
Record amount, reason, owner, approval and expected resolution for open items; never hide them with manual totals.
- 07
After close, sample from ledger to business document and back, retaining reconciliation and approval evidence.
Implementation notes
- Pilot one representative loop before expanding scope.
- Every exception needs a source document, cause, owner and closure evidence.
- Menus, fields, licences and automation depend on the current release and approved blueprint.
References
- 标准成本、实际成本与项目成本核算体系 ↗用友 U9 cloud · Accessed: 2026-08-21 · Applicable version: 官方公开能力范围；具体菜单、许可和字段以客户当前版本与批准蓝图为准
- U9 cloud 成本管理数智化 ↗用友 U9 cloud · Accessed: 2026-08-21 · Applicable version: 用于核对成本体系、成本要素、取数公式及标准实际对比的公开说明
- YonSuite 客户成功服务 ↗用友 · Accessed: 2026-08-21 · Applicable version: 用于核对业财对账、历史凭证迁移和实施服务范围