Systems and records
Purchase price allocation workflow data: when workpapers become evidence
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Acquisition accounting workpapers become useful evidence for an AI task when each allocation figure can be traced from the closing documents through intangible identification, valuation inputs, review challenges and any measurement-period adjustment to a posted entry, and when every document has passed a rights screen. A file holding only the final allocation schedule shows the answer without the reasoning, so it cannot test a model's judgment.
Value drivers
Purchase price allocation
Key takeaways
- The reasoning in a purchase price allocation sits in identification memos, valuation inputs, review notes and adjustment memos, not in the final schedule.
- Screen every workpaper on four separate questions: access, personal data, ownership and contractual limits.
- Valuation reports and auditor documentation usually belong to, or are restricted by, someone other than the company.
- A good task freezes the evidence available at one decision point and checks the answer against a posted outcome.
- IFRS 3's one-year measurement period gives tasks a clean boundary between provisional and final amounts.
What makes purchase price allocation workflow data usable evidence for an AI task?
Purchase price allocation workflow data is usable evidence when every number in the final allocation can be walked back through the judgment that produced it: the consideration, the opening balance sheet, the list of identified intangibles, the valuation inputs, the reviewer's challenges and any later adjustment. A file that holds only the signed allocation schedule shows what was booked. It does not show why, so a model trained or evaluated on it learns to reproduce totals rather than to reason.
Acquisition accounting is a good test of this because the process is judgment heavy and rule bound at the same time. IFRS 3 requires the acquirer to recognize identifiable intangible assets separately from goodwill, and an intangible is identifiable only if it meets the separability criterion or the contractual-legal criterion. Fair values then rest on a hierarchy of inputs, and IFRS 13 ranks quoted prices for identical items highest and unobservable inputs lowest. Each of those steps leaves a document trail when the team works well.
So the question for a finance team is not whether it has workpapers. It is whether the workpapers link source, judgment, review and outcome tightly enough that a reviewer could check an answer against them, and whether the company has the right to use each one outside the deal.
This also explains why one acquisition can be more useful than many routine transactions. A single allocation forces the team to decide which assets exist, which inputs are credible, what changes are corrections and what are new events, and to defend each choice to an auditor. Few other finance processes produce that much documented judgment in such a short, bounded window.
Which acquisition workpapers carry the reasoning, and which only carry the result?
The reasoning lives in the middle of the file: identification memos, valuation input files, review notes and adjustment memos. The beginning and end of the file, the purchase agreement and the final journal entry, frame the task but rarely explain it. The table maps each stage of a typical allocation to the records it produces and the gap that most often breaks the chain.
| Workflow stage | Typical records | What the records prove | Common gap |
|---|---|---|---|
| Consideration and closing | Purchase agreement, funds flow, closing statement, contingent consideration terms | What was transferred and what remains contingent | Working capital true-up recorded only in email |
| Opening balance sheet | Acquiree trial balance at close, conforming adjustments, policy alignment memo | Starting carrying amounts and policy differences | Conforming entries posted without a memo explaining them |
| Intangible identification | Identification memo, customer contract list, trademark and domain registrations | Which assets met separability or the contractual-legal test | Customer relationships assumed rather than tested against contracts |
| Fair value measurement | Valuation report, input workbook, discount rate support, useful life analysis | Inputs used and their place in the fair value hierarchy | Unobservable inputs with no support beyond management assertion |
| Goodwill residual | Allocation schedule, deferred tax computation | How the residual was derived | Deferred tax effects in a separate file with no link |
| Tax allocation | Asset class schedule prepared for Form 8594 where it applies | How consideration was assigned across tax asset classes | Tax and book classifications differ with no reconciliation |
| Audit review | Auditor requests, management responses, revised schedules | Which assumptions were challenged and how they changed | Responses kept but the auditor's request text is missing |
| Measurement period | Adjustment memos, updated valuation, restated schedule | Which provisional amounts changed on new information about the acquisition date | Post-close events booked as adjustments without a memo |
Who owns each workpaper, and what does that mean for using it?
Holding a document is not the same as being free to reuse it. Four separate questions apply to every workpaper: who can access it today, whether personal data in it limits reuse, who owns it, and whether any contract restricts what the company may do with it. De-identifying a file answers only the second question.
Company-prepared schedules and memos are usually the strongest candidates, because the company created them and the main limits come from confidentiality terms in the deal documents. Third-party valuation reports are different: they are commonly delivered under an engagement letter that restricts use and distribution, so the letter decides, not the fact that the report sits in the company's files. Audit documentation is the auditor's record. Under PCAOB AS 1215 the audit firm must retain its documentation for seven years from the report release date; what the company holds is the subset of requests and responses that passed through its hands.
Records that came from the seller in a data room add a further layer. The purchase agreement or a surviving confidentiality agreement may govern them, and employee-level records such as census files carry privacy obligations no matter who owns them. Counsel reviews the specific agreements before any of these leave the finance team.
What should a rights screened workpaper task inventory include?
The inventory is one row per document, with enough fields that a reviewer can decide its screen status without opening the document again. Use the fields below as written; the example column is illustrative and uses no real company data.
At a glance
What should a rights screened workpaper task inventory include
- Cleared: company-prepared, no restrictive terms, personal data removable without losing the reasoning.
- Restricted: usable only after a third party consents or a clause is confirmed to allow it.
- Excluded: owned by someone else, barred by contract, or impossible to de-identify without destroying the task.
| Inventory field | What to record | Illustrative entry | Why it matters |
|---|---|---|---|
| Document ID and title | Stable ID, title, file type, location | PPA-07, customer relationship useful life memo, PDF, close binder folder 3 | Lets every task reference evidence by ID |
| Workflow stage | One stage from the stage table | Fair value measurement | Shows where the document sits in the reasoning chain |
| Author and origin | Preparer role and organization | Controller's team, company prepared | Drives the ownership screen |
| Governing terms | Agreement or letter that limits use, with clause reference | None beyond deal confidentiality clause | Decides whether reuse needs consent or is barred |
| Personal data present | Categories of personal data, if any | Named sales representatives in a customer list appendix | Flags redaction or exclusion work |
| Third-party confidential data | Customer, vendor or seller confidential terms | Customer contract renewal terms | May need removal even after de-identification |
| Version and date | Draft or final, date, superseded by | Final, month 5 after close, supersedes PPA-04 | Keeps provisional and final amounts apart |
| Linked records | IDs of inputs, reviews and outcomes it connects to | PPA-03 contract list, AUD-12 auditor request, JE-221 adjustment | Makes reconciliation possible |
| Outcome evidence | Posted entry or final schedule that confirms the result | JE-221 posted in the adjustment period | Separates a verified outcome from a draft position |
| Screen status | Cleared, restricted, excluded, with reason | Cleared for internal task use; licensing pending counsel review | The decision the inventory exists to record |
How do you turn the inventory into a task with a checkable answer?
A task is a question asked at a specific point in the workflow, with only the evidence that existed at that point, and an answer that a later document confirms. The cleanest PPA tasks come from decisions the team actually made and then booked: whether a customer list met the contractual-legal criterion, which input level a valuation relied on, or whether a change after closing was a measurement-period adjustment.
Build each packet from five parts: the starting state, the cleared evidence IDs available at that moment, the decision question, the expected answer in the team's own terms, and the outcome record that verifies it. Keep later documents out of the starting state. If the month 5 valuation memo is in the packet for a question asked at close, the task leaks its own answer.
IFRS 3's one-year limit on the measurement period gives these packets a natural boundary. Adjustments inside that window, made on new information about facts that existed at the acquisition date, belong in the packet as outcomes. Changes caused by later events, such as an earnings target being met, are not measurement-period adjustments and should be labelled as a different task type.
Write the decision question the way the team actually faced it. A question such as whether non-contractual customer relationships are separable, given the evidence of exchange transactions the team found, is far better than a generic request to allocate the purchase price. It narrows the evidence, names the rule and makes the expected answer checkable against the identification memo and the booked allocation.
Worked example: one allocation file screened and packaged (illustrative)
This example is illustrative. A mid-sized distributor acquires a regional competitor and wants to know which of its acquisition workpapers could become tasks. Its controller inventories 18 documents from the close binder and the audit request log.
The screen clears 11 documents: the identification memo, the contract list with representative names removed, the opening trial balance, the policy alignment memo, the allocation schedule, the deferred tax workbook, three management responses to auditor requests, the useful life memo and the month 5 adjustment memo. Four are restricted, all parts of the external valuation report whose engagement letter limits distribution. Three are excluded: a seller-provided employee census and two auditor workpapers the company never received in full.
From the cleared set the team writes 6 tasks. One asks, with only the close-date evidence, whether the acquiree's customer relationships meet the contractual-legal criterion. The identification memo answers yes for customers with signed supply agreements and no for spot buyers, and the posted allocation confirms only the contracted group was recognized. The exception is instructive: one proposed task asked whether a later revision to the trademark's useful life was a measurement-period adjustment. The memo showed it came from a rebranding decision made after closing, so the team relabelled it as a post-acquisition estimate change rather than a measurement-period task.
How should book and tax allocations be linked in the same packet?
Link them through a reconciliation table rather than treating them as separate tasks. The book allocation follows the financial reporting standard, while a U.S. asset acquisition also produces a tax allocation that the IRS Form 8594 instructions describe as a residual method: reduce the consideration by cash and deposit accounts, fill Classes II through VI in order, and leave goodwill and going concern value in Class VII. The two allocations start from the same deal but answer different questions, and the differences between them are where a lot of real judgment sits.
A packet that shows both, with a line-by-line reconciliation and the deferred tax workbook that bridges them, lets a task ask a sharper question: why does this intangible carry a different value or life for tax than for books, and is that difference explained? Teams that keep the tax schedule with the tax adviser and the book schedule with the controller often lose this link. Bringing both into the inventory, each with its own screen status, can be one of the most useful improvements to the file.
Where the deal was a stock purchase rather than an asset purchase, the tax side looks different and Form 8594 may not apply at all. Record the deal structure as a field in the starting state so that a task never assumes the wrong tax treatment.
What must an independent reviewer be able to trace in each packet?
Each packet passes only if an independent reviewer can trace the expected answer to cleared evidence and to a posted outcome without asking the original preparer. That standard mirrors the one PCAOB AS 1215 sets for auditors, where documentation must let an experienced auditor with no previous connection to the engagement understand the procedures, evidence and conclusions.
- Every figure in the expected answer appears in a cited evidence ID or is derived by a stated calculation.
- The fair value input level claimed in the answer matches the support in the input workbook.
- Significant assumptions are judged together, not one at a time, because AS 2501 asks auditors to evaluate them individually and in combination.
- The outcome record is posted or final, not a draft schedule.
- Book and tax classifications either agree or have a written reconciliation, including the Form 8594 class order where the deal was an asset acquisition.
- Provisional and final amounts are both present and labelled, so the task tests the change, not just the end state.
- No document in the starting state is dated after the decision point.
Which acquisition files should stay out of the inventory entirely?
Stop when the reasoning cannot be separated from material you are not free to use. A valuation workbook that only makes sense alongside a restricted valuation report is one example; a customer relationship analysis that depends on named customers' confidential pricing is another.
Narrow the scope rather than abandon it when only one stage is blocked. Many teams can clear identification, opening balance sheet and adjustment tasks even when the valuation inputs remain restricted. Ask for specialist review before going further whenever the file involves contingent consideration disputes, tax positions under examination, or a deal still inside its indemnity claims period, because those documents can become evidence in a live disagreement.
Watch for files where the outcome is still moving. An allocation still inside its measurement period has provisional amounts by definition, so tasks built from it should wait until the period closes or label those amounts as provisional and keep the final value out of the expected answer.
Taking a screened acquisition file into a licensing review
If the inventory shows a meaningful cleared set, the next step is a structured rights and preparation review rather than a bulk export. SourceX offers one such route, covering sourcing and qualification, rights review, contracting, preparation, delivery and payment for businesses licensing operational records to AI developers. Nothing is delivered before the company approves scope and terms and signs, and a short assessment with no upload shows whether it qualifies.
Frequently asked questions
What is purchase price allocation workflow data?
It is the linked set of records produced while assigning an acquisition's consideration to identifiable assets, liabilities and goodwill: identification memos, valuation inputs, review correspondence, adjustment memos and the posted entries. Its value for AI lies in the links between those records, not in the final schedule alone.
Can we use the valuation firm's report in an AI dataset?
Only if the engagement letter allows it or the firm consents. Valuation reports are commonly delivered with use and distribution limits, so the company's possession of the report does not settle the question; counsel should read the letter.
Are auditor workpapers part of our acquisition file?
Not usually. The audit firm keeps its own documentation, and PCAOB AS 1215 requires it to retain that documentation for seven years from the report release date. The company typically holds the requests it received and the responses it sent, which can still be useful task evidence.
How many acquisitions does a useful dataset need?
There is no fixed number, and one well-documented file can yield several tasks. What matters more is that each task has a decision point, cleared evidence and a posted outcome; many thin files with only final schedules are worth less than a few complete ones.
Does de-identification make acquisition workpapers safe to license?
No. Removing personal data addresses privacy, but ownership and contractual limits remain. A de-identified valuation report is still subject to its engagement letter, and seller documents may still be covered by deal confidentiality terms.
Sources
- IFRS 3 says the measurement period shall not exceed one year from the acquisition date, and that an intangible asset is identifiable if it meets either the separability criterion or the contractual-legal criterion. Source
- The IFRS 3 illustrative examples treat contractual customer relationships, registered trademarks and registered domain names as meeting the contractual-legal criterion, and walk through a valuation received within the measurement period. Source
- IFRS 13 gives the highest priority to quoted prices in active markets for identical items (Level 1) and the lowest priority to unobservable inputs (Level 3), which are used only where relevant observable inputs are not available. Source
- PCAOB AS 1215 requires audit documentation that lets an experienced auditor with no previous connection to the engagement understand the procedures, evidence and conclusions, and requires retention for seven years from the report release date. Source
- PCAOB AS 2501 treats a fair value measurement as a form of accounting estimate and requires the auditor to evaluate the reasonableness of significant assumptions individually and in combination. Source
- The IRS Form 8594 instructions allocate consideration under the residual method across seven asset classes, filling Classes II through VI in order and leaving goodwill and going concern value in Class VII. Source
See if your company qualifies
A short company assessment. No data uploads are needed.