Opening the cover is not a complete handoff check
A PDF portfolio can act as a container for several component files. A recipient who sees an opening page or preview may not yet have opened the bank statements, spreadsheets or other records within it. Before treating the tax package as delivered, confirm that the preparer can identify and access the actual components needed for the assignment.
Ask the sender whether the item is a single merged document or a portfolio containing separate files. These are different arrangements even when both arrive with a PDF filename. Record the expected contents from the sender's inventory. A page count for the cover or visible document is not necessarily a count of every record the package is meant to carry.
Adobe documents opening, listing and extracting component files in Acrobat. It also describes circumstances in which working with a portfolio in a browser opens a component in the standalone application. Use a supported viewer for the actual package rather than assuming that every browser, email preview or portal thumbnail exposes the same content.
References: Adobe: Working with component files in a PDF Portfolio
Inventory components by their business purpose
Create a receiving list containing the component filename, file type, entity, period and the question it supports. Include the version where several copies exist. A folder containing three files called statement can still leave the preparer unable to determine which account or month each one covers. The inventory should connect the package to the requested evidence.
Compare that list with the sender's expected package before opening every document in detail. If twelve monthly statements are expected but the portfolio contains eleven statement files and one unrelated spreadsheet, a total of twelve components does not establish completeness. Identify the missing period explicitly and request that record through the normal secure channel.
Keep the inventory proportionate. It usually does not need complete account numbers, employee identifiers or tax figures. Use the company's approved references and restrict the underlying records appropriately. The receiving check should improve retrieval without creating another broadly shared list of sensitive information.
Distinguish viewing a component from using its native file
A spreadsheet inside the portfolio may need to be opened in its native application to examine formulas or perform the agreed review. Adobe explains that a component can be opened in its native application when that application is installed. Confirm the preparer's requirements before replacing a usable workbook with a static picture or printed rendering.
Likewise, determine whether a signed or otherwise structured document must be preserved in its original form. A convenient combined printout can change what the reviewer can inspect. Keep the source component and any separate presentation copy clearly identified. The package should not silently substitute a visual approximation for evidence the preparer requested in its original format.
Follow the company's normal handling rules for unfamiliar component types. A portfolio is a delivery container, not an assurance that every included file is safe or appropriate to execute. If a component asks for an unexpected application, active content or access, resolve that requirement with the sender and systems owner before proceeding.
Extract a controlled working set when the workflow needs one
Where the tax portal or review process requires separate files, extract the approved components into an authorized location. Adobe states that extraction does not delete the component from the portfolio. Preserve the original received package and distinguish the extracted working copies so staff understand which artifact represents the original delivery.
Check the resulting filenames and folder structure. Two components with similar names may become difficult to distinguish after extraction, particularly if several portfolios are processed together. Apply an approved naming convention that preserves the original name or a mapping to it. Do not overwrite an earlier document simply because another component uses the same visible label.
Open representative extracted files and compare them with the corresponding portfolio components. Confirm the expected pages, worksheet content or other necessary structure remains available. Where the transfer process uses file checksums, preserve that evidence through the appropriate tooling. A successful extraction message does not establish that the receiving workflow selected every required component.
References: Adobe: Working with component files in a PDF Portfolio
Keep revisions traceable across the container and working copies
Adobe notes that editing a component inside a portfolio does not change the original file outside that portfolio. That distinction matters when a sender maintains a separate source folder and a preparer works from extracted copies. There can be several related versions, and an update to one should not be assumed to update all the others.
Agree how corrections arrive. The sender might provide a replacement portfolio, one revised component or a corrected native file. Identify which earlier record is superseded, what changed and whether the preparer has already used it. Keep the original delivery and the correction history under the applicable records process rather than quietly replacing files in place.
For a fictional package, suppose a revised November statement replaces one of twelve monthly statements. The receiving task is to confirm that specific replacement and preserve its relationship to the earlier copy. It is not to add the new statement as a thirteenth period or discard the entire original package without documenting the change.
References: Adobe: Working with component files in a PDF Portfolio
Obtain confirmation about usable records, not merely upload success
Ask the preparer to confirm the components needed for the engagement are accessible in the agreed format. An upload receipt establishes that the portal received something; it does not establish that the intended reviewer can open the spreadsheet, locate the missing month or interpret a filename. Resolve those differences before marking the request complete.
Record any remaining exception with an owner and the next action. Examples include a password obtained through a separate approved route, an unsupported native format or an absent component. Keep that list tied to the evidence request rather than burying it in an email saying the PDF had a problem.
Retain the final inventory, original package and accepted working copies according to the company's records policy. For the next recurring handoff, use the format the preparer can reliably consume. A portfolio can be a useful container when both sides understand it; the acceptance standard is the availability of the required records, with their identity and version intact.
Sources
Requirements and product details can change. Check the linked guidance for the facts that apply to your situation.
Related reading
Need help with this work?
General information, not personalized accounting, tax, legal, or investment advice. Have the appropriate qualified professional review decisions that depend on your circumstances.