What account are R&D department travel expenses recorded under? And how do they differ from the sales department?
Travel expenses incurred by R&D personnel for R&D projects are included in R&D expenditure; those incurred by sales personnel for sales activities are included in selling expenses; all other cases are included in administrative expenses. The basis for judgment is which business activity the expense serves, not which department the person is attached to. Separately listing R&D expenditures also directly affects whether the R&D expense super deduction can be fully enjoyed.
Judgment boundaries for the three accounts
| Scenario | Account | Basis for judgment |
|---|---|---|
| R&D personnel travel for an R&D project (research, testing, technical exchange) | R&D expenditure—expensed expenditure / capitalized expenditure | Serving a specific R&D project, can be collected under a project number |
| Salespeople visit customers, attend exhibitions, and conduct business negotiations | Selling expenses—travel expenses | Serving sales activities |
| Business trips by administrative, finance, HR, and other functional staff | Management expenses — travel expenses | Serving daily administrative management |
| R&D personnel attend the company annual meeting and administrative meetings | Management expenses — travel expenses | Although the person is an R&D staff member, the nature of the activity is not R&D |
The last line is the key:Department attribution does not equal expense attribution. Not all R&D department travel goes into R&D expenditure; it depends on what the trip is for.
Why R&D expenditure must be listed separately
The R&D expense super-deduction is a tangible tax incentive, and the prerequisite for enjoying it is that expenses can be Accurately aggregate by R&D project.. Travel expenses fall within the scope of costs that can be included in R&D expenses, but it must be possible to prove that they are related to specific R&D activities.
If, for convenience, all travel expenses of R&D personnel are included in administrative expenses, then at the time of annual corporate income tax settlement, if you want to enjoy the super deduction, you have to go back and flip through the accounts item by item, judge item by item, and adjust item by item. Once there are many documents, the workload becomes so large that it simply cannot be completed, and the result is often giving up part of the benefit.
A more prudent approach is Attribute to the R&D project at the moment reimbursement occurs——Reimbursement forms carry project numbers, vouchers automatically enter R&D expenditure according to rules, and year-end aggregation tables are produced directly.
Three scenarios that are easy to misjudge
R&D personnel travel to meet customers. Although the person is from the R&D department, this activity is pre-sales support and serves sales in nature, so it should be recorded as a selling expense.
Salespeople attend product training. The nature of the activity is internal training, usually recorded under employee education funds or training fees within administrative expenses, not selling expenses.
R&D personnel travel to customer sites for implementation. This belongs to project delivery rather than R&D, and should be included in operating costs or main business costs, not R&D expenditure.
The common point of these three categories is:Inconsistency between personnel department and activity nature。Automatic judgment by department alone will misjudge everything, so reimbursement forms need fields that distinguish the nature of the activity in addition to department.
How to configure in the system to automatically distinguish
A single condition (department) cannot solve it; multi-condition matching is required. Taking travel expenses as an example, the rules are roughly as follows:
The more conditions a rule has at matching time, the more precise and higher priority it is. If R&D department staff travel without filling in the R&D project number, it will not fall into Rule A and will go to Rule C and be included in administrative expenses—this is exactly the effect we want,Make whether a project number is filled in the distinguishing basis。
This must be aligned with tax treatment before go-live
Which expenses can be included in R&D expenses and the specific scope of additional deduction may vary in implementation across regions. This correspondence cannot be decided unilaterally by IT,It must be confirmed by finance and tax definitions and signed line by line。
This is also the place most likely to hide pitfalls in expense control projects: finance often verbally simplifies it to "travel expenses are just administrative expenses," and only when doing super deductions after go-live do they discover they cannot aggregate them. By then it is too late to change the rules, and all historical data must be redone.
How is this scenario handled in Kailing Technology's expense control system?
Supports matching accounts by combining multiple conditions such as expense type, department, and project type. The more precise the conditions, the higher the priority, with no need to manually fill in priority numbers. Reimbursement forms can carry R&D project numbers and use them as matching conditions. Expenses complete project collection at the time of reimbursement, and R&D expenditures can directly generate collection tables by project. Rule changes retain effective periods and hit snapshots, leaving historical vouchers unaffected.
Learn about the Kailing Technology expense control and reimbursement system →
Common Questions
No. It depends on which activity this business trip serves. R&D personnel traveling to meet clients is pre-sales support and should be recorded as sales expenses.
It falls within the scope that can be included in R&D expenses, but the premise is that it can be accurately collected by R&D project and supporting evidence is retained.
Include in administrative expenses under general rules. The benefit of this design is that the project number becomes the basis for judgment, forcing completion.
It must be confirmed and signed line by line by the financial officer in conjunction with tax definitions, and cannot be decided on behalf of the enterprise by IT or the implementation party.