Accounting in D365, Part 5: Contract to Close (Fixed-Price Projects : Kick-Off to Go-Live)

A fixed-price ERP implementation followed from contract to close in Dynamics 365 Finance & Operations: the business events, the documents in D365 and the vouchers they post.

Introduction

Not every business event becomes an entry in an ERP system, and not every ERP entry becomes a voucher in the general ledger.

Consider an ERP implementation project. A customer signs a contract, the project team runs Fit/Gap workshops, the solution design is approved, and the team eventually deploys the solution into production. These are business events. Some are recorded in Dynamics 365 Finance & Operations as project records, milestones or stage changes. Others trigger transactions that post to the general ledger.

The accounting becomes more interesting when the project is sold at a fixed price. The customer pays an agreed amount in stages, while the implementation team incurs cost every week. The billing schedule, the project cost, the revenue recognised and the customer collections do not happen at the same time, and D365 keeps each of them in its own accounts until the project is closed.

In this fifth part of the Accounting in D365 series, we follow an ERP implementation project from contract signature to project closure. For each business event, we look at the document or data entry in D365 and the accounting entry it generates, with the voucher as posted. The objective, as in the earlier parts, is to understand not only which transactions to post, but why they are posted and how they affect the financial statements.

Understanding the business scenario

ABC Ltd. (customer INMF-000009, Noida, Uttar Pradesh) engages INMF to implement Dynamics 365 Finance & Operations. The project is agreed at a fixed fee of INR 2,50,00,000 excluding GST, and runs from 01-10-2026 to 31-03-2027, including hypercare.

This part is standalone. It does not carry forward the closing balances of Parts 1 to 4, so the trial balance and statements at the end show only the postings of this project.

Contractual payment terms

These milestones decide when INMF can bill the customer. They do not, by themselves, decide how much revenue belongs to a period. That distinction is central to fixed-price project accounting.

Understanding the project lifecycle

The project cost is driven by the implementation activities. The work breakdown structure has one task for each activity:

The project team includes a project director, program and project managers, architects, functional and technical consultants and infrastructure specialists. Their time is recorded against these tasks and their role categories. A shadow consultant who joins for training records time on a separate internal project, INMF-000027, so that training effort is kept out of the revenue recognition of the contract.

How project accounting works in D365 F&O

In D365, a project groups transactions that record costs, and then posts those costs to the general ledger. For a fixed-price project, invoices consist of on-account transactions billed according to a billing schedule, and revenue can be calculated and posted throughout the project using the completed percentage method, or at completion using the completed contract method (Project management and accounting overview).

The transaction types used in this cycle are:

• Hour: consultants' time, recorded through timesheets or hour journals.
• On account: the scheduled milestone billings of the fixed-price project.
• Revenue recognition (estimate): the monthly calculation of revenue earned. In recent versions, estimates are labelled revenue recognition (Fixed price revenue estimate projects).

Customer payments are recorded in the accounts receivable payment journal, outside the project.

What decides the accounting

The ledger result of a project transaction is decided by the combination of transaction type, project category and category group, project group, line property and ledger posting setup (How project groups, categories and line properties determine project posting). The settings that matter for this project are:

The ledger posting setup maps each posting type to a main account:

Business Event 1 — Project contract signed

ABC Ltd. signs the implementation agreement for 2,50,00,000.00 excluding GST.

In D365: project contract INMF-000003 is created with ABC Ltd. as the funding source (100%).

Does signing the contract generate a voucher? No. A project contract records the commercial terms and the funding source; it is not a general ledger transaction.

Accounting impact: none.

Business Event 2 — Project created and planned

INMF creates the project and prepares the work breakdown structure, the cost budget and the billing schedule.

In D365:

• Fixed-price project INMF-000026 in project group FP-IMPL, linked to contract INMF-000003, and internal project INMF-000027 in project group INT-TRAIN.
• Work breakdown structure with the 12 tasks listed in the project lifecycle above, published.
• Hour forecast for the model FP-BUDGET: the planned hours of each role at its cost price, 1,77,74,000.00 in total. The shadow consultant is not included.
• Five on-account transactions, one for each billing milestone, together equal to 2,50,00,000.00.
• Project stage changed from Created to “In process” at kick-off on 01-10-2026.

Does creating a project or entering a forecast generate a voucher? No. The forecast is a plan; it becomes important at each month end, when it is the denominator of the completion percentage.

Accounting impact: none.

Business Event 3 — Advance invoice raised

At kick-off, INMF becomes entitled to invoice 25% of the contract value.

