Trace recognized project revenue through billing and ledger relief, and separate genuine unbilled balances from missing work or incomplete reversals.
An invoice has been issued, but the original unbilled amount still appears in the project report. Elsewhere, completed work never entered the report at all. A single total can conceal both problems.
Unbilled receivables reconciliation needs two tests: whether the recorded unbilled balance is supported and agrees with the relevant ledger accounts, and whether completed work has reached the right billing or accounting decision. This guide gives service-business finance teams a line-level bridge, exception decisions and a partial-billing example.
Define the balance before investigating it
Start with your accounting policy and system configuration. “Unbilled,” “accrued revenue” and “WIP” are not interchangeable labels in every environment. Identify precisely which recognized balances, accounts and project transactions your reconciliation covers. Keep operational work awaiting a recognition decision outside that accounting balance until the responsible accountant determines its treatment.
Completing a task, approving time, recognizing revenue, creating an invoice and receiving cash are separate events. Do not use a work-complete flag as automatic authorization for revenue recognition or an invoice as proof that the earlier balance was relieved.
For example, Microsoft’s Project Operations transaction connections link original unbilled sales to billed sales and reversal records. That is a documented product workflow, not a claim that every accounting system works identically.
The controls below are recommended internal practices. Your controller determines recognition, classification, adjustments, materiality and period treatment under the applicable accounting framework; this procedure does not prescribe universal journal entries or tax rules.
Freeze a common cutoff and collect two populations
The project accountant owns preparation. Delivery managers explain work and acceptance; billing owns invoice status; accounting approves financial treatment and corrections. Record one accountable reviewer for the final tie-out, separate from preparation where practicable.
Population one: recorded unbilled transactions
Export the prior approved opening detail, current recognized additions, invoice-related relief, reversals, corrections and closing detail. Obtain the corresponding general-ledger balances and activity. Retain entity, currency, account mapping, period, report filters and export time. Include closed projects with residual balances.
Use the same accounting cutoff for detail and ledger. A later invoice can explain a subsequent event without changing what existed at period-end. Investigate transaction-currency amounts separately from any functional-currency translation or valuation movements; do not sum unrelated currencies.
Population two: work that may need a decision
Obtain completed service records, accepted milestones and approved time through cutoff from the operational source. Compare them with the billing and recognition records using stable work and contract-line identifiers. The purpose is to find missing decisions, not to book every completed item as revenue.
For each unmatched item, the delivery owner supplies completion evidence and the contract owner explains billing conditions. Accounting decides whether the item is already recognized, not yet eligible, awaiting support, nonbillable or incorrectly omitted. Preserve that conclusion even when the result is no posting.
Build the transaction bridge, not just an aging total
Use one row per identifiable source transaction or separately traceable portion. If one invoice combines several work items, retain the allocation; if one work item is billed in parts, retain each invoice line. Names, dates and equal amounts alone are weak matching keys.
| Record group | Fields and evidence | Review question |
|---|---|---|
| Origin | Entity, currency, customer, project, contract line, work ID, completion evidence | Which service and obligation does this amount represent? |
| Recognition | Original posting ID, accounting date, amount, account, approved basis | Is this a supported recorded balance, rather than only an operational estimate? |
| Billing and relief | Invoice and line IDs, billed amount, posting status, linked relief or reversal IDs and amounts | Did the correct portion leave unbilled once, in the appropriate period? |
| Residual | Expected and actual closing amounts, difference, age basis, reason code | Is the remaining balance genuine, misclassified or erroneous? |
| Resolution | Owner, evidence, proposed treatment, approver, posting reference, next review | Can another reviewer reproduce the decision and its completion? |
For the defined account population, calculate: opening recorded balance + recognized additions − posted relief ± separately supported adjustments = expected closing balance. Reconcile that result to the transaction detail and mapped ledger accounts. Explain reclassifications, valuation movements and other adjustments separately rather than concealing them in “billing.”
Choose and retain an aging basis, such as recognition date for the accounting balance and completion date for an operational billing backlog. Oracle’s legacy Unbilled Receivables Aging documentation illustrates why report dates and aging parameters matter. Do not compare two aging reports as equivalent without checking those settings.
Worked example: an invoice does not prove full relief
This is a constructed USD example, excluding taxes, exchange movements, deposits and other adjustments. Assume accounting has already approved the underlying recognition and that the system’s configured process should relieve unbilled by the recognized amount included in the posted invoice.
A service project opens with $12,000 of recorded unbilled revenue. It adds $8,000 during the month. A posted invoice includes $15,000 from those recognized transactions, but the linked relief postings total only $13,000.
- Expected closing balance: $12,000 + $8,000 − $15,000 = $5,000.
- Recorded closing balance: $12,000 + $8,000 − $13,000 = $7,000.
- Difference requiring investigation: $2,000.
The preparer follows the invoice lines back to the original work and postings, verifies that $15,000 really belongs to this population and checks for a later-period relief entry, cancellation or allocation error. If the $2,000 is confirmed as missing relief rather than valid timing, accounting approves the appropriate correction. The authorized posting owner records it, and the reviewer reruns the same-cutoff reports.
Microsoft’s accrued revenue reconciliation guidance documents investigating original and reversal amounts, reviewing corrections and checking the result again. Use your own system’s supported accounting process; do not duplicate revenue or overwrite the spreadsheet to force agreement.
Now apply the second test. Delivery also lists a completed $3,000 item absent from both billing and recognized detail. It does not automatically increase the $5,000 close balance. Assign the contract and accounting review needed to determine its treatment. A ledger tie-out cannot prove that an item missing from both ledger and detail was considered.
Route exceptions by the decision they need
| Exception | Decision owner | Evidence needed to move forward |
|---|---|---|
| Completed work absent from billing and recognition | Delivery and accounting | Work evidence, contract conditions and documented recognition/billing conclusion |
| Recognized item remains unbilled | Billing and contract owner | Valid billing trigger, missing prerequisite, responsible person and next action date |
| Invoice posted but relief is missing or partial | Project accountant and accounting approver | Original-to-invoice allocation, reversal trace, approved correction or supported timing explanation |
| Credit, cancellation or invoice correction restores a balance | Billing and accounting | Original and corrective documents, restored amount and decision on rebilling or other treatment |
| Old residual on a closed project | Contract owner and controller | Remaining entitlement, dispute/support review and authorized accounting conclusion |
Use a recovery path of Identified → Evidence collected → Treatment approved → Posted or documented → Rechecked → Closed. Reopen the affected review when source work, contract terms, invoice allocation or postings change. Preserve the earlier evidence and obtain renewed approval for a changed financial conclusion.
Do not zero an old balance because the project is marked closed. Equally, do not keep it indefinitely because someone expects a future invoice. Age should trigger an accountable assessment of support, classification and recoverability—not an automatic write-off or indefinite carry-forward.
Sign off the balance and the unfinished decisions
Retain the frozen source exports, opening-to-closing bridge, ledger tie-out, invoice allocations, accounting approvals, correction references and exception list. Each outstanding case needs an amount, owner, next action date and controller-approved period treatment. The reviewer decides whether any unresolved difference prevents sign-off under company policy.
Separate a supported unbilled balance awaiting a contractual billing date from an unexplained reconciliation difference. Report unresolved operational decisions separately so an agreeing accounting total does not hide missing-work investigations. Once invoices are released, the downstream accounts receivable workflow handles delivery, collections and payment follow-up; those activities do not replace this close test.
Where Workhint fits
Workhint’s Workflow Engine describes routing approvals to defined roles and requiring details or files before work advances. Those building blocks are relevant to a proposed handoff in which delivery supplies completion evidence, billing supplies invoice references and accounting reviews an exception.
The Finance Leaders solution describes connecting approved work to invoicing and finance review. Keep the unbilled calculation, financial postings and recognition judgments in the appropriate accounting system and accountable roles. These pages do not establish a native unbilled subledger, automatic ledger reconciliation or a ready-made integration to your project system; verify any implementation requirement separately.
Frequently asked questions
Is unbilled reconciliation the same as reviewing overdue invoices?
No. Overdue-invoice review starts with billed receivables and due dates. This process examines the defined recognized unbilled population, its movement into billing and any missing accounting or billing decisions.
Should the unbilled balance be zero at month end?
Not necessarily. Supported recognized amounts may remain unbilled under the contract and accounting policy. The objective is an explained, correctly classified balance—not an empty account.
Can a draft invoice close an unbilled exception?
Not by itself. Verify the invoice’s actual posting state and the linked relief required by your system. A draft, proposed bill or emailed approval is not proof of completed financial postings.
Does a matching ledger total prove all completed work was reviewed?
No. Work omitted from both accounting detail and the ledger can leave the totals agreeing. Compare the independent operational population with documented billing and recognition decisions as a separate completeness test.
Leave a Reply