How to handle cross-period reimbursement vouchers? What if an August document is approved in September and the books are already closed?

First decide which accounting date to use:Submission date, approval completion date, finance confirmation date, actual payment date, choose one of four. An August order approved in September: if the approval completion date is used, the voucher is recorded in September, with no cross-period issue; if the submission date is used, you must face whether the August accounting period has already been closed.The key is not which one to choose, but that once chosen, it is unified across the entire company and never changed.

Four bookkeeping date bases

In practice Approval completion date is used most often, because it naturally avoids the closed-account issue and has the lowest implementation cost. Companies pursuing accurate expense periods will choose the submission date, but they must simultaneously resolve the closing conflict.

The actual payment date is generally not recommended—it postpones expense recognition to the payment stage, is inconsistent with the accrual basis, and all unpaid reimbursements at month-end will be omitted.

Two paths when August has already been closed

Path One: Deferred and recorded in September

The simplest approach, and also what most companies do. If August has already been closed, don't go back; record the voucher directly in September. The cost is that some of August's expenses are understated, which is acceptable if the amount is not large.

This path needs a constraint:Stipulates the reimbursement form submission deadline, for example, submitting last month's documents before the 5th of each month. Anything past the deadline is counted in the current month, which gives employees an incentive to reimburse on time.

Path Two: Accrual

When the amount is relatively large and has a material impact on period profit and loss, accrue expenses at month-end and reverse them when reimbursed the following month. This way, August expenses are complete, and the September voucher is merely a reversal of the accrual.

The cost is two additional manual steps for accrual and reversal, and the amount must be estimated.Use only when the amount is significant; do not use as a routine practice.——Otherwise, a pile of accruals must be done at the end of every month, and the workload will spiral out of control.

This must be locked down at the design stage

The handling rules for cross-period and closing are one of the two most error-prone areas in expense control projects (the other is departmental differences in debit accounts).

If it is not decided before go-live, what happens: in the first month-end after go-live, a batch of cross-month documents floods in, Finance finds that vouchers cannot be recorded, the business department finds that reimbursements are stuck, and both sides come to IT. If the rules are changed at that point, all generated vouchers must be redone.

So during the research stage, three things must be clearly asked:Which bookkeeping date to use, when the accounting period is usually closed, and whether adjustments need to be supported after closing. The answers to these three questions determine the design of the entire voucher generation module.

Two capabilities required at the system level

First, select the rule version by document date. When generating vouchers, rules effective at the time should be matched according to the period to which the document belongs, not the current time. Otherwise, when generating an August voucher in September, a new rule effective only in September might be used.

Second, advance the payment term status verification. Before generating vouchers, first check whether the target period has been closed. If it has been closed, intercept it directly at the draft stage and prompt, rather than pushing it to the general ledger, having it rejected, and then checking back.