TL;DR
Nobody is on call for the portfolio when incoming reporting packs wait for quarterly review. Lumonic reads each pack overnight and stages what needs attention by morning.
A reporting pack lands in whatever format the portfolio company uses, and Lumonic starts the job.
Overnight, the power user reads the pack and proposes numbers using your extraction rules and prior decisions for that company.
Lumonic checks for restatements, missing values, changed mappings, and formula health. It also tests covenants and compares results with budget. Lumonic displays new values in green and restatements in orange.
By morning, Lumonic has staged exceptions and proposed changes for review. Your policy determines whether you approve every publication or review exceptions when required checks fail.
Every published number traces to its source document, page, and cell.
What is a portfolio company reporting pack?
The set of documents a portfolio company sends each period: financial statements, compliance certificate, borrowing base, board pack or KPI report, in whatever format the company uses.
A PDF may report figures in thousands, while an Excel workbook uses different tabs or line-item names. Financial statement data extraction must identify each figure's unit and period before mapping it to the firm's definitions. A changed format or a switch between quarterly, year-to-date, and LTM figures requires a fresh check of the mapping.
What happens when reporting packs wait for manual review?
Without overnight review, a reporting pack can sit unopened until someone prepares for the quarterly review. Arrival alone does not trigger someone to interpret the documents or alert the deal team.
Someone must open each document and interpret it using the firm's reporting rules and prior decisions about that company. The reviewer then tells the deal team what changed and which items need attention. Review and handoff both wait until that person has time, especially when a format or metric definition has changed.
A pack may contain results that fail a covenant test or miss budget, but the firm cannot assess those results until someone reviews the documents. The firm should be able to re-underwrite a company on the day its reported results reveal a failed test or budget miss, rather than wait for quarterly review preparation.
What changes when Lumonic reviews packs overnight?
Lumonic reads each pack when it lands and stages proposed changes and exceptions by morning. Reviewers can inspect the source pages instead of starting with unopened documents.
How does Lumonic review a reporting pack overnight?
At 11:42 pm, the pack lands and Lumonic marks its queue row In progress. The Lumonic 12.0 release introduction describes the launch.
After the job starts, the power user reads the pack and proposes numbers under the firm's extraction rules and permissions. The power user also uses the firm's history with that company, including tracked metrics and previously allowed adjustments.
Lumonic checks each proposal for missing values, changed mappings, formula health, and revisions to previously reported periods. Lumonic then runs the firm's covenant tests and compares reported performance with budget.
Lumonic returns each change as a proposal and flags failed checks for review. Each proposal shows the previous and proposed values, so you can inspect the change without rebuilding the comparison in Excel.
Toward morning, Lumonic stages completed jobs for review. New values appear in green and restatements in orange, with each change displayed. Under a review-every-publish policy, you publish approved proposals. If your policy permits publication after every required check passes, Lumonic can publish those proposals and stage exceptions for your review.
By 6:27 am, completed queue rows have changed from In progress to Ready for review. The timestamps show when each pack entered the queue and when its job became ready. You can start with proposed numbers and completed checks, while Lumonic marks the exceptions that require attention.
Why restatements are the hard part
If a company reports a last-twelve-month figure in one pack and a quarterly figure in the next, the two numbers cover different periods. You cannot compare them directly or infer the intervening months without checking the underlying figures. The change in reporting period is not, by itself, a restatement.
A restatement revises a figure the company already reported for a prior period. When a company corrects an error, ASC 250 calls for affected prior periods to be adjusted. Overwriting the original figure would hide what the company reported before the correction.
Lumonic keeps the original and revised values visible with the affected period, the change, and a trail to the source page. Lumonic retests calculations affected by the revision, including covenant and budget tests, and stages the result for your review.
What is ready for review by morning?
By the time you log in, last night's documents are extracted and what needs your attention is waiting for you.
By morning, Lumonic shows companies late on reporting and puts the portfolio watchlist in view. Its built-in power user drafts flash commentary from the latest approved numbers and overnight checks for your review.
You can inspect staged changes alongside the watchlist and flash commentary before deciding what needs follow-up. Once published under your policy, those values are available for quarterly review.
Who approves and publishes overnight reporting changes?
Your firm's approval policy determines whether you publish each approved proposal or Lumonic publishes proposals that pass every required check.
Lumonic co-founder Kevin Hsu explains how firms can place approvals within the workflow.
You decide how much of this runs on its own and where manual approvals sit. Some teams review every publish. Others set the rules, let the health checks publish when nothing fails, and only look at exceptions. Depending on your internal controls like maker-checker sign-off or SOX documentation, the approval steps go where your policy puts them, and every step Lumonic takes is logged for review.
If your policy requires maker-checker sign-off, assign separate people to prepare and approve proposals. If it requires SOX documentation, specify the evidence to retain. Lumonic logs its checks and the approval and publication steps.
How can reviewers trace a number to its source?
Reviewers can trace a published number to its source document, page, and cell. Click a value in Lumonic, an MCP-generated output or its Excel plugin, and Lumonic opens the page with the source boxed.
A number on its own does not show whether the power user chose the correct period or mapped the right line item. The boxed source lets you verify those decisions before publishing or using the value in a covenant calculation. The source trail also lets you check a number extracted by a person against one proposed by the power user.
What should "ready for review" mean for a reporting pack?
A reporting pack is ready for review when its required fields and checks have been assessed, changes to prior periods are identified, and a publisher is assigned under the firm's policy. Define those conditions for each portfolio company before automating review.
Set the required checks. Specify which fields must be present and which period, mapping, and formula checks must pass. If you require a balance-sheet or cash-flow reconciliation, define it in your review policy. Set the covenant and budget checks that apply to each company, and flag failed checks for review.
Define a restatement. Decide which changes to previously reported periods your firm classifies as restatements, and distinguish them from updates to an open period. Keep the original figure beside the revision and identify the affected period. Flag a switch between LTM and quarterly reporting separately so the reviewer reconciles the periods rather than treating the switch itself as a restatement.
Assign publishing authority. Decide whether a reviewer approves every publish or only submissions that fail a check. When your controls require separate roles, document who acts as maker and checker. Record approvals and exceptions alongside the final publication so another reviewer can reconstruct the decision.
Lumonic's team configures these rules with you. Lumonic then checks packs for restatements, missing values, changed mappings, and formula health. It tests covenants and budgets, then stages proposals according to your approval policy.
How are overnight reporting workflows set up today?
Today, Lumonic's team sets up overnight workflows with the firm. The firm specifies how Lumonic should read company documents, which prior decisions carry forward, and where approvals sit. Lumonic uses those rules to read documents, run checks, and stage proposed changes for review.
A planned setup option would let you describe the work once, as you would brief a new analyst. Lumonic's team still handles setup with you today.
How can a firm test overnight reporting pack review?
Test Lumonic against documents from a reporting cycle your firm has already approved. Compare the proposed numbers and flagged issues with your record, then inspect their source pages. LAGO Innovation Fund stopped sending reminder emails and keeping tracking spreadsheets, and cut portfolio review prep from weeks to days.
Check whether each proposed value matches your approved record, whether Lumonic flags the issues you identified, and whether you can trace each number to its source before publication.
Frequently asked questions
Is Lumonic's power user a person?
No. The power user is built into Lumonic. It reads reporting packs, proposes numbers under the firm's rules, and runs the configured checks overnight. People review exceptions and approve publication wherever the firm's policy requires it.
Does "ready for review" mean the numbers are published?
No. Ready for review means Lumonic has staged proposed values and the results of its checks. The firm decides whether a person approves each publish or Lumonic publishes when every required check passes.
What happens if a reporting pack has missing values or a failed check?
Lumonic flags the issue and stages the proposed numbers for review. Your firm's rules determine which checks must pass before publication and who approves an exception.
Is a switch from LTM to quarterly reporting a restatement?
No. LTM and quarterly figures cover different periods, so the reviewer must reconcile the periods before comparing them. A restatement revises a figure the company previously reported for a prior period.
Put your last reporting cycle through Lumonic
Lumonic reads portfolio company reporting packs overnight, tests covenants and budgets, and stages proposed changes for review. Every number traces to its source page. Schedule a demo to run documents from your last reporting cycle through Lumonic and compare the proposed numbers with your approved record.
Disclaimer
This article was written by Lumonic, a PitchBook company, and reflects Lumonic's views as of October 2026. Statements about third-party products and companies are based on publicly available information, including the vendors' own websites, press releases and documentation, and on the sources linked in the text. Lumonic has not independently tested third-party products, and their capabilities, pricing and positioning may have changed since this article was last updated. Statements about Lumonic's own product describe the platform at the time of writing, and customer outcomes are taken from the published customer stories linked in the text. Nothing here is a guarantee of results. Third-party names and trademarks belong to their respective owners and are used for identification only. If you represent a company named here and believe a statement is inaccurate, contact support@lumonic.com and Lumonic will review and correct it.
TL;DR
Nobody is on call for the portfolio when incoming reporting packs wait for quarterly review. Lumonic reads each pack overnight and stages what needs attention by morning.
A reporting pack lands in whatever format the portfolio company uses, and Lumonic starts the job.
Overnight, the power user reads the pack and proposes numbers using your extraction rules and prior decisions for that company.
Lumonic checks for restatements, missing values, changed mappings, and formula health. It also tests covenants and compares results with budget. Lumonic displays new values in green and restatements in orange.
By morning, Lumonic has staged exceptions and proposed changes for review. Your policy determines whether you approve every publication or review exceptions when required checks fail.
Every published number traces to its source document, page, and cell.
What is a portfolio company reporting pack?
The set of documents a portfolio company sends each period: financial statements, compliance certificate, borrowing base, board pack or KPI report, in whatever format the company uses.
A PDF may report figures in thousands, while an Excel workbook uses different tabs or line-item names. Financial statement data extraction must identify each figure's unit and period before mapping it to the firm's definitions. A changed format or a switch between quarterly, year-to-date, and LTM figures requires a fresh check of the mapping.
What happens when reporting packs wait for manual review?
Without overnight review, a reporting pack can sit unopened until someone prepares for the quarterly review. Arrival alone does not trigger someone to interpret the documents or alert the deal team.
Someone must open each document and interpret it using the firm's reporting rules and prior decisions about that company. The reviewer then tells the deal team what changed and which items need attention. Review and handoff both wait until that person has time, especially when a format or metric definition has changed.
A pack may contain results that fail a covenant test or miss budget, but the firm cannot assess those results until someone reviews the documents. The firm should be able to re-underwrite a company on the day its reported results reveal a failed test or budget miss, rather than wait for quarterly review preparation.
What changes when Lumonic reviews packs overnight?
Lumonic reads each pack when it lands and stages proposed changes and exceptions by morning. Reviewers can inspect the source pages instead of starting with unopened documents.
How does Lumonic review a reporting pack overnight?
At 11:42 pm, the pack lands and Lumonic marks its queue row In progress. The Lumonic 12.0 release introduction describes the launch.
After the job starts, the power user reads the pack and proposes numbers under the firm's extraction rules and permissions. The power user also uses the firm's history with that company, including tracked metrics and previously allowed adjustments.
Lumonic checks each proposal for missing values, changed mappings, formula health, and revisions to previously reported periods. Lumonic then runs the firm's covenant tests and compares reported performance with budget.
Lumonic returns each change as a proposal and flags failed checks for review. Each proposal shows the previous and proposed values, so you can inspect the change without rebuilding the comparison in Excel.
Toward morning, Lumonic stages completed jobs for review. New values appear in green and restatements in orange, with each change displayed. Under a review-every-publish policy, you publish approved proposals. If your policy permits publication after every required check passes, Lumonic can publish those proposals and stage exceptions for your review.
By 6:27 am, completed queue rows have changed from In progress to Ready for review. The timestamps show when each pack entered the queue and when its job became ready. You can start with proposed numbers and completed checks, while Lumonic marks the exceptions that require attention.
Why restatements are the hard part
If a company reports a last-twelve-month figure in one pack and a quarterly figure in the next, the two numbers cover different periods. You cannot compare them directly or infer the intervening months without checking the underlying figures. The change in reporting period is not, by itself, a restatement.
A restatement revises a figure the company already reported for a prior period. When a company corrects an error, ASC 250 calls for affected prior periods to be adjusted. Overwriting the original figure would hide what the company reported before the correction.
Lumonic keeps the original and revised values visible with the affected period, the change, and a trail to the source page. Lumonic retests calculations affected by the revision, including covenant and budget tests, and stages the result for your review.
What is ready for review by morning?
By the time you log in, last night's documents are extracted and what needs your attention is waiting for you.
By morning, Lumonic shows companies late on reporting and puts the portfolio watchlist in view. Its built-in power user drafts flash commentary from the latest approved numbers and overnight checks for your review.
You can inspect staged changes alongside the watchlist and flash commentary before deciding what needs follow-up. Once published under your policy, those values are available for quarterly review.
Who approves and publishes overnight reporting changes?
Your firm's approval policy determines whether you publish each approved proposal or Lumonic publishes proposals that pass every required check.
Lumonic co-founder Kevin Hsu explains how firms can place approvals within the workflow.
You decide how much of this runs on its own and where manual approvals sit. Some teams review every publish. Others set the rules, let the health checks publish when nothing fails, and only look at exceptions. Depending on your internal controls like maker-checker sign-off or SOX documentation, the approval steps go where your policy puts them, and every step Lumonic takes is logged for review.
If your policy requires maker-checker sign-off, assign separate people to prepare and approve proposals. If it requires SOX documentation, specify the evidence to retain. Lumonic logs its checks and the approval and publication steps.
How can reviewers trace a number to its source?
Reviewers can trace a published number to its source document, page, and cell. Click a value in Lumonic, an MCP-generated output or its Excel plugin, and Lumonic opens the page with the source boxed.
A number on its own does not show whether the power user chose the correct period or mapped the right line item. The boxed source lets you verify those decisions before publishing or using the value in a covenant calculation. The source trail also lets you check a number extracted by a person against one proposed by the power user.
What should "ready for review" mean for a reporting pack?
A reporting pack is ready for review when its required fields and checks have been assessed, changes to prior periods are identified, and a publisher is assigned under the firm's policy. Define those conditions for each portfolio company before automating review.
Set the required checks. Specify which fields must be present and which period, mapping, and formula checks must pass. If you require a balance-sheet or cash-flow reconciliation, define it in your review policy. Set the covenant and budget checks that apply to each company, and flag failed checks for review.
Define a restatement. Decide which changes to previously reported periods your firm classifies as restatements, and distinguish them from updates to an open period. Keep the original figure beside the revision and identify the affected period. Flag a switch between LTM and quarterly reporting separately so the reviewer reconciles the periods rather than treating the switch itself as a restatement.
Assign publishing authority. Decide whether a reviewer approves every publish or only submissions that fail a check. When your controls require separate roles, document who acts as maker and checker. Record approvals and exceptions alongside the final publication so another reviewer can reconstruct the decision.
Lumonic's team configures these rules with you. Lumonic then checks packs for restatements, missing values, changed mappings, and formula health. It tests covenants and budgets, then stages proposals according to your approval policy.
How are overnight reporting workflows set up today?
Today, Lumonic's team sets up overnight workflows with the firm. The firm specifies how Lumonic should read company documents, which prior decisions carry forward, and where approvals sit. Lumonic uses those rules to read documents, run checks, and stage proposed changes for review.
A planned setup option would let you describe the work once, as you would brief a new analyst. Lumonic's team still handles setup with you today.
How can a firm test overnight reporting pack review?
Test Lumonic against documents from a reporting cycle your firm has already approved. Compare the proposed numbers and flagged issues with your record, then inspect their source pages. LAGO Innovation Fund stopped sending reminder emails and keeping tracking spreadsheets, and cut portfolio review prep from weeks to days.
Check whether each proposed value matches your approved record, whether Lumonic flags the issues you identified, and whether you can trace each number to its source before publication.
Frequently asked questions
Is Lumonic's power user a person?
No. The power user is built into Lumonic. It reads reporting packs, proposes numbers under the firm's rules, and runs the configured checks overnight. People review exceptions and approve publication wherever the firm's policy requires it.
Does "ready for review" mean the numbers are published?
No. Ready for review means Lumonic has staged proposed values and the results of its checks. The firm decides whether a person approves each publish or Lumonic publishes when every required check passes.
What happens if a reporting pack has missing values or a failed check?
Lumonic flags the issue and stages the proposed numbers for review. Your firm's rules determine which checks must pass before publication and who approves an exception.
Is a switch from LTM to quarterly reporting a restatement?
No. LTM and quarterly figures cover different periods, so the reviewer must reconcile the periods before comparing them. A restatement revises a figure the company previously reported for a prior period.
Put your last reporting cycle through Lumonic
Lumonic reads portfolio company reporting packs overnight, tests covenants and budgets, and stages proposed changes for review. Every number traces to its source page. Schedule a demo to run documents from your last reporting cycle through Lumonic and compare the proposed numbers with your approved record.
Disclaimer
This article was written by Lumonic, a PitchBook company, and reflects Lumonic's views as of October 2026. Statements about third-party products and companies are based on publicly available information, including the vendors' own websites, press releases and documentation, and on the sources linked in the text. Lumonic has not independently tested third-party products, and their capabilities, pricing and positioning may have changed since this article was last updated. Statements about Lumonic's own product describe the platform at the time of writing, and customer outcomes are taken from the published customer stories linked in the text. Nothing here is a guarantee of results. Third-party names and trademarks belong to their respective owners and are used for identification only. If you represent a company named here and believe a statement is inaccurate, contact support@lumonic.com and Lumonic will review and correct it.