In D365: a project invoice proposal is created for the advance on-account transaction of project INMF-000026 and posted on 11-10-2026 (Project > Manage > Project invoice proposals). IGST is calculated from tax information on the on-account line.

Accounting entry (voucher INMF-180000000, 11-10-2026)

The credit goes to WIP - invoiced on-account, a balance sheet account, because on-account invoicing is set to Balance. The invoice records what has been billed; it does not recognise revenue. Revenue is left to the month-end revenue recognition.

Business Event 4 — Advance received from the customer

ABC Ltd. pays the advance invoice on 25-10-2026, deducting TDS at 10% of the taxable amount.

In D365: customer payment journal (Accounts receivable > Payments > Customer payment journal), settled against the advance invoice, with the TDS group on the line calculating the amount withheld.

Accounting entry (voucher INMF-CU000052, 25-10-2026)

The receipt settles the receivable. It does not create another 62,50,000.00 of revenue: the invoice and the collection are two separate transactions with different purposes.

Business Event 5 — Project team records its time

As the implementation progresses, consultants record their weekly hours against the project, the WBS activity and their role category: Business Understanding Sessions and Fit/Gap Workshops in October, design and development from November, master data and UAT in January and February, go-live and hypercare in March.

In D365: timesheets are entered for each resource, approved and posted (Project management and accounting > Timesheets > All timesheets); hours can also be posted through a project hour journal. Each hour is valued at the cost price of its category of, for example 5,000.00 an hour for the Project Director and 750.00 an hour for a Functional Consultant. The shadow consultant's hours are posted to internal project INMF-000027 at 437.50 an hour.

Accounting entry (each posted hour transaction)

Fixed-price project INMF-000026: timesheet line of Jean Grey (Functional Consultant - Trade & Logistics, 750.00 an hour) for the week of 11-01-2027. Each day's 13 hours post their own pair of lines: Dr Cost - hour 9,750.00, Cr Payroll allocation 9,750.00 (voucher INMF-01549).

Internal project INMF-000027: timesheet line of the shadow consultant, 5 hours at 437.50 = 2,187.50, posted to Cost - hour (internal project) against Payroll allocation.

Payroll allocation is the offset to salaries, which are booked separately through payroll. Posting hours therefore moves employee costs into project cost; it does not create a new expense.

The project team posted 11,594 hours to the contract and the shadow consultant 720 hours to the internal project.

Business Event 6 — Fit/Gap Workshops completed and Activate milestone invoiced

The team completes the Business Understanding Sessions and the Fit/Gap Workshops, and the customer signs off. The requirements and the gaps identified in the workshops are documented, and INMF raises the Activate milestone invoice for 20% of the contract value on 31-10-2026.

In D365: project invoice proposal for the Activate on-account transaction, posted.

Accounting entry (voucher INMF-180000001, 31-10-2026)

Business Event 7 — Customer pays the Activate milestone

ABC Ltd. pays the Activate invoice on 31-10-2026, deducting TDS of 5,00,000.00.

In D365: customer payment journal, settled against the Activate invoice.

Accounting entry (voucher INMF-CU000053, 31-10-2026)

Month-end close, October — revenue recognition

This is the most important accounting step of the cycle. By 31-10-2026, INMF has invoiced 1,12,50,000.00 (45% of the fee) but has completed only a fifth of the work. If revenue followed the invoices, October would report almost half the contract as earned. Revenue must instead follow the work performed.

In D365: Project > Manage > Revenue recognition. A revenue recognition is created for period code PT with date 31-10-2026 and forecast model FP-BUDGET, calculated, reviewed and posted.

The cost template FP-POC measures completion on cost amount. Its cost to complete method takes the forecast and deducts the actual cost to date, which corresponds to the Total budget – actual method described by Microsoft: actual costs are compared with the selected forecast model (Project management and accounting overview).

• Cost to complete = Forecast cost − Actual cost to date (never below zero)
• Completion % = Actual cost to date ÷ (Actual cost to date + Cost to complete)
• Cumulative revenue = Contract value × Completion %
• Revenue for the month = Cumulative revenue − Revenue recognised in earlier months

Accounting entry (voucher INMF-170000000, 31-10-2026)

There is no cost line in the revenue recognition voucher. Hour cost posts straight to profit and loss, so October's cost of 37,23,000.00 already sits in Cost - hour, so October earns 52,36,581.52 against 37,23,000.00 of cost: a gross margin of 28.90%, the planned margin.

Contract position at 31-10-2026: WIP - sales value 52,36,581.52 (debit) against WIP - invoiced on-account 1,12,50,000.00 (credit) leaves a net credit of 60,13,418.48. Billing is ahead of the work, so the project carries a contract liability — an advance from the customer.

Business Event 8 — Fit-Gap Design sign-off and November close

The team turns the Fit/Gap results into detailed solution design, and the customer approves the Fit-Gap Design on 30-11-2026. INMF raises the third invoice for 20% of the contract value.

Accounting entry (voucher INMF-180000002, 30-11-2026)

At the November month end, cumulative cost is 70,17,500.00, completion is 39.48% and cumulative revenue is 98,70,456.85. November's revenue is the increase over October: 98,70,456.85 − 52,36,581.52 = 46,33,875.33.

Accounting entry (voucher INMF-170000001, 30-11-2026)

The monthly revenue cannot be calculated by multiplying the month's cost by the contract value; it is always the change in cumulative revenue. The contract liability rises to 63,79,543.15, because the third milestone was billed while the design was still in progress.

Business Event 9 — Fit-Gap Design payment and December close

ABC Ltd. pays the Fit-Gap Design invoice on 18-12-2026, net of TDS.

Accounting entry (voucher INMF-CU000056, 18-12-2026)

Development runs through December with no milestone due. At 31-12-2026, cumulative cost is 97,27,250.00, completion is 54.73% and December's revenue is 38,11,395.86.

Accounting entry (voucher INMF-170000002, 31-12-2026)

With revenue growing and no new billing, the contract liability falls to 25,68,147.29.

Month-end close, January — work overtakes billing

In January, the team completes development, loads master data for UAT and prepares the UAT environment. There is no milestone, invoice or receipt this month — only hours and the month-end revenue recognition. Cumulative cost reaches 1,20,71,500.00, completion 67.92%, and January's revenue is 32,97,302.24.

Accounting entry (voucher INMF-170000003, 31-01-2027)

Cumulative revenue of 1,69,79,154.95 now exceeds cumulative billing of 1,62,50,000.00. For the first time, the project shows a contract asset (unbilled revenue) of 7,29,154.95: INMF has done work that it is not yet entitled to bill.

Business Event 10 — UAT sign-off and February close

The project enters UAT and CRP. The team prepares test scenarios, fixes defects and collects user sign-off, and the UAT milestone is invoiced on 28-02-2027.

Accounting entry (voucher INMF-180000003, 28-02-2027)

UAT defect fixing makes February the costliest month after October. At 28-02-2027, cumulative cost is 1,58,24,750.00, completion is 89.03% and February's revenue is 52,79,129.62.

Accounting entry (voucher INMF-170000004, 28-02-2027)

The milestone invoice and the revenue recognition happen in the same month but for different amounts: 50,00,000.00 billed, 52,79,129.62 earned. The contract asset grows to 10,08,284.57.

Business Event 11 — Go-Live and final collections

The team completes cutover and production deployment, and the system goes live on 01-03-2027. INMF raises the final milestone invoice for 15% of the contract value on 03-03-2027.

Accounting entry (voucher INMF-180000004, 03-03-2027)

ABC Ltd. settles the UAT invoice on 12-03-2027 and the Go-Live invoice on 30-03-2027, each net of TDS.

Accounting entry (voucher INMF-CU000060, 12-03-2027)

Accounting entry (voucher INMF-CU000064, 30-03-2027)

Month-end close, March — the project reaches 100%

Hypercare runs through March. By 31-03-2027, cumulative cost is 1,81,12,750.00 — above the forecast of 1,77,74,000.00. The cost to complete can never be negative, so it becomes nil, completion jumps to 100%, and the March revenue recognition takes the remaining contract value: 2,50,00,000.00 − 2,22,58,284.57 = 27,41,715.43.

Accounting entry (voucher INMF-170000005, 31-03-2027)

March earns 27,41,715.43 against 22,88,000.00 of cost, a margin of 16.55% for the month against 28.90% in every earlier month. The forecast was never revised, so the whole cost overrun of the project falls into the last period (see Plan vs actual).

Business Event 12 — Hypercare ends: elimination and project closure

Hypercare ends on 31-03-2027. Revenue recognized (2,50,00,000.00) now equals the amount invoiced (2,50,00,000.00), and the two WIP balances are no longer needed.

In D365: on the Revenue recognition page, the posted 31-03-2027 line is eliminated (Eliminate) with posting date 31-03-2027 and Set stage to Finished, which moves the project to stage Completed. The internal project INMF-000027 is set to Completed separately; it has no revenue recognition to eliminate.

Accounting entry (voucher INMF-170000006, 31-03-2027)

