Kailing TechnologyExpense Control and Reimbursement System › Automatically generate vouchers from reimbursement forms

Reimbursement forms automatically generate vouchers: how to connect business documents to accounting vouchers

Kailing Technology · 2026-08-31

It is not that buying a system automatically generates vouchers. Three prerequisites are indispensable:The chart of accounts is standardized to the final level, the correspondence between expense types and accounts has been confirmed line by line, and auxiliary accounting dimensions can be passed through from document fields. If these three things are not done, no system can generate vouchers that can be directly posted.

Why this matter is not as simple as it sounds

A reimbursement form is business language, recording who spent how much on what; a voucher is accounting language, expressing debit and credit accounts, amounts, and auxiliary accounting dimensions. A translation mechanism is needed between the two.

The difficulty of translation lies in One-to-many: For the same "travel expense", travel by the R&D department goes to R&D expenditure, travel by the sales department goes to selling expenses, and travel by other departments goes to administrative expenses; for the same document, a special invoice requires splitting out input tax, while a general invoice does not; for the same expenditure, employee advance payment is credited to other payables, while direct company payment is credited to bank deposits.

The eight steps of voucher generation

Reimbursement form approved ↓ ① Read document details, match debit accounts line by line ↓ ② Tax amount split: invoice type + expense type deductibility + tax rate ↓ ③ Merge entry lines with the same account + same dimensions (configurable switch) ↓ ④ Match credit accounts (by payment method; handle advance offset and overspending supplementary payment) ↓ ⑤ Fill auxiliary accounting dimensions (passed through from document fields) ↓ ⑥ Pre-validation: debit-credit balance / leaf-level accounts / required dimensions complete / non-zero amounts ↓ ⑦ Generate voucher draft (status: pending push) ↓ ⑧ Push to general ledger → record the returned voucher number, or record the failure reason

The verification in Step 6 must be front-loaded

The verification in this step Never rely on general ledger system error reporting. A validation failure should stop in draft status and give an error message that finance staff can understand, such as "Account 660201 requires a project to be filled in, but the document does not provide one," so that they can adjust the rules themselves and regenerate.

If it is rejected only after being pushed to the general ledger, what finance sees is a technical error code thrown by the general ledger system, and they neither know which document has the problem nor what to change.

What Exactly Are the Three Prerequisites

I. Chart of Accounts Standardized to the Last Level

Only leaf-level accounts are allowed for bookkeeping. The account master data needs to indicate is_leaf, as well as which auxiliary accounting dimensions each account must carry. This data usually needs to be exported from the general ledger system, and the enabled status must be confirmed item by item.

II. Confirm the relationship between expense types and accounts line by line

This is the most core output of the entire project, and also the place where pitfalls are most likely to be buried. Finance often verbally simplifies it to "travel expenses are administrative expenses," only remembering after go-live that the sales department should record them under selling expenses.

So this mapping table must be filled in line by line, confirmed line by line, and signed by the finance head. The structure of the table is roughly:

Expense TypeDepartment conditionsDebit Account CodeDebit Account NameWhether input tax can be deducted
Travel expenses - Transportation(leave blank = general)660201Management expenses — travel expensesDeductible
Travel expenses - TransportationSales department660101Selling expenses—travel expensesDeductible
Business entertainment660209Management expenses — business entertainment expensesNot deductible

Leaving department conditions blank means it applies to all departments; branches with department exceptions should fill them in, and the system prioritizes matching the more precise rule conditions.

III. Auxiliary Accounting Dimensions Can Be Passed Through

Voucher lines need to carry dimensions such as department, cost center, project, employee, and supplier. These do not need mapping, but it must be ensured that the reimbursement form has these fields and that the codes are consistent with the general ledger system.If the codes are inconsistent, an additional conversion mapping table is required., this point must be clarified during the research stage.

Verification method: compare historical documents one by one

After rule configuration is complete, the most effective verification method is to request 10 to 20 real reimbursement forms and their corresponding manual vouchers from finance, and simulate and compare them one by one. This exposes missed exception rules better than any formal requirements interview.

Samples should cover special situations as much as possible: advance write-off, merging of multiple details, non-deductible input VAT, cross-period, and voiding/red-letter reversal. These categories are precisely the ones most prone to problems.

How is this scenario handled in Kailing Technology's expense control system?

Built-in configurable rule engine completes three types of derivation: debit account, credit account, and tax amount splitting, with auxiliary accounting dimensions passed through directly from document fields. Before voucher generation, four validations are completed: debit-credit balance, leaf-level account, required dimensions, and non-zero amount; failures remain in draft status with readable error messages. A trial calculation tool is provided, supporting item-by-item comparison against historical documents to verify rule correctness.

Learn about the Kailing Technology expense control and reimbursement system →

Common Questions

Can vouchers be generated automatically after deploying the system?

No. Three conditions must first be met: the chart of accounts must be standardized to the lowest level, expense types must be confirmed line by line against account relationships, and auxiliary accounting dimensions must be able to pass through from documents.

What is the most common reason for voucher generation failure?

Missing required auxiliary accounting dimensions, followed by deactivated accounts and closed accounting periods. The former should be validated at the generation stage rather than waiting for the general ledger to reject it.

Should multiple line items be merged into one journal entry line?

Entries under the same account and same dimension can be merged for simpler reconciliation; if not merged, the details are clearer. It is recommended to make this a configurable switch decided by finance.

How do you verify whether the rules are configured correctly?

Take 10 to 20 real reimbursement forms and the corresponding manual vouchers and perform trial calculations and comparisons item by item, covering special situations such as advance write-off, non-deductible, cross-period, and red-letter reversal.