Find site costs missing from month-end accounts

State the reporting date, time where relevant and the finance timetable for submissions and review. Identify the site populations likely to contain uninvoiced items: accepted subcontract work, equipment hire, services, utilities, material receipts and other project-specific categories.

Use physical event and service-period dates, not just document-entry dates. A receipt entered on 2 October may relate to material physically received on 30 September. A September-dated invoice may include work performed in October. Both require review against the underlying facts.

Do not assume that every outstanding purchase order creates a current-period accrual. Unperformed future work belongs in commitment or forecast reporting, not automatically in the current-period accounting entry. The distinction should be explicit in the site submission template.

For each proposed accrual, identify the supplier or subcontractor, contract or order, work package, service period or receipt date, source evidence and amount basis. Record who prepared and checked the proposal, and whether the value is measured, agreed or estimated.

Attach the relevant acceptance, measurement or service confirmation under the project's procedure. Where the amount is provisional, state the assumption and uncertainty. A round number with no supporting basis is difficult to review and difficult to reconcile later.

Finance should define the appropriate account, tax treatment, recognition conditions and approval requirements. The operational register should not prescribe a universal journal for all materials and services. Different transaction types and accounting configurations can require different treatment.

The cutoff example uses a fictional site with ₹4 lakh of accepted September service work that has not been invoiced or otherwise recognised. A separate ₹2 lakh material receipt has already generated the configured receipt-related accounting entry. Assume finance confirms those facts and the service recognition basis.

ERPNext's received-but-not-billed documentation illustrates a stock receipt debiting inventory and crediting a clearing account. That example concerns inventory recognition, not an automatic project expense. Finance must assess the configured transaction and its place in the reporting view.

The example does not say that every accepted service requires the same journal or that every receipt is correctly valued. It shows why the proposal must check existing records before adding another amount.

Match proposals against posted invoices, purchase receipts, service entries, existing accruals and relevant clearing accounts. Use order line, acceptance reference, supplier, period and amount together. Amount alone is a weak duplicate key because several legitimate transactions can have the same value.

Check prior-period accruals still outstanding. A service spanning two months may need a new period allocation, a revised estimate or a reconciliation of the earlier entry. It should not automatically be accrued in full again.

ERPNext's purchase invoice documentation describes links to receipt records and warns about duplicate stock updates in relevant configurations. The broader control is to understand which source transaction already posted what, rather than assuming an invoice is always the first recognition event.

Some cutoff amounts cannot be measured precisely before close. Finance may permit a supported estimate under its policy. Record the calculation, source assumptions, reviewer and expected resolution date.

For equipment hire, the basis may involve verified operating or hire days and the agreed commercial rate. For services, it may involve accepted progress and the contract valuation basis. Do not invent a standard percentage of open orders as a substitute for reviewing whether work occurred.

Compare estimates with later invoices to understand recurring bias. A difference can arise from changed scope, incomplete evidence, rate disputes or an estimation error. Investigate material patterns so the next close improves rather than treating every variance as unavoidable.

The organisation may use automatic reversals, invoice matching, accrual clearing or another approved process. State which method applies and preserve the link between the original proposal, posted entry, reversal where applicable and later invoice.

If the ₹4 lakh service proposal is posted and the eventual valid invoice is ₹4.2 lakh, finance assesses the ₹0.2 lakh difference under policy. The system should not leave both the full accrual and full invoice as duplicated cost. Nor should it remove the accrual before the intended replacement recognition without considering the reporting effect.

Cancelled or disputed invoices need follow-up. A scheduled reversal does not prove that the underlying obligation disappeared. Review outstanding accruals by source and age, with a named owner for unresolved items.

Give site teams a short, consistent submission format and enough lead time to obtain evidence. Finance should return unclear proposals with specific questions: missing period, unsupported quantity, duplicate recognition or an unresolved rate.

Keep a close checklist showing submitted, reviewed, posted, rejected and carried-forward proposals. Record reasons for rejection so the site does not resubmit the same item without resolving the issue. Material late discoveries should follow the organisation's correction and reporting policy.

Review gate records, inspection holds and service confirmations alongside the financial extracts where relevant. These operating sources can reveal missing transactions, but they need interpretation. Physical presence alone does not settle ownership, acceptance or expense recognition.

Choose an uninvoiced service, a receipt already recognised and a prior accrual awaiting invoice. Trace all three through proposal review, posting and the next period's resolution. Confirm that source identities prevent duplicate entries and that the report preserves the basis of any estimate.

Then test a late invoice for a prior period and an invoice that covers two periods. Finance should be able to explain the treatment consistently. A successful accrual process produces a reconciled trail, not merely a list of journals posted before the deadline.

The site and finance teams should finish the review knowing which work belongs to the period, where it is already recognised and which estimates remain open for reconciliation.

1. Review performed work and receipts against the reporting cutoff.
2. Prepare proposals with identifiable source evidence and valuation assumptions.
3. Check invoices, receipt accounting and existing accruals for overlap.
4. Apply finance-approved recognition and posting rules.
5. Reconcile every proposal to its later invoice, reversal or authorised resolution.