In D365 the elimination voucher posts one line for each invoice and each revenue recognition; the table shows the totals. Elimination clears the two WIP accounts against each other, and the contract revenue of 2,50,00,000.00 stays in Accrued revenue - sales value. Invoiced revenue - on-account (420300) is not used in this building. Microsoft also notes that once a fixed-price project is eliminated, any new postings to it go directly to profit and loss (How project groups, categories and line properties determine project posting).

Revenue recognition across the project

Contract asset and contract liability

At each month end, WIP - sales value (revenue earned) is set against WIP - invoiced on-account (amount billed). If billing is ahead of revenue, the net is a contract liability; if revenue is ahead of billing, it is a contract asset.

Billing is front-loaded — 45% of the fee is invoiced in October — so the project is in a contract liability for the first three months. From January, development and UAT run ahead of the next milestone and the position turns into a contract asset, which closes when the Go-Live milestone is invoiced.

Plan vs actual

A fixed price protects the customer, not the margin. Actual cost came in 3,38,750.00 above the forecast, mainly from logistics design complexity, additional development and UAT defect fixing, and the whole overrun reduced INMF's margin.

From October to February, actual cost stayed within the forecast, so each month earned the planned margin of 28.90%. In March, cumulative cost passed the forecast: cost to complete fell to nil, completion jumped to 100%, and the month earned only 16.55%. Because the forecast was not revised, the whole overrun fell into the last period. Revising the forecast model when the overrun first appears — Microsoft recommends keeping the original forecast as a baseline and adjusting a copy — spreads the loss of margin over the remaining months instead.

The training cost of 3,15,000.00 on the internal project sits outside the contract. It does not affect completion % or the project margin, but it reduces the margin of the engagement to 65,72,250.00 (26.29%).

Business event vs accounting event

Key takeaway: invoices move amounts between the customer and the balance sheet; revenue reaches profit and loss only through the monthly revenue recognition.

Accounting vouchers of the Contract to Close process

Hour transactions are summarized by month and project, as each timesheet line posts its own voucher.

Trial balance after the Contract to Close process

Observations from the trial balance:

• WIP - sales value and WIP - invoiced on-account both close at nil: the monthly revenue recognitions and the milestone invoices were cleared against each other at elimination.
• Trade Receivables closes at nil, as all five invoices are settled.
• The receipts reconcile: Bank 2,70,00,000.00 + TDS Recoverable 25,00,000.00 = contract value 2,50,00,000.00 + IGST 45,00,000.00 = 2,95,00,000.00.
• Cost - hour and Cost - hour (internal project) together equal Payroll allocation of 1,84,27,750.00.

Profit and loss statement after the Contract to Close process

As in Part 2, the absorption credit (Payroll allocation) is not a real profit. In a live ledger, the matching salaries would be booked through payroll, and the profit from the engagement would be 65,72,250.00: the project margin of 68,87,250.00 less the training cost of 3,15,000.00. GST collected and TDS withheld do not affect profit.

Balance sheet after the Contract to Close process

At the close of the project, the contract balances are nil: everything earned has been billed and everything billed has been collected. During the project they were not — a balance sheet at 31-10-2026 would show contract liability of 60,13,418.48, and at 28-02-2027 a contract asset of 10,08,284.57.

Key takeaways

Every stage of the fixed-price project can be traced from the implementation milestone to the D365 document, the voucher and the financial statements:

Contract (no entry) → Milestone invoice (WIP - invoiced on-account) → Customer receipt → Timesheets (project cost) → Monthly revenue recognition (WIP - sales value / revenue) → Elimination → Project closed

• Billing is not revenue. The billing schedule decides when the customer is invoiced; the revenue recognition decides what is earned.
• Completion drives revenue. With the cost-to-cost method, the hour forecast is as important as the hours posted: revenue each month is only as accurate as the cost to complete.
• The contract balance changes sign. Front-loaded billing creates contract liability; work running ahead of milestones creates a contract asset.
• Configuration decides the route. The project group, the line property's Capitalize cost and the ledger posting setup together decide whether hour cost passes through WIP or goes straight to profit and loss.
• Overruns land at the end unless the forecast is revised during the project.

The objective of this series remains the same: to understand not just which steps to perform in D365 F&O, but the accounting logic behind every important transaction. The configuration and process steps for project accounting will follow in separate posts.

Sources

• Project management and accounting overview, Microsoft Learn
• How project groups, categories and line properties determine project posting, Microsoft Learn
• Fixed price revenue estimate projects, Microsoft Learn