How does Feishu approval integrate with expense control systems? Approval stays in Feishu, where does the business go

Kailing Technology · 2026-08-31

A reasonable division of labor is:Approval entry stays in Feishu, while voucher generation, expense allocation, and loan write-off stay in the expense control system。Employees do not need to change their usage habits, and finance's professional capabilities are not limited by the collaboration platform's framework. The two sides synchronize documents and approval status through APIs.

Why divide the work this way

Platforms like Feishu, DingTalk, and WeCom are best at Document Routing and Multi-level Approval: Who submits, how many levels of approval, whether large amounts require routing, and how pending tasks are reminded. They do this part very well, and employees use it every day, so no additional training is needed.

But the deep water area of expense control is not in approval.One expense must be allocated to three projects, borrowings must be reconciled with reimbursements, the same expense type must enter different accounts by department, and special invoices and general invoices must generate different vouchers— These are accounting logics, and the form engine of a collaboration platform struggles greatly to handle them; even if it can, it is very hard to maintain.

So there is no need to choose one over the other. Leave to each what each does best, and just connect the middle.

Data flow

Employees submit reimbursement requests in Feishu ↓ (Feishu approval routing, multi-level approval) Approval passed ↓ (callback / active pull, synchronized to expense control system) Expense control system receives the document ↓ Invoice verification and duplicate checking → expense allocation → loan write-off → voucher generation ↓ Push to general ledger + enter payment queue ↓ (status write-back) Feishu side shows payment completed

The key is in the final step's Status write-back。For forms submitted by employees in Feishu, whether payment was ultimately made and when must be visible in Feishu. Without this link, employees still have to ask finance, and the experience is broken.

Connection Method

The approval APIs of the Feishu Open Platform are public, mainly using three types of capabilities:Subscription approval event(receive callback upon approval),Read approval instance details(obtain form fields and attachments),Send message card(push the payment result back to the employee).

Two points should be noted during implementation. First,Form fields must be aligned with the fields of the expense control system., especially for fields such as expense type, department, and project that participate in voucher rule matching, the option values in Feishu forms must be mappable to the codes on the expense control side.

Second,Transfer of invoice attachments。Invoice images or OFD files uploaded by employees in Feishu must be synchronized to the expense control system for verification and duplicate checking, and cannot remain only in Feishu.

DingTalk is the same as WeCom

Platform	Approval capabilities	Connection Key Points
Feishu	Improved subscription and query APIs for approval instances	Field mapping + attachment sync + status write-back
DingTalk	OA approval open interfaces are mature	Same as above; note that field codes change when approval templates are modified
WeCom	Approval application APIs available	Same as above; attachments must be downloaded via the temporary media interface

The connection methods for the three are basically the same, with the main differences in attachment acquisition methods and the stability of field encoding.

Under what circumstances is this connection not recommended?

If the company's reimbursement volume is very small and the rules are simple (for example, no project allocation, no loans, and one-to-one voucher mapping is sufficient), then directly using Feishu approval plus manual bookkeeping is actually lower in cost. Adding another layer of integration carries maintenance costs.

The criteria can be:Has the time finance spends manually processing reimbursement vouchers each month already exceeded one or two days?. If not exceeded, manual work is more cost-effective; if exceeded, the benefits of integration only then hold.

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

Supports integration with Feishu, DingTalk, and WeCom approvals. Employees complete submission and approval on the original platform, and documents and attachments are automatically synchronized to the expense control system for verification, allocation, write-off, and voucher generation, with payment status written back to the collaboration platform. Form fields and expense control codes support mapping configuration, and the corresponding relationships can be adjusted online when approval templates change.

Learn about the Kailing Technology expense control and reimbursement system →

Common Questions

Why not just use Feishu to handle the entire expense control process?

Feishu excels at document flow and approval, but accounting logic such as expense allocation, loan reconciliation, and conditional voucher generation is difficult and hard to maintain with form engines.

Approvals stay in Feishu—how do employees know whether payment has been made?

It relies on status write-back. After the expense control system completes payment, it pushes the result back to Feishu; without this link, employees still have to ask finance.

How are invoices uploaded to Feishu processed?

It needs to be synchronized to the expense control system for verification and duplicate checking, and cannot remain only in Feishu. Attachment synchronization is an easily overlooked part during integration.

Under what circumstances is it unnecessary to do this integration?

When reimbursement volume is small and rules are simple, Feishu approval plus manual accounting is lower cost. This can be judged by the time finance spends processing vouchers each month.