There is a need for a scalable, controlled, and operationally viable process to pay high volumes of contractors through Dynamics 365 while ensuring that project actuals, subledger entries, and GL postings are created accurately and without duplication. As it stands time is entered through project operations in CE, and the approved time is posted. This creates actuals, which then flow into Finance & Operations. Finance & Operations subsequently generates integration journals containing the required GL and subledger entries, which are then posted to the general ledger. The challenge is that contractor payment require processing through the AP Vendor Invoice module, which also create actuals by default. If contractor time is already creating actuals through the time card process, and the vendor invoice process creates another set of actuals, there is a risk of duplicate project costs, duplicated actuals, and incorrect GL impact. While this could be handled through cost accurals that reverse on invoice posting, this isn't sustainable for high volume The core issue is therefore how to design a contractor payment process that allows:
Time to be captured, approved, and posted correctly.
Project actuals to be created once only.
Contractor invoices to be processed and paid through AP.
Finance postings to flow correctly into the subledger and general ledger.
Duplicate actuals and duplicate cost recognition to be avoided.
Manual intervention, matching, and reconciliation effort to be minimised.
This is particularly important at high transaction volumes, where manual matching or exception handling across thousands of vendors, multiple entities, multiple currencies, and large monthly line volumes would be operationally difficult to sustain.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Share
Report
All responses (
Answers (
461